Διαχείριση μιας variation βάσει NZS 3910

Record which form the job is built on and which edition of it: NZS 3910 for a build to the Principal's design, NZS 3916 where the Contractor also designs, NZS 3917 for a term contract. Then name the people. On the 2023 edition of NZS 3910 that is a Contract Administrator and an Independent Certifier; on the 2013 edition it is a single Engineer to the Contract. Record the special conditions that change either, because they usually do.

Γιατί: Every step below depends on this answer and none of them announce it. A notice addressed to the Engineer on a contract that has no Engineer, or a valuation determined by the person acting for the Principal when the contract reserves that to the Independent Certifier, is defective on its face, and it is defective in a way that is only noticed once somebody has a reason to look.

Build the approval route the contract and the Principal's own delegations actually create: who may issue a variation instruction, what value the Contract Administrator may instruct without going back to the Principal, and which decisions the Independent Certifier makes rather than either of them. Put site staff and the Contractor's representative on the same route so nobody is guessing.

Γιατί: Work carried out on the word of somebody with no authority to instruct it is work the Contractor has done at its own risk, and the argument that follows is never about whether the work was needed. It is always about who said so. Naming the route in advance costs an afternoon and settles a class of dispute that otherwise arrives at the final account.

Raise the variation as an instruction that describes the change in the works, references the drawing or the specification clause it comes from, and states whether the Contractor is to proceed or to price first. Where the Contractor believes it has already been given an instruction in substance, record that as a claim for a variation rather than waiting for a document that may never come.

Γιατί: A variation is a change the contract allows the Principal to make, and the mechanism is the instruction. Work built first and documented afterwards leaves the Contractor arguing that a conversation was an instruction, which is a much weaker case than a piece of paper, and it leaves the Principal paying for work whose scope nobody wrote down while it was still describable.

Work down the contract's order of preference rather than starting at the end of it. Use the contract rates where the varied work is of similar character and carried out under similar conditions. Where it is similar but the conditions differ, derive a rate from the contract rate and say what you adjusted. Only where neither holds do you build a reasonable price from cost with the margins the contract allows, and then the build-up is part of the valuation rather than backup for it.

Γιατί: The order of preference exists so that neither side gets to re-price the job through the variation account. A Contractor that goes straight to cost plus on work the schedule already prices is asking for a better rate than it tendered; a Principal that forces a contract rate onto work being done in genuinely different conditions is taking a discount it never negotiated. Stating which step of the order was used is what makes the valuation reviewable.

Log the date the circumstances arose, give the notice the contract requires within the working days it allows, and attach the records that support it as they are made: the labour and plant on the work, the photographs, the diary entries, the correspondence that shows when each side knew. Keep time and cost as separate claims where the contract treats them separately.

Γιατί: NZS 3910 is a notice-driven contract. An entitlement that is real on the merits can still fail because it was raised outside the period, and the 2023 edition leans harder on early warning, so silence while a problem develops is itself a position. Records assembled at the end of a job describe what somebody remembers; records kept in the week the work happened describe what happened.

Put the varied work into the programme and read what it does to the critical path, then claim or determine the extension of time on that basis. Where the variation absorbs float rather than moving the completion date, record that too, because the next event will land on a job with less room than the programme shows.

Γιατί: Cost and time are separate entitlements under this form and they are lost separately. A Contractor paid for a variation and never granted the days it took is a Contractor heading into liquidated damages for a delay the Principal instructed. Reading the effect while the programme is still current is the difference between a demonstrated extension and an argument about what would have happened.

Publish the register: every variation with its instruction, its status, the amount claimed, the amount determined and the days granted, rolled up to a forecast final contract sum. Show the ones still unpriced as well as the settled ones, with a figure against them rather than a blank.

Γιατί: The final account argument on this form is almost never about a single variation. It is about forty of them that two organisations were tracking in two spreadsheets that never agreed, and about the ten nobody priced because they were still open. One register that both sides read each month turns the final account into an arithmetic exercise instead of a negotiation.