Retention Is a Date, Not a Deduction: A UK Contractor's Release Calendar

Retention rarely feels urgent when it is first deducted. It appears as a percentage on a valuation, a familiar feature of UK construction payment practice, and the project team moves on to the next drawing, the next site instruction, the next invoice. The money is not lost at that point. It is deferred, and deferral is precisely why it needs a diary rather than a memory.

For contractors and subcontractors, retention can represent a meaningful slice of working capital. On a modest job, five per cent withheld from each valuation may be manageable. Across several projects, and across two release events per project, the cumulative effect is a cash flow programme hiding inside the accounts. The practical response is to treat every retention as a small project of its own: with an owner, a trigger date, an evidence pack and a follow-up routine.

Begin with a retention register

The calendar should sit behind a register, not replace it. A spreadsheet is sufficient for most firms, provided it captures the information needed to act. For each project, record the counterparty, the contract form and any amendments, the retention rate, the amount held to date, the first release trigger, the second release trigger, the defects period, the notice requirements and the person responsible for the claim.

Three distinctions matter. First, retention is not the same as a Construction Industry Scheme deduction; the two should never be netted together in a single line. Second, retention terms are contractual, not universal, so the register must point to the relevant clause rather than assume a standard five per cent split. Third, sectional completion can create several release dates on one project. A single project entry with one date will eventually mislead.

Map the dates that actually trigger release

Most UK construction contracts link the first release to practical completion and the second to the end of the defects liability period, often followed by a final certificate or final account agreement. The precise wording matters. Practical completion may be evidenced by a certificate rather than the date the last piece of work was finished. The defects period may run from the certificate date, not from site demobilisation. A final account may need to be agreed before the final release is paid.

The calendar should therefore hold three kinds of date: the contractual trigger, the evidence date and the claim date. The contractual trigger tells you when the right to apply arises. The evidence date tells you when the certificate, inspection record or making-good confirmation was issued. The claim date is the date your application or invoice must be submitted to meet the contract's payment cycle. Where the contract is silent or ambiguous, the safest course is to seek clarification early rather than discover the point when the money is due.

Use a rolling forward view

A retention calendar works best as a twelve-month forward view, reviewed monthly. For each release event, set reminders at sensible intervals: ninety days before the trigger, sixty days, thirty days, the trigger date itself, and then seven and thirty days after submission. The intervals need not be elaborate. Their purpose is to force an early question: is the trigger still expected, and is the evidence in hand?

At the ninety-day point, confirm the expected completion or defects date with the project team. At sixty days, assemble the evidence pack. At thirty days, prepare the release application and check the contract's notice mechanics. On the trigger date, submit the application with a clear statement of the amount sought and the basis for it. Seven days later, confirm receipt and ask for the payer's proposed payment date. Thirty days later, escalate if no payment or valid notice has arrived.

Build the evidence pack before it is needed

Retention claims fail less often because the money is disputed than because the file is thin. A useful pack contains the contract and any relevant amendments, the practical completion certificate or equivalent record, the schedule of defects and confirmation that defects have been made good, the valuation or application that created the retention, invoices and statements of account, and the correspondence trail. For second releases, add the final certificate or final account agreement where the contract requires it.

The pack should be assembled at the same time as the commercial team closes the project file, not reconstructed months later when staff have moved on. A simple checklist attached to the register entry is enough. If a document is missing, the calendar entry should show that gap plainly. A missing certificate is not an administrative inconvenience; it is a cash flow risk.

Respect the notice discipline

UK payment rules give withholding a procedural shape. A payer who intends to withhold payment generally must issue the appropriate notice within the contractual or statutory timeframe, and a pay less notice may follow. Retention release can be governed by specific contract terms, so the calendar should record the exact notice and application requirements rather than rely on general assumptions. Informal emails are useful evidence but should not replace the contractual document.

When a payer issues a notice, diary the response. When no notice arrives, diary the follow-up. When a payment is short, compare it with the application and the notice before accepting it as final. The point is not to turn every retention into a dispute, but to ensure that silence does not become agreement by default.

Watch the common failure points

Several problems recur. The practical completion certificate is never issued, so the first release has no clear trigger. The defects schedule is closed informally, leaving no evidence for the second release. A contract amendment changes the release mechanism but the register still reflects the original form. Sectional completion creates multiple dates that were never separated. Small retentions on short jobs are considered too minor to chase and are eventually written off. A counterparty becomes insolvent, and the retention is discovered to be unsecured or subject to trust arrangements that were never properly recorded.

None of these failures is exotic. They are the ordinary consequence of treating retention as a deduction rather than a dated obligation. A monthly review of aged retention, sorted by next trigger date, will surface most of them while there is still time to act.

Make the calendar a control, not a reminder

A calendar that nobody owns is merely a list. Give each release event a named owner, a status and a next action. Review the register in the same meeting as the sales ledger and the payment run. Reconcile the total held against the accounting records so that a release is both claimed and posted correctly. Where a release is overdue, escalate on a defined timetable rather than waiting for the next project meeting.

Retention is not a mysterious feature of UK construction payment. It is a scheduled event, often with a certificate, a defects period and a notice attached. The firms that recover it reliably are not necessarily the most aggressive; they are the ones that know the date, hold the evidence and submit the claim on time. A release calendar turns a passive deduction into an active cash flow control.