CONSTRUCTION PERCENTAGE OF COMPLETION PROBLEMS — HOW POC GOES WRONG.
The percentage of completion method is how construction revenue and profit are recognized over the life of a project. When it is applied correctly, the WIP schedule accurately reflects project status and the income statement reflects reality. When it is applied incorrectly — through cost-based percent complete, overbilling, or inconsistent methodology — the WIP schedule becomes unreliable, the income statement misleads, and sureties and banks lose confidence in the numbers.
Most POC problems in subcontracting are not intentional. They are the result of measuring percent complete the wrong way, applying the method inconsistently, and not having an independent financial control function that verifies completion from field data rather than PM estimates. The operational and financial corrections are straightforward once the failure modes are identified.
HOW THE PERCENTAGE OF COMPLETION METHOD GOES WRONG — AND WHAT IT COSTS.
Percentage Complete Based on Cost Spent, Not Work Performed
The most common POC error is calculating percent complete by dividing costs incurred by total estimated cost. This produces a number that looks like project progress but is actually a cost consumption ratio. A project that is 60% of estimated cost consumed is not necessarily 60% complete — it may be 40% complete with cost overruns already embedded in the first half of the project. Cost-based percent complete systematically overstates progress on jobs that are over budget and understates the remaining cost to complete. The correct method is progress-based: measure actual physical completion against the total scope. How many of the 400 linear feet are in the ground? How many of the 8,000 square feet are placed? That number divided by the total is the actual percent complete.
Overbilling Relative to Actual Completion Creates a WIP Liability
When billing outpaces actual physical completion — which happens intentionally through front-loaded SOVs and unintentionally through aggressive billing — the result is a WIP overbilling position. The contractor has billed $420,000 on a project that is only $380,000 complete. The $40,000 difference is a liability — work billed but not yet performed. This liability is visible in an accurate WIP schedule. It is invisible without one. When sureties and banks review WIP schedules, overbilling is a red flag. When a project closes with consistent overbilling history, the final billing is smaller than expected — a cash surprise at the worst time.
POC Applied Inconsistently Across Projects
Some projects are measured by cost, some by physical units, some by milestone, some by estimate of completion. The inconsistency means the WIP schedule is not comparable across projects — and the aggregated over-under billing position is not reliable. Sureties and banks lose confidence in WIP schedules that are measured inconsistently. The fix is a documented POC methodology that is applied identically to every project every month.
Delayed Loss Recognition — Hiding Bad News in WIP
A PM who knows a project is heading for a loss has an incentive to defer recognizing that loss by overstating percent complete or understating cost to complete. The project looks profitable in the WIP schedule while the actual field outcome is heading for a significant loss. When the loss is finally recognized — at closeout or when it can no longer be deferred — it hits the income statement all at once. Sureties call this delayed loss recognition and it is one of the most common triggers for surety concern. The CFO function's job is to independently verify cost-to-complete figures from field production data, not accept PM estimates without review.
BUILDING A POC METHODOLOGY THAT PRODUCES RELIABLE NUMBERS.
The surety implication: Sureties underwrite based on WIP accuracy. A contractor with a documented POC methodology, monthly WIP from closed books, and no history of delayed loss recognition gets better terms and higher capacity than one whose WIP is inconsistent. The financial infrastructure is the underwriting argument.
FREQUENTLY ASKED.
