Cost Control: Budgets, Forecasts & the Monthly Cost Report

Welcome

Hello, and welcome. This is Super Structures General Contractors — a national general contractor headquartered in Powhatan, Virginia — here to help you and your clients build something that lasts. We're glad you're with us, and we look forward to connecting with you.

Alright, Cost Control: Budgets, Forecasts & the Monthly Cost Report. Don't let the plain title fool you. Here's the part that actually matters on the job: The PM's job is to know, every month, what the job will cost at the end — and to act on it while there's still time. Learn it well and the company's financial statements tell the truth.

Cost control isn't about not spending money; it's about knowing where the job stands and forecasting where it will finish while there is still time to change the answer. A cost report that is accurate in month four is a management tool. One that is accurate only in the last month is an autopsy.

The four numbers for every cost code

Every line in the budget — concrete, steel, drywall, general conditions — is a cost code, and each carries four numbers:

1. Budget — what the estimate allowed, plus or minus signed change orders, nothing else.
2. Committed cost — the subcontracts and purchase orders actually issued against the code. Once the drywall subcontract is signed for $455,000, that is committed whether or not a dollar has been billed.
3. Cost to date — invoices received, labor hours burdened and posted, equipment and materials charged. What accounting has recorded so far.
4. Estimated cost at completion (EAC) — what the PM believes the code will finally cost: cost to date plus the estimated cost to complete. It is a judgment, not a formula. The difference between budget and EAC is the projected gain or loss on that code. Add every code together and you have the job's projected final cost and margin — the number the company is relying on.

Building the forecast code by code

For a subcontracted code, the EAC is the committed subcontract value plus pending and anticipated sub change orders, less expected back-charges, plus any excluded scope the GC must cover. For a self-performed code, it is built from work remaining: quantities left, the crew's actual production rate, and the burdened labor rate. For general conditions, it is driven by time: supervision, trailer, and temporary utilities for however many months the job will actually take. The rule: forecast the work remaining, not the percent spent. A code 50 percent spent and 30 percent complete is not on budget.

The monthly cost review

Once a month, on a fixed date before the pay application goes out, the PM sits down with the superintendent and the accounting team and walks every cost code:

• Change orders — approved, pending with the owner, and anticipated but not yet priced, each with a revenue number and a cost number.
• Remaining commitments — subcontracts and POs still to be issued, with the current buyout expectation.
• Labor productivity on self-performed work — units installed versus hours spent.
• General conditions against the current schedule, not the baseline.
• Risks and exposure — disputed changes, sub performance, weather, long-lead items. The output is a projected final cost and margin, signed off by the PM. It feeds the company's work-in-progress (WIP) schedule, which drives revenue on the financial statements. When the PM's forecast is wrong, the company's books are wrong.

Profit fade and what it tells you

When the EAC rises over the life of the job, the margin fades. Some fade is normal — unforeseen conditions, a sub that underperforms. The pattern that matters is when it shows up. A job that adjusts its forecast by small amounts every month, up and down, is under control. A job that reports "on budget" for fourteen months and then fades 40 percent of its margin in the last two is the signature of a PM who was not forecasting honestly, or not looking. Leadership, the accountants, and the bank all learn to read that pattern. A large gain at the end is a lesson too: the forecast was sandbagged, and estimating never learned the bid was high.

Where money leaks on a job

The same leaks show up on job after job: scope gaps found after buyout; change orders performed in the field but never priced or billed; extra work the super "took care of" with no ticket; self-performed labor overruns nobody measured; general conditions running past the estimate's schedule; back-charges discussed but never deducted; and retainage uncollected after completion. A PM who knows the list looks for each one every month.

Going Deeper (Intermediate)

Separate budget transfers from forecast changes. A transfer moves money between codes — say, a roofing buyout gain to cover a concrete overrun — and hides the problem by making both codes look fine. A forecast change leaves the original budget visible and shows the overrun where it happened, so leadership can react and estimating can learn. Keep the original estimate column intact for the life of the job.

Change orders belong in the forecast the day they become probable — as pending revenue and pending cost — not the day they are signed. A job with $300,000 of unapproved change orders in the field is not "on budget"; it is a job with $300,000 of risk. Know how your company handles contingency, too, so you know how much cushion is real and never spend it twice.

Advanced / Pro-Level

Pros forecast labor by productivity, not by percent of budget spent. The superintendent tracks quantities installed each week — square feet of formwork, linear feet of wall, tons of steel — against hours charged, and that production rate applied to the quantity remaining is the true cost to complete. They forecast general conditions by time: they know the daily cost of keeping the site open, so every week of slip has a cost before anyone argues about it. They track exposure items — claims, disputed changes, potential sub defaults — on a separate, probability-weighted list, so the forecast reflects likely outcomes without pretending disputes are already won.

They also reconcile three documents every month: the cost report, the pay application, and the schedule update. If the pay app says 60 percent billed, the schedule says 50 percent complete, and the cost report says 70 percent of cost incurred, at least one is wrong, and the PM finds out which before the owner or the accountants do. They understand how the forecast flows into the company: percentage-of-completion revenue under the cost-to-cost method most contractors use, over- and under-billing on the WIP schedule, and how the bank reads it.

Practice Challenge

Your framing code has a $600,000 budget, a $590,000 subcontract, $350,000 billed to date, and the sub just told the super they'll need six extra weeks. What goes in this month's forecast? (Answer: the sub's six weeks likely means more general conditions and possibly acceleration or impacts to other trades — forecast those costs now, review whether the delay is the sub's responsibility and whether back-charges apply, and ask whether the framing scope itself is complete or if the sub is about to submit change orders; the $10,000 buyout gain is not the story.)

In Practice

A PM who reviews every cost code monthly finds a $40,000 problem in month three and fixes it. A PM who forecasts "on budget" until closeout hands the company a $400,000 surprise that nobody can fix, and the next job is run by someone else.

Common Mistakes to Avoid

• Forecasting by percent spent instead of by work remaining
• Hiding overruns with budget transfers so the original estimate disappears
• Leaving pending change orders out of the forecast until they are signed
• Treating general conditions as fixed when the schedule has already slipped
• Not reconciling the cost report, the pay app, and the schedule each month

Takeaway: The PM's job is to know, every month, what the job will cost at the end — and to act on it while there's still time.

Educational content — not legal, accounting, or contractual advice. Follow your contract's specific procedures and deadlines and consult your attorney and CPA as needed.