In my experience, MEP coordination failures typically originate in project files long before they show up on site.
Every commercial building is designed by separate mechanical, electrical, and plumbing engineering teams working from separate models, producing separate drawing sets, and writing separate specification sections.
When those designs converge in the physical structure, conflicts are inevitable. MEP coordination identifies and resolves those conflicts before they become field rework, change orders, and litigation.
How MEP Scopes Are Defined Across Drawings and Specifications
On the projects I've worked, MEP scope is established through two co-equal project file sets that carry contractual weight, drawings and specifications. Per AIA A201-2017 §1.2.1, neither supersedes the other without an explicit order-of-precedence clause. When they conflict, disputes follow.
The Drawing Side
Drawings define location, routing, and configuration. They are organized by discipline prefix:
M-sheets for mechanical HVAC
P-sheets for domestic water and sanitary
FP-sheets for fire protection
E-sheets for power and lighting
T/C-sheets for data and security
Each discipline's drawings are produced by separate engineering firms or departments. That structural independence creates coordination problems.
The Specification Side
Specifications define materials, performance criteria, installation requirements, and testing, organized by CSI MasterFormat divisions. Division 23 of the CSI MasterFormat covers HVAC scope, and standards from ASHRAE (the American Society of Heating, Refrigerating and Air-Conditioning Engineers) inform the performance criteria these specifications reference, such as ventilation rates, energy efficiency targets, and equipment testing protocols.
The Facility Services Subgroup spans Divisions 21 through 28, covering fire suppression through electronic safety. On many commercial projects, these divisions are often bid and managed as separate trade packages or subcontracts.
Most MEP systems physically cross division boundaries. The contractual question of who furnishes, installs, and tests each interface sits in parallel spec sections written by different engineers and bid by different subcontractors.
The controls wiring problem is the clearest example. Divisions 21, 22, and 23 often contain parallel "09 00" instrumentation and control sections. A GC establishing Building Automation System (BAS) scope must simultaneously read Section 23 09 00, Section 25 53 00, and Section 28 46 00. When these sections fail to explicitly cross-reference or exclude scope between them, the project gets either a scope gap, where no sub claims the work, or a scope overlap, where two subs price the same work and a dispute follows.
The BIM-Based MEP Coordination Workflow
If you've ever run coordination across federated models (separate discipline models linked into a single coordination view without altering the source files), you know BIM-based clash detection addresses the geometric dimension of MEP coordination. It finds physical conflicts between building elements when discipline models are combined into a shared coordination environment.
Roles and Model Federation
The workflow involves distinct, non-interchangeable roles. A peer-reviewed study on enhancing the MEP coordination process with BIM technology and management strategies documents how BIM-based coordination has become the standard approach for managing the complexity of MEP services across construction industries, and it details the roles and model development levels used to execute clash detection in practice.
BIM coordinators federate those models and run clash detection in tools like Navisworks Manage. MEP coordinators assign clashes to the right trade and escalate complex issues via RFI.
From Clash Detection to Field Execution
Clash detection identifies hard clashes, soft clashes, and workflow clashes. Each clash gets documented with an owner, due date, viewpoint, and re-test confirmation.
The critical gap is that the clash-detection component of this workflow is model-based. Field conditions, equipment manufacturing variations, and installation challenges can still arise once construction begins. The model catches geometry. Standard clash detection does not resolve specification-based scope assignment.
Where Trade Overlaps and Scope Gaps Surface During MEP Coordination
The conflict zones that generate RFIs, change orders, and litigation risk are predictable. Three areas recur across projects.
Ceiling Plenum Space
HVAC ducts, cable trays, plumbing mains, sprinkler headers, and structural members all compete for the same ceiling plenum volume. ENR reports on a life-sciences building where the architect and MEP engineer used BIM to fit systems into the ceiling plenum but failed to document that the tight fit depended on a specific installation sequence. At 70% completion, the contractor ran out of space. The contractor sued the owner, the owner sued the architect, and the MEP engineer was drawn into the claim.
Controls Wiring (Division 23 / Division 26)
Both the mechanical contractor and electrical contractor routinely assume the other is responsible for specific connection types.
If the phrase "unless otherwise noted" is used to delineate scope between Division 23 and Division 26, and the drawings are silent on a specific connection, then both trades risk reading their specification as excluding that work. Gray zone items include control transformers, interlock wiring, VFD communication wiring, and shutdown signals.
Datagrid's Scope Checker Agent directly targets the Division 23 / Division 26 controls wiring gray zone by cross-referencing parallel spec sections, contract documents, and project metadata to surface where "unless otherwise noted" language leaves connection types unassigned between trades.
The agent flags controls transformers, interlock wiring, VFD communication, and shutdown signal scope gaps and overlaps before buyout, so mechanical and electrical contractors aren't pricing the same work or excluding it entirely.
Fire Alarm and HVAC Shutdown Interfaces
Fire alarm systems (Division 28) must interface with HVAC systems to shut down air handlers and activate stairwell pressurization. The wiring, control logic, and testing responsibility fall into a three-way gap between the fire alarm contractor, mechanical contractor, and controls contractor. This one carries a hard consequence. Life-safety deficiencies can prevent certificate of occupancy.
On this interface, the same scope-reconciliation problem appears across project documentation, especially where life-safety work sits between divisions, change orders, and trade assumptions.
Where Manual MEP Scope Reconciliation Breaks Down
I've seen manual cross-discipline review fail for the same reasons over and over. It cannot keep pace with the project file volume, cross-reference density, or timeline pressure of modern built-world projects. These failure modes are structural in nature, rooted in how project documentation is organized rather than in any single reviewer's diligence.
File Volume Exceeds Human Processing Capacity
The AIA acknowledges that "each architectural design is essentially a unique one-of-a-kind, first-time prototype, and thus can never be 100 percent perfected in advance of construction." The manual model of a human reading one sheet and interpreting information onto another sheet breaks down when translating the work product of different teams across different phases at scale.
Cross-References Are Buried and Invisible
A Division 26 spec from Jefferson County Public Schools requires the electrical contractor to obtain the HVAC Equipment Schedule from Division 23 before beginning work. That cross-reference is buried in the spec, requiring the contractor to know it exists and actively retrieve a project file from a separate division.
The Cost of Getting It Wrong
Manual scope review failures translate directly into measurable cost on MEP projects.
The Navigant Construction Forum study of 1,362 projects found that the average construction RFI costs roughly $1,080 in review time and requires approximately 8 labor hours to process. Design error and omission is the category most directly tied to MEP coordination failures. On a typical project, this category can account for a meaningful share of total rework costs in direct expenses alone (excluding schedule delay and dispute costs).
These numbers compound on MEP-heavy projects where Division 23 / Division 26 ambiguities and buried cross-references generate repeated RFI cycles. A second failure point shows up during scope buyout, when reviewing subcontractor exclusions against adjacent specification sections is how project teams catch exclusions that create unassigned work between trades rather than a clean scope boundary.
How AI Agents Reconcile MEP Scope Across Divisions
The most consequential MEP coordination failures are textual and contractual rather than geometric. A duct penetration through a fire-rated assembly may be geometrically correct in a federated model while being contradicted by language in the fire protection specification. BIM clash detection has no mechanism for this category of conflict, but AI agents can execute Division-against-Division reconciliation across a full specification set as a project-file review workflow.
Datagrid's Scope Checker Agent operates on the full project file set directly by analyzing specifications, drawings, contracts, change orders, and project metadata. It cross-references parallel spec sections, flags scope gaps at trade boundaries, and surfaces buried cross-references that manual review misses at scale. The shift here is from ad hoc human scanning to systematic, repeatable scope reconciliation across MEP divisions.
What Datagrid's AI Agents Execute
Reconcile parallel CSI divisions to flag scope gaps and overlaps between mechanical, electrical, and adjacent trades
Compare drawings against specifications to surface conflicts in schedules, quantities, and equipment requirements
Validate exclusions and cross-references to catch unassigned work and buried trade dependencies before buyout
What Project Teams Are Seeing
Project teams using Datagrid for scope review and RFI workflows report faster review cycles and improved accuracy in catching scope items that manual review previously missed.
"Buro is deploying Datagrid to help our designers and engineers resolve RFIs. We are on our way to reduce CA work by 50%."
— Brad Klick, Estimator
That kind of improvement matters in preconstruction because scope conflicts that survive manual review often surface later as RFIs, commissioning delays, or change-order disputes.
Start Reconciling MEP Scope Across Your Full Project File Set
Every week your team spends manually scanning parallel spec sections for scope gaps is a week those gaps get closer to becoming field disputes. Datagrid's Scope Checker Agent cross-references your specifications, drawings, and contracts to flag trade overlaps and scope gaps before they reach the field. See how it works on your next project.
