Capture a potential variation before its value is agreed

Record the date, location, work package, observed condition or instruction, person reporting it and the available source evidence. If the instruction was verbal, say so and record who was present. Seek confirmation through the applicable project communication process.

Describe the difference from the current scope or information. Link the relevant drawing, specification, quantity or instruction revision. The comparison should show what the project understood before the event and what is now proposed or being requested.

Avoid wording that settles responsibility before review. “Cable route changed following a site discussion” is a factual starting point if supported. “Client-approved payable variation” is a conclusion requiring authority and contractual evidence. The register should distinguish the two.

The commercial owner assesses whether the event falls within existing obligations, constitutes a potential change or requires another treatment. They also review notice requirements, communication channels and the authority of the person issuing the instruction.

The works manual provides public-works contract administration context. Project-specific notice and variation requirements must be taken from the executed contract and reviewed by the authorised commercial or legal owner.

Do not wait for a final estimate before checking time-sensitive obligations. An early record can preserve the event while quantities and costs are still developing. Conversely, issuing a notice does not establish acceptance of entitlement, valuation or time consequences. Keep those statuses separate.

Consider a synthetic route initially shown as 100 metres. A site instruction proposes a 125-metre route around an obstruction. The initial quantity difference is 25 metres, subject to measurement and scope review. It is not yet an agreed payable quantity.

Record additional supports, terminations, testing or other effects only where the actual scope requires them. Do not assume that every extra metre creates the same proportional cost or delay. The changed route may also omit work elsewhere, and those reductions belong in the assessment.

An estimate helps the project decide how to proceed. Actual cost records what the organisation incurred under its accounting and cost-control rules. Proposed value is the amount submitted under the contract's valuation basis. These figures may differ legitimately.

Keep quantity assumptions, rates, resource records and supporting quotations linked to the appropriate figure. Label provisional amounts and record revisions. A site estimate should not become an agreed client value merely because it is copied into a change-order field.

For work proceeding before agreement, define the authorised recording method. Daily labour, equipment, material and measurement evidence may be needed, depending on the contract and circumstances. Obtain required acknowledgements through the prescribed process while recognising that an acknowledgement may confirm a record without agreeing liability or price.

The project may need to act urgently to maintain progress or address a condition. Preserve the actual authority for that action and its limits. A potential-variation entry is an administrative record, not permission to execute changed work.

If authority is unclear, escalate the decision promptly through the project process. Engineering, site management and commercial teams may need to resolve different parts of the issue. The register should show the pending decision and the consequence of waiting, rather than leaving the crew to interpret an ambiguous email.

Link related RFIs, drawings and instructions. An RFI response may supply technical information while commercial treatment remains under review. Keeping the records connected prevents the information issue from disappearing when the RFI closes.

A client may accept the changed scope while disputing rates, or agree part of the quantity while rejecting another part. Track those components separately. A single “approved” status can overstate the commercial position.

Retain submitted versions, responses, meeting records and agreed adjustments. Show the current position and its basis, including any reservations. Where a potential variation is rejected, preserve actual costs already incurred and the decision on future work; rejection should not erase the operating history.

For multiple related events, decide whether they should remain separate or be grouped for submission. Preserve their individual identities either way so quantities and costs are not counted twice across claims or change orders.

Review open potential variations with site, planning and commercial owners while work is ongoing. Prioritise missing instruction evidence, unmeasured quantities and resource records that will be difficult to reconstruct later.

Test the register with a verbal instruction, a partially agreed change and a rejected submission with incurred costs. The records should preserve facts, show the unresolved decision and maintain links to cost reporting. An “open variations” total should explain whether it represents estimates, submitted values or another defined measure.

Measure evidence completeness and age of unresolved reviews alongside submitted value. A large pipeline of poorly evidenced changes is not necessarily a commercial asset. The quality of the underlying record determines how useful it will be in negotiation and review.

Early capture gives the project choices: clarify, notify, estimate, seek authority and record the work properly. Waiting for agreement can remove those choices.

1. Record the event and the prior scope basis promptly.
2. Obtain commercial review of authority, notices and contractual treatment.
3. Preserve quantity, resource and programme evidence as work develops.
4. Keep estimates, actual costs and proposed values distinct.
5. Track partial agreements and unresolved components without losing the original event history.