Why You Avoid the Margin Drift Meeting (And What It's Costing You)

Construction business owners at $2-10M revenue already know which job is bleeding margin. You knew two weeks ago when your PM mentioned the pending change order, when your lead mentioned rework hours, when someone asked about owner-supplied materials that now seem like your problem. The issue isn't lack of information—it's that looking at the data while there's still time to act means you have to make a decision that costs something.

---

TL;DR — What You Need to Know:

• You already have the data showing margin drift—it's in daily reports, time cards, and material receipts no one reviews mid-job
• Post-mortems feel safe because the damage is done; mid-job margin reviews force real-time decisions with no good options
• By the time you "wait for month-end," the job is 60% complete and drift has become locked-in loss
• The margin didn't disappear in the final week—it bled out in every moment you chose not to look because looking required deciding
• A weekly 15-minute margin drift meeting catches problems when you can still renegotiate, reallocate, or cut losses

---

Why does the margin drift meeting not exist in most construction companies?

The meeting doesn't exist because owners are terrified of what it will reveal while there's still time to do something about it.

A post-mortem is emotionally safe. The job is closed. You can review the overruns, shake your head, lecture the team about better tracking, and promise to "do better next time." There's disappointment, but no decision required. The damage is already done.

But a mid-job margin review—one conducted when the job is 30% or 40% complete—forces you to make a decision while the clock is running. Do you stop work and fight for the change order? Do you eat the hours to protect the client relationship? Do you pull your best crew off this job and push the schedule, knowing the client is expecting you tomorrow morning?

Every option costs something. None of them feel good. So you don't schedule the meeting.

What data are you actually avoiding?

You're not missing data. You're avoiding it.

The drift is already visible in:

• Daily reports that show crew hours exceeding the estimate by 15-20% week over week
• Time cards coded to the wrong cost code because your lead didn't want to show overruns on his phase
• Materials sitting in the yard that should have been returned three weeks ago, quietly adding carry costs
• Pending change orders that your PM mentioned in passing but haven't been formalized or approved
• Rework hours that "shouldn't have happened" but consumed six labor hours last Tuesday

According to the Construction Financial Management Association (CFMA), most contractors don't review Work-in-Progress (WIP) reports until month-end. By then, job completion often exceeds 50-60%, and the levers you could have pulled—renegotiating scope, reallocating labor, or stopping work—are no longer available without blowing up the schedule or the relationship.

The data exists. You're not looking at it on a cycle that allows intervention.

Why do you wait until month-end to review job costs?

You tell yourself you'll get the "full picture" at month-end. You'll see everything clearly then. You'll have time to analyze it properly.

But here's the operator reality: By month-end, the job is 60% done and the drift isn't drift anymore—it's locked-in loss.

The margin didn't disappear in the last week of the job. It bled out in all those small moments over three weeks when you chose not to look. Because looking would have required deciding. And deciding would have required you to be the guy who:

• Stops the work and demands client approval before proceeding
• Has the hard conversation with your PM about why the estimate was wrong
• Admits you bid it wrong while there's still something you can do about it
• Pulls your A-team off the job, knowing it will disappoint the client

None of those moves feel good in the moment. But waiting doesn't make them easier—it just makes them irrelevant. By the time month-end arrives, your only option is damage control.

What does margin drift actually cost your business?

Let's get specific.

A $300,000 job bid at 15% gross profit margin should generate $45,000 in gross profit. If labor overruns by 20% (a common drift rate when no one's watching), and labor represents 40% of job cost, you've just burned an additional $24,000. Your gross profit dropped from $45,000 to $21,000—a 53% margin erosion.

That's one job. Here's the compounding effect across your business:

• You now need to find another $24,000 job just to break even on this one
• Your cash flow tightens because you're funding unplanned labor costs
• Your estimating feedback loop breaks because no one learns what went wrong until it's too late to matter
• Your team learns that overruns are normal because no one stops them in real time

The CFMA's benchmarking data shows that contractors who conduct weekly WIP reviews identify cost overruns an average of 3-4 weeks earlier than those who wait for month-end financials. Three weeks on a 12-week job is 25% of the project timeline—the difference between renegotiating scope and eating the loss.

How do you run a margin drift meeting without creating chaos?

You don't need a two-hour financial review with your entire team. You need a 15-minute weekly margin drift meeting with three people: you, your PM, and whoever manages job costing data.

Here's the structure:

1. Review jobs in progress (5 minutes) Pull up your WIP report or job cost summary. Ask one question for each active job: "Are we on track, drifting, or in trouble?"

Don't analyze. Don't problem-solve yet. Just triage.

2. Deep dive on one drifting job (7 minutes) Pick the job that's drifting and ask:

• What's burning hours? (specific phase, specific task)
• What's the exposure? (how much more drift if we do nothing?)
• What's the decision? (change order, eat it, stop work, reallocate crew?)

This is where the discomfort lives. You're naming the problem while you can still do something about it.

3. Assign ownership and deadline (3 minutes) Someone leaves that meeting with a specific action and a deadline. Not "let's keep an eye on it." A decision:

• "[PM Name] will submit the change order by Friday or we pull the crew."
• "[Foreman Name] will re-code last week's time cards to the correct phase by Wednesday."
• "We eat the rework hours and I have a conversation with the client about why we're pausing work until the owner-supplied materials arrive."

The meeting ends when someone owns the next move.

What will derail this meeting?

Let's be honest about the human friction:

Your PM will resist. He doesn't want to admit the job is drifting while it's his responsibility. He'll say "I've got it under control" or "I'm waiting on the client to approve the change order." He'll tell you he's tracking it in his head or he'll have numbers by Friday. Push anyway. If he's got it under control, he can show you the data that proves it.

You'll want to skip the meeting when things are busy. You won't. The meeting is 15 minutes. If you can't find 15 minutes, you're not running the business—it's running you.

You'll be tempted to problem-solve every job. Don't. Triage fast. Deep dive on one drifting job. Move on. The goal isn't perfection; it's early detection.

Bring This to Your Leadership Meeting

The Question (forces alignment):
"Which job are we all pretending isn't drifting right now?"

The Prompt (forces clarity):
"Pull up the WIP report. For every active job, answer this: Are we on track, drifting, or in trouble? No analysis. Just name it."

The Action (forces ownership):
"Starting this week, [PM Name] will run a 15-minute margin drift meeting every Wednesday at 8:00 AM. First meeting is in three days. Bring the WIP report and be ready to name the job that's bleeding."

---

You already know which job is drifting. The question is whether you're willing to look at it while there's still time to do something about it. Cash is the truth teller, but only if you look at it on a cycle that allows you to act. Fifteen minutes a week. One drifting job. One decision. That's the meeting that saves the margin.