What Are NZS 3910 Performance Bond Requirements
Under NZS 3910:2023, performance bond requirements are established through Clause 5 (Security) and detailed in the Contract Data. The performance bond serves as security for the contractor's proper performance of their contractual obligations, including completion of the works and rectification of defects.
The bond amount is typically expressed as a percentage of the contract price, commonly ranging from 5% to 10% depending on project risk and contractor track record. Unlike retention, which is deducted from progress payments, the performance bond is provided by a third-party guarantor, usually a bank or insurance company.
Performance bonds under NZS 3910 are unconditional guarantees. This means the guarantor must pay on demand without requiring proof of actual breach or loss, provided the claim complies with the bond terms.
Bond Amount and Duration Requirements
The performance bond amount is specified in the Contract Data and typically remains constant throughout the construction phase. However, NZS 3910 performance bond requirements include provisions for bond reduction as key milestones are achieved.
Common bond structures under NZS 3910 include:
- Full amount during construction: 10% of contract price until practical completion
- Reduced amount during defects period: Typically 2.5-5% from practical completion until end of defects period
- Progressive reduction: Stepped reductions tied to specific completion milestones
The bond duration must cover the entire performance period, including the defects liability period. Under Clause 5.1, the contractor must maintain the bond until all obligations are fulfilled or alternative security is provided.
Calculating Bond Amounts
| Contract Value | Typical Bond % | Construction Phase | Defects Phase |
|---|---|---|---|
| Under $5M | 5-10% | $250k-$500k | $125k-$250k |
| $5M-$25M | 5-7.5% | $250k-$1.875M | $125k-$625k |
| Over $25M | 5% | $1.25M+ | $625k+ |
Bond Calling Procedures Under NZS 3910
The process for calling a performance bond under NZS 3910 performance bond requirements is straightforward but must be followed precisely. The principal can make a claim when the contractor fails to perform their obligations, but the claim must be made in accordance with the bond terms.
Typical grounds for bond calling include:
- Contractor abandonment or repudiation of contract
- Insolvency or receivership of the contractor
- Failure to complete works by the time for completion
- Failure to rectify defects within specified timeframes
- Non-compliance with contract administrator directions
Bond claims must be made before the bond expires. Many bonds have strict notice requirements, typically 30-90 days before expiry. Missing these deadlines can leave the principal without security even if grounds for calling exist.
Step-by-Step Bond Calling Process
- Review bond terms: Confirm calling grounds and notice requirements
- Document the breach: Gather evidence of contractor non-performance
- Provide formal notice: Issue written notice to contractor of intention to claim
- Submit claim: Lodge claim with guarantor in accordance with bond terms
- Follow up: Track claim progress and respond to any queries
Contract Administrator Obligations
Under NZS 3910:2023, contract administrators have specific obligations regarding performance bonds that form part of the overall NZS 3910 performance bond requirements framework. These obligations ensure proper management of security throughout the contract period.
Key contract administrator responsibilities include:
- Verification: Confirming bond authenticity and compliance with contract requirements
- Monitoring: Tracking bond expiry dates and renewal requirements
- Assessment: Evaluating contractor performance against bond calling criteria
- Recommendation: Advising the principal on bond calling decisions
- Release: Confirming when bond release conditions are satisfied
The contract administrator must maintain detailed records of all bond-related activities, including copies of bonds, renewal notices, and any correspondence with guarantors. This documentation is crucial if disputes arise over bond calling or release.
Contract administrators can face liability for failing to properly monitor bonds or advise on calling procedures. Ensure you have systems to track expiry dates and regularly review contractor performance against bond criteria.
Common Bond Issues and How to Avoid Them
Even experienced project teams encounter problems with NZS 3910 performance bond requirements. Understanding common pitfalls helps prevent costly mistakes that can leave projects without adequate security.
Bond Expiry Problems
The most frequent issue is bonds expiring before project completion or end of defects periods. This typically occurs when:
- Original bond terms don't account for project extensions
- Renewal notices are missed or ignored
- Contractor financial difficulties prevent renewal
- Guarantor refuses renewal due to changed circumstances
Inadequate Bond Terms
Some bonds contain terms that make calling difficult or impossible. Common problems include:
- Bonds requiring proof of actual loss rather than simple demand
- Complex notice requirements that are difficult to satisfy
- Exclusions that remove coverage for likely breach scenarios
- Dispute resolution clauses that delay payment
Documentation Failures
Poor record-keeping can undermine bond effectiveness. Essential documentation includes:
- Original bond documents and all amendments
- Proof of premium payment and renewal notices
- Correspondence with contractor and guarantor
- Evidence of contractor performance issues
Bond Release Criteria and Timing
Understanding when and how to release performance bonds is as important as knowing when to call them. NZS 3910 performance bond requirements include clear criteria for bond release, but the timing requires careful consideration of ongoing risks.
Typical release criteria include:
- Practical completion: Partial release (usually 50%) when works reach practical completion
- Defects rectification: Further release when defects are satisfactorily remedied
- Final completion: Full release when all contractual obligations are fulfilled
- Alternative security: Release when equivalent security is provided
The contract administrator should only recommend bond release when satisfied that the contractor has fulfilled their obligations for the relevant phase. This includes not just completion of works, but also provision of required documentation, warranties, and manuals.
Consider retaining a portion of the bond for 12-24 months after practical completion to cover latent defects and warranty obligations. This provides ongoing security while recognising the contractor's performance.
Integration with Other NZS 3910 Securities
Performance bonds work alongside other securities under NZS 3910, including retention money, advance payment bonds, and maintenance bonds. Understanding how these securities interact is crucial for effective risk management.
The total security package typically includes:
- Performance bond: 5-10% of contract value for performance security
- Retention: 5% of progress payments held until practical completion
- Advance payment bond: 100% of any advance payments made
- Maintenance bond: 2.5-5% for defects liability period
Some contracts allow retention release upon provision of a maintenance bond, effectively substituting one security for another. This can improve contractor cash flow while maintaining principal protection.
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 bond expiry date, renewal obligation, and release milestone across your NZS 3910 portfolio, alerting you before deadlines pass. Built from 10 years managing projects from $10M to $750M.
Never Miss Another Bond Deadline
Provan's AI-powered system tracks all your NZS 3910 performance bond requirements automatically. From expiry dates to calling criteria, we monitor everything so you can focus on delivering projects.
Book a Working Session