The Work You Did but Never Billed

Every contractor knows the industry has a payment problem. Rabbet put the cost of slow payments to U.S. construction at $280 billion in 2024, and found nearly all general contractors floating payments out of their own pockets while money moves slowly down the chain. That is the famous half of the cash problem — the half you mostly cannot control.

The unfamous half is fully self-inflicted: work performed, completed, sometimes even praised — and never invoiced. No slow-paying developer required. The money was earned and simply never asked for.

How earned money disappears

Unbilled work is not one leak; it is four, each with its own disguise:

The informal change order. The super says "can you also take care of that?" and your foreman — a builder, not a paralegal — says yes and builds it. The agreement lives in a text thread. The cost lands in your job. The invoice never exists. This is the largest and most chronic leak, and it is a direct symptom of the estimate-versus-actual blindness covered last week: hours accumulating against work the estimate never contained is the unbilled change order, announcing itself weekly to anyone measuring.

The lagging progress bill. The milestone passed on the 28th; the billing cycle closed on the 25th; assembling support took a week nobody had. You just financed your client for another month — voluntarily, in an industry already financing everyone downstream.

The forgotten retainage. Five or ten percent of every invoice, sitting in someone else's account, waiting for a request that requires remembering, paperwork, and follow-through — months after the crew moved on and attention moved with it.

The absorbed small ticket. Service calls, warranty-adjacent extras, the "while you're here" items. Individually too small to chase. Annually, for many companies, a crew-month of free work.

The recovery system

The pattern across all four: the evidence of earned money exists — in daily logs, texts, photos, schedules, and contracts — but no one's job is to cross-reference it against what was actually invoiced. That cross-reference is mechanical, which makes it preparation-layer work:

• Compare field records to the estimate weekly; hours against unestimated work get flagged as probable changes while the client's memory of asking is still fresh.
• Sweep communications for directives. The 6:40 a.m. "go ahead" text becomes a drafted change-order record with date, source, and scope, queued for the PM to confirm.
• Watch milestones against invoices. Passed milestone, no bill: flagged the day it happens, with the support package drafted.
• Track retainage as receivable inventory — every held dollar, its release conditions, and the date it becomes claimable, surfaced instead of remembered.
• Age everything. A one-page weekly brief: what is billable now, what is aging, what is floating — the financial-intelligence pipeline pointed at the revenue you already earned.

The boundary holds here with special force, because billing is where sloppy automation becomes fraud: the system drafts and supports; a human approves every invoice. No unsupported billing, ever. What changes is not who decides to bill — it is that the decision finally arrives with the evidence attached, while billing is still possible and polite.

The cheapest money in the company

Recovering unbilled work is the rare financial improvement with no downside to weigh. It requires winning zero new jobs, hiring nobody, and negotiating nothing. The margin was already earned by crews you already paid. Most contractors who look honestly at a year of jobs find the number is not small — and the discipline that finds it is the same weekly measurement that catches margin drift.

Next week the series leaves the ledger for the highest-stakes part of the control layer: what AI can honestly do for safety — and the hard limits on what it never should.