Retention Is Money You've Already Earned. Most of It Is Sitting Uncollected.
Retention is one of the few places in a contracting business where cash is lost through inattention rather than error. Nobody makes a bad decision. Nobody underprices. The work is done, the money is earned, and then it simply doesn't come back.
Small on one job, structural across a year
Five per cent held on a $400,000 job is $20,000. Half released at practical completion, half at the end of the defects liability period. Nobody loses sleep over it.
Run thirty of those jobs a year and you're carrying somewhere between $300,000 and $600,000 of your own money in other people's bank accounts at any given time. That is working capital you have already funded — you paid the wages, you paid the suppliers, you carried the overhead — and it is sitting outside the business earning nothing for you.
The businesses that feel permanently cash-tight despite reasonable margins are very often the businesses with an uncontrolled retention balance. They're not unprofitable. They're under-collected.
Why it goes uncollected
Retention falls into an ownership gap that exists in almost every project-based business.
The project manager owns the job until handover. Once the job is handed over, their attention moves to the next one, and the commercial tail of the completed job becomes nobody's priority. Finance owns the debtors ledger, but retention doesn't behave like a normal debtor — it isn't overdue, it isn't disputed, and it doesn't appear on an aged receivables report as a problem. It's simply not due yet.
Then the release date passes, and it still isn't chased, because no system flagged it. Twelve months after practical completion, the person who could confirm the defects were rectified has left. The contract file is somewhere in a shared drive. The client's project manager has changed. What was a straightforward claim becomes a negotiation.
By the time it surfaces, the conversation has shifted from "please release our retention" to "can you demonstrate the defects were closed out".
What a retention register actually does
A retention register is not a sophisticated instrument. It's a single sheet that lists, for every job:
Contract value and retention percentage
Amount held to date
First release date and trigger condition (usually practical completion)
Second release date and trigger condition (usually expiry of the defects liability period)
Evidence required to support release
The person responsible for claiming it
What it does is convert a passive balance into an active task list with dates against it. Once release dates are visible three months out, someone can act on them before the trail goes cold.
The register also gives you something you almost certainly don't have now: a clear picture of how much of your balance sheet is retention, and how that balance is trending. If it's growing faster than revenue, you have a collection problem, not a growth problem.
Treat release as a claim
The most useful change is one of framing. Most businesses treat retention release as an administrative request. It should be treated as a claim, with the same discipline applied to a progress claim.
That means: a formal submission, on your letterhead, referencing the contract clause, attaching the practical completion certificate or defects sign-off, and stating the amount due and the date due. It means diarising the follow-up before you send it. It means escalating to the same person you'd escalate an overdue progress claim to.
The difference in recovery rates between businesses that email "just checking on our retention" and businesses that submit a documented claim is substantial, and it's entirely down to process.
The commercial point
Retention is often the last money in a job and the first money forgotten. It's also, by definition, pure margin — the costs have already been incurred and paid. Every dollar of retention you fail to collect comes straight off your net profit.
You don't need a new system to fix it. You need a register, a date, and a name against the date.