MEP coordination is where most construction conflicts hide \u2014 and where the cost of catching them late is highest.<\/p>\n
Mechanical, electrical, and plumbing scope cross every floor plate and touch every other discipline. When those trades coordinate well, the project runs predictably. When they don’t, the failures land as change orders, RFIs, and rework \u2014 often traced back to a conflict that was sitting in the drawings the whole time.<\/p>\n
This guide walks through the MEP coordination process step by step: what each phase covers, where the seams break down, how to classify the conflicts you find, and where document-level review fits into the sequence \u2014 including before a BIM model ever exists.<\/p>\n
MEP coordination is the process of reconciling mechanical, electrical, and plumbing scope with each other \u2014 and with architecture and structure \u2014 so that the trades can build without running into each other. In practice, it means aligning duct routing, pipe runs, conduit layouts, cable trays, structural framing, ceiling heights, and fire-protection systems across a set of drawings that were produced by separate design teams on separate schedules.<\/p>\n
The failure mode is structural to how projects are designed. Each discipline produces its own set of drawings, solving its own scope. The MEP engineer routes ductwork with the floor-to-floor clearance in mind. The structural engineer sizes the beams and frames the shear walls. The architect carries the ceiling heights and the room programs. Nobody draws on the same sheet. The conflicts are in the seams \u2014 and the seams are where the documents don’t overlap.<\/p>\n
The costliest seams are:<\/p>\n
These aren’t exotic edge cases. On one real project, more than 40 change orders traced back to conflicts entre<\/em> 2D plan sheets \u2014 conflicts that existed in the documents long before ground broke. A single structural-MEP conflict \u2014 a shear wall colliding with HVAC duct routing \u2014 carried $28,000\u2013$45,000 in rework and 14\u201321 days of schedule. And errors discovered during construction cost roughly diez veces m\u00e1s para arreglar<\/strong> than the same errors caught at plan review.<\/p>\n Each MEP trade submits its design-intent scope: the mechanical engineer’s drawings, the electrical engineer’s drawings, the plumbing engineer’s drawings, and the fire-protection design (if separate). At this stage, the inputs are typically discipline-specific and haven’t been overlaid. A revisi\u00f3n de constructibilidad<\/a> at this point checks whether each discipline’s scope is buildable on its own terms \u2014 adequate clearances, code-compliant routing, sequencing logic \u2014 before the overlay begins.<\/p>\n What to catch here: incomplete scope (a discipline that hasn’t resolved its routing in a critical area), missing details, or spec documents that don’t yet align with the drawing set.<\/p>\n Before a 3D model exists \u2014 and sometimes instead of one \u2014 the coordination process starts with a disciplined overlay of the 2D drawing sets. This is where most coordination conflicts are actually identified on projects that don’t have fully federated BIM: reading the architectural, structural, and MEP sheets against each other, sheet by sheet and spec section by spec section.<\/p>\n This is the step that manual coordination most consistently shortchanges. Reading hundreds of sheets against each other, without missing the seam where two disciplines intersect, is exactly the kind of work that fatigue and deadline pressure defeat. Plan de revisi\u00f3n de construcci\u00f3n con IA<\/a> runs this overlay systematically \u2014 catching the cross-discipline conflicts, spec mismatches, and missing-coordination gaps that distributed human review misses. On projects without BIM coordination, this is the only comprehensive conflict check that happens before bid.<\/p>\n What to catch here: structural-MEP clashes, spec-vs-drawing mismatches, cross-sheet dimension conflicts, missing fire protection or electrical coverage, ceiling height conflicts.<\/p>\n Not every conflict has the same urgency or resolution path. A workable classification keeps the coordination log actionable:<\/p>\n Hard conflicts<\/strong> are physical impossibilities. Two objects cannot occupy the same space: the duct main cannot pass through the shear wall as drawn. Resolution requires a design change \u2014 rerouting, resizing, or revising the structural element \u2014 before the job can proceed. These are the $28,000\u2013$45,000 items.<\/p>\n Soft conflicts<\/strong> are clearance problems. Two elements can technically coexist but don’t meet minimum maintenance access, code clearance, or installation-sequence requirements. A pipe run that leaves inadequate maintenance access above a ceiling tile is buildable as drawn but will cause problems for the life of the building.<\/p>\n Coordination conflicts<\/strong> are sequencing or priority questions. Duct, conduit, and pipe all want to run in the same interstitial space. There’s room for all three if someone decides who runs high and who runs low \u2014 but that decision has to be made explicitly, not left to the field.<\/p>\n Document conflicts<\/strong> are disagreements within the written record \u2014 spec vs. drawing, sheet vs. sheet, note vs. detail. These don’t create a physical problem until someone in the field has to decide which document controls, and that decision has real cost (an RFI, a stoppage, a potential change order). See cu\u00e1nto cuesta una RFI<\/a> for what that decision-by-field looks like in dollars.<\/p>\n Identified conflicts go back to the responsible design disciplines for resolution. The process here is typically: conflict log \u2192 RFI to design team \u2192 revised drawing or spec clarification \u2192 updated set issued. For hard conflicts, this often requires a coordination meeting where structure, MEP, and architecture are all at the table. For document conflicts, a written clarification or spec addendum usually suffices.<\/p>\n The coordination log is the record of what was found, who owns it, and what the resolution is. Without it, resolved conflicts can reopen \u2014 a revised sheet that doesn’t carry the coordination note, a sub who works from an old drawing, a late-issued addendum that doesn’t reach the field.<\/p>\n Before the set goes issue-for-construction, the coordination log should be closed: every identified conflict has a resolution, a revised drawing or written clarification, and a responsible party. This is the pre-construction QA gate \u2014 and it’s where the pre-construction QA checklist<\/a> is most useful as a structured final check.<\/p>\n The sign-off step isn’t just administrative. It’s the moment when the team confirms that what’s on the drawings is actually buildable. Without it, coordination work done in Steps 2\u20134 can leak back into the field as unresolved conflicts because the updated scope was never reconciled across all discipline packages.<\/p>\n The classification above (hard\/soft\/coordination\/document) is a practitioner’s working taxonomy. The formal BIM taxonomy adds a fourth term: 4D clashes<\/strong>, which are sequencing conflicts \u2014 elements that don’t interfere in the finished building but do<\/em> interfere during construction (a structural pour that blocks MEP access for a required installation window, for example). 4D clash detection is a BIM-native capability and requires a scheduled 3D model to run.<\/p>\n For the 2D-PDF coordination process, the relevant distinction is simpler: design conflicts<\/em> (what the documents show can’t be built as drawn) vs. coordination conflicts<\/em> (what the documents show is technically buildable but hasn’t been sequenced or prioritized). Both categories show up in the document set. Design conflicts require redesign; coordination conflicts require explicit decisions.<\/p>\n The full MEP coordination process described above assumes that someone is doing Step 2 \u2014 the overlay \u2014 comprehensively. In practice, that step is often partial: one reviewer working through a critical path of known-risky areas, a coordination meeting that covers the major MEP rooms but not every floor plate, a visual pass that catches the obvious spatial clashes but misses the spec discrepancies and missing-coordination gaps.<\/p>\n Clash detection without BIM<\/a> is not only possible \u2014 for most projects at design review, it’s the only<\/em> form of coordination review that happens before bid. AI plan review runs the full overlay on the 2D PDF set you already have, at design review speed, before a 3D model exists or is needed. It catches the hard structural-MEP clashes, the spec-vs-drawing discrepancies, and the missing-coordination items that manual review at pace misses.<\/p>\n Where does BIM fit? If you have a coordination-ready federated model, run BIM clash detection for the hard spatial geometry \u2014 that’s what it’s built for. But BIM doesn’t read your specs. It doesn’t catch the cross-sheet dimension conflicts or the fire-alarm coverage omission. And it arrives late, after a model has been built and federated. The two tools catch different things at different moments in the same process.<\/p>\n Multifamily MEP coordination has a particular failure pattern: high repetition creates overconfidence. A 10-story residential tower runs the same floor plan 10 times, so the coordination logic on floors 3\u20139 feels like it follows from floors 1\u20132. But unit stacks shift. Mechanical rooms are on different floors than originally assumed. A change to the structural layout on level 4 doesn’t automatically propagate to the MEP drawing for level 4.<\/p>\n The MEP coordination failures in multifamily<\/a> post covers this in detail, but the short version is: repetition masks drift. The conflicts that surface on a multifamily project are frequently in the difference<\/em> between a typical floor and a non-typical floor \u2014 and they’re caught either by a systematic overlay or in the field as a change order.<\/p>\n Flikt’s drawing-quality benchmark \u2014 conflictos por cada 100 hojas<\/strong> \u2014 is particularly useful on multifamily because it reveals whether the conflict rate climbs on the non-typical floors and transition levels. That signal is invisible to a coordination process that samples rather than reads the full set. See the conflictos por cada 100 hojas<\/a> post for how the metric is constructed and what “good” looks like.<\/p>\n MEP coordination doesn’t fail because the design teams aren’t competent. It fails because the seams between disciplines are distributed across hundreds of sheets that no individual reviewer reads comprehensively against each other. The shear-wall-vs.-duct conflict sits in the drawings from the moment both drawings are issued. The question is whether someone finds it before the field does.<\/p>\n The step-by-step process above creates the structure for finding it: systematic trade input, disciplined overlay, classified conflict log, tracked resolution, and a signed-off issue-for-construction set. The gap, on most projects, is the overlay step \u2014 and that’s where document-level AI review closes it, without requiring a model, without requiring BIM staff, and at the moment in the schedule when catching a conflict is still cheap.<\/p>\n If you coordinate MEP on your projects, Flikt reads your 2D drawing sets for cross-discipline conflicts before construction \u2014 no BIM required. Ver la evidencia<\/a> o contact us<\/a> to walk through a real set.<\/em><\/p>\n Sube tu conjunto de planos y obt\u00e9n detecci\u00f3n de conflictos con IA, no se requiere BIM.<\/p>\n Comenzar<\/a> MEP coordination is where most construction conflicts hide \u2014 and where the cost of catching them late is highest. Mechanical, electrical, and plumbing scope cross every floor plate and touch every other discipline. When those trades coordinate well, the project runs predictably. When they don’t, the failures land as change orders, RFIs, and rework \u2014 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-517","post","type-post","status-publish","format-standard","hentry","category-blogging"],"yoast_head":"\nStep by step: the MEP coordination workflow<\/h2>\n
Step 1 \u2014 Trade input and constructability review<\/h3>\n
Step 2 \u2014 Document-level overlay and conflict identification<\/h3>\n
Step 3 \u2014 Conflict classification<\/h3>\n
Step 4 \u2014 Resolution and design coordination<\/h3>\n
Step 5 \u2014 Sign-off and issue-for-construction confirmation<\/h3>\n
Hard, soft, and 4D clashes: the full taxonomy<\/h2>\n
Where 2D AI review fits before and without BIM<\/h2>\n
Multifamily-specific pitfalls<\/h2>\n
El resultado final<\/h2>\n
\u00bfListo para detectar conflictos a tiempo?<\/h3>\n
\n\ud83d\udcc5 Reservar una demostraci\u00f3n<\/a>\n<\/div>","protected":false},"excerpt":{"rendered":"