Understanding NZS 3910 Retention Release Obligations
Retention under NZS 3910 is governed by strict procedural obligations that both parties must follow. The contract sets clear timeframes and processes, but the real challenge is ensuring these obligations are tracked and met across all your projects.
Under Clause 9.7 of NZS 3910:2013, retention is typically released in two tranches: 50% at Practical Completion and the remainder at Final Completion. However, your NZS 3910 retention release obligations extend far beyond simply releasing money. They include notification requirements, assessment procedures, and strict compliance with contractual deadlines.
Retention release isn't automatic. Both Principal and Contractor have active obligations to trigger, assess, and complete the release process within contractual timeframes.
Principal's NZS 3910 Retention Release Obligations
As Principal, your retention release obligations under NZS 3910 centre on assessment and timely response. When the Contractor requests retention release, you cannot simply sit on that request. The contract imposes specific timeframes for your response.
Your primary obligations include:
- Prompt assessment: Review the Contractor's application for retention release within the timeframes specified in the contract
- Certificate issuance: Issue the appropriate certificate (Practical Completion or Final Completion) if the works satisfy the contractual requirements
- Defects assessment: Before releasing the final retention tranche, assess whether all defects have been remedied
- Timely payment: Release retention within the payment terms once the certificate is issued
The challenge is tracking these obligations across multiple projects simultaneously. When you're managing a portfolio of contracts, retention deadlines can easily slip through the cracks, creating unnecessary disputes and cash flow issues for contractors.
Contractor's NZS 3910 Retention Release Obligations
As Contractor, your retention release obligations under NZS 3910 focus on triggering the release process and providing the necessary documentation. You cannot simply wait for retention to be released. You must actively pursue it through the correct contractual channels.
Your key obligations include:
- Formal application: Submit a written application for retention release when you believe the relevant milestone has been achieved
- Supporting documentation: Provide all necessary documentation to support your application
- Defects remediation: Complete all outstanding defects before applying for final retention release
- Compliance demonstration: Show that all contractual requirements have been satisfied
The timing of your retention release application is crucial. Apply too early, and the Principal can legitimately reject your application. Apply too late, and you're delaying your own cash flow without cause.
Many contractors assume retention release is the Principal's responsibility once milestones are met. Under NZS 3910, the Contractor must formally trigger the process. Retention won't release itself.
Retention Release Timeframes and Deadlines
NZS 3910 retention release obligations are governed by specific timeframes that both parties must observe. These deadlines are contractual obligations, not suggestions, and missing them can trigger disputes or additional costs.
| Event | Timeframe | Party Responsible |
|---|---|---|
| Application for Practical Completion | When works are substantially complete | Contractor |
| Assessment of Practical Completion | Within timeframes specified in Special Conditions | Principal |
| First retention release (typically 50%) | Within payment terms after Practical Completion Certificate | Principal |
| Application for Final Completion | After defects liability period and defect remediation | Contractor |
| Final retention release | Within payment terms after Final Completion Certificate | Principal |
The specific timeframes for assessment are typically defined in the Special Conditions of your contract. Standard timeframes might be 10 or 15 working days, but this varies by project. The critical point is that these are binding deadlines, not targets.
Documentation Requirements for Retention Release
Proper documentation is essential for smooth retention release under NZS 3910. Both parties have obligations to maintain and provide specific records, and inadequate documentation is one of the most common causes of retention release delays.
For Practical Completion retention release, the Contractor typically needs to provide:
- Written application stating that Practical Completion has been achieved
- Evidence that all substantial works are complete
- List of minor outstanding items (if any)
- Compliance certificates and test results as required
For Final Completion retention release, additional documentation includes:
- Evidence that all defects have been remedied
- Final as-built drawings and specifications
- Operation and maintenance manuals
- Warranty documentation
- Final invoicing and payment schedule
The Principal's obligation is to assess this documentation promptly and either issue the certificate or provide clear reasons for withholding it. Vague objections or unreasonable delays in assessment can constitute a breach of the Principal's NZS 3910 retention release obligations.
Consequences of Non-Compliance with Retention Obligations
Failing to meet your NZS 3910 retention release obligations carries real commercial consequences. These are contractual breaches that can trigger additional costs, disputes, and damaged relationships.
For Principals, the consequences of late retention release include:
- Interest payments: You may be liable for interest on the retained amount from the due date
- Contractor claims: Delays can trigger time-related cost claims from the Contractor
- Reputation damage: Word spreads quickly about Principals who hold retention unreasonably
- Relationship strain: Late releases damage working relationships and future tender responses
For Contractors, failing to properly trigger retention release results in:
- Cash flow delays: Your money sits unnecessarily in the Principal's account
- Administrative costs: Chasing overdue retention costs time and resources
- Opportunity cost: Retained funds can't be invested in other projects or operations
- Dispute costs: Formal recovery processes are expensive and time-consuming
In 10 years of project management, I've seen more retention disputes caused by poor process management than by genuine disagreements about work completion. Most retention delays are avoidable through proper tracking and communication.
Managing Retention Release Across Multiple Projects
The real challenge with NZS 3910 retention release obligations is managing them consistently across multiple projects simultaneously. Each project has different milestone dates, different Special Condition timeframes, and different documentation requirements.
Effective retention management requires:
- Centralised tracking: A system that monitors retention deadlines across all projects
- Automated alerts: Notifications before deadlines to allow time for proper assessment
- Document management: Organised storage and retrieval of retention-related correspondence
- Status reporting: Clear visibility of retention positions for senior management
Without systematic tracking, retention release becomes a reactive process. You're constantly chasing overdue releases or scrambling to meet deadlines. This creates unnecessary stress and increases the risk of disputes.
Provan builds AI-powered operating systems for infrastructure and engineering businesses, covering six domains: Pipeline, Contracts, Projects, People, Finance, and Risk. The Contracts domain tracks every retention milestone, release trigger, and payment deadline across your NZS 3910 portfolio so nothing gets overlooked. Built from 10 years managing projects from $10M to $750M.
Stop Chasing Overdue Retention
Get intelligent tracking of all your NZS 3910 retention release obligations. Provan ensures deadlines are met and relationships stay strong.
Book a Working Session