Retainage

Definition

Retainage (called retention in much of the world outside North America) is the portion of each progress payment the owner withholds from a contractor — typically 5% or 10% — to be released at defined performance points, most commonly substantial completion and the end of the defects liability period. It is one of the oldest commercial mechanisms in construction and remains one of the most consequential.

Why It Matters

Retainage aligns contractor cashflow with finished, accepted work. It funds the punch-list discipline. It also pinches contractor liquidity, drives a lot of subcontractor risk, and is a recurring source of dispute. Project controls teams need to track it accurately on both sides of the contract.

Typical Mechanics

• Standard rate: 5%–10% of each progress invoice.
• Reduction at substantial completion: commonly stepped down to 2.5% on the held amount, releasing the rest.
• Final release: at the end of the defects liability period (often 12 months from substantial completion).
• Substitution: some contracts allow a retention bond to replace cash retainage from a specified point, freeing contractor working capital.
• Cap: some standard forms cap total retainage at a percentage of the contract value once it is reached, regardless of further progress.

Real-World Construction Example

On a $92m hospital extension, the owner held 10% retainage for the first half of progress, reducing to 5% thereafter and to 2.5% at substantial completion. By contract close-out, the contractor had $2.3m sitting in retention. Final release was tied to clearance of a 280-item punch list and the as-built drawing pack. The punch list closed in 14 weeks, but the as-built submission slipped by four months, and so did the final retention release. The contractor's subcontractors — who had been promised release on the same schedule — escalated to disputes. The lesson the owner team took into the next project: tie release to each deliverable, not to the bundle.

Real-World IT / Agile Example

Software and digital contracts rarely call it "retainage" but increasingly use the same idea. A platform-build contract held 15% of each milestone invoice until the relevant feature had run in production for 90 days at the agreed SLO. Performance regressions reset the clock. The mechanism aligned vendor incentives with operational stability, not just feature delivery, and ended a long history of "ship and disappear" projects.

Best Practices

• Define release events precisely — substantial completion, defects liability, deliverable acceptance — and write the evidence requirements into the contract.
• Allow retention bond substitution from an appropriate point; cash retention beyond a year is a liquidity hammer that distorts behaviour.
• Mirror the retainage downstream. The main contractor cannot release subcontractors faster than they are released themselves without absorbing the cost.
• Track retainage as a separate ledger line in the cost report; lumping it into payables hides the running balance.
• Forecast retainage release on the cashflow curve; surprises here destabilise the contractor.

Project Controls Treatment

Controls teams track three numbers per contract: retainage held to date, retainage forecast at each release point, and retainage at risk (the portion tied to deliverables currently behind schedule). These three feed both the cost report and the cashflow forecast. Retainage release dates are also live items on the integrated master schedule; if they slip, contractor cashflow slips with them.

Common Mistakes

• Vague release events ("upon completion" rather than "upon owner acceptance of items X, Y, Z"). Disputes follow.
• Not flowing the retainage profile down to subcontracts; main contractor absorbs the squeeze.
• Forgetting to track retainage in the cashflow forecast; the working-capital position is mis-stated.
• Releasing retention without confirming all release conditions are met; future leverage is gone.
• Using retainage as a punitive tool — withholding more than the contract allows. Disputes and damages follow.
• Treating retainage and warranty as the same thing; they overlap but serve different purposes.

Expert Tips

• Tie release to each acceptance deliverable, not to a bundled "everything done" moment. It removes one of the most common dispute triggers.
• Permit a retention bond from substantial completion. The contractor's cost of capital drops sharply; the owner keeps the security.
• Walk the punch list with the contractor weekly in the run-up to release; surprises here add months.
• Reconcile retainage monthly between owner and contractor ledgers. Drift in either direction becomes a dispute later.
• Plan the as-built submission early. It is the single deliverable that most often delays final release.

Practical Lessons Learned

• Most retainage disputes are not about the percentage — they are about the release conditions.
• Subcontractor distress almost always traces back to retainage misalignment between tiers.
• Cash retainage is a blunt instrument; well-defined release events plus a bond is a precision tool.

Key Takeaways

• Retainage aligns contractor cashflow with accepted performance.
• 5%–10% is the conventional band, with structured reduction at substantial completion.
• Define release events and evidence precisely; vagueness is the dispute trigger.
• Flow retainage down to subcontracts to avoid squeezing the lowest tier.
• Track held, forecast, and at-risk amounts as a live ledger line.

Related Encyclopedia Entries

• Punch List
• Handover Management
• Cost Control
• Change Order Management
• Procurement Management
• Operational Readiness

Related Research Articles, Case Studies & Tools

• Project Controls Academy: Contract Administration
• Retainage Ledger Template
• Learning Tracks: Commercial Management
• Hospital extension retention dispute
• Retention bond economics