A construction WIP report shows earned revenue versus billings for every active job, and the right move is to run it monthly with a defensible set of columns and a cross-functional review. Project managers, estimators, and accountants each bring information the others don't have, so the report only works when all three sit down together. Done right, it catches margin fade before it becomes a cash problem.
TL;DR:
- Review larger portfolios or fast moving projects every two weeks; otherwise, keep the review monthly, since slower cycles can leave emerging problems unnoticed.
- Match the method to the job: use delivered units for repetitive work, labor hours for labor intensive trades, and avoid cost ratios distorted by uninstalled materials.
- Before finalizing each schedule, reconcile posted costs, open purchase orders, and billings against their ledgers, then update completion estimates with project manager and estimator input.
- Auditors, lenders, and sureties expect consistent methods, documented estimates, ledger traceability, and review notes; consult a CPA about disputed changes or method shifts.
Table of Contents
- What a WIP report is and when to use it
- Standard WIP report components: columns and what each means
- Calculation methods for percent complete and earned revenue
- Accounting and revenue-recognition implications
- Step by step: build the monthly WIP report
- Common mistakes, red flags, and best practices
- Cadence and governance: running the monthly WIP meeting
- Tools and automation for WIP reporting
- Why WIP deserves executive attention, not just bookkeeping
- Get live profit visibility alongside your WIP process
- FAQ
- Sources
What a WIP report is and when to use it
A work-in-progress report connects day-to-day job activity to the company's accounting and forecasting. It takes raw numbers like costs spent, contract value, and billings issued, and turns them into a single view of how a job is actually performing against the estimate that won it. Without this link, a project can look profitable on the invoice side while quietly losing money on the cost side.
Three groups rely on the output. Project managers use it to flag schedule or scope issues before they compound. Accountants use it to post accurate revenue entries. Lenders and sureties use it to judge whether a contractor's backlog is healthy enough to support a bond or a credit line.
Cadence matters as much as content. CFMA's guidance stresses monthly WIP reviews as standard practice, with more frequent updates warranted for larger portfolios.
- Monthly review is the baseline for most contractors running active jobs.
- Biweekly reviews suit larger portfolios or projects with fast-moving costs.
- Any cadence slower than monthly risks letting problems sit undetected for too long.
Standard WIP report components: columns and what each means
A WIP schedule is only as useful as the columns behind it. Each one answers a specific question about a job's financial state, and skipping any of them leaves a blind spot.
- Original contract value: the base amount the job was awarded for, before any changes.
- Change orders: approved additions or reductions that adjust the contract.
- Revised contract value: original value plus approved change orders, the real target.
- Estimated cost at completion (ECAC): the current best estimate of total cost to finish.
- Actual costs to date: everything posted to the job so far, labor, materials, subcontracts.
- Percent complete: the chosen method's calculation of how much of the job is done.
- Earned revenue: revenue recognized based on percent complete and revised contract value.
- Billings to date: what has actually been invoiced to the client.
- Over or under billing: the gap between earned revenue and billings, the number everyone in the meeting watches first.
A few optional fields sharpen the picture further: open purchase orders, retention held, and committed subcontract costs not yet invoiced. These surface commitments that haven't hit the books yet but will. In the monthly meeting, the over/under billing column usually drives the conversation, since a large under-billing can signal either slow invoicing or a job that's losing ground on cost.
Calculation methods for percent complete and earned revenue
Choosing how to calculate percent complete is the single decision that shapes everything downstream in a WIP report. Three methods dominate construction accounting, and each fits different job types.
- Cost-to-cost divides costs incurred to date by the estimated total cost. It's the most common method, but it assumes cost incurred equals progress made, which breaks down when uninstalled materials or front-loaded purchases are sitting on the books.
- Units-of-delivery measures physical output, like linear feet installed or units completed, against the total scope. It works well for repetitive work such as pipeline or paving jobs.
- Labor-hours compares hours worked to estimated total hours. It suits labor-intensive trades where material costs don't track progress well.
Avoid eyeballing percent complete. A contractor who estimates progress by feel rather than by a documented method creates numbers that neither an auditor nor a lender can verify, and that inconsistency is one of the fastest ways to lose credibility during a bonding review.
Here's a simplified worked example. Say a job has a revised contract value of $500,000 and an estimated cost at completion of $400,000. If actual costs to date are $200,000, the cost-to-cost method puts percent complete at 50% ($200,000 divided by $400,000). If billings to date are $300,000, the job is over-billed by $50,000, a flag worth discussing before the next invoice goes out.
Defensible percent-complete methods tied to measurable output, rather than cost-spent ratios alone, hold up better under audit scrutiny, a point the IRS Construction Industry Audit Techniques Guide addresses directly when describing acceptable long-term contract methods.
Accounting and revenue-recognition implications
WIP numbers don't stay inside a spreadsheet. They feed directly into revenue recognition entries, and under ASC 606, how a contractor measures progress has real consequences for financial statements.
RSM's revenue recognition guidance for construction walks through several judgment calls that affect WIP accounting:
- Units of account: whether a contract is treated as one performance obligation or split into several changes how revenue is recognized across phases.
- Variable consideration: unresolved change orders, claims, or incentive payments require judgment about how much revenue to recognize before final agreement.
- Uninstalled materials: materials purchased but not yet installed can distort a cost-to-cost percentage if they're counted as progress when they haven't contributed to the physical work yet.
On the audit and lending side, the IRS Construction Industry Audit Techniques Guide lays out what examiners look for: consistent application of a chosen method, supporting documentation for estimates, and traceability between the WIP schedule and the general ledger. Lenders and sureties expect the same discipline, often requesting meeting notes alongside the schedule itself as proof that estimates are reviewed, not just rolled forward.
When a contract includes unusual terms, contested change orders, or a method change mid-project, that's the point to loop in a CPA or auditor rather than resolve it internally. Technical guidance from the Financial Accounting Standards Board is the reference point for those judgment calls.
Step by step: build the monthly WIP report
Building an accurate WIP schedule follows a consistent sequence, regardless of whether it lives in a spreadsheet or a connected system. The inputs come from a handful of sources that need to agree with each other before the numbers mean anything.
- ERP or job-cost ledger: actual costs posted to date, broken out by job.
- Open commitment log: purchase orders and subcontracts not yet invoiced.
- Change-order log: everything approved, pending, or rejected.
- Billing ledger: invoices issued and payments received per job.
The build itself follows a clear order: gather cost and billing data for every active job, verify open commitments against the PO log, update the estimated cost at completion with input from the PM and estimator, calculate percent complete using the chosen method, compute earned revenue, reconcile that figure against billings to date, and write up meeting notes documenting any changes or flags.
A simple template layout keeps this reproducible from month to month:
Pro Tip: Lock the data cutoff date before the meeting so every number reflects the same snapshot in time.
A short reconciliation checklist closes the loop before the schedule is finalized: confirm every posted invoice is reflected in costs to date, confirm open commitments match the PO log, confirm the ECAC was reviewed (not just copied forward), and confirm billings tie to the AR ledger. Skipping any one of these is how small errors turn into a schedule nobody trusts by year-end.
Common mistakes, red flags, and best practices
The same handful of errors show up again and again in WIP schedules, and most trace back to data that wasn't refreshed.
- Stale estimates: carrying last month's ECAC forward without PM input understates cost growth.
- Missing commitments: open POs and subcontracts that haven't hit the ledger yet create a false sense of available margin.
- Unposted invoices: costs incurred but not yet entered understate costs to date and overstate percent complete.
Lenders and sureties watch for jobs with consistent under-billing, frequent large swings in percent complete, and estimates that never change month to month. Internally, those same patterns are often the first visible sign of margin fade.
Three practices keep a schedule credible: require PM and estimator sign-off on every ECAC change, reconcile open POs against the cost ledger before finalizing numbers, and hold the monthly review with accounting, PMs, and estimators in the same conversation.
Pro Tip: Treat a WIP schedule that never changes month over month as a red flag, not a sign of stability.
Cadence and governance: running the monthly WIP meeting
A WIP report only earns its keep when the meeting around it happens on schedule, with the right people in the room.
- Set attendees: project managers, estimators, and the accounting lead belong at every meeting; bring in operations leadership when a job is flagged for cost or schedule issues.
- Fix the agenda: confirm the data cutoff date, review each job's percent complete and over/under billing, and assign action items for any flagged projects.
- Document outputs: save a versioned copy of the WIP schedule, log the action items agreed on, and file the reconciliation notes where an auditor or lender can find them later.
Treating these three steps as fixed routine, rather than an occasional check-in, is what keeps the schedule audit-ready.
Tools and automation for WIP reporting
Spreadsheets work until job count or complexity outgrows them. The signal to move on is usually one of three things: job costs change daily and manual entry can't keep up, open commitments are hard to track across multiple POs, or forecasting requires pulling numbers from several disconnected files.
Automated systems cut down on the "black hole" entries where a cost exists but hasn't been posted, speed up estimate certification, and surface forecast issues earlier.
- Real-time job cost data removes the lag between work performed and costs recorded.
- Connected commitment tracking keeps open POs visible instead of buried in email threads.
- A Profit Intelligence feature can be built to flag margin variance as it happens rather than at month-end, pulling from connected job, cost, invoice, and photo data in one place.
Why WIP deserves executive attention, not just bookkeeping
Treating WIP as a compliance exercise misses its real value: it's an early-warning system, not paperwork. A schedule that flags a cost overrun in month three is worth more than a clean-looking report in month nine, after the damage is done.
Training project managers to read earned revenue and over-billing numbers, not just schedules, pays off directly. Ask leadership to sponsor the monthly WIP process itself, not just the report it produces.
— Ricky
Get live profit visibility alongside your WIP process
Running a disciplined monthly WIP is the foundation, and pairing it with connected data removes the lag between work performed and numbers reviewed. We built TradePilot to link estimates, job costs, crew activity, jobsite photos, invoices, and payments in one place, so the figures feeding your WIP schedule update as the work happens rather than at month-end cleanup.
- Start by testing Profit Intelligence against your next WIP cycle to see where margin variance shows up first.
- Compare your current ECAC updates against what connected job-cost data surfaces in real time.
- Review pricing and trial details on the TradePilot landing page, including the TRADEPILOT MONTHLY plan at $175 per month.
If you're ready to see how connected data changes your monthly review, explore our features and AI capabilities built around job cost, commitments, and forecasting.
FAQ
What does WIP stand for in construction?
WIP stands for work in progress, referring to active construction jobs that are underway but not yet complete. In accounting, it specifically refers to the costs, billings, and revenue tracked for those unfinished contracts.
What does a "WIP report" mean?
A WIP report is a schedule that compares a job's earned revenue to its actual billings, based on percent complete and estimated cost at completion. It tells a contractor whether a job is over-billed or under-billed relative to the work actually performed, as outlined in CFMA's WIP guidance.
How do you build a WIP report?
Building one means gathering actual costs, open commitments, and billings for each job, updating the estimated cost at completion with PM input, and calculating percent complete using a consistent method like cost-to-cost or units-of-delivery. From there, earned revenue is calculated and reconciled against billings to find the over or under billing position.
What does a WIP report look like?
A typical WIP report is a table with one row per active job and columns for contract value, change orders, estimated cost at completion, costs to date, percent complete, earned revenue, billings to date, and over or under billing. Most contractors review this table monthly alongside notes on any flagged jobs.
Sources
- Work-in-Progress in Construction - CFMA
- Construction Industry Audit Techniques Guide (ATG)
- Revenue recognition considerations for the construction industry - RSM