How Many Obligations Are in an NZS 3910 Contract? — More Than You Think

Start With the Standard Conditions

The standard conditions of NZS 3910 are not a long document. But density is not measured in page count. It is measured in the number of things that must happen, by a specific party, within a specific timeframe, or else something goes wrong.

Take a walk through a typical project and count the time-bound obligations that the standard conditions create:

Programme and Planning

Under Clause 9.2.1, the contractor must submit a construction programme within 10 working days of contract execution. This is not optional. The programme establishes the baseline against which delay, disruption, and extensions of time will be assessed for the life of the project. If the contractor misses this deadline, their ability to substantiate future time claims is weakened from the outset.

The programme is also not a one-off submission. It must be updated and resubmitted when circumstances change. Creating a recurring obligation that runs for the duration of the contract.

Performance Security

Under Clause 9.3, the contractor must provide a performance bond in the form and amount specified in the special conditions. The timing is typically linked to contract execution. Late provision can technically place the contractor in default before any physical work begins.

Variations

The variation process under NZS 3910 generates multiple obligations from a single event. The Contract Administrator instructs a variation. The contractor prices it. Under Clause 9.8.3, the CA must respond to the contractor's variation pricing within 10 working days. If the CA does not respond within that timeframe, the consequences depend on the specific contract drafting. But silence is rarely neutral in a construction contract.

Claims and Notices

Under Clause 13.3.1, the contractor must give notice of a potential claim "as soon as practicable." That phrase sounds flexible, but it is frequently tightened by special conditions to a fixed period. Often 10 or 20 working days. With the consequence that late notice bars the claim entirely.

Extension of time applications under Clause 13.5 carry their own notice and substantiation requirements. The contractor must demonstrate not just that a delay occurred, but that it was caused by an event for which the principal bears risk, and that the contractor took reasonable steps to mitigate it.

Payment and Retention

The payment cycle generates obligations on both sides. The contractor submitting claims, the CA or IC processing them, and payment being made within the contractual timeframe. These obligations are also governed by the Construction Contracts Act 2002, which imposes its own deadlines independently of the NZS 3910 provisions.

Retention release under Clause 12.4 creates obligations at two points: at practical completion and at the expiry of the defects liability period. Miss either release window and a payment dispute is created. Often months after the project team has moved on to other work.

Practical Completion and Defects

Certification of practical completion under Clause 11.3 triggers a cascade of further obligations: the start of the defects liability period, the first retention release, the assessment of liquidated damages under Clause 10.3, and the contractor's ongoing maintenance obligations.

Then Add the Special Conditions

The standard conditions are the baseline. Special conditions are where the obligation count escalates.

The Construction Sector Accord. A joint government and industry initiative aimed at improving procurement practices in New Zealand construction. Examined the special conditions attached to government NZS 3910 contracts. What they found was striking: the number of special conditions ranged from 7 to 310 across the contracts reviewed.

Three hundred and ten special conditions on top of a standard form contract. That is not a modification. That is a rewrite.

The NZ Treasury reached a similar conclusion in its 2019 review, identifying a "culture of mistrust" in the construction sector that drives principals. Particularly government agencies. To add layer upon layer of special conditions to standard form contracts. The intent is risk transfer. The effect is complexity that neither party can reliably manage.

What Special Conditions Actually Do to the Obligation Count

Special conditions modify the standard form in several ways, each of which creates new obligations or changes existing ones:

• Tightened timeframes. The "as soon as practicable" notice requirement under Clause 13.3.1 is frequently replaced with a fixed period (10, 15, or 20 working days) with strict time-bar consequences. This converts a flexible obligation into a hard deadline.
• Additional reporting requirements. Monthly progress reports, financial forecasts, resource schedules, and quality assurance submissions all add new obligations, each with its own deadline and its own consequence for non-compliance.
• New approval gates. Special conditions often require the contractor to obtain approval before proceeding with specific activities such as temporary works designs, traffic management plans, and environmental management plans. Each approval gate is an obligation for the contractor to submit and an obligation for the CA to respond.
• Modified payment terms. Special conditions may change retention percentages, introduce milestone-based payment instead of monthly claims, require additional documentation before payment can be processed, or extend the period for responding to payment claims.
• Additional insurance and bond requirements. Beyond the standard performance bond under Clause 9.3, special conditions may require specific insurance policies, parent company guarantees, or additional security, each with its own compliance obligations.
• Health and safety additions. Additional hold points, third-party audits, incident reporting requirements, and safety committee participation obligations are common in government contracts.

Each of these additions creates new obligations. And many of them create reciprocal obligations. A requirement for the contractor to submit a monthly resource schedule creates an obligation for the CA to review and respond to it. A new approval gate creates deadlines on both sides.

Why Manual Tracking Breaks Down

The PlanGrid and FMI 2018 industry research found that construction professionals spend 35% of their time on non-productive activities including looking for project information, managing conflict resolution, and dealing with rework and mistakes. That translates to more than 14 hours per week per person spent on activities that do not directly advance the project.

Now consider what obligation tracking looks like on a live project with, say, 120 special conditions layered on top of the NZS 3910 standard form. The contract administrator has a spreadsheet. Possibly several. Each obligation is a row. Each row has a deadline, a responsible party, a status, and dependencies on other obligations. When a variation is instructed, multiple rows are affected. When an extension of time is granted, the entire programme baseline shifts and deadlines cascade.

The spreadsheet does not cascade. It does not link obligations to their trigger events. It does not alert the CA when a deadline is approaching. It does not distinguish between CA obligations and IC obligations. It relies entirely on the person maintaining it to remember what needs updating, when, and why.

On a single contract, this is difficult. On three or four contracts running simultaneously. Which is the reality for most PMC firms. It is unsustainable.

The 2023 CA/IC Split Adds More Obligations

NZS 3910:2023 replaced the single Engineer to Contract role with two roles: the Contract Administrator and the Independent Certifier. This was the right decision. Separating administrative functions from certification functions reduces the conflict of interest inherent in the old model.

But it also increases the obligation count. Functions that were previously assigned to one person are now split across two. The CA has obligations. The IC has obligations. Some obligations that were previously one step (the Engineer certifies practical completion) are now multi-step (the CA confirms the works are complete; the IC independently certifies practical completion under Clause 11.3).

For teams that are already struggling to track obligations under the old model, the CA/IC split adds complexity to an already challenging task. For teams with systematic tracking, it simply means two obligation registers instead of one. With clear ownership for each item.

For a deeper look at how the CA/IC roles work in practice, see our article on NZS 3910 Contract Administrator vs Independent Certifier.

The Numbers That Matter

Arcadis has consistently identified failure to properly administer the contract as the number one cause of construction disputes globally. The WorldCC (formerly IACCM) found that poor contract management costs organisations an average of 9.2% of annual revenue.

These are not abstract numbers. On a $50M construction project, 9.2% of revenue lost through poor contract management is $4.6M. That is not a rounding error. It is the difference between a profitable project and a loss-making one.

The cost of systematic obligation tracking is a fraction of the cost of one missed deadline that triggers a dispute. The question is not whether you can afford to track every obligation. It is whether you can afford not to.