NZS 3910 describes the Engineer’s duties in a few clauses. What it does not describe is the rhythm of the work: what has to happen before the contractor is on site, what happens every week, what the month-end looks like and how the job closes. This is ours.
Before site possession
The compliance pack. Bonds, insurances, the site-specific safety plan, the traffic management plan, the environmental and erosion controls, the quality plan and the inspection and test plans. We verify every one before access to site is granted. Non-compliance stops possession. It is the one moment in a contract when the Principal holds all the cards, and it is wasted more often than you would think.
The registers, empty. Instructions, notices, RFIs, variations, extensions of time, payment claims, defects. They are set up on day one so that nothing is ever reconstructed later.
The authority letter. What the Engineer’s Representative may decide on site, in writing, so the contractor knows who to ask.
Every week
Site. A visit at the frequency the monitoring level demands: CM3 or CM4 under the Engineering New Zealand guidelines, agreed with the designer. We do not supplant the contractor’s quality assurance; we verify it, and the observations are logged with photographs and, where it helps, drone records.
Instructions. A verbal instruction on site is confirmed in writing within 24 hours. An unconfirmed instruction is a variation claim waiting to happen.
RFIs. Routine clarifications are answered within five working days. If the answer needs the designer, the designer is chased, not the contractor.
Minutes. Out within two working days, with actions, owners and due dates.
Every month
The payment claim. Assessed against the schedule of prices and the work actually done, and the payment schedule issued inside the Construction Contracts Act timeframe, with reasons for any difference. This is the one document in the contract that is tested every single month, so it is the one where sloppy habits show first.
Variations and time. Every variation, proposed, agreed, directed or rejected, is tracked with its running effect on the contract price and the completion date. Slippage triggers a programme recovery discussion before it becomes an extension of time claim. The client sees the trajectory at all times; there are no end-of-job surprises.
Health and safety. A monthly audit of the contractor’s practices on the client’s own template.
The report. Written to be decision-useful: what has been spent, what it will cost to complete, what has moved, what needs a decision and by when.
When something goes wrong
A qualified engineer on site within 4 to 48 hours for storm damage, a delay event or a safety incident. Decisions in writing, with reasons. Liquidated damages applied consistently with the contract and only after proper process; never as leverage.
At the end
Practical completion certified when it is reached, not when it is convenient. The completion records, as-builts, operation and maintenance manuals, producer statements and warranties, audited for completeness before they go to the asset team. Then the defects period, run from the register that was set up on day one.
None of this is clever. It is a discipline, kept every week for the life of the contract, which is why it is worth asking who, exactly, will be doing it.