A clash-free model is not a field-ready model. MEP coordination exists to move conflict discovery upstream, but automated clash detection is only one part of that process. A model can pass every automated check and still reach the field with inaccessible equipment, installation sequences that don't hold up, and maintenance clearances no one walked through in practice. From MEP coordination drawings and the difference between clash detection and build-readiness to what an MEP coordinator's salary reflects about the role on complex projects, this piece covers how BIM MEP coordination works and where Resolve's VR and web BIM reviews bridge the gap between a clear model and one the field can actually build.

TLDR:

• MEP coordination resolves mechanical, electrical, and plumbing conflicts in the model before crews build them in the field.
• MEP rework drives 5% to 15% of total construction costs; BIM-based coordination cuts field rework by up to 40%.
• Three clash types matter: hard clashes, soft clearance violations, and workflow sequencing conflicts. Clash detection software catches hard clashes reliably. The rest require a BIM review to surface.
• US MEP coordinators earn $93,837 to $161,012 annually; Revit and Navisworks proficiency accelerates career growth into VDC roles.
• Resolve fills the gap between clash-free and field-ready with VR and web BIM reviews, catching access problems, sequencing conflicts, and constructability issues that automated detection misses.

What MEP Coordination Means

MEP coordination is the process of aligning mechanical, electrical, and plumbing systems with each other and with the structural and architectural elements of a building before construction begins. The goal is to catch conflicts in the model, not in the field.

On complex builds, these systems share tight ceiling plenums, shaft spaces, and mechanical rooms where routing decisions made by one trade directly affect every other. Without coordination, those conflicts become RFIs, rework, and schedule delays.

BIM MEP coordination moves this resolution process upstream, where changes cost drawings, not labor. Clash detection is one layer of that process. A model that clears every automated check can still reach the field with inaccessible equipment, broken installation sequences, and maintenance access that works in 2D but not in practice. A BIM review is what bridges that gap, and it is what drives measurable BIM and VR review ROI.

Why MEP Systems Demand Coordination

MEP systems share space in ways that reward early planning and punish late discovery. Mechanical ducts, electrical conduit, plumbing runs, and fire suppression lines all compete for the same ceiling cavities, shafts, and interstitial spaces. When those systems conflict, the cost to resolve issues in the field runs far higher than catching them in design.

• Rework accounts for roughly 5% to 15% of total construction costs, with MEP conflicts among the most frequent drivers.
• Tight floor-to-floor heights in commercial and healthcare projects leave almost no room for unplanned routing changes.
• Trade crews work on fixed schedules, so a single MEP conflict can create cascading delays across multiple subcontractors.

Getting coordination right before work begins keeps schedules intact and avoids costly surprises once crews are on site.

Types of MEP Clashes

Three categories of clashes show up repeatedly across MEP coordination workflows.

Hard clashes occur when two systems physically occupy the same space. A duct running through a beam web is the clearest example.

Soft clashes involve clearance violations. A pipe routed too close to a structural member may pass code but leave no room for insulation, hangers, or maintenance access.

Workflow clashes are less visible but equally disruptive. These arise when sequencing conflicts prevent one trade from completing work before another must begin, creating field delays that no drawing review caught. Clash detection software does not flag these. They surface in a BIM review, when the team walks the model together and checks whether the installation sequence actually holds.

The MEP Coordination Process Step by Step

Model files get imported, typically from Revit or a similar authoring tool, and merged into a federated model. Trades submit their discipline-specific drawings: mechanical ducts, electrical conduit, plumbing lines, fire protection. From there, the coordination team runs clash detection, reviews conflicts in scheduled meetings, and works through resolution before anything gets built.

The steps look roughly like this:

• Each trade produces a coordination drawing showing their systems routed within the available space, accounting for structure and architectural elements.
• The federated model combines all disciplines so conflicts become visible across the full building section.
• Clash detection software flags hard clashes, soft clashes, and clearance violations for review.
• The coordination team meets to assign ownership of each clash and agree on resolution.
• Trades update their models, resubmit, and the cycle repeats until the model is clash-free. Once it clears, a BIM review is the next step before fabrication: clash detection confirms there are no collisions; a review confirms the model is actually ready to build.

On complex builds, this process runs in parallel with active design changes, which means the cycle rarely stops cleanly before the next one starts. Treating clash-free as the finish line is one of the most common ways coordination gaps reach the field.

MEP Coordination Drawings

MEP coordination drawings are the spatial record of how mechanical, electrical, and plumbing systems fit together in a building. They show routing paths, clearances, and installation sequences across trades in a single unified view.

These drawings are produced during the coordination phase before fabrication or installation begins. Teams use them to catch conflicts early, align on sequencing, and give field crews a clear picture of what gets built where.

What Goes Into a Coordination Drawing

A complete set covers several layers of information across all MEP disciplines:

• Ductwork routing with elevation and clearance data so mechanical systems don't compete for the same space as structural elements
• Pipe runs showing main lines, branches, and hangers with enough detail to support prefabrication
• Conduit and cable tray paths coordinated against other systems to preserve access and code-required clearances
• Section cuts at congested areas like corridors and mechanical rooms where conflicts are most likely

BIM-Based vs. 2D Drawing Sets

Most teams now produce coordination drawings directly from a federated BIM model. With that approach, the geometry is live, clash detection runs against actual 3D geometry, and any revision updates the drawing set automatically.

2D drawing sets are still common in smaller scopes or on projects with limited BIM adoption, but they require manual reconciliation across trade files, which increases the chance of coordination gaps reaching the field.

BIM-Based vs. 2D MEP Coordination

Two different workflows exist for MEP coordination, and they produce very different outcomes.

2D coordination relies on printed or static drawings. Teams overlay sheets manually, flag conflicts by eye, and mark up paper. It works for simple builds, but on dense mechanical floors or high-rise cores, the volume of overlapping systems makes manual review unreliable.

BIM-based coordination runs in 3D. Clash detection software finds conflicts automatically, and teams resolve issues in the model before anything gets fabricated.

The gap in outcomes is real. Studies show BIM coordination can cut field rework by up to 40%, but that outcome depends on more than running automated detection. A clash-free model still needs a review before it is field-ready, for equipment access, installation sequences, and constructability issues no software flags automatically. Immersive BIM VR software and web-based reviews close that gap by getting the right people into the model before fabrication locks in.

Who Is Responsible for MEP Coordination

MEP coordination is a team effort, but ownership sits with specific roles. The MEP coordinator, often a BIM or VDC engineer, runs clash detection, manages coordination drawings, and keeps trade contractors aligned. That role delivered results like Fortis Construction's $3M VR savings. On larger projects, each trade, mechanical, electrical, plumbing, may have its own coordination lead feeding into a central process.

The general contractor typically owns the schedule and sequence, while trade foremen bring field knowledge into the room. Design engineers of record stay involved to approve changes when clashes require design decisions beyond routing adjustments.

When those roles communicate clearly and early, issues get resolved before steel goes up.

MEP Coordinator Salary and Career Path

Per Glassdoor data, US MEP coordinators earn between $93,837 and $161,012 annually, with a median near $122,223. California, New York, and Texas carry premiums above that midpoint, reflecting project volume and market demand in those regions.

Career growth follows skill depth. Coordinators who build proficiency in Revit, Navisworks VR integration, and BIM issue management move faster into VDC management or MEP engineering roles, where compensation rises well beyond the coordinator range.

MEP Coordination Checklist and Best Practices

A few setup items determine whether coordination runs smoothly or stalls out before the first clash meeting.

• Confirm model LOD requirements with all trades before coordination begins
• Set a spatial priority hierarchy: structure first, then the largest mechanical systems, then smaller disciplines
• Assign one coordination lead per discipline, with clear decision authority
• Run clash detection at defined milestones, not ad hoc
• Schedule a BIM review after each clash detection cycle, a clash-free model still needs the team to walk access routes, verify sequencing, and confirm constructability before fabrication
• Document every resolution decision and name who made it
• Verify maintenance access clearances from day one, not after routing is locked
• Lock the coordinated model before any trade begins fabrication, a step made more reliable when model federation across disciplines combines and updates automatically

The practices that separate good coordination from great coordination are mostly about timing. Starting during design gives teams far more room to maneuver. Bringing superintendents in early surfaces constructability concerns while the model can still absorb them. One shared BIM issue tracking log across all trades, not separate trade logs, prevents the version control problems that undo weeks of work.

Immersive BIM Review in MEP Coordination: Where Resolve Fits

Resolve brings BIM into shared spatial environments so coordination teams can review MEP systems before construction begins. Where coordination drawings show clashes in 2D cross-sections, Resolve lets teams use real-time BIM collaboration to walk through the model together, spotting congestion, access problems, and sequencing conflicts that flat drawings miss.

This matters most on dense, fast-moving projects where the cost of a late-stage MEP change far exceeds the cost of an extra coordination session, as shown by Anglian Water's $4M VR savings. Resolve supports data center construction planning and other hyperscale builds where that tradeoff is constant.

The workflow fits directly into standard MEP coordination: teams load the federated model, flag issues spatially, and carry those decisions back into Revit or their coordination software of record. It is the same workflow that helped M3G achieve schedule certainty with Resolve coordination.

Final Thoughts on MEP Coordination

MEP coordination done well keeps crews moving and schedules intact. The process is only as strong as how early your team gets into it, how clearly ownership is assigned, and how quickly clash resolution decisions get documented and acted on. That part doesn't change regardless of project size. See Resolve in action for coordination teams.

FAQ

What is MEP coordination and why does it matter on complex builds?

MEP coordination is the process of aligning mechanical, electrical, and plumbing systems with each other and with structural and architectural elements before construction begins. On dense builds like data centers, hospitals, and pharma facilities, these systems compete for the same ceiling plenums and shaft spaces, so conflicts caught in the model cost drawings, not labor and schedule.

What's the best way to run MEP coordination on a fast-moving project where design is still changing?

Start coordination during design, not after it locks. Set a spatial priority hierarchy with structure first and largest mechanical systems next, assign one coordination lead per discipline with clear decision authority, and run clash detection at defined milestones, not on an ad hoc basis. A single shared issue log across all trades prevents the version control problems that undo weeks of resolved clashes.

How do Navisworks clash detection and immersive BIM review like Resolve fit together in MEP coordination?

Navisworks answers whether two systems physically collide. Resolve handles everything that falls outside that question: inaccessible equipment, poor installation sequencing, maintenance clearances a foreman would catch on a site walk. Teams load the federated model in Resolve, flag spatial issues together, and carry those decisions back into Revit or their coordination software of record.

How much does an MEP coordinator earn, and what skills accelerate the career path?

US MEP coordinators earn between $93,837 and $161,012 annually, with a median near $122,223 according to Glassdoor. California, New York, and Texas carry premiums above that midpoint. Coordinators who build depth in Revit, Navisworks, and BIM issue management move faster into VDC management or MEP engineering roles, where compensation rises well beyond the coordinator range.

Can BIM-based MEP coordination reduce field rework compared to 2D drawing sets?

Yes. Studies show BIM coordination can cut field rework by up to 40%, compared to 2D workflows that rely on manual sheet overlays and visual conflict checking. On projects with dense mechanical floors or tight floor-to-floor heights, that gap widens because the volume of overlapping systems makes manual review unreliable.