How to Use Your WIP Report to Find Profit Fade Before Closeout

Most contractors meet the WIP report when a lender, bonding agent, or CPA asks for one. It gets treated as a compliance document: important, technical, and safely outside day-to-day operations.

That is a missed opportunity. A WIP report is one of the few places where an owner can see whether the margin promised at bid is still likely to arrive at closeout.

The report does not prevent a job from going bad. It gives you a chance to notice the drift while the job is still active, identify what changed, and decide what to do next.

The number that matters is revised margin

Every job begins with an expected gross profit. As the work progresses, actual costs, projected costs to complete, approved changes, and production performance should change your view of that number.

If the job was estimated at 22% gross margin and now appears headed toward 14%, do not wait for closeout to explain it. The gap is a management question now:

• Did labor productivity miss the estimate?
• Did a subcontractor or material cost rise?
• Did field conditions change?
• Is work being performed that has not been approved or billed?
• Was the original estimate wrong in a way that may repeat?

A revised margin is not an accusation. It is an early warning that lets the team separate a recoverable problem from a loss that needs to be contained.

Do not let percent complete become a guess

The usefulness of WIP depends on the quality of its inputs. If percent complete is whatever number feels reasonable in a meeting, the resulting margin is only a polished guess.

Use observable progress wherever possible: installed units, completed phases, verified quantities, approved milestones, or a documented cost-to-complete estimate. The goal is not false precision. It is a consistent method that makes changes from one month to the next meaningful.

The same applies to cost-to-complete. Ask the project manager what labor, materials, subcontractor work, equipment, and closeout effort remain. “We are probably fine” is not a forecast.

Watch for the jobs that look too good

An unexpectedly strong margin deserves the same attention as a declining one. A job can look excellent because costs have not been entered, a major purchase order has not been committed, or revenue has been recognized ahead of the work required to earn it.

Those jobs are dangerous because they reassure everyone at exactly the moment the estimate should be challenged. A healthy WIP review asks both questions: which jobs are fading, and which jobs may be flattering us?

Build a monthly review around exceptions

Do not spend an hour reading every active job line by line. Flag the exceptions first:

• Revised gross margin down more than a defined number of points
• Large underbilled or overbilled positions
• Cost-to-complete that changed materially from last month
• Approved change orders not yet billed
• Unapproved change orders where work has already started
• Jobs approaching closeout with a large amount of remaining forecast cost

Then assign an owner and a next action. A good review ends with a small list: issue this invoice, price this change, verify this labor forecast, meet with this customer, revise this production rate for future estimates.

Turn recurring fades into estimating intelligence

One job that loses labor can be weather, an unusual site condition, or a bad week. Three similar jobs that lose labor are a production-rate problem.

That distinction is why job-level WIP matters. It lets you look across completed and active work by estimator, project manager, customer, job type, and cost code. The patterns are where an operating system gets better.

If closeout, mobilization, supervision, or a particular scope repeatedly consumes more hours than the estimate allows, change the next estimate. The WIP report should not be the final record of a loss. It should be the input that stops the next one.

Make it a management meeting

The best WIP process is simple enough to run every month and serious enough that actions are followed up. Bring the owner, project leadership, and whoever owns the accounting data into the same conversation. Review the exceptions. Record the decision. Check whether last month’s actions happened.

That rhythm is more valuable than a perfect spreadsheet delivered once a year. Margin rarely disappears all at once. It fades through ordinary decisions that nobody has connected yet.