The $15K to $50K a Week You Are Paying for a Meeting That Should Have Been a Diff

The Meeting Is Not the Cost. The Waiting Is.

Your coordination meeting has a price tag. It reads $15K to $50K a week in field labour standing idle. That is not the meeting room. That is the crews on site who showed up ready and got told to hold until the clash list gets sorted.

When I ran jobs, Monday morning coordination was ninety minutes of us walking through a batch of conflicts that had not been touched since the last export. Much of that time was usually spent hunting one duct. Somebody moved the riser, somebody else moved the beam, and the version in the room was neither of them. We paid for that in standing labour, not in meeting minutes.

The brutal part is that the answer existed. Something in the model had already changed. Nobody had a clean record of what changed, when, and what it did to the other trades. So the room re-litigated geometry instead of deciding work.

Run the math on a mid-size job. If a hundred field hours get burned in a week waiting on coordination answers, and loaded labour runs $75 to $150 an hour depending on trade and region, you are looking at $7,500 to $15,000 in a quiet week. Stack a couple of active areas and a deadline at the same time and you clear the top of that range without trying.

The fix is not a shorter meeting. The fix is arriving with a diff: here is what moved in the model since last week, here is what it touched, here is what it costs, here is who owns it. That is a fifteen-minute conversation. The ninety-minute one is what you get when nobody has it.

What Two Hours Hunting a Duct Looks Like

Picture the scene every MEP contractor knows. The mechanical foreman flags a duct that will not fit above a corridor ceiling. The structural model says the beam is deeper than the last coordination set showed. The architect moved a soffit two weeks ago to make room for a light cove. Three people in the room have three different versions open, and the version on the projector is four days old.

So the meeting turns into archaeology. Someone goes back through email to find the last IFC set. Someone else calls the detailer to see if the change ever made it into the working model. The plumber waits to know if he can hang. The electrician waits to know if the rack moves. The drywall crew is on site and cannot start until the ceiling grid is set. Two hours later you have a decision, and a full day of field labour has gone by.

That is the specific, repeating moment this whole article is about. Not a big dramatic failure. Just a duct nobody could find a straight answer on, eating a morning and a paycheck.

When you run BIM coordination services for MEP contractors, the whole value you sell is being the team that knows what is current. If your own coordination meetings cannot establish that in the first ten minutes, your client is paying you to be confused on their behalf.

There is a version of that morning where the diff lands in everyone's inbox before the meeting starts. Duct at grid C4, elevation dropped 6 inches. Beam depth changed last Tuesday. Soffit added by architect on Thursday. Cost impact calculated at whatever your labour and material rates are. The meeting becomes an assignment sheet instead of a deposition.

A Standing Meeting Is a Slow Release Valve

Most firms coordinate on a weekly rhythm because that is what they have always done. Friday export, Monday meeting, Wednesday answers, repeat. In a design that is moving every day, that cycle is a five-day lag on every single change. Multiply that by every trade every week and you have a steady bleed.

Weekly meetings are not evil. Weekly meetings where the content is five days stale are the problem. If coordination ran as a diff every morning, the Monday meeting would still exist. It would just be where you solve the hard strategic clashes, not where you reconstruct what happened last Tuesday.

The cost of that lag is not abstract. It is time on the clock in the field. A crew that showed up and cannot proceed is a crew that is being paid to wait.

The Number That Makes This Real

Here is how I want you to think about the cost of a stale coordination meeting. Write down, for one week, every hour a crew stood idle waiting on an answer that lived inside the model. Include the half hours. Include the times a foreman had to walk back to the trailer to check something. Include the rework when a duct got installed at the wrong elevation because a superseded drawing was in the truck.

On many jobs that lands between $15K and $50K a week once the labour is loaded properly. The low end is a coordinated team with a light schedule. The high end is a job in active construction where three trades are chasing each other through the same corridor.

And it compounds. Idle time misses a milestone, the milestone slips a week, the week pushes back the drywall, the drywall push changes the ceiling grid, and the ceiling grid changes the light layout. Every one of those downstream moves is a new coordination problem, which creates another slow meeting, which creates more idle time.

What makes this hard to see is that none of it appears as a line item called idle labour. It appears as a labour rate that looks a little high. It appears as a schedule that keeps sliding two weeks at a time for reasons nobody can quite name. It appears as a general contractor who likes your work but thinks you are slow.

That is the cost of not having a diff. Not one big hit. A persistent drip that hides inside your labour factor and slowly eats your margin.

Why an AI Pass Beats Holding the Meeting First

The old workflow was: meet, discuss, decide, update, export, meet again. The modern workflow flips it. Update, export, classify, cost, then meet for fifteen minutes to confirm ownership. You are not replacing human judgment. You are giving the humans something to judge.

This is where the AI versus human estimator argument stops being real for me. The AI is not pricing the job. It is doing the reading. Two AI models look at the geometry and the metadata, classify the BOQ line items, and pull current pricing, and the classification comes out around 86% accurate. That is good enough that your estimator starts from a populated list instead of a blank spreadsheet. Their job becomes checking the line items that matter rather than typing every one of them.

If you have been tracking construction estimating accuracy benchmarks, you know that manual takeoffs typically land in a range where a few percent of error is considered normal. A few percent on a $40M project is seven figures of exposure. An 86% classification rate routed into a human review process is a very different reality. You are not asking the machine to be perfect. You are asking it to take most of the boring work and leave the risky remainder for a person.

That is what makes the fifteen-minute meeting possible. Your estimator already knows the duct moved, the system already knows what it costs, and the room just decides who does what. The team that used to spend two hours hunting the duct spends ten minutes assigning the fix.

And the model keeps updating, so the next meeting starts from current data instead of last Friday's snapshot. The meeting stops being a recap and becomes a decision.

What This Does to Your Bid Win Rate

There is a second-order benefit here that is bigger than the labour savings. When your estimate is live and current, you can answer the question the client is asking during design development, which is: what does this cost and how confident are you?

Most firms lose bids because they are slow, not because they are expensive. The GC needs a number by Friday, your estimator is still chasing a model update, the number goes out Monday, and somebody else already had the conversation. If you are working on how to improve your bid win rate, speed is the lever, and speed only comes from having the record in one place.

When you can price the architect's two-inch move while they are still on the call, you stop being a bidder and start being a partner. That is the value engineering with BIM models conversation, just at the right moment. The client asks what happens if the ceiling goes up six inches. You say here is the delta. Here is what it saves in duct, here is what it adds in sprinkler, here is the new number. You closed a $12,000 decision in a two-minute conversation because you had the data.

That is how bids get won. Not on price. On being the one in the room who knows the answer before the question finishes.

One team we work with reports a 35% higher win rate since its estimates stopped being a weekend project. They were not cheaper. They were faster and their numbers were defensible. That is the whole pitch, and it fits in a sentence an estimator would say on a site walk.

How to Turn the Meeting Into a Diff

The practical version of this is not complicated. You pick one live record of the project and you export it on a schedule. Every morning, not every Friday. That export gives you labour, equipment, material, and time costs in minutes, and the number updates when the design changes instead of when somebody remembers to update it.

Then the meeting agenda becomes a diff. What moved. What it cost. Who owns it. The foreman opens the list, sees the duct at C4 changed, checks the cost, and tells the room when he can install it. The estimator opens the same list and confirms the totals. There is no catching up because there was no gap to catch up across.

Plans run from $260 per licence per year on the low end to $590 on the high end, with Enterprise pricing for the larger setups. If you are paying $15K a week in idle labour, that math is not close. One avoided meeting on one job pays for a full team several times over.

You also gain the option to sell this as a service. If you already do done-for-you BIM work like execution plans, 4D and 5D, and fabrication detailing, adding live estimating to the offering is the natural next step. Clients pay for speed and certainty. Being the firm that shows up with a current number instead of a promise is a billable difference.

The point is not to abolish the coordination meeting. The point is to stop paying $15K to $50K a week for one that should have been a diff. Run the diff, hold the meeting, and watch what it does to your labour factor, your schedule, and your win rate.