Construction variation template and register

A construction variation template has two jobs most versions of it only do one of. The first is the request: what is changing, where it came from, and what it costs and delays. The second is the register — every variation raised on a contract, in one place, so the origin, the cost breakdown and the approval decision are still visible months later when a final account is being argued. A folder of individual emails is a folder; a variation register is the record a final account is actually built from.

It is written for the client side of a head contract: the developer, the client-side project manager or the superintendent who has to decide whether a change is a variation, what it is worth, and who wears it. A contractor’s own variation submission will arrive in its own format. This is the structure you assess it against, so that every variation on a job is recorded against the same fields rather than reconstructed from a different set of emails each time.

Origin is the field that decides the argument. A client direction, a contractor proposal, a consultant change and a latent condition are four different entitlement positions, and recording which one applies now saves reconstructing it from correspondence later. Background on how a variation is raised, priced and directed is in variations in construction, and on how an unapproved variation reaches a claim in variations, claims and margin.

The identification block — variation number, date raised, raised by — is the part that has to stay disciplined. Numbers must not be reused or skipped, a claim, an extension-of-time claim and a final account all refer back to this number, and the date raised is what a notice period in your contract is measured against.

The origin and description block is where the entitlement argument actually lives. Write the description in enough detail that someone who was not on site can price it, and record the origin as one of client direction, contractor proposal, consultant change, latent condition, statutory requirement or an RFI response — not as a general note.

The contract clause reference is which clause of your own executed contract the variation is directed and valued under. AS 4000-1997 and AS 2124-1992 each carry a variation clause and a latent-conditions clause, but the numbering is specific to the contract you signed — write your contract’s own clause number here rather than relying on memory.

The cost breakdown — labour, materials, subcontract, plant, overhead and margin — is what lets the total be assessed rather than just accepted or refused. In the demonstration row, $6,400.00 labour, $0.00 materials, $3,800.00 subcontract, $11,200.00 plant and $2,600.00 overhead and margin add to the $24,000.00 total cost effect.

Time impact and the approval chain are the last two blocks. Record the time impact in working days even when the answer is none, and note whether a separate extension-of-time claim has been lodged — in the demonstration row it is 4 working days, carried as EOT-03. Assessed by and approved by are different roles: on a superintended contract the superintendent assesses, and approval sits with whoever holds the delegation to approve at that value.

Raising it without a clause reference. A variation priced and argued with no reference to the contract it sits under is a negotiation, not an entitlement. Write your own contract’s clause number in at the time the variation is raised, while it is still easy to check.

Missing the notice period. Your contract sets its own notice period for raising a variation, and it is not the same period as any other contract’s. Read your executed contract to find yours, rather than assuming a figure that belongs to a different document.

A total with no breakdown behind it. Labour, materials, subcontract and plant, each on its own line, is what lets a total be checked against quotes and rates. A single lump figure can be accepted or refused, but it cannot really be assessed.

Leaving the time impact blank instead of writing zero. Zero is a valid answer and should be stated. A blank field is not a recorded position, and it leaves a later extension-of-time claim with nothing to be built on.

Confusing assessed by with approved by. Assessing the price and the time is one role; holding the delegation to approve at that value is another. If nobody in the chain has that delegation, the variation is not approved yet, whatever the status field says.