WIP schedules: the one report that tells you whether the year is real

Overbilling is not profit, underbilling is not virtue

Both conditions are normal and both are dangerous when they are not understood.

Overbilling — billing ahead of the work — is standard practice and is how most contractors fund their operations. Front-loading the schedule of values, billing stored materials, collecting a deposit: all of it produces cash before the cost is incurred. The danger is that this cash feels like profit. It is not. It is money owed in labor and material that has not been spent yet, and a company that spends it on overhead is financing itself with work it still has to perform. When the job winds down, the billing stops while the cost continues, and the cash gap arrives precisely at the moment the job is least able to help.

Underbilling — performing work that has not been billed — is the more serious warning, because it usually means one of three things, and none of them is good. The billing is behind, which is an administrative failure costing real interest. Or costs are running over and the percent complete is climbing faster than the schedule of values allows billing, which means the job is losing money. Or work was performed outside the contract without a signed change order, which means it may never be billable at all.

The rule of thumb that holds across contractor sizes: a large underbilling on a job that is nearly complete is the single most reliable early signal of a loss job.

Gross profit fade, and how the schedule catches it

Fade is what the industry calls the gap between the margin a job was bid at and the margin it finishes with. It is almost never one dramatic event. It is a hundred small ones: a crew that took nine days instead of six, material bought at a price that moved, a subcontractor who came back for more, rework nobody logged.

A WIP schedule reviewed monthly catches fade while there is still time to react, because the estimated cost at completion has to be revised in front of everyone. That revision is the whole exercise. If a project manager reports 60% complete while costs say 74%, one of the two is wrong and the conversation happens in month four rather than in month nine.

Two practices sharpen this considerably. Compare percent complete by cost against percent complete by physical observation — the superintendent's judgment of what is actually built — and treat any meaningful divergence as a flag rather than as noise. And track fade as its own number, job by job, comparing bid margin against current projected margin. A company whose average fade is four points does not have a bidding problem; it has an execution or a change order problem, and those are fixed in completely different places.

Cost-to-cost is a convention, not a law

Measuring percent complete as cost incurred divided by estimated total cost is the standard method and it works well on most jobs. It also misleads in two specific situations that every contractor eventually hits.

The first is a job with a large front-loaded material purchase. Buying the equipment package in month two can put a job at 45% complete by cost when almost nothing has been installed, which pulls forward earned revenue and margin that has not been earned by anyone. The fix is to exclude uninstalled materials from the calculation, or to carry them separately, rather than to let a purchase order create profit.

The second is a job whose remaining work is disproportionately labor-intensive — the punch list, the finishes, the commissioning. Cost-to-cost tends to be optimistic there, because the cheap-to-buy, slow-to-finish work sits at the end.

Where either applies, other measures do better: units completed on repetitive work, labor hours against a labor budget, or milestone-based recognition on jobs with clean phases. The method matters less than applying it consistently and disclosing which one is in use.

The monthly rhythm, and who owns each number

WIP fails in most companies for a boring reason: the accountant fills it out alone. The accountant knows cost to date and billed to date and cannot possibly know estimated cost at completion, which is an operations judgment.

The cadence that works is a monthly meeting, on a fixed date, with three roles present. Accounting brings cost to date, billings and the previous month's schedule. Each project manager brings a revised estimated cost at completion for their jobs, with the reason for any movement. The owner or an operations lead asks the same two questions about every job: what changed since last month, and what would have to happen for this number to be wrong.

An hour a month covers a portfolio of a dozen jobs. What that hour buys is the difference between finding a problem in month four and finding it at closeout, when the only remaining options are absorbing it or arguing about it.

A schedule that tells a story

Four jobs at a small commercial builder, at the end of month seven.

Job A. Revised contract 1,240,000. Estimated cost 1,060,000. Cost to date 742,000. Percent complete 70%. Earned revenue 868,000. Billed 910,000. Overbilled by 42,000 — normal, funded by a front-loaded schedule of values, and money that will have to be given back in labor over the next four months.

Job B. Revised contract 680,000. Estimated cost 598,000. Cost to date 561,000. Percent complete 94%. Earned revenue 639,200. Billed 578,000. Underbilled by 61,200 on a job that is nearly finished. This is the alarm on the page. Either two months of billing were missed, or there is unbilled change order work, or the estimate at completion is still too low and the real margin is already gone.

Job C. Revised contract 415,000. Estimated cost 372,000 — revised up from 340,000 at bid. Cost to date 205,000. Percent complete 55%. Earned revenue 228,250. Billed 231,000. Roughly in balance on billing, and carrying eight points of fade at the halfway mark, which is where the conversation belongs this month, not at closeout.

Job D. Revised contract 96,000. Estimated cost 71,000. Cost to date 12,000. Percent complete 17%. Earned 16,320. Billed 30,000. Overbilled by 13,680 — a deposit, which is exactly what a deposit looks like on this report.

Portfolio totals: earned revenue 1,751,770 against billings of 1,749,000, which nets out to almost nothing and would tell an owner reading only the total that everything is fine. The total is the least useful number on the page. Job B's 61,200 underbilling and Job C's fade are the entire story, and both are invisible in aggregate.

Why the bank and the bonding company read it first

A surety underwriter looks at a WIP schedule before the income statement, and reads three things. Whether the company is chronically overbilled, which signals that its working capital is borrowed from unperformed work and that a slowdown in new contracts would produce an immediate cash crisis. Whether estimates at completion move meaningfully every month, which signals weak cost control. And whether jobs that closed matched what the schedule predicted three months before they closed — a company whose predictions come true gets more bonding capacity than one whose numbers only reconcile at the end.

That last point is the argument for keeping the schedule honest even when nobody is looking. A schedule that is optimistic every month and correct only at closeout teaches the surety exactly one thing, and it is not flattering.

Five mistakes that ruin the report

• Never revising the estimate at completion. Keeping the bid number in that column makes every job look like it is performing exactly as bid, which is the one thing that never happens.
• Counting pending change orders as contract value. It inflates earned revenue and hides an underbilling that is real until the change order is signed.
• Excluding committed costs. Material delivered but not yet invoiced understates cost to date and overstates margin, in exactly the months when it matters most.
• Letting accounting own the whole report. The number that drives the page is an operations judgment, and it has to be defended out loud by the person who owns the job.
• Reading only the totals. Overbilling on one job masks underbilling on another, and the aggregate hides both problems perfectly.

What to watch every month

Four numbers turn the schedule from a report into a management tool. Net over/underbilled position by job, never only in total. Fade by job, measured as bid margin minus current projected margin, tracked across the portfolio to reveal whether the pattern lives in estimating or in execution. Underbilling on jobs above 80% complete, which is the earliest reliable warning of a loss. And the size of the monthly revision to estimated cost at completion, which measures how well the company knows its own jobs — and is, in the end, the number that decides how much work it can safely take on next year.

Frequently asked questions

What is a WIP schedule and why does it matter more than the P&L?

It is a single page listing every open contract that answers three questions per job: how much of the job is actually done, how much revenue has been earned by doing it, and how that compares with what has been billed. That matters more than the profit and loss statement because the P&L shows revenue that was billed rather than work performed, and costs that were paid rather than the jobs they belong to. A builder can read a profitable month while sitting on two jobs that are quietly eating the year, or a terrible month simply because one large billing landed on the first of the following month. The WIP schedule converts billings and costs into earned revenue, and the difference between earned and billed is the number that changes decisions. Banks and surety companies ask for it before anything else, which tells you what it reveals.

Is overbilling a problem?

Not by itself — it is standard practice and it is how most contractors fund their operations, through a front-loaded schedule of values, billing for stored materials or collecting a deposit. The danger is that the cash it produces feels like profit. It is not: it is money owed in labor and material that has not been spent yet, and a company that spends it on overhead is financing itself with work it still has to perform. The consequence arrives predictably at the end of the job, when billing stops while cost continues, and the cash gap shows up exactly when the job is least able to help. A chronically overbilled position is also the first thing a surety underwriter flags, because it signals that working capital is borrowed from unperformed work and that any slowdown in new contracts would produce an immediate crisis.

Why is underbilling considered a warning sign?

Because performing work you have not billed almost always means one of three things, and none of them is good. The billing is behind, which is an administrative failure that costs real interest. Costs are running over, so percent complete climbs faster than the schedule of values allows billing — which means the job is losing money and the schedule is showing it before the closeout does. Or work was performed outside the contract without a signed change order, in which case it may never be billable at all. The strongest version of this signal, and the most reliable early warning of a loss job at any contractor size, is a large underbilling on a job that is nearly complete. In a four-job example, a 61,200-dollar underbilling on a job at 94% complete is the entire story of the page — and it is completely invisible in the portfolio totals.

How do you calculate percent complete?

The standard method is cost-to-cost: cost incurred to date divided by estimated total cost at completion. It works on most jobs and misleads in two situations. The first is a large front-loaded material purchase — buying an equipment package in month two can show 45% complete when almost nothing is installed, pulling forward revenue and margin nobody has earned; the fix is to exclude uninstalled materials or carry them separately, rather than letting a purchase order create profit. The second is a job whose remaining work is disproportionately labor-intensive, such as punch list, finishes and commissioning, where cost-to-cost runs optimistic because the cheap-to-buy, slow-to-finish work sits at the end. Where either applies, units completed, labor hours against a labor budget, or milestone recognition can do better. The method matters less than applying it consistently and disclosing which one is in use.

Who should fill out the WIP schedule?

Not accounting alone, which is why it fails in most companies. Accounting knows cost to date and billed to date, and cannot possibly know estimated cost at completion — the number that drives every other figure on the page and is an operations judgment. The cadence that works is a monthly meeting on a fixed date with three roles present: accounting brings costs, billings and last month's schedule; each project manager brings a revised estimate at completion for their own jobs, with the reason for any movement; and the owner or operations lead asks the same two questions about every job — what changed since last month, and what would have to happen for this number to be wrong. An hour a month covers a dozen jobs, and it buys the difference between finding a problem in month four and finding it at closeout, when the only options left are absorbing it or arguing about it.