What a WIP Schedule Is and Why Your Surety Wants One

A subcontractor with $4 million in active contracts can be profitable on paper and overbilled by $200,000 at the same time, and without a WIP schedule, nobody inside the company knows it until the jobs finish and the cash gets strange.

The work-in-progress schedule is the report that surfaces this, which is why your surety asks for one at renewal, why banks want one attached to financial statements, and why construction CPAs treat it as the first page worth reading.

This explainer covers what the schedule shows, how the math works, and what the numbers mean, written from the accounting side for subs who keep getting asked for one.

The problem the WIP schedule solves

Contract work creates a gap that ordinary financials can't see: what you've billed and what you've earned are almost never the same number at any given moment. Billings follow the pay app schedule and the SOV.

Earnings follow actual progress, which follows costs going into the work. A job can be billed ahead of its real progress or behind it, and the monthly P&L, which for many subs simply records billings as revenue, papers over the difference entirely.

That difference has a direction, and each direction means something.

Billed ahead of progress, overbilled, means you're holding cash you haven't earned yet, which feels great and can be dangerous, because the remaining work has to be completed with money already spent elsewhere.

Billed behind progress, underbilled, means you've done work you haven't collected on, financing the GC's project with your own cash, and sometimes it means something worse: costs are running past estimate and the billing hasn't caught up because the margin isn't there to bill.

The WIP schedule is the report that quantifies this, job by job, every month or quarter.

The math, one job at a time

The engine is the percentage-of-completion method, and the standard version is cost-to-cost: your progress on a job equals costs incurred to date divided by total estimated costs at completion.

A worked example.

Contract price $1,000,000, estimated total cost $850,000, so estimated gross profit $150,000.

Costs to date: $425,000, which makes the job 50 percent complete.

Earned revenue is 50 percent of the contract: $500,000. Now the comparison that matters: you've billed $560,000 on pay apps to date.

Billed $560,000 against $500,000 earned means the job is overbilled by $60,000, carried on the balance sheet as a liability, billings in excess of costs and estimated earnings.

If you'd billed $460,000 instead, the job would be underbilled by $40,000, an asset, costs and estimated earnings in excess of billings.

The schedule runs this for every open job and totals the columns: contract price, estimated cost, estimated profit, costs to date, percent complete, earned revenue, billed to date, and over/under billing per job.

What the reader is actually looking for

A surety or construction lender reads the WIP schedule for patterns, and knowing what they look for tells you what the report reveals.

Fade is the first. If a job's estimated profit was $150,000 at 30 percent complete and $110,000 at 70 percent complete, the margin is fading, and fade across multiple jobs is the classic signal of estimating problems or field problems. Profit that grows as jobs progress, gain, reads well; persistent fade reads badly, and sureties track it job by job across your schedules.

Systematic overbilling is the second. Modest overbilling is normal and even healthy, front-loaded SOVs produce it by design. Heavy overbilling across the whole schedule means future work is already paid for and spent, and the reader knows the last 20 percent of those jobs will consume cash the company no longer has. That's the borrow-from-the-next-job treadmill, and a WIP schedule shows it plainly.

Chronic underbilling is the third. One underbilled job might be a billing lag. Underbilling across the schedule suggests either an office that can't keep pay apps current or, worse, jobs whose costs are outrunning their estimates, meaning the "profit" in the estimate column isn't real. Reviewers probe underbilled jobs hardest, because that's where surprises live.

The honesty of the whole document rests on one input: estimated cost at completion, per job.

Costs to date are facts from the books; the estimate is judgment, and it has to be updated as jobs move, because a WIP schedule built on stale estimates is fiction with good formatting.

This is why the schedule is only as good as the job costing underneath it, the cost-by-job machinery covered in How to Track Job Costs in QuickBooks Online, and why revenue recognized this way connects to billing discipline, the pay app mechanics covered in How AIA Progress Billing Works.

Why it's worth running monthly, not annually

Most subs meet the WIP schedule once a year, when the surety or the CPA preparing reviewed statements requires it, and treat it as compliance. The operational case is stronger than the compliance case: a monthly WIP schedule shows margin fade while the job is still running, when the response can be a change order conversation, a production fix, or a hard look at the estimate, instead of a post-mortem. It shows overbilling building up while there's still time to bank the cash for the back end of the job. It turns "how are the jobs doing" from a feeling into a page.

The prerequisites are unglamorous: complete job-level cost capture, labor at real burdened rates, and current estimates at completion, maintained with the same discipline as the billing. For a sub whose books already run clean job costing, producing the schedule is arithmetic on data that exists. For a sub whose costs live in one undifferentiated pile, the schedule is impossible, which is itself the diagnosis.

On bonded and public work, the WIP schedule joins the rest of the paper spine, the certified payroll compliance covered in Certified Payroll for Subcontractors: The Complete Guide and the retainage tracking covered in Retainage Accounting in QuickBooks Online, as part of what separates subs who scale on public work from subs who get squeezed by it.

At Prophet Accounting, we run the back office that makes contract work legible: job costing at burdened rates, retainage tracked by contract, certified payroll on covered projects, and monthly reporting that shows margin by job while there's still time to act on it.

If your surety keeps asking for numbers your books can't produce, schedule a consultation at prophetaccounting.com/construction or give us a call at (772) 380-2871.