What Is MEP Coordination?

Coordination follows a rough hierarchy set by physics rather than politics. Gravity-driven systems go first: sanitary drainage and storm piping need continuous slope, so their routing is the least negotiable thing in the ceiling. Large-section ductwork comes next, because it consumes the most volume and has limited ability to change shape without affecting airflow.

Sprinkler mains, which need specific coverage geometry, follow. Electrical conduit and cable tray come last, because conduit bends easily and a run can take a longer path with little consequence. Understanding this order is what makes a coordination meeting productive — arguing about who moves is only useful when the answer is not already determined by slope.

The project is divided into zones — usually by level and area — and worked through on a fixed cycle. Trades model or draw their systems, a coordinator federates the results and runs interference checks, and a coordination meeting resolves conflicts zone by zone. Trades revise, and the zone is signed off before anyone fabricates.

The pressure comes from where this sits in the schedule. Coordination happens after award, when trades are finally on board, and before fabrication, when long-lead ductwork and piping have to be released. That window is short, it is on the critical path, and every week coordination overruns is a week the fabrication shops are idle.

The most common failure is coordinating the wrong thing: the systems get modelled and deconflicted, but the space required to install and maintain them does not. A valve is technically clear of the duct and unreachable. A coil has no pull space. A filter cannot be changed without dismantling a hanger. All of this passes a clash test, and all of it is discovered by whoever has to service the building.

The second is treating coordination as a modelling exercise rather than a decision-making one. Producing a federated model with a clean clash report is not coordination if the trades never agreed to it — the layout has to be one the foremen who will install it actually accept, or it gets changed in the field and the coordinated drawings become fiction.

A coordinated model is not the contract. Clearances required by a specification section, separations required by code, access dimensions stated in Division 01 and equipment requirements listed in a schedule all live in documents that the coordination environment usually does not carry.

So a layout can be geometrically clean and still violate a written requirement nobody read during coordination. Checking the agreed arrangement back against the specifications and code requirements is the step most often skipped, and it is where the expensive surprises come from — particularly clearances around electrical equipment and separations around fire-rated assemblies.