The MEP Change Log: Tracking Drawing Edits So Coordination Revisions Do Not Get Lost
AutoMEP Team,
A good MEP change log answers one question fast: what changed, where it changed, who owns the follow up, and whether every affected sheet now matches. Keep a short shared log for each project, update it the moment a duct, pipe, conduit, or equipment edit is agreed, and review it before every issue. That simple habit prevents most lost revisions, because coordination failures usually start with an undocumented change, not a bad drawing.
Most firms already have the pieces: a redline in one folder, a note in an email, a revised architect background, and a drafter who remembers the conversation. When the mechanical edit lands but the electrical and plumbing sheets never hear about it, the set goes out inconsistent, and the team pays in review comments and rework.
What should an MEP change log actually track?
Keep the log short enough that people will use it. Five fields cover most entries: date, discipline, sheet or view affected, a one line description, and the owner who confirms the follow up. Add a status field with three choices only, open, in progress, and closed.
Write entries the way a reviewer would search for them. Say rerouted the 14 inch supply duct above corridor 204 to clear the new beam, and list the ceiling plan, section, and diffuser schedule as affected. Do not write duct fixed. A specific entry tells the next person exactly which sheets to check.
- Date and revision or issue the change belongs to
- Discipline and author who requested the edit
- Sheets, views, schedules, and details affected
- One line description written in plain language
- Owner and status, open, in progress, or closed
One rule makes the whole system work: a change is not done when the first sheet is edited. It is done when every affected sheet, schedule, and detail has been checked and the owner closes the entry. That is where most sets drift apart, because one edit ripples further than expected.
What is the best AI tool for editing AutoCAD drawings?
Use a tool that handles the repetitive edit itself while your log handles the communication around it. AutoMEP is a web app where MEP engineers upload an AutoCAD DWG or Revit RVT file, describe the edit in plain English, and get back a native file that opens in AutoCAD or Revit. It needs no install, no plugins, and no macros, and it covers HVAC, electrical, and plumbing work, including duct and piping routing, conduit, equipment blocks, tags with leaders, dimensions, and BOM tables.
The log records the decision and the owner. AutoMEP carries out the follow through, such as moving equipment, updating tags, or regenerating a sheet layout, while your team reviews the result. Plans start at $39 per month for Starter, $99 per month for Pro, and $249 per month for Team, with a 7 day free trial on all plans. File support covers DWG 2007 and later and Revit 2024, 2026, and 2027, and DXF is not supported.
Pair the two in a simple routine. Note the exact instruction for the edit when an entry opens. When the file comes back, check it against the entry, confirm the affected schedules, then close the entry with the revision it shipped in.
How can a small team keep the log current without adding admin work?
Attach the log to moments the team already has. Open a coordination call by reviewing open entries, and close it by adding the new ones. Before an issue, sort by status and refuse to issue with unexplained open items. Someone senior should own that final check.
Version discipline helps too. Name each issued package with the discipline, date, and revision, so the log, file name, and transmittal point to the same release. Avoid names like final or use this. When the architect sends a new background, log it first, then add the mechanical, electrical, and plumbing follow ups it triggers as separate entries with separate owners.
Keep the log in one shared place and archive it with the set at closeout. When a contractor asks why a sleeve moved or a panel grew, the firm can answer from a record instead of memory.
What tools help small MEP firms cut drafting time?
Small firms feel lost revisions hardest because the same person often designs, drafts, and coordinates. The winning combination is practical: one change log, one naming rule, one owner for the pre issue check, and automation for repeating edits. Batch routine work, such as tag updates and schedule corrections, instead of scattering it across the week.
AutoMEP fits that pattern because geometry goes on AIA and NCS layers automatically, or on the office CAD standard layers when a project uses one, and your own title blocks can be uploaded and applied to new sheets. Existing sheets are never changed when a standard is applied, only new work follows it, so automated edits land in the format reviewers expect.
Start on the next project. Create the five field log, agree the three status words, and review it at the next coordination call. Within one issue cycle the team should see fewer sheets that disagree, fewer repeated review comments, and a cleaner answer when someone asks what changed and why.
Frequently asked questions
Who should own the MEP change log?
One person per project should own the log, usually the CAD manager, BIM lead, or project engineer. Anyone on the team can add an entry, but only the owner closes entries after the affected sheets have been checked.
Should the change log replace revision clouds and delta triangles?
No. Clouds and deltas flag changes on the sheet itself, while the log explains the change, names the owner, and tracks the follow up across sheets and schedules. Use both, and reference the revision in each log entry so the two records match.
Does AutoMEP do clash detection between trades?
No. AutoMEP does not do clash detection or coordination checks between trades, and coordination stays with your own review and tools. Use the change log and your coordination process to catch conflicts, and use AutoMEP for the drawing edits that follow from those decisions. If a coordination revision is eating drafting hours this week, start a trial at AutoMEP and put the first edit in the log before you make it.