This week’s quick read
Reading a WIP Report Like a Surety Underwriter: What the Schedule Says About You
Most contractors meet their WIP schedule the same way: a banker or bonding agent asked for it, so it got built — sometimes the weekend before the renewal. Then it gets handed over with the hope that nobody reads it too closely. The underwriter reads it closely. Before anyone says a word, that schedule has already told them whether you see your own jobs in real time or discover them at closeout.
The first thing an underwriter checks is whether the WIP ties to the financials. Contract values, costs to date, billings — the schedule and the balance sheet have to reconcile, job by job. When they do, the conversation is about capacity: how much work you can carry and how fast the program can grow. When they don't, the conversation shifts to which number is real — and a credibility conversation is a much more expensive one.
Over- and under-billings get read as behavior, not bookkeeping. An overbilling means collected cash is ahead of work earned; an underbilling means you're financing your customer for free. Neither one is fatal, but the underwriter wants them explained job by job. Unexplained swings — or "we'll true it up at year-end" — say the contractor finds out about job performance late, and late discovery is exactly what a bond is designed to protect against.
Gross profit by job tells the same story as a trend. One job that came in light is a job; margins slipping across several jobs is a system — an estimating problem or a cost-capture problem, and the underwriter doesn't get to choose which. Either way, the risk they're asked to carry just got harder to price, and the program reflects it.
Backlog gets audited for honesty. Signed contracts with real start dates support overhead and next year's aggregate. Backlog padded with verbal awards, stale jobs that never mobilized, or work booked at full contract value before scope is agreed does the opposite — it makes every number on the page worth double-checking, which is the opposite of what you want an underwriter doing.
And the classic flag: change-order work sitting in job costs with no approved contract value behind it. That's revenue being performed on a handshake, and sureties have watched enough of those handshakes turn into disputes to price them in advance. Post the CO the day it's approved, and the flag never exists. Post it "when the customer signs," and the WIP quietly carries dispute risk nobody priced.
That's the play at Groundwork Financial: weekly bookkeeping underneath so the WIP is built from current numbers instead of reconstructed ones, job costing that codes every dollar to the job that earned it, and fractional controller support that keeps the schedule tied out before anyone asks — so the WIP is a capacity tool all year instead of a renewal-week scramble.
Bottom line: An underwriter reads the WIP schedule before they read you. Build it weekly from clean books and it argues for bigger programs; rebuild it the weekend before renewal and it asks the questions that cost weeks.