NZS 3910 Contract Administrator vs Independent Certifier — The Practical Guide

Why the Split Happened

Under the 2013 edition of NZS 3910, the Engineer to Contract was the single point of authority. They administered the contract day-to-day on behalf of the principal. They also issued certifications. Practical completion, payment certificates, defects assessments. That were meant to be impartial. The problem was structural: the Engineer was appointed by the principal, paid by the principal, and often employed by the principal's PMC firm. But for certification purposes, they were expected to act as though none of that mattered.

It was always a tension. And it produced real consequences. Contractors challenged certifications on the basis that the Engineer was not truly independent. Principals questioned why the person they were paying was making decisions that went against their commercial interests. The legal commentary from firms including Duncan Cotterill, Russell McVeagh, and Hesketh Henry consistently identified this dual role as a source of confusion and dispute.

NZS 3910:2023 resolved it by splitting the role in two. The Contract Administrator handles administration. The Independent Certifier handles certification. Different functions. Different duties. Different accountability.

What the Contract Administrator Does

The Contract Administrator (CA) is the principal's representative for the day-to-day running of the contract. They act on behalf of the principal. There is no pretence of impartiality in this role. The CA is there to protect the principal's interests within the framework of the contract.

The CA's responsibilities include:

• Issuing instructions to the contractor — including directions on methodology, sequencing, and site access
• Managing correspondence — receiving and processing notices, claims, and submissions from the contractor
• Administering variations — receiving variation proposals, instructing variations, and managing the pricing process under Clause 9.8.3 (where the response to variation pricing must occur within 10 working days)
• Processing notices — including notices of potential claims under Clause 13.3.1 and extension of time applications under Clause 13.5
• Monitoring the contractor's programme — reviewing the programme submitted under Clause 9.2.1 (due within 10 working days of contract execution) and tracking progress against it
• Coordinating site activities — managing interfaces between the contractor, subcontractors, and the principal's other consultants
• Enforcing contractual obligations — including compliance with performance bond requirements under Clause 9.3

In short, the CA does what most people think of when they hear "contract administration." They run the contract. They represent the principal. And they are entitled to act in the principal's interests when doing so.

What the Independent Certifier Does

The Independent Certifier (IC) is responsible for decisions that require impartiality. Their duty is to the contract and to fair process, not to either party. This is the fundamental distinction from the CA role.

The IC's responsibilities include:

• Certifying practical completion — under Clause 11.3, the IC determines whether the works have reached practical completion and issues the certificate accordingly
• Issuing payment certificates — the IC certifies payment amounts based on the work completed, ensuring neither party is advantaged or disadvantaged
• Assessing defects — the IC determines whether defects exist and whether they have been remedied during the defects liability period
• Making determinations on disputed matters — where the contract requires an independent assessment (for example, on the value of a variation or the validity of a claim), the IC acts as the impartial decision-maker
• Certifying retention release — under Clause 12.4, the IC issues the certificate that triggers release of retention monies at practical completion and at the end of the defects liability period

The IC does not take instructions from the principal on how to certify. They do not adjust a payment certificate because the principal disagrees with the valuation. They do not withhold practical completion because the principal wants more leverage in a commercial negotiation. If the IC is seen to be acting on instruction rather than independently, their certifications are vulnerable to challenge.

The Same Person, Two Hats — How It Works in Practice

NZS 3910:2023 permits the same individual to hold both the CA and IC roles. On many projects. Particularly those in the $10M to $100M range where appointing two separate professionals is not commercially practical. This is exactly what happens. The PMC's contract administrator acts as both CA and IC.

This is not inherently problematic. But it requires discipline that most teams have not yet built.

When you are the CA and you issue an instruction to the contractor about a variation, you are acting on behalf of the principal. When you then assess the value of that variation and issue a payment certificate, you are acting as the IC. Same person. Same desk. Same day. Different function. Different obligation.

The practical requirement is documentation. Every decision should make clear which role the person is acting in. A payment certificate is an IC function. An instruction to the contractor is a CA function. A letter rejecting a claim notice as out of time is a CA function. Certifying practical completion is an IC function.

If a dispute arises and the contractor argues that a certification decision was compromised by the certifier's dual role, the first thing a tribunal or adjudicator will look at is whether the person distinguished between the two functions. If every letter is signed "Contract Administrator" regardless of whether it is an administrative or certification function, the argument that the IC was not truly independent becomes much harder to resist.

Common Mistakes Teams Are Making

The CA/IC split is now embedded in the standard form, but the industry is still transitioning. Based on what we are seeing across projects, these are the most common mistakes:

1. Treating both roles as one job with a new name

Some teams have simply replaced "Engineer to Contract" with "Contract Administrator" in their documentation and carried on as before. They are not separately identifying which decisions are IC functions and which are CA functions. This defeats the purpose of the split and creates exactly the vulnerability the 2023 revision was designed to eliminate.

2. Not documenting which role applies to each decision

Even teams that understand the distinction are not consistently documenting it. A payment certificate should state that it is issued by the Independent Certifier. A site instruction should state that it is issued by the Contract Administrator. Without this, the record is ambiguous. And ambiguity is where disputes grow.

3. Allowing the principal to influence IC decisions

This was the core problem under the 2013 edition and it has not disappeared. The principal may still expect that because they are paying the PMC, they should have input into certification decisions. The IC must resist this. Practical completion is either achieved or it is not. A payment certificate reflects the value of work done, not the principal's cash flow preferences.

4. Failing to update special conditions for the new roles

Many special conditions were drafted for the 2013 edition and refer to "the Engineer." If these have not been updated to specify whether an obligation falls to the CA or the IC, ambiguity is built into the contract from day one. This is a drafting issue that should be caught during contract review. But often is not.

5. Not tracking obligations separately for each role

The CA has deadlines. The IC has deadlines. They are not the same deadlines. A team tracking all obligations in a single register without distinguishing which role owns each obligation is setting itself up for a missed deadline. And the wrong person taking responsibility for it.

Practical Checklist: CA Decision or IC Decision?

The following table provides a practical reference for which decisions belong to which role. This is not exhaustive, but it covers the most common functions on a live NZS 3910:2023 project.

Function	Role	Reference
Issue site instructions to contractor	Contract Administrator	—
Review and accept contractor's programme	Contract Administrator	Clause 9.2.1
Instruct a variation	Contract Administrator	—
Respond to variation pricing	Contract Administrator	Clause 9.8.3
Receive and process a notice of claim	Contract Administrator	Clause 13.3.1
Assess and grant an extension of time	Contract Administrator	Clause 13.5
Monitor performance bond compliance	Contract Administrator	Clause 9.3
Certify practical completion	Independent Certifier	Clause 11.3
Issue payment certificates	Independent Certifier	—
Assess and certify defects	Independent Certifier	—
Certify retention release	Independent Certifier	Clause 12.4
Assess liquidated damages entitlement	Independent Certifier	Clause 10.3
Determine value of disputed variations	Independent Certifier	—

Why This Matters for Dispute Avoidance

The Arcadis Global Construction Disputes Report consistently identifies failure to properly administer the contract as the number one cause of construction disputes worldwide. The NZS 3910:2023 CA/IC split is a direct response to one specific failure mode: the blurred accountability of the Engineer to Contract role.

When a contractor believes the certifier is not acting independently, they do not trust the certifications. When they do not trust the certifications, they challenge them. When they challenge them, the project moves from administration to dispute. The cost of that transition, in time, legal fees, and damaged relationships, is almost always greater than the cost of getting the administration right in the first place.

The CA/IC split gives both parties a framework for clarity. But only if the team actually uses it. A split on paper that is not reflected in practice is worse than the old single-role model, because it creates an expectation of independence that is not being delivered.

What You Should Do Now

If you are administering an NZS 3910:2023 contract, or about to start one, here is a practical starting point:

1. Confirm who holds each role. Is the CA and IC the same person or different people? Is this clearly stated in the contract documents?
2. Review your special conditions. Do they still refer to "the Engineer"? If so, clarify which role each obligation falls to before the contract is executed.
3. Separate your obligation register. CA obligations and IC obligations should be tracked independently, even if one person holds both roles.
4. Document every decision with the role identified. Payment certificates: IC. Site instructions: CA. Claim assessments: check the function, not the form.
5. Brief the contractor. They need to know who holds each role and what to expect from each. Clarity at the start prevents arguments later.