DELAYED LOSS RECOGNITION IN CONSTRUCTION HOW JOB LOSSES HIDE IN WIP.
Delayed loss recognition is what happens when a contractor knows a job is heading for a loss but defers recognizing it, through an overstated percent complete, an understated cost to complete, or overbilling that masks the underlying financial position. The loss is real. It just doesn't appear in the financial statements until it can no longer be hidden. When it finally does, it hits all at once and surprises everyone except the contractor who knew it was coming.
Sureties are trained to look for this specifically, which is why it costs more than the loss itself. A contractor whose WIP always shows profitable jobs that turn into losses at closeout, or whose cost to complete figures never move even when field conditions clearly warrant a revision, will lose surety confidence however strong the rest of the financial package looks. That confidence is what backs your bonding capacity, so the damage outlives the job that caused it. Recognizing a loss early costs you one quarter. Hiding it costs you the underwriter's trust.
WHAT IT MEANS.
Delayed loss recognition is what happens when a contractor knows a project is heading for a loss but defers recognizing that loss in the financial statements by overstating percent complete, understating cost to complete, or both.
A surety looks for three things when it suspects this. Projects that are always profitable in WIP and then produce losses at closeout. WIP that shows consistent overbilling without matching completion progress. Cost to complete figures that never change even when field conditions should have changed them.
THREE MECHANISMS THAT HIDE A KNOWN LOSS.
Percent complete is overstated
The PM reports 75 percent complete on a phase where the field data supports 65 percent. Because revenue is recognized off percent complete, the overstatement pulls revenue forward and makes the job look like it's earning margin it hasn't earned. Nobody has to lie for this to happen. A PM who is confident the crew will make it up next month reports what he expects rather than what has been built.
Cost to complete is understated
The cost to complete comes in at $180,000 on a phase where a realistic figure is $240,000. That $60,000 difference is the loss, and leaving it out of the estimate keeps it off the financial statements for another month. The estimate is usually built on the production rate the crew was supposed to hit rather than the rate they have been hitting, which is what makes it optimistic instead of dishonest.
Overbilling covers the overrun
Billing ahead of completed work brings in cash that makes the job feel fine while the underlying margin is deteriorating. The cash covers the cost overrun in the short run, so nothing looks wrong in the bank account. What it produces is a job that owes work it has already been paid for, and the reckoning comes at closeout with no billing left to draw against.
WHAT IT LOOKS LIKE IN DOLLARS.
When the PM reports 75 percent complete and the field data supports 65 percent, the WIP should reflect 65 percent. Ten points of overstatement on a phase pulls revenue forward and hides the shortfall inside a job that reads as profitable. The correction is a verification step rather than an argument about who is right.
A cost to complete of $180,000 against a realistic $240,000 defers $60,000 of loss into a future period. If the crew is running at 72 percent of the estimated production rate, the cost to complete has to be calculated at 72 percent productivity and not at 100 percent. That single adjustment is usually the difference between a WIP that reads true and one that doesn't.
THE CFO FUNCTION AS THE INDEPENDENT VERIFIER OF COST TO COMPLETE.
Completion gets verified from field data, meaning foreman logs, inspector reports, and quantity tracking, and not from a PM's estimate of where the job stands. When the PM says 75 percent complete and the field data supports 65 percent, the WIP reflects 65 percent. That's not a judgment about the PM. It's a second set of eyes on a number that decides how much revenue the month reports.
The cost to complete uses the production rates the crew has been achieving on this job. If the crew is running at 72 percent of the estimated production rate, the cost to complete is calculated at 72 percent productivity and not at 100 percent. Assuming the crew will suddenly hit the estimate is the most expensive assumption in construction accounting.
When a cost to complete analysis produces a projected loss, that loss is recognized in the current period rather than deferred until closeout. This is the part owners resist and the part sureties reward. A single recognized loss in a clean set of books reads very differently than the same loss discovered at closeout in books that never flagged it.
Early recognition is what leaves you options. A loss identified while the job is open can be attacked with change order documentation, tighter labor management, or faster billing on the remaining scope. A loss discovered at closeout can only be absorbed. That difference is worth more than the accounting treatment it comes wrapped in.
FLAT MONTHLY FEE. NO SURPRISES.
Three tiers, priced by your trailing twelve month revenue. Which one you're in depends on how much of the work you want off your desk. No hourly billing, no payroll, and no add-ons.
Pricing
| Last 12 months revenue | Monthly fee |
|---|---|
| Up to $1M | $1,900 to $2,900 |
| $1M to $3.5M | $2,600 to $3,900 |
| $3.5M to $6.5M | $3,800 to $5,700 |
| $6.5M to $9.5M | $5,100 to $7,100 |
| $9.5M to $12.5M | $6,100 to $8,500 |
| $12.5M to $15.5M | $7,400 to $11,000 |
| $15.5M to $18.5M | $9,400 to $13,500 |
| $18.5M+ | Quoted individually |
Range reflects the three tiers below. Which one you're in depends on how much of the work you want off your desk. No payroll. No hidden line items.
You stop guessing.
You get the CFO work. Job costing built against the way you estimate, a 13 week cash forecast, monthly WIP, and a meeting every month that ends in decisions rather than a report.
Your bookkeeper keeps doing the books.
You stop touching the books.
Everything in Core, and we run the bookkeeping and the controllership as well. Nobody in your office is answering coding questions or chasing a reconciliation at month end.
We do the books. No payroll.
Every job shows its margin while it's still running.
Everything in Executive, plus the job costing and WIP platform set up, loaded with your cost codes, and managed for you every month. You never have to learn it.
We do the job costing.
FREQUENTLY ASKED.
