Practical Completion and Defects Liability: When Is Retention Released?
Retention is often treated as "we will get it later". That is not a strategy.
Luke Sanders
IT Developer
Updated 17 April 2026
Table of contents
Retention is often treated as "we will get it later". That is not a strategy.
The money is yours in principle, but only if release triggers are tracked and actioned. In most subcontractor environments, retention release depends on practical completion milestones and the end of the defects period under the contract.
Practical completion in real terms
Practical completion usually means the works are complete enough for use, subject to minor snagging. It is an operational threshold, not a signal to stop commercial control.
From a retention perspective, it is often the first trigger point for release mechanics.
Defects liability period: why it matters
After practical completion, contracts commonly include a defects period (sometimes called a rectification period). Remaining retention is often tied to this period ending and agreed defects being addressed.
The key risk is timing drift:
- completion date recorded late
- defects period end date not diarised
- release application not submitted promptly
Typical release structures subcontractors see
Depending on contract terms, firms often encounter patterns such as:
- split release structure (for example first release at practical completion, remainder after defects period)
- full release at a single final trigger
- bespoke client schedule
Your exact rights are contract-led. Do not assume another project's pattern applies automatically.
Practical controls to stop retention leakage
1) Record trigger dates at project setup
Capture planned practical completion date and planned defects period end date in one register.
2) Link retention amounts to explicit trigger events
For each project, store:
- total retention held
- amount linked to trigger 1
- amount linked to trigger 2/final
3) Run a monthly release sweep
Review all projects with upcoming trigger dates in the next 60 days and pre-draft release requests.
4) Keep evidence attached
If release is delayed, evidence of completion, defects close-out, and prior notices helps move matters faster.
How BuildQS supports retention control
BuildQS includes retention workflows designed around release scheduling:
- project-level retention settings
- release schedule support (including split timing models)
- clear visibility of held vs released amounts
Related reading:
- Retention in Construction: What It Is and Your Rights
- Retention Release in Construction: How BuildQS Handles It
Frequently asked questions
Is practical completion the same as final completion?
No. Practical completion and final close-out are different stages. Your contract definitions control which milestone triggers each retention release.
Can we request release before defects period ends?
You can request whatever your contract allows. If your schedule ties remaining release to post-defects milestones, early payment is usually harder to secure.
What is the biggest retention admin mistake?
Not tracking dates and trigger conditions centrally. The money then drifts into aged debt.
Should retention be tracked in the same system as valuations?
Yes. Separating retention from valuation history makes reconciliation and recovery harder.
Want a cleaner retention release process? Track held amounts, release schedules, and project triggers in one place. View BuildQS Pricing
Sources
- Joint Contracts Tribunal (JCT), contract suite overview: https://www.jctltd.co.uk/
- NEC Contracts, contract family overview: https://www.neccontract.com/
- BuildQS retention guide and release workflow examples: https://buildqs.com/blog/retention-release-construction-how-buildqs-handles-it