The $180,000 Conflict We Caught in Week Three
Three weeks into a major multifamily project, I walked into what should have been a routine coordination meeting.
Our mechanical lead had just uploaded the HVAC routing to the shared model. Our electrical contractor was already three days into conduit runs on the fourth floor. And our project engineer noticed something that made my stomach drop.
The main electrical chase and the primary HVAC trunk were trying to occupy the same 18 inches of ceiling space.
If we had discovered this during rough-in inspection? Six weeks of rework. Minimum. We were looking at demo, re-route, re-install, and re-inspect across four floors. I estimated $180,000 in direct costs, and that didn’t account for schedule impact or the cascade effect on finishes.
We caught it because of a framework we built after getting burned on two previous projects.
I’m going to walk you through the exact coordination protocol that saved us, how it works in practice, and why most projects skip the steps that matter most.
The Problem Most Projects Never See Coming
Here’s what I used to think: if you hire good subcontractors and hold regular meetings, coordination happens naturally.
That’s not how it works.
Subcontractors optimize for their own scope. Mechanical wants the most efficient duct runs. Electrical wants the straightest conduit paths. Plumbing wants gravity-fed drainage. Every trade designs in isolation, then shows up on site expecting their plan to work.
The conflicts don’t appear until someone starts drilling.
By then, you’re choosing between expensive rework or expensive redesign. You’re already behind schedule. The owner is asking questions. And everyone is pointing at everyone else’s drawings.
I’ve watched projects lose four weeks because a plumber roughed in waste lines that blocked the electrical panel location. I’ve seen mechanical systems installed six inches lower than structural allowed, discovered only when the ceiling grid contractor showed up.
The standard approach is reactive coordination. You wait for conflicts to surface, then you solve them.
We needed something different.
The Framework: Four Layers of Conflict Prevention
After two projects where coordination failures cost us serious time and money, I built a protocol that treats conflict detection as a production system, not a meeting topic.
It has four components. Each one serves a specific function. Remove any layer, and you’re back to reactive firefighting.
Layer One: Daily Morning Huddles (15 Minutes, No Exceptions)
Every morning at 7:00 AM, before any trade starts work, we run a 15-minute coordination huddle.
Not a safety talk. Not a schedule review. A coordination-specific check-in.
Three questions get asked, in order:
What are you installing today, and where?
What did you discover yesterday that wasn’t on the drawings?
Who needs access to the same space in the next 48 hours?
The mechanical lead says they’re running ductwork on the fourth floor, north wing, above the corridor. The electrical foreman says they’re pulling wire in the same corridor, same day. The plumber mentions they need to tie into the waste stack in that chase tomorrow.
Right there, in 90 seconds, we identify a potential conflict before anyone moves material.
We don’t solve it in the huddle. We flag it. The superintendent and I take it offline, pull the drawings, and make a call before lunch. The trades adjust their sequence. No one loses time.
This sounds simple. It is simple.
Most projects don’t do it because it requires discipline. You have to run it every single day. You can’t skip it when you’re busy. You can’t let it turn into a 45-minute discussion session.
Fifteen minutes. Three questions. Every morning.
Layer Two: Real-Time Documentation Protocol
Drawings lie.
Not because they’re wrong when they’re issued. Because conditions change, and drawings don’t update themselves.
We use a shared cloud model that every trade updates in real time as they install. Not at the end of the week. Not when they remember. The same day they install it.
When mechanical hangs a duct run, they photograph it, measure the ceiling height at three points, and upload the as-built location to the model before they leave that floor.
When electrical runs conduit, they log the route, the mounting height, and any deviations from the plan.
When plumbing rough-in is complete, they mark the exact locations of every penetration and every fixture tie-in.
This creates a living record of what actually exists in the building, not what the drawings say should exist.
That’s how we caught the HVAC-electrical conflict in week three.
Our project engineer was reviewing the updated model during his afternoon check. Mechanical had uploaded their duct routing that morning. Electrical had logged their conduit runs two days prior. The model showed the clash in red.
We called both trades into the trailer, pulled up the 3D view, and identified three alternative routes in 20 minutes. Mechanical adjusted their trunk line six inches to the west. Electrical stayed on their original path. Zero rework. Zero delay.
In the same project, we caught a plumbing waste line that would have blocked a structural beam penetration. Cost to fix in week four: $3,000 and one day. Cost to fix after drywall: $28,000 and two weeks.
We identified a fire sprinkler head location that conflicted with a light fixture. Adjustment during rough-in: 30 minutes. Discovery during final inspection: full ceiling grid removal and reinstall.
We found a door swing that would have hit a wall-mounted electrical panel. Change during framing: move the panel six inches. Change after finishes: relocate the panel, re-route conduit, patch and paint.
These aren’t dramatic failures. They’re the standard friction that every project experiences.
The difference is timing.
Catch them early, they’re minor adjustments. Catch them late, they’re expensive rework.
This framework compresses the discovery window from weeks to days, sometimes hours. That compression is where the value lives.
The Pattern I Keep Seeing
I’ve run this protocol on four projects now. Different building types. Different trade partners. Different schedules.
The pattern holds.
Projects that implement all four layers catch 60-70% of coordination conflicts before installation. Projects that skip layers catch maybe 30%, and usually only the obvious ones.
The morning huddle alone doesn’t do it. Real-time documentation alone doesn’t do it. Owner updates alone don’t do it.
You need the complete system, running continuously, embedded into how the project operates day to day.
That’s the mechanism.
Most contractors know coordination matters. They just treat it like a meeting topic instead of a production system. They react to conflicts instead of systematically hunting for them.
The projects that win are the ones that build conflict detection into their daily operating rhythm, not the ones that hold better coordination meetings.
That’s what saved us $180,000 in week three.
And that’s what keeps saving us on every project since.