Work in Progress (WIP) Schedule

Definition — what it is

A work in progress schedule is the contractor-wide report that lists every active contract and, for each, reconciles the current contract value, the estimated cost at completion, the percent complete, the revenue earned, and the amount billed, to derive over- or under-billing and the earnings recognized to date. It is the central financial control document of a construction company: it is where project-level cost accounting meets financial accounting, and where the health of the entire backlog is visible on one page. A WIP schedule is not a single job's cost report — it is the portfolio reconciliation across all jobs — and it is not the general ledger, though it must reconcile to it. Because percent complete and estimated cost at completion drive the numbers, the WIP schedule is only as trustworthy as the cost-to-complete behind each job, which is why sureties, lenders, and auditors treat it as the primary lens on a contractor's financial condition.

Also known as: WIP Report, Work in Progress Report, Contract Status Report, Job Schedule

Why it matters — what it protects

The WIP schedule is how construction earnings are actually determined. Under percentage-of-completion, revenue is recognized as cost is incurred against estimated cost at completion, and the WIP schedule is the document that performs that calculation across every job. It is therefore the bridge between the field's cost reality and the company's income statement, and an error in one job's estimate at completion flows straight through to reported profit.

It is the surety's and the lender's primary window into the company. Bonding capacity, credit lines, and covenant compliance are assessed largely from the WIP schedule, because it reveals underbilled jobs quietly financing the company, overbilled jobs that have borrowed against future work, and the quality of management's forecasting. A contractor whose WIP schedule shows large swings in estimated cost at completion is telling its surety it cannot forecast, whatever the final margins turn out to be.

It exposes the cash and earnings risks that job-level reports miss. Over/under billing, only visible at the portfolio level, shows whether the company is financing its owners or its owners are financing it, and whether reported profit is backed by billings or is sitting as unbilled earnings that may never convert. The WIP schedule is where a company discovers it is profitable on paper but starved for cash.

It is the discipline that makes profit fade explainable across the business. By carrying prior-period estimates alongside current ones, the WIP schedule shows which jobs are deteriorating, by how much, and when the deterioration was recognized. A well-maintained WIP schedule turns fade from a year-end surprise into a tracked, attributable trend that management and the surety can both see coming.

Lifecycle — how it moves

1. Job intake

   Each newly awarded contract is added with its original contract value and estimated cost, establishing the baseline gross margin. Errors or optimism at intake propagate through every subsequent period.

2. Period cost and billing capture

   Cost incurred to date and amount billed to date are pulled per job from the job cost reports and pay applications as of the cutoff. Timing mismatches between cost and billing are the source of most over/under noise.

3. Estimate at completion update

   Each job's estimated cost at completion is refreshed from its cost to complete. This is the judgment-laden step that determines earnings, and the one sureties probe hardest for optimism.

4. Percent complete and earned revenue

   Percent complete is computed, usually cost-to-cost, and applied to contract value to derive earned revenue. The method must be consistent across jobs and periods for the schedule to mean anything.

5. Over/under billing derivation

   Earned revenue is compared to billed-to-date to classify each job as overbilled (billings ahead of earnings) or underbilled (earnings ahead of billings), producing the balance-sheet entries for costs in excess of billings and billings in excess of costs.

6. Reconciliation to the general ledger

   The WIP schedule's revenue, cost, and over/under figures are tied to the general ledger and the financial statements. A schedule that does not reconcile to the books is not usable for reporting.

7. Review and analysis

   Management and often the surety review the schedule for fade, large swings in estimate at completion, heavily overbilled jobs, and margin erosion. The analysis, not the table, is what protects the company.

8. Close and trend

   Completed jobs roll off and the schedule is archived so estimate-at-completion accuracy and fade can be trended across periods and across project managers. The trend is the truest measure of forecasting discipline.

Anatomy — the data it carries

Contract number and job

The identity of each active contract, the row the whole reconciliation is built around.

Original contract value

The baseline contract amount before changes, the reference for measuring how scope and margin have moved.

Approved change orders

Executed changes to contract value, kept separate so original-scope performance is distinguishable from added scope.

Current contract value

Original plus approved changes, the revenue ceiling the percent complete is applied against.

Estimated cost at completion

Cost incurred plus cost to complete, the number that drives percent complete and earnings, and the schedule's chief integrity risk.

Estimated gross profit

Contract value minus estimate at completion, the projected margin whose movement across periods is the fade signal.

Cost incurred to date

Actual plus accruals per job, the numerator of cost-to-cost percent complete.

Percent complete

Usually cost incurred over estimated cost at completion. The lever that most affects earned revenue, and the one most sensitive to a soft cost-to-complete.

Earned revenue to date

Percent complete applied to current contract value, the recognized revenue that must reconcile to the income statement.

Billed to date

Cumulative amount invoiced to the owner via pay applications, compared to earned revenue to derive the billing position.

Over / under billing

Billed minus earned. Positive is billings in excess of costs (a liability); negative is costs in excess of billings (an asset).

Prior-period estimate at completion

Last period's forecast, carried so the current-period swing and fade are visible rather than buried.

Backlog / remaining to bill

Contract value not yet earned or billed, the forward revenue and cash the job still represents.

Failure modes — how it breaks

Soft estimate at completion inflates earnings

An optimistic or stale cost to complete understates estimated cost at completion, which overstates percent complete and recognized revenue across the schedule. Reported profit is fiction, and the correction lands as a sudden fade when the real cost finally posts.

Overbilling mistaken for profitability

A heavily overbilled job shows strong cash and looks healthy, but the billings are borrowed against future work not yet performed. As the job finishes, billings flatten while cost continues, cash reverses, and the borrowed money must be earned out under pressure.

Underbilling hiding a financing problem

Costs in excess of billings mean the contractor is financing the owner, tying up cash in unbilled earnings. Left unmanaged, a profitable company runs out of cash, and the WIP schedule is where the problem should have been caught periods earlier.

Inconsistent percent-complete method

Some jobs are measured cost-to-cost, others by units or milestones, or the method changes between periods. Earned revenue is no longer comparable across the portfolio, and the over/under figures are not meaningful.

Schedule does not reconcile to the GL

The WIP revenue and cost do not tie to the general ledger because of coding drift, missing accruals, or timing. The financial statements and the WIP tell different stories, and neither is trusted.

Fade recognized all at once

Deteriorating estimates at completion are held flat and then corrected in a single late period, so fade appears as a shock rather than a tracked trend. This is the pattern that destroys surety confidence, regardless of the eventual margin.

Changes in contract value but not in cost

Approved change orders add revenue but the associated cost is never added to estimate at completion, so the change appears pure margin. Earnings are overstated until the cost of the added scope finally posts.

Metrics — how it is measured

Total over/under billing position

Portfolio net of billings in excess versus costs in excess. Reveals whether the company is financing owners or being financed by them.

Estimate-at-completion swing

Period-over-period movement in estimated cost at completion by job. Large swings signal weak forecasting and draw surety scrutiny.

Profit fade

Decline in estimated gross profit from a prior period or from the original estimate, by job and in aggregate. The core measure of forecasting and execution health.

Underbilled backlog

Total costs in excess of billings across jobs. Cash tied up financing owners, and a working-capital risk if it grows.

Overbilled exposure on near-complete jobs

Billings in excess of costs on jobs past a high completion threshold, the money that must still be earned out.

WIP-to-GL reconciliation variance

Gap between the WIP schedule and the general ledger. Should be immaterial; a persistent gap undermines the whole report.

Gross margin by job and trend

Projected margin per job and its trajectory, the portfolio-level view of where earnings are made and lost.

The AI shift — what actually changes

Conversational

The WIP schedule becomes interrogable across the whole portfolio. You ask which jobs swung most in estimate at completion since last period, which overbilled jobs are past 80 percent complete and must earn out, and which underbilled jobs are tying up the most cash — and get the specific jobs and the cost-to-complete drivers cited rather than reading a wide table by eye.

Generative

The schedule and its analysis are drafted. Given each job's cost, billings, and estimate at completion, a model assembles the full WIP schedule, derives percent complete and over/under consistently, carries prior-period figures for fade, and writes a portfolio narrative naming the biggest fade, the largest swings, and the cash risks for management to review rather than compile.

Orchestrated

The WIP schedule stops being a manual month-end assembly. It pulls cost from job cost reports, billings from pay applications, estimates at completion from cost-to-complete, and change values from the change log, reconciles the whole thing to the general ledger, and flags every job where percent complete, billings, and cost tell inconsistent stories with the source records attached.

Autonomous

The routine production runs unattended: cost and billing captured on cutoff, over/under derived consistently, GL tie-out checked, and an exception report of jobs with material estimate swings, fade, heavy overbilling near completion, or reconciliation breaks surfaced — while humans own every estimate at completion that changes earnings, the percent-complete method, and the sign-off that turns the schedule into reported financials.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Reviewing the portfolio WIP before it goes to the surety.

Analyze this WIP schedule the way a surety would. Identify the jobs with the largest swing in estimated cost at completion since last period and tell me whether the swing came from cost, from forecast change, or from added scope. Flag every job that is overbilled and past 80 percent complete, quantifying the billings that still have to be earned out. Flag underbilled jobs and total the cash they are tying up. Show me profit fade by job against both prior period and original estimate, and reconcile the schedule's revenue and cost to the general ledger, naming any account that does not tie. Cite the cost-to-complete driver behind each material finding and separate real deterioration from billing-timing noise.

What good output looks like: A surety-grade portfolio read that attributes estimate swings to cause, quantifies overbilled earn-out and underbilled cash, decomposes fade against two baselines, and reconciles to the GL, each finding cited.

Follow-ups:

• Which jobs would a surety question first, and what will they ask?
• Recompute total earnings if the three softest estimates at completion were made realistic.
• What is our true over/under position excluding jobs under 20 percent complete?

Generative — Month-end and the WIP schedule with its narrative is due.

Produce this period's WIP schedule from the job cost, billing, and estimate-at-completion data attached. For every active contract, present original contract value, approved changes, current contract value, cost incurred to date, estimated cost at completion, estimated gross profit, percent complete computed cost-to-cost, earned revenue, billed to date, over/under billing, and the prior-period estimate at completion for comparison. Apply the percent-complete method consistently across all jobs. Derive the portfolio over/under position and total backlog. Then write a management narrative naming the largest fade, the biggest estimate swings, the most overbilled near-complete jobs, and the underbilled cash exposure. Flag any job whose cost, billings, and percent complete are internally inconsistent rather than smoothing over it.

What good output looks like: A complete, consistently computed WIP schedule with prior-period comparison and a management narrative that names fade, swings, and cash risks, plus explicit flags on internally inconsistent jobs rather than smoothed numbers.

Follow-ups:

• Draft the board summary: total earnings, fade, over/under, and the three jobs to watch.
• Show the schedule with a downside case on the two softest estimates at completion.
• Which jobs' change orders added contract value but no matching cost to the estimate?

Orchestrated — You want the WIP assembled and reconciled across every system and downstream document.

Assemble this period's WIP schedule across the connected systems as of cutoff. Pull cost incurred and accruals from the job cost reports, billings from the pay applications, estimates at completion from each job's cost to complete, and contract-value changes from the change log. Compute percent complete cost-to-cost and derive earned revenue and over/under billing per job. Reconcile total revenue, cost, and the over/under balances to the general ledger and the balance-sheet accounts for costs in excess and billings in excess, naming any account that does not tie. Flag every job where the pay application billing and the earned revenue diverge unusually, or where the estimate at completion has not been refreshed this period. Return the schedule plus a full reconciliation statement and a list of stale or inconsistent jobs.

What good output looks like: A cross-system WIP schedule reconciled to the GL and balance-sheet accounts, with stale estimates and billing-versus-earnings divergences flagged and the reconciliation breaks attributed to cause.

Follow-ups:

• For jobs that did not refresh their estimate this period, whose cost-to-complete is stale?
• Where WIP and GL disagree, tell me if it is timing, accrual, or coding.
• Show the over/under entries that will post to the balance sheet.

Autonomous — Standing policy for how the WIP schedule should be produced and monitored.

Produce and monitor our WIP schedule each period under these rules. On cutoff, capture cost and billings per job, apply the standing percent-complete method consistently, and derive over/under billing. Pull each job's estimate at completion from its cost to complete, but never change an estimate at completion yourself — if a job's estimate has not been refreshed or diverges materially from the productivity evidence, flag it for the project manager. Reconcile the schedule to the general ledger and escalate any account that does not tie. Track profit fade and estimate swings by job and raise any job whose fade or swing exceeds the threshold. Never alter the percent-complete method, never adjust contract value, and never sign the schedule into the financial statements without human approval — route those, and give me an exception report each period of jobs with material fade, swings, stale estimates, heavy near-complete overbilling, or reconciliation breaks, rather than the full table.

What good output looks like: A self-producing WIP schedule where routine capture, derivation, and GL reconciliation are automatic, estimates at completion and the method stay human-owned, and every material fade, swing, or reconciliation break is escalated with evidence.

Follow-ups:

• Show me which estimates you flagged as stale and how the PMs resolved them.
• Report our estimate-at-completion accuracy this year against jobs that have since closed.

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Year-end reconstruction

   There is no periodic WIP schedule; over/under and earnings are reconstructed at year-end. Fade appears as an annual surprise and the surety sees a company that cannot forecast.

1. Level 1 — Periodic manual WIP

   A monthly WIP schedule is assembled by hand from job data. It computes over/under and earnings but reconciliation to the GL and fade analysis are inconsistent.

2. Level 2 — Reconciled and consistent

   Percent complete is applied consistently, estimates at completion come from disciplined cost-to-complete, the schedule reconciles to the GL, and fade is tracked against prior period and original estimate.

3. Level 3 — Assisted and integrated

   The schedule is assembled from connected systems, reconciled automatically, and analyzed for fade, swings, and cash risk, with inconsistent or stale jobs flagged for review.

4. Level 4 — Operated

   Routine production, derivation, and reconciliation run unattended, while humans own every earnings-affecting estimate, the percent-complete method, and the sign-off into the financial statements.

Common questions

Why do sureties care so much about the WIP schedule?

Because it is the clearest single view of a contractor's financial condition and, crucially, of management's ability to forecast. Bonding capacity depends on the company's earnings, backlog, and working capital, and the WIP schedule shows all three along with the over/under position and the stability of estimates at completion. A surety reads large or frequent swings in estimated cost at completion as evidence the company cannot see its own jobs, which is a bigger red flag than a single thin margin.

What does it mean when a job is overbilled?

Overbilled means the contractor has billed the owner for more than it has earned based on percent complete, so billings are running ahead of cost — billings in excess of costs, a liability on the balance sheet. Modest front-loading is normal and helps cash flow, but a heavily overbilled job near completion is a warning: the billings were effectively borrowed against work not yet done, and as the job finishes, cash reverses and the borrowed amount must be earned out with little billing left to do it.

How does the WIP schedule relate to the income statement?

It is where the income statement's construction revenue is determined. Under percentage-of-completion, the WIP schedule computes earned revenue per job from percent complete and current contract value, and the sum of those figures is the revenue recognized. Because it also derives cost and gross profit, the WIP schedule must reconcile to the general ledger; when it does not, either the books or the schedule is wrong, and neither can be trusted until they tie.