Why Your Monthly Job Cost Review Is Actually a Post-Mortem

Construction business owners at $2-10M revenue run detailed monthly job cost reviews but can't tell you mid-job whether they're winning or bleeding. Here's what actually happens: the job starts drifting on Tuesday. By Wednesday you could still turn it. By month-end it's a post-mortem.

---

TL;DR — What You Need to Know:

• Monthly job cost reviews document outcomes, not manage decisions—the drift happens daily, but you see it 30 days later
• The information exists in real-time (your foreman knows, your PM knows), but there's no forcing function to surface it before it costs money
• Weekly meetings become "status theater" without actual data—vibes and verbal updates don't produce decisions
• You need a 15-minute repeatable structure: budgeted vs. spent vs. committed vs. labor through yesterday vs. billed, then one decision
• Without this forcing function, you'll keep finding out too late when you can't do anything except absorb the loss

---

Why do construction owners wait for month-end to know if a job is profitable?

Because that's when accounting closes the numbers. Your bookkeeper or controller runs job cost reports after month-end close—sometimes on the 5th or 10th of the following month. GAAP accrual accounting requires this timing for proper financial reporting, so you've built your management rhythm around an accounting compliance requirement, not an operational necessity.

The monthly review feels thorough. You sit down with job cost detail, compare budget to actual, calculate percent complete, review WIP schedules. It's disciplined. It's data-driven.

It's also 30-45 days after the decisions that mattered.

Here's the brutal truth: the owner who waits for month-end financials to know how a job is tracking isn't managing the work—he's documenting the outcome. You've had that moment where you walk a job on Thursday and realize the crew's been half-stalled since Monday because materials didn't show or the previous trade didn't finish or the homeowner changed their mind. And you think, "Why am I just hearing about this now?"

The information existed. The foreman knew Monday afternoon. The PM probably knew Tuesday morning. But there was no routine moment where it surfaced before it became expensive.

What does waiting for month-end actually cost your business?

Let's be specific about what happens in those 30 days of operational blindness.

Week One: Job starts drifting. Maybe you're running 15% over on labor hours because the scope wasn't clear or the crew has a new guy who's slow. Your foreman sees it. Nothing gets flagged.

Week Two: Material costs are tracking 8% high because the supplier raised prices or the quantity takeoff was optimistic. Your PM suspects it when approving invoices. Still no formal flag.

Week Three: You're now $12K over budget on an $80K job, but it feels on track because the work is getting done. No client complaints. Crew is busy. You bill the next progress payment based on percent complete.

Week Four: Month closes. Accounting runs reports. You finally see the variance. The job is 15% over budget with 60% of scope complete. Basic projection math says you're heading toward a 20% loss.

Now you have a conversation. Now you make adjustments. But you're managing damage, not preventing it.

The Construction Financial Management Association (CFMA) benchmarks average net profit margins in construction at 1.4% to 3.5% depending on sector. A single job that swings 15-20% over budget doesn't just lose money—it wipes out profit from three other jobs. And you're finding out when there's nothing left to do except absorb it.

Why do weekly meetings fail to solve this problem?

Most owners recognize the month-end gap and add a weekly project meeting. Smart move. Except the meeting becomes what I call status theater.

Everyone reports things are "on track" or "under control." The PM says the electrician is finishing up this week. The foreman says they'll hit the schedule. You nod along because you don't have the numbers in front of you to call bullshit.

The meeting exists, but it doesn't produce decisions. Why?

Because decisions require actual data, and most weekly meetings run on vibes and verbal updates.

You're asking "How's the Johnson job?" instead of "We budgeted $18K for framing labor through this phase. We've spent $16.2K and committed another $4K to finish. That puts us $2.2K over. What happened and what are we changing?"

See the difference? The first question gets a story. The second question forces a decision.

Without structured data in the room, people report what feels true or what makes them look competent. No malice. No incompetence. Just human nature in the absence of a forcing function.

What does a forcing function actually look like for job cost control?

Here's what's missing: a simple, repeatable 15-minute structure that surfaces decision-critical data before it becomes a loss.

You don't need a complex dashboard. You don't need real-time ERP integrations. You need six numbers per job, reviewed weekly, with a decision attached.

The 15-Minute Weekly Job Review Structure:

1. Budgeted cost to complete this phase (from your estimate/bid)
2. Actual cost spent through yesterday (from AP and payroll, doesn't need to be closed)
3. Committed costs not yet paid (POs issued, subcontractor SOVs, materials ordered)
4. Labor hours through yesterday vs. budgeted hours (from timecards, even if rough)
5. Amount billed to date (from progress billing or contract schedule)
6. The decision required this week (not next month, this week)

This isn't month-end accounting. This is operational math. Your PM or foreman can pull these numbers in 10 minutes if you make it a routine expectation.

Let me be blunt: if you can't answer these six questions about an active job within 15 minutes, you're not managing it.

You don't need precision. You need direction. If budgeted labor was $12K and you've spent $9K with 60% of scope done, you're probably fine. If you've spent $11K at 50% done, you have a decision to make now—not at month-end.

What kills this discipline before it takes hold?

You'll resist this. Let me tell you why, because the resistance is predictable.

Resistance #1: "My people don't have time for another meeting." This isn't another meeting. This replaces the useless status update meeting you're already having. And 15 minutes of data beats an hour of vibes.

Resistance #2: "The numbers aren't clean enough mid-month." You're not filing a 10-K. You're making an operating decision. Rough numbers today beat perfect numbers in 30 days when the money's already gone.

Resistance #3: "I don't want to micromanage my PMs." Accountability isn't micromanagement. If your PM can't tell you budgeted vs. actual vs. committed without a month-end close, they're not managing the job either—they're hoping it works out.

Resistance #4: "We tried weekly reviews and they didn't stick." Because you didn't attach a consequence. The forcing function isn't the meeting. It's the expectation that every job review ends with a decision and a name. "By Friday, [Name] will re-bid the electrical scope with two other subs," or "We're pulling [Name] off this crew and adding [Name] because labor hours are tracking 20% over."

No decision, no point to the meeting.

How do you implement this without blowing up your workflow?

Start with one job. Not all of them. Pick the active job with the most risk or the tightest margin.

Week One: Pull the six numbers. Budget, actual spend, committed, labor hours, billed, decision needed. Do it yourself. Time how long it takes. It won't be 15 minutes the first time—it might be 45. That's fine. You're learning where the data lives.

Week Two: Have your PM pull the numbers. Sit with them. Show them the structure. Make the decision together.

Week Three: PM pulls numbers, brings them to a standing 15-minute check-in (same day, same time every week). You review, you decide, you move on.

Week Four: Add a second job to the rotation.

Within two months you've built the forcing function. It's not a new system. It's a rhythm. And rhythm creates accountability without drama.

You'll catch drift on Tuesday instead of discovering it in April. You'll have the conversation when you can still turn the job. And your monthly job cost review becomes what it should be—a confirmation of what you already managed, not a surprise autopsy.

Bring This to Your Leadership Meeting

The Question: "Name one job in the last six months where we knew it was bleeding before month-end closed. If you can't name one, why not?"

The Prompt: "Pick our riskiest active job right now. Walk me through budgeted cost, actual spend, committed costs, labor hours, and what we've billed—right now, without waiting for accounting to close the month. If we can't do that in this room in fifteen minutes, we're not managing the job."

The Action: By next [Day of Week], [PM Name] will pull the six numbers (budget, actual, committed, labor, billed, decision needed) for [Specific Job] and bring them to a 15-minute standing check-in. We'll repeat every week for 90 days, then expand to all active jobs over $50K.

---

You already know the information exists. You've always known. The foreman knows when labor's running heavy. The PM knows when materials are over. The question isn't whether you have access to the data. The question is whether you've built a forcing function that surfaces it before it's too late.

Monthly reviews are compliance. Weekly reviews with data are management.

You don't need ten steps. You need six numbers, fifteen minutes, and a decision. Every week. Same time. No theater, no vibes, just budgeted vs. actual vs. committed and what we're doing about it.

That's how you stop running post-mortems and start managing jobs.