The WIP schedule is one of the most important financial statements a construction business produces. Lenders use it. Bonding companies use it. Buyers use it in M&A due diligence. Your own leadership team uses it to understand where the business actually stands.
It is also one of the most common places where bad underlying data hides in plain sight.
A WIP schedule that is built on incorrect job cost data does not look broken. It looks like a WIP schedule. The numbers fill in, the percentages calculate, the totals reconcile. The problem is that the inputs are wrong — and the errors compound into material misstatements that nobody catches until it is too late.
Here are the signs that your WIP schedule may not be telling the truth.
Sign 1: Percent complete is always close to what the PM estimated
The percent complete in a WIP schedule is typically derived one of two ways: cost-to-cost (actual costs incurred divided by total estimated costs) or an engineer/PM estimate submitted at month-end.
If your percent complete is always close to what the PM submitted — rather than what the cost data implies — that is a warning sign. It usually means the cost data is not trusted, so the finance team defaults to the PM's feel for where the job stands. The WIP is being built on opinion, not data.
This happens because the underlying job cost data has problems: wrong period, wrong job code, costs that hit the GL but not the subledger. When finance cannot reconcile the cost data to the PM's view of the job, they override the data. The WIP schedule looks clean. The underlying problem is invisible.
Sign 2: Backlog and remaining cost do not track together
As a job progresses, remaining costs should decline roughly in proportion to the work completed. If percent complete is going up but the remaining cost estimate is not coming down proportionally — or if both numbers jump at the same time — that is a sign that either the cost data is being corrected in batches or the EAC (estimate at completion) is being manually adjusted to make the numbers work.
Both are signs that the job cost data underneath the WIP is not reliable enough to drive automatic calculations.
Sign 3: The WIP schedule and the income statement tell different stories
Over-billing creates deferred revenue. Under-billing creates a current asset (costs in excess of billings). Both of these should move in ways that are consistent with the underlying gross margin on the income statement.
If your WIP schedule implies a gross margin materially different from what the income statement shows for the same period, there is a reconciliation gap. Either revenue is being recognized inconsistently, costs are being period-shifted, or the percent complete methodology is producing different results than the accrual-basis income.
This reconciliation gap is one of the most common findings in construction finance audits — and it almost always traces back to job cost data that is either incomplete, mis-coded, or recorded in the wrong period.
Sign 4: Month-end close requires significant WIP adjustments
If your month-end process includes a regular step where someone manually adjusts WIP entries to "get the numbers right" — to make the backlog look reasonable, to smooth a job that is technically over budget, or to defer a loss — that is a data problem masquerading as a process step.
Manual WIP adjustments are sometimes legitimate (genuine estimate revisions, scope changes). But when they are routine, it usually means the automated calculation cannot be trusted, so someone is layering judgment on top of unreliable data. The WIP becomes a document that reflects management intent rather than actual job economics.
Sign 5: Completed jobs do not look like the WIP said they would
The ultimate test of a WIP schedule is whether completed jobs came in close to what the WIP predicted at the 90% complete mark. If your completed jobs regularly come in with materially different gross margins than the WIP implied, the schedule is not working as a predictive tool.
This is the most consequential version of the problem. Bonding capacity gets sized based on WIP. Bids get built based on historical margin data that traces back to the same WIP. Leadership makes decisions about capacity and growth based on their read of the WIP. If those numbers are off, the downstream effects are real.
What to do about it
The fix starts with the job cost data, not the WIP schedule. The WIP is downstream — it is a report built on top of the cost data. If the cost data is unreliable, no amount of WIP methodology work will produce a trustworthy schedule.
A useful diagnostic looks at whether job cost coding is consistent, whether the GL and subledger are in agreement, whether costs are hitting the right period, and whether change order costs are being tracked separately or getting absorbed into original budget lines.
The goal is not to find a number to plug into the WIP. It is to get the underlying cost data accurate enough that the WIP calculation runs automatically and produces numbers the finance team trusts.
That is the difference between a WIP schedule that reflects reality and one that just looks like it does.
If your WIP schedule requires significant manual adjustments at month-end, or if your finance team does not fully trust the numbers it produces, a data diagnostic is the right starting point. A free Data Health Score surfaces the key risk areas. A Data Autopsy goes deeper — examining the job cost inputs that feed your WIP and identifying where the data breaks down.