MEP field coordination: how mechanical, electrical, and plumbing crews stay aligned during rough-in

A four-inch sanitary line lands dead center in a corridor where a 12-inch duct trunk should run, even though the model cleared clash detection months ago. That gap between a clean model and a messy jobsite is what MEP coordination (mechanical, electrical, and plumbing crews staying aligned) has to close.

Most crews already run clash detection and still watch conflicts surface in the field, because routing decisions made on the floor reach other trades a week late, through a text thread or a Monday walk. Each one costs a reroute, a stalled crew, or both, and no BIM clash detection tool catches a decision nobody wrote down.

This article covers what a clash-free model can't do for you: a routing hierarchy, a meeting cadence, a lookahead that clears constraints before crews compete for space, and who resolves what when code, structure, or a rated assembly is on the line.

What this article covers:

• A clash-free model still leaves foremen responsible for installation sequence, field deviations, and communication between trades.
• A written routing hierarchy, set before the first hanger goes in, gives priority to the systems that are hardest to move.
• Weekly foreman meetings and a two- to three-week lookahead clear constraints before crews compete for the same space.
• Conflicts involving code minimums, structure, or rated assemblies go to the engineer through the RFI process instead of being decided by the foreman on site.
• The GC settles routing disputes on the written hierarchy and the critical path, never on who complained first or who's on their own payroll.
• Shared, current plans and task records keep every trade working from the same routing call.

Design coordination vs. field coordination: why a "clash-free" model isn't the end

Design coordination resolves conflicts in a federated trade model, usually run by the GC's VDC (virtual design and construction) team working from subcontractor shop models before installation starts. Field coordination starts when trades sequence installs around what's actually built, and the foremen own it; the handoff between the two is where rough-in goes wrong.

What BIM clash detection catches before construction

Clash detection finds trade-to-trade geometry conflicts, equipment service clearances, and accessibility problems in the model before material is ordered. When it works, it pays: resolving clashes before installation helps crews avoid field conflicts, limit mechanical rework, and save MEP labor.

Design models rarely include field deviations or tolerance zones, which is how fire dampers, panels, and valves end up with noncompliant clearances after an install that matched the drawing. Design issues can survive coordination and still need to be settled on the jobsite.

What still goes wrong once crews are on site

A coordinated set breaks in the field through sequence, drift, and silence between trades.

• Everything can fit in the plenum in the model but still depend on a specific installation order; if that order never reaches the contractor, the plenum can run out of room during assembly.
• Then the building itself drifts: structure gets shimmed and substituted equipment moves connection points.

Poor communication is a leading driver of rework industry-wide, and a chunk of that shows up right here: a drain location sitting in one foreman's text thread.

Fieldwire is a mobile-first, field-first jobsite management app built for the people doing the work, where crews manage plans, tasks, quality control, and documentation from any device. When a foreman marks where the drain actually landed on the sheet, your crew and your office open the same marked-up plan, and the markup carries forward when the next revision drops.

Setting the routing hierarchy before rough-in starts

A written routing order, agreed before the first hanger goes in, replaces "who got there first" with a rule every foreman can look up. There’s no national standard; the order comes from the spec or the GC’s coordination plan, so if both are silent, ask the GC to set one at kickoff and put it in writing.

Routing gravity drains, then ductwork, then conduit and piping

The harder a system is to move, the earlier it claims space. A common rough-in hierarchy, ranked by how little flexibility each system has: gravity plumbing, then large HVAC ducts, then fire sprinkler mains, then pressurized piping, then line-voltage electrical, then low-voltage and fiber last.

• Gravity goes first because pitch is code. Horizontal drains need a continuous slope that meets the applicable plumbing code, so when a drain meets a duct, the drain keeps its required pitch and the duct offsets.
• Large duct comes next because sections can't shrink without affecting airflow.
• Electrical and low-voltage conduit come last because they bend, and a run can take a longer path within the 360° limit the electrical code sets on bends between pull points.

Exact placement, especially for structure, major equipment, and fire sprinkler mains, still varies by project and trade sequencing, so check your spec before you assume where a given system falls.

Flagging congested areas in the preconstruction walk

Walk the jobsite with the GC and the other trades’ foremen two to four weeks before rough-in. You're checking the drawings against what's built, because conditions often don't match.

Ceiling plenums on many commercial floors are tight, with several systems competing for limited space between deck and grid, so spend the most time in mechanical rooms and congested corridors, and check risers that don't line up floor to floor as well.

Document every hot spot as you walk. Fieldwire works without a signal, so you can pin a task to the congested corridor on the plan with a photo of the shimmed beam before rough-in starts.

Keeping trades aligned during rough-in

The hierarchy settles who yields; the meeting cadence and lookahead settle when each crew gets the space. Neither works if a decision made in the trailer takes a week to reach the floor.

Running weekly (or twice-weekly) foreman coordination meetings

All three MEP foremen meet once a week at minimum, twice weekly on jobs that need it, for 30 minutes. Each foreman explains what they're working on and where, then identifies where they're running into other trades, and the group walks the space together before breaking.

Between meetings, a five- to eight-minute daily stand-up in the work area covers what got done, what didn't and why, and tomorrow's commitments.

Resolve routing conflicts the day they surface; a week's wait turns a drawing conflict into a conflict with installed work. Settle it face to face, then send a short email to document it.

In Fieldwire, the conflict gets logged as a task on the plan during the walk, assigned to the foreman responsible, with the photo attached.

Jarrell Mechanical ran into this on a $2.5 million mechanical renovation at a Missouri middle school, with up to eight foremen on site during the tightest stretch of a 10-week schedule. The HVAC and plumbing contractor rolled out Fieldwire months before mobilization so foremen could see what every other crew was doing on the plan in real time instead of working off paper and whoever they ran into that day. The project finished on time and on budget.

Sequencing: plumbing first, then HVAC, then electrical

Ask the GC to cut each floor into zones so plumbing works zone two while mechanical starts zone one. In a takt (fixed-pace) plan, trades chase each other up the tower on a diagonal instead of stacking in one area.

Planning two to three weeks ahead, not day to day

Use a lookahead window that extends beyond the immediate work, updated weekly, with every constraint logged against an owner and a removal date. Two to three weeks is typically enough to clear a constraint once you find it, though some teams run a longer window on more congested jobs.

Foremen flag material not on site and areas occupied by another trade. They also flag open requests for information (RFIs) that stall rough-in.

Fieldwire's Microsoft Project integration converts the master schedule into Fieldwire tasks, so the crew sees its lookahead window on the same phone that holds the plans.

Common field conflicts and who resolves them

Rough-in conflicts split into two groups: offsets and reroutes your foremen make inside the contract, and anything touching code minimums, structure, or rated assemblies. That second group goes to the engineer or the authority having jurisdiction (AHJ) in writing before anyone cuts. Typical mechanical notes call the drawings diagrammatic and leave offsets and fittings to the contractor; those offsets can usually be handled in the field.

Ductwork, drain pitch, and panel clearance clashes

A duct meets a drain: the drain keeps its pitch and the duct offsets, at no added cost to the owner under typical contract notes.

• Sloping a drain below code minimum isn't a field call. UPC-based text lets 4 in. and larger pipe fall to 1/8 in./ft when it's impractical because of sewer depth, structural features, or the building's layout, but only "when first approved by the Authority Having Jurisdiction."
• A duct that needs a new size waits too: alternative sizes need prior A/E approval and no greater pressure drop per linear foot.
• Panel clearance is a clash electricians can't afford to lose. Under section 110.26(E) of the electrical code (NEC), dedicated space above a panelboard or switchboard runs from the floor to six feet above the equipment or to the structural ceiling, whichever is lower, with no foreign piping, ducts, or equipment allowed in it. A dropped ceiling isn't a structural ceiling, so a duct above the grid still counts.

There's no field-level waiver for this. Stop work in that area, notify the architect/engineer (A/E) and the electrical inspector in writing, and relocate only per their written direction; check the NEC edition your jurisdiction adopted.

Under most specification sections, any work done before written instructions arrive is at your expense. Move fast on that paperwork, because one open mechanical RFI can strand two other trades.

Penetrations through structural members: always route to the engineer first

No foreman cuts a joist, beam, or rated wall on their own authority.

• Any modification affecting an open web steel joist's strength requires the structural engineer of record's approval under OSHA 1926.757.
• Many project supplementary conditions prohibit cutting structural members or changing air duct shapes, piping sizes, and related system design elements without the architect's written permission. AIA A201-2017's own cutting-and-patching clause (§3.14) requires the contractor's work to protect existing structure and other contractors' work, and separately requires written consent before cutting into the owner's existing construction; your contract governs the exact language, so check its cutting-and-alteration clause.
• In post-tensioned slabs, a severed strand can mean significant repair.
• Fire-rated assemblies follow the same path. Penetrations through rated walls need a tested firestop system. When a field condition doesn't match a listing, the fix is an engineering judgment from the manufacturer, a registered fire protection engineer, or an independent testing agency, approved by the building official. Firestop installation errors can compromise a fire-rated wall's protection.

An RFI documents the question, and a signed change order or construction change directive authorizes the fix.

In Fieldwire, the RFI pins to the beam on the plan with the photo attached, and the answer is logged against that RFI where the crew can find it (RFIs are a Business Plus and above feature).

The GC's role: neutral arbiter, not just scheduler

A common contract provision gives the GC the right and responsibility to coordinate all forces, which makes the GC the referee; a referee who favors one trade loses the other two.

Resolving routing disputes without playing favorites

The GC should decide on the written hierarchy and the critical path, and never on who complained first. Before directing a duct reroute, the GC should consult every trade it touches, since one reroute can land on electrical, plumbing, and sprinkler at once.

Self-performing GCs have a harder version of this, since one of the “subs” is their own crew; the written order and photo record let them rule against their own division when the hierarchy says so.

Processing change orders fast when a reroute adds cost

A reroute that adds labor or material beyond the contract scope is a change, and the paperwork has to move at field speed. The usual failure is a verbal field approval, with schedule pressure pushing the sub to proceed.

• Under AIA A201-2017 §7.4, a contractor who believes a minor change affects cost or time must notify and not proceed, and performing the work without notice waives the adjustment.
• Work done ahead of approval is cost the contractor incurs without a guarantee of payment.

In Fieldwire, tasks link directly to change orders (also a Business Plus and above feature), so the reroute, its photos, and the directive travel as one record, and the cost is documented before the crew eats it.

Keeping every crew on the same routing decisions

The model got you a coordinated set; your foremen, the written hierarchy, and a two- to three-week lookahead keep it coordinated through rough-in. Fieldwire keeps your crew and your office on one current set of plans, tasks, and photos, so the routing call made Tuesday is the one your crew works from Wednesday. It runs on more than 4,000,000 projects and has a free tier for up to five users.

Start free