How to Read a Construction Job Cost Report (Budget vs. Actual vs. Committed)

What a job cost report is actually for

A job cost report is a cost-code-by-cost-code statement of where the money on a job has gone and where it is going to end up. Every contractor's report looks a little different, but the good ones all answer the same question: given what we have spent and committed so far, where is this job going to finish versus what we budgeted?

The mistake most people make is treating it like a checkbook — they look at how much has been spent and feel fine because there is budget left. That tells you nothing. A code can be 40 percent spent and 90 percent done, or 40 percent spent and 10 percent done. The report only earns its keep when you read the forecast columns, not just the actuals.

The columns, in order, and what each one means

From left to right, a complete job cost report walks you from the bid to the projected outcome. Read them as a story:

• •Original budget — what you carried in the estimate for this cost code, before any changes.
• •Approved changes — the dollar value of change orders and approved budget transfers that move money into or out of this code.
• •Revised budget — original budget plus approved changes. This is the number you are now responsible for. Always measure performance against the revised budget, never the original.
• •Committed cost — the value of subcontracts and purchase orders you have issued but not yet been billed for. The money is spoken for even if no invoice has hit.
• •Actual cost to date — what has actually been incurred: labor run through payroll, invoices received, and equipment charges posted.
• •Cost to complete (ETC) — your estimate of the remaining cost to finish the work in this code. This is a judgment number, not a calculation, and it is where a good PM adds value.
• •Projected final cost (EAC) — actual cost to date plus cost to complete. The single most important number on the page: what you now believe the code will cost at completion.
• •Gain/fade variance — revised budget minus projected final cost. Positive is a gain (you expect to come in under), negative is a fade (you expect to overrun).

A worked example on one cost code

Take cost code 03-3000, Place and Finish Slab. Your original budget was 80,000 dollars of labor. A change order added a thickened edge worth 8,000 dollars, so your revised budget is 88,000 dollars.

You have run 60,000 dollars of actual labor through payroll. You have no open POs against the labor code, so committed cost is zero. The slab is roughly 60 percent placed. A lazy reader sees 60,000 spent against an 88,000 budget, concludes there is 28,000 left, and moves on.

Now do it properly. At 60 percent complete you have spent 60,000, so your run-rate says the full job is trending toward about 100,000 dollars (60,000 divided by 0.60). That is your projected final cost. Against the 88,000 revised budget, the gain/fade is negative 12,000 — a fade. The job is not fine. It is heading 12,000 dollars over on one code, and you found out at 60 percent instead of at closeout when it is too late to fix.

The fix might be tightening the crew size, addressing a rework problem, or filing a change for an unforeseen condition. The point is the report flagged it early. That early warning is the entire reason the document exists.

How to read it like a PM, not a bookkeeper

In Field PM the PM dashboard builds this view automatically from job costing — pulling committed cost from POs and subcontracts, actuals from time and invoices, and surfacing budget-vs-actual with a projected final so you are reading the forecast, not assembling it by hand each month.

• •Scan the gain/fade column first. Sort by largest fade and start there — that is your problem list for the week.
• •Distrust any code where cost to complete equals revised budget minus actual. That is a straight-line default, and it means nobody has actually forecast the code.
• •Watch committed cost on subcontracted codes. A code can show low actuals but be fully committed, meaning there is no room left even though the spend looks small.
• •Reconcile percent complete against percent spent. If a code is 50 percent spent and 25 percent done, the fade is already baked in whether the report shows it yet or not.
• •Look for codes with zero movement that should be active. A flat actual on work that started last week usually means costs are sitting uncoded, not that the work is free.

Common ways the report lies to you

The numbers are only as honest as the inputs. Two failures show up again and again. First, costs land in the wrong code — labor charged to a catch-all, or material booked to the closest code instead of the right one. That makes one code look like a gain and another like a fade, both of them fiction.

Second, committed cost gets ignored. If a subcontract is signed but the report only shows invoiced actuals, the code looks like it has budget left when the money is already gone. Always read actuals and committed together; the pair is what is truly consumed.