Weekly Job Costing Reviews: The 30-Minute Habit That Saves Builders $50K/Year

Sound Familiar?

Signs your job costing review process is missing:

• You find out a job lost money when it closes — not before
• Your P&L by job shows a snapshot from weeks ago, not the current picture
• You don't know which active jobs are on track and which ones are running over
• Change orders aren't connected to the job budget, so the budget is stale
• You have a feeling about which jobs are in trouble but no data to back it up
• Your weekly team meeting covers scheduling but never financial status

What We Found

The Three Numbers That Matter in a Weekly Job Costing Review

The weekly review isn't about detailed cost analysis. It's about three headline numbers that tell you whether your active jobs are on track and what to do about the ones that aren't.

1. Committed Costs

Committed costs are what's been spent plus what's contracted but not yet invoiced. Pull this from JobTread's Cost Code Detail report for each active job. The key insight most builders miss: committed costs include open purchase orders, contracted sub work not yet billed, and change orders in progress — not just what's been invoiced. A job can look under budget on cash spent while being over budget on committed costs. That's the most dangerous misread in job costing. The committed cost number is your true financial exposure on the job right now.

2. Projected Cost at Completion

Projected cost at completion is where the job will finish based on current burn rate, known scope changes, and pending change orders. This isn't a gut feeling — it's a calculation. Take the current spend divided by the percentage complete, add pending committed costs, and add any approved scope changes not yet reflected in the budget. The number will be directionally accurate even if it's imprecise. The point is directional accuracy: is this job tracking to finish on budget or over?

Update this number weekly. When it's consistently off from actual, the estimating assumptions are wrong — and that information belongs in the estimating process, not just the job costing process.

3. Projected Profit

Projected profit is the contract value minus the projected cost at completion. This is the number that answers the question "will this job make money?" in real time, not in retrospect. On fixed-price contracts, a projected profit below target means either the scope needs to be tightened, change orders need to be sent for pending work, or the PM needs to look at production rates and material specs on remaining scopes. On cost-plus jobs, a projected profit below target usually means the budget is being managed against the wrong markup floor.

The 30-Minute Meeting Framework

The meeting works because it's structured, brief, and produces decisions. Here's how to run it:

Before the meeting (5 minutes, office team):

The office team pulls the three numbers for all active jobs before the meeting starts and distributes them — either as a printed sheet, a shared screen, or a document. Nobody should be generating numbers during the meeting. The meeting is for decisions, not data collection.

During the meeting (20 minutes, owner + PM + office team):

Go through each active job. For each job, review the three numbers and ask one question: does this job need an action before next week's meeting? An action is:

• A change order that needs to be written up and sent
• A conversation with a sub about billing discrepancies
• A schedule adjustment that affects production rate
• A client conversation about an approved change order that hasn't been billed yet
• A scope cut to protect remaining margin

Jobs on track get 30 seconds: "Job 14, projected profit at 22%, on budget, no action." Jobs off track get 2-3 minutes each. The meeting stays brief because the goal is decisions, not detailed analysis.

After the meeting (5 minutes):

Assign an owner and deadline for every action identified. Actions without owners and deadlines don't happen. A job costing review without follow-up is a status meeting, not a management tool.

Meeting cadence: Weekly. Every week. The value of a weekly review is consistency, not depth. A brief weekly review catches problems 3-4 weeks earlier than a detailed monthly review — and 3-4 weeks is enough time to send a change order, renegotiate a sub scope, or adjust a production rate. A monthly review often catches problems when there's nothing left to do.

What Gets Tracked — and What Doesn't — in a Weekly Review

The weekly review is a management tool, not a bookkeeping session. It should produce clear answers to three questions: which jobs are in trouble, what specific action will be taken, and who owns that action. It should not turn into a detailed cost code audit. That kind of analysis is for the monthly financial deep-dive, not the weekly stand-up.

The builders who stop doing the weekly review after a few weeks are usually doing it wrong — getting lost in detail instead of making decisions. The fix is to keep the scope of the weekly meeting tight. Three numbers, one question per job, actions assigned before the meeting ends.

Over time, the weekly review builds pattern knowledge. You'll notice that certain cost codes consistently run over on certain job types. That pattern belongs in your estimating assumptions — and the weekly review is how you build that dataset. But that's a quarterly output, not a weekly task. Keep the weekly review operational.

Frequently Asked Questions