COST TO COMPLETE IS
ALWAYS WRONG.
Cost to complete drives your WIP schedule. Your WIP drives your projected job margin. Your projected job margin drives your cash forecast. When cost to complete is wrong — and it almost always is — every decision downstream gets made on a number that doesn't exist.
FOUR WAYS COST TO COMPLETE
GETS CORRUPTED.
It is not that project managers are bad at estimating. Most of them are actually good at knowing what work is left. The problem is the inputs they are working from — and the process that is supposed to challenge them when the number looks too good.
WHAT BREAKS DOWNSTREAM
WHEN THE NUMBER IS WRONG.
Cost to complete is not just a job-level number. It is the input that drives four other financial outputs. When it is wrong, all four of them are wrong simultaneously.
The PM estimates cost to complete on a Friday. The CFO builds the monthly WIP from it. The controller closes the books with that WIP. The owner reviews it in the monthly meeting and decides whether to bid the next project. Every step in that chain ran on a bad input.
Catching this early is the job. A cost-to-complete review run within 10 days of the prior month-end close catches labor trending over before it becomes a full-margin problem. T&M work that needs to be billed before leverage is gone gets flagged here. Rework that needs a change order gets surfaced here. At closeout, none of those levers exist anymore.
THE EXAMPLE THE BOOK
USES.
Real job costing means your PM can answer this question without calling the bookkeeper: How much have we actually spent on labor on Phase One as of last month, fully burdened? The answer should come from a screen, not from memory or a spreadsheet being emailed around.
Scenario B is not a crisis if you catch it at 70% complete. There is still 30% of the phase left to manage. You can adjust crew mix, accelerate material delivery, or tighten productivity targets. Catch it at closeout and the only thing left to do is explain the loss.
THREE THINGS THAT MAKE
COST TO COMPLETE RELIABLE.
CLOSE FIRST, ESTIMATE SECOND
Cost-to-complete reviews run after the books are closed — not before. The controller closes by the 10th. The CFO runs cost-to-completes after that. The PM sees actual costs as of the close date, not a partially-posted mess. Every cost code shows what has actually been spent before the PM estimates what is left.
ESTIMATE IN COST DOLLARS, NOT SCHEDULE PERCENT
The PM answers: how many labor hours are left at what burden rate, what materials need to be purchased, what equipment is still needed? That produces a cost number. The percent complete falls out of the math — it does not drive it. When PMs estimate in cost first, the number is grounded in what is actually left to build.
CFO CHALLENGES THE NUMBER EVERY MONTH
The CFO reviews the cost-to-complete against the actuals and asks one question on every job: does this estimate make sense given what we have already spent? If the job is 75% spent on labor but the PM says 55% complete, something is wrong. The CFO surfaces it before it becomes a loss at closeout. This is the review process most subcontractors are missing entirely.
The Job Profitability System inside CFOS builds this review into the monthly cadence. Cost-to-completes run within 10 days of the close. Every active job reviewed. Trending issues flagged while there is still something to do about them.