What the Engineer to Contract Used to Do
Under NZS 3910:2013, the Engineer to Contract was the central figure in contract administration. One person, or one firm acting in that capacity, carried two distinct sets of responsibilities simultaneously.
On one hand, they acted as the principal's representative for day-to-day contract administration: issuing instructions, managing correspondence, processing notices, and coordinating the flow of information between the parties.
On the other hand, they were required to act independently and impartially when making certification decisions. Certifying practical completion, issuing payment certificates, assessing variations, and determining extensions of time.
This dual role worked in theory. In practice, it created a structural tension that the industry had been grappling with for years.
Why the Change Was Made
The core problem was independence. The Engineer to Contract was appointed by the principal, often paid by the principal, and responsible for representing the principal's interests in day-to-day administration. Then, when it came time to certify a payment or determine practical completion, that same person was expected to switch into an impartial role. Making decisions that could go against the principal who engaged them.
This was always a difficult line to walk. In disputed projects, contractors frequently challenged whether the Engineer's certification decisions were genuinely independent. The perceived conflict of interest undermined confidence in the process on both sides of the contract.
The 2023 revision directly addresses the conflict of interest inherent in one person both representing the principal and making impartial certification decisions. Multiple NZ law firms, including MinterEllison, Dentons, and Duncan Cotterill, have published guidance noting this as the most significant structural change in the revision.
The Standards New Zealand committee decided the cleanest solution was to separate the functions entirely. Two roles, two sets of obligations, two clear mandates.
The New Structure: Independent Certifier vs Contract Administrator
NZS 3910:2023 replaces the Engineer to Contract with two distinct roles. Each has its own scope, its own obligations, and its own relationship to the parties.
Independent Certifier
The Independent Certifier is responsible for certification decisions. The functions that require impartiality. This includes certifying practical completion, issuing payment certificates, assessing defects, and making determinations on matters where both parties are entitled to an unbiased assessment.
The critical point: the Independent Certifier must be independent and impartial. Their obligation is to the contract and to fair process. Not to either party. This independence requirement is now structurally reinforced by separating the role from the principal's day-to-day representative.
The Independent Certifier's duty of impartiality is no longer just a contractual expectation buried within a broader role. It is the defining characteristic of a standalone function. Projects need to consider how they appoint, instruct, and communicate with the Independent Certifier to preserve that independence.
Contract Administrator
The Contract Administrator takes on the day-to-day administration functions that were previously part of the Engineer to Contract role. This includes managing correspondence between the parties, issuing instructions, processing notices, coordinating site activities, and generally acting as the principal's representative in administering the contract.
Unlike the Independent Certifier, the Contract Administrator acts on behalf of the principal. There is no pretence of impartiality in their administrative functions. They represent the employer's interests in running the contract. This clarity is, in many ways, an improvement. Everyone now knows where they stand.
Old Structure vs New Structure
| Aspect | NZS 3910:2013 | NZS 3910:2023 |
|---|---|---|
| Key role | Engineer to Contract (single role) | Independent Certifier + Contract Administrator (two roles) |
| Certification decisions | Engineer to Contract | Independent Certifier |
| Day-to-day administration | Engineer to Contract | Contract Administrator |
| Independence obligation | Required for certification functions (within a dual role) | Structurally separated — Independent Certifier's sole mandate |
| Represents the principal | Yes (for administration); impartial (for certification) | Contract Administrator represents principal; Independent Certifier is impartial |
| Appointment | One appointment covers both functions | Separate appointments required for each role |
| Communication flow | Single point of contact for both parties | Separate channels depending on function |
Practical Implications for Projects
This is not a cosmetic change. The role split affects how projects are set up and how they operate day to day.
Appointments and Resourcing
Principals now need to appoint two separate roles rather than one. This raises practical questions: Can the same firm hold both appointments? How is the Independent Certifier's independence preserved if they are from the same organisation as the Contract Administrator? These are questions each project will need to address in its special conditions. Consult the updated standard and your legal advisors for the specific requirements.
Communication Flows
Under the old model, the Engineer to Contract was the single conduit for most contractual communication. Under the new structure, parties need to understand which communications go to the Contract Administrator and which go to the Independent Certifier. Sending a payment claim to the wrong person could create procedural problems.
Project teams accustomed to the old single-role structure will need to adjust their communication protocols. Every notice, instruction, and claim has a correct recipient under the new structure. Getting this wrong, particularly for time-sensitive obligations under the adjudication, and suspension rights in construction">Construction Contracts Act 2002, could have real consequences.
Payment Certification
Payment certificates are now the domain of the Independent Certifier, not the Contract Administrator. This means the person certifying payment is structurally separated from the person managing the principal's day-to-day commercial interests. In theory, this should increase confidence in the certification process. In practice, it requires clear protocols for how payment claims flow from the contractor, through any administrative processing, to the Independent Certifier for certification.
Practical Completion and Defects
Certification of practical completion, one of the most consequential decisions in any construction contract, now sits with the Independent Certifier. The Contract Administrator may still be coordinating inspections and managing the process, but the formal certification decision is made by someone whose only obligation is impartiality.
Dispute Resolution
The split may actually reduce disputes around certification decisions, because the person making those decisions has a clearer mandate for independence. However, it also introduces a new potential area of dispute: the boundary between administrative decisions and certification decisions. Where does the Contract Administrator's scope end and the Independent Certifier's begin? Expect special conditions to address this boundary in detail.
What This Means for AI Project Intelligence
From a systems perspective, the role split makes contract administration more complex, not less. Any platform tracking obligations under NZS 3910:2023 needs to understand which obligations fall to the Independent Certifier and which fall to the Contract Administrator. Deadlines, notice requirements, and response obligations now route to different people depending on the function.
A system built only on the 2013 edition, where everything flows through the Engineer to Contract, will not correctly map the obligation structure of a 2023 contract. The routing logic is fundamentally different.
Provan builds AI-powered operating systems for infrastructure and engineering businesses, covering six domains: Pipeline, Contracts, Projects, People, Finance, and Risk. The Contracts domain maps every obligation to the correct role under NZS 3910:2023, tracking CA and IC deadlines separately so nothing falls into the gap between the two functions. Built from 10 years managing projects from $10M to $750M.
Most of the published guidance on this change comes from law firm blog posts and static PDFs. That is useful for understanding the change. It does not help you operationalise it across a live project with dozens of concurrent obligations, overlapping deadlines, and two separate roles that both need the right information at the right time.
That operational layer, turning contractual knowledge into daily project intelligence, is what Provan is built for.
This article provides a practical project management perspective on the NZS 3910:2023 changes. It is not legal advice. For specific guidance on how the role split affects your project's contractual arrangements, consult the updated standard and your legal advisors.