NZS 3910 Notice Requirements Time Bars

What Are NZS 3910 Notice Requirements Time Bars?

NZS 3910 notice requirements time bars are contractual deadlines that prevent you from pursuing certain claims if you don't give notice within the specified timeframe. These are not just administrative requirements. They are absolute barriers. Once the time bar expires, the contract treats your claim as if it never existed.

The principle is harsh but clear: if you don't notify the other party within the prescribed period, you lose the right to claim. Even if you have a legitimate entitlement worth millions. Courts have consistently upheld these time bars, viewing them as fundamental to commercial certainty in construction contracts.

Key NZS 3910 Notice Requirements and Time Bars

NZS 3910 contains multiple notice requirements with varying time bars. Here are the most critical ones that project teams encounter:

Claim Type	Clause	Time Bar	Who Gives Notice
Variation Claims	10.1	20 working days from awareness	Contractor to Contract Administrator
Extension of Time	12.1	20 working days from awareness	Contractor to Contract Administrator
Compensation Events	12.2	20 working days from awareness	Contractor to Contract Administrator
Disputed Instructions	6.2	5 working days from instruction	Contractor to Contract Administrator
Payment Disputes	21.3	10 working days from payment certificate	Contractor to Principal

The "Awareness" Test

Many NZS 3910 notice requirements are triggered by "awareness" rather than the actual occurrence of an event. Clause 10.1 requires notice within 20 working days of when the contractor "becomes aware, or should reasonably have become aware" of circumstances giving rise to a claim.

This creates complexity. You don't start the clock when the variation work begins. You start it when someone in your organisation becomes aware that the work constitutes a variation. This might be your site manager, project manager, or even a subcontractor supervisor.

Common Mistakes That Trigger Time Bars

Project teams regularly lose valid claims through simple procedural failures. These mistakes often stem from misunderstanding how NZS 3910 notice requirements actually work:

Assuming Verbal Notice Counts

Telling the Contract Administrator about a potential claim over coffee doesn't satisfy NZS 3910 notice requirements. The standard requires written notice that clearly identifies the circumstances and indicates an intention to claim. Casual conversations, meeting minutes that mention issues in passing, or RFIs that hint at problems don't constitute proper notice.

Waiting for Certainty

Many contractors delay giving notice until they fully understand the scope and cost of their claim. This approach is fatal under NZS 3910. The notice requirement is triggered by awareness of circumstances that may give rise to a claim, not certainty about the final quantum.

Misidentifying Who Must Give Notice

Not all NZS 3910 notice requirements flow from contractor to Contract Administrator. Payment dispute notices under Clause 21.3 go to the Principal. Defect notices under Clause 16.1 flow from Contract Administrator to contractor. Getting the recipient wrong can invalidate your notice.

Inconsistent Internal Processes

Large projects involve multiple people who might become aware of claim circumstances. Site supervisors, design managers, quantity surveyors, and subcontractor coordinators all interact with work that could trigger NZS 3910 notice requirements. Without clear internal processes, critical notice periods can expire while different team members assume someone else is handling it.

Who Is Responsible for NZS 3910 Notice Requirements?

Responsibility for NZS 3910 notice requirements isn't always obvious, especially on complex projects with multiple stakeholders. The standard creates different obligations for different parties:

Contractor Obligations

Contractors bear the primary burden for most NZS 3910 notice requirements. They must notify the Contract Administrator of variations, extensions of time, compensation events, and disputed instructions. This obligation can't be delegated to subcontractors. Even if a subcontractor becomes aware of claim circumstances, the head contractor remains responsible for giving timely notice.

Contract Administrator Obligations

Contract Administrators have fewer notice obligations, but they're equally strict. They must notify contractors of defects under Clause 16.1 and any instructions under Clause 6.1. They also have obligations around payment certificates and dispute resolution processes.

Principal Obligations

Principals have limited direct notice obligations under NZS 3910, but they receive certain notices (particularly payment disputes) and must respond within prescribed timeframes. Their main exposure comes through the actions of their Contract Administrator.

Notice Content Requirements Under NZS 3910

NZS 3910 notice requirements are not just about timing. Content matters too. A notice given within the time bar can still fail if it doesn't contain the required information:

Essential Elements

• Clear identification of circumstances: Describe what happened, when it happened, and why you believe it gives rise to a claim
• Reference to contract provisions: Identify which clause of NZS 3910 you're claiming under
• Intention to claim: Make it clear you're giving notice of a potential claim, not just reporting information
• Supporting documentation: Attach relevant drawings, correspondence, or other evidence available at the time

What You Don't Need

The notice doesn't need to include final costings, detailed programmes, or comprehensive legal analysis. NZS 3910 recognises that you're giving notice of circumstances that may develop into a claim, not presenting a final, quantified demand.

Managing Multiple Notice Requirements on Complex Projects

Large projects generate multiple potential claims simultaneously, each with different NZS 3910 notice requirements and time bars. A design change might trigger variation claims, extension of time claims, and compensation event claims. All with separate notice obligations.

Tracking Awareness Dates

The biggest challenge is tracking when different people in your organisation become aware of circumstances. Your design manager might become aware of a design change on Monday, your site manager might understand its cost implications on Wednesday, and your project manager might recognise the programme impact on Friday. Which awareness date triggers the 20-day clock?

The answer is Monday. The first awareness in your organisation starts the time bar running. This makes internal communication critical to NZS 3910 compliance.

Coordination Between Claims

Related claims need coordinated notice strategies. If a design change affects cost, time, and creates compensation events, give notice for all potential claims simultaneously. This prevents arguments about whether later notices are time-barred and ensures comprehensive protection of your position.

Electronic Notice Systems and NZS 3910 Compliance

Modern projects increasingly rely on electronic systems for contract administration, but NZS 3910 doesn't specifically address electronic notices. The key question is whether your electronic notice satisfies the standard's requirements for written notice.

Email Notices

Email generally satisfies NZS 3910 notice requirements if it contains all required content and is sent to the correct recipient. However, ensure your contract doesn't specify alternative electronic processes. Some projects require notices through specific project management platforms.

System-Generated Alerts

Project management systems can generate automatic alerts when claim circumstances arise, but these alerts don't constitute NZS 3910 notice. You still need formal written notice that complies with the standard's content requirements.

Time Bar Defences and Extensions

NZS 3910 notice requirements time bars appear absolute, but limited circumstances can extend or excuse late notice:

Prevention by the Other Party

If the party who should receive notice prevents timely notification, time bars may not apply. However, this defence requires clear evidence that prevention occurred, not just difficulty in communication.

Continuing Events

Some claim circumstances continue over time rather than occurring at a specific moment. For continuing events, you may be able to give notice for ongoing impacts even if the initial notice was late. However, this defence has narrow application and shouldn't be relied upon.

Contractual Modifications

Parties can agree to extend time bars or accept late notice, but such agreements must be clearly documented and signed by authorised representatives.