Variation Order Control in Construction: How a QS Tracks Change

Variation order control in construction should not start and end with a contractor quotation. A quotation may be part of the record, but controlled change needs a clear instruction, defined scope, evidence, valuation, approval status, forecast impact, and final-account close-out.

That control matters because variations can move cost, time, procurement, design coordination, and cash flow at the same time. If the record is loose, the owner may approve work without knowing the full exposure, reject a legitimate change because the evidence is incomplete, or carry unresolved items until the final account becomes a negotiation instead of a reconciliation.

The exact entitlement, notice period, valuation method, and approval authority always depend on the executed contract and applicable law. The workflow below is a practical quantity surveying control sequence, not a substitute for reading the project contract.

What creates a variation?

A variation is a post-contract change to the work or obligations that is recognised under the contract. It may arise from a formal instruction, a design revision, a site condition, a specification change, an omission, an acceleration request, or a coordination decision that changes what the contractor must provide.

The first control step is to separate a real variation from ordinary delivery movement. A contractor spending more labour than expected is not automatically a variation. A late drawing may create a change, delay, or disruption issue, but the correct route depends on the contract. A revised drawing may also include both changed and unchanged work, so the variation record should identify the precise difference from the agreed baseline.

RICS guidance on change control and management explains that contracts usually define what constitutes change, the control mechanism, and who is authorised to make it. The first QS check is therefore the executed contract, not the quotation total.

Start with instruction and notice

Every change should be logged from the moment it appears. The record should state who raised it, what document or site event triggered it, whether a formal instruction exists, whether notice is required, and what deadline applies. If the contract requires written instruction before work proceeds, the team should not rely on a meeting comment or informal message as though it carries the same authority.

Notice is not just paperwork. It protects time bars, creates a dated record, and forces the team to clarify whether the item is being treated as a cost change, time issue, design clarification, or rejected request. The QS should keep the commercial log aligned with the contract administrator, project manager, engineer, or employer’s representative responsible for issuing instructions.

When urgent site decisions are needed, the record still needs to catch up. The variation register should show the temporary instruction, the person who authorised it, the affected scope, the evidence collected, and the action required to regularise the item.

Define scope before pricing the change

A controlled variation starts with scope definition. The QS should compare the original contract documents with the revised instruction, drawing, specification, request for information, site record, or agreed clarification. The purpose is to define what changed and what did not change.

The scope record should identify location, drawing reference, affected trade, original requirement, revised requirement, reason for change, and any assumptions used for measurement. Where information is incomplete, the register should show the missing information and a provisional value rather than presenting the number as final.

This is where many variation disputes begin. If the team prices a broad narrative such as “additional mechanical works” without separating labour, material, plant, preliminaries, design, testing, temporary works, abortive work, and omissions, the owner cannot see whether the quotation is reasonable. A clean scope definition makes the valuation review possible.

Collect evidence while the work is still visible

Evidence should be captured before work is covered, removed, or absorbed into the next activity. Useful records include dated photographs, marked drawings, site instructions, inspection records, delivery notes, labour and plant records, subcontractor quotations, measurement sheets, correspondence, and programme references.

The evidence should answer four questions:

• What changed from the agreed baseline?
• Who instructed or accepted the change route?
• How much work, material, time, or resource was affected?
• What basis supports the proposed rate, price, or adjustment?

For owner-side control, the QS should not treat evidence as something collected only after disagreement. It is part of routine project control. A dated site photo, measured sketch, and instruction reference can prevent weeks of later reconstruction.

Measure quantities and test rates

Variation valuation normally follows the contract’s valuation rules. The contract may require existing bill rates where work is similar, adjusted rates where conditions differ, fair valuation where no applicable rate exists, daywork for properly recorded work, or another defined mechanism. The QS should follow that hierarchy and record why the chosen basis was used.

The RICS practice information on valuing change shows why the contract form matters. Some contracts use rates for identical or similar work, some permit adjusted or new rates when quantity or conditions differ, and others use a defined-cost mechanism. Measurement discipline helps the team avoid duplicated quantities, missing omissions, and unsupported lump sums.

The QS should also check whether the variation includes both additions and omissions. If omitted work remains in the original contract value and the added work is priced separately, the owner may pay twice. A proper variation assessment shows the net position.

Use the variation register as the control centre

The variation register should not be a storage list. It should be the live commercial control record. Each item needs a unique reference, title, source instruction, date raised, scope summary, status, submitted value, assessed value, approved value, forecast value, owner decision, and next action.

Status matters. A submitted quotation is not the same as an assessed variation. An assessed exposure is not the same as an approved budget movement. A pending instruction may need to appear in the forecast even before final agreement. The register should keep these categories separate so the monthly cost report does not confuse agreed cost with likely exposure.

Good change order cost control depends on keeping those distinctions visible.

This is why variation control links directly with post-contract quantity surveying. The QS is not only checking arithmetic; the QS is keeping the instruction, valuation, approval, forecast, and final account records aligned.

Reflect the forecast before final approval

Owners often wait for final agreement before recognising variation exposure. That can make the project look healthier than it is. A better report separates approved variations, assessed pending variations, submitted claims, and potential future changes, then explains how each category is treated in the forecast final cost.

The RICS Cost Reporting guidance distinguishes agreed contract instructions from anticipated instructions or early warnings. Both can affect the outturn forecast, but pending items should remain clearly identified as not yet instructed or agreed.

If a change affects programme, procurement, or sequencing, the QS should coordinate with the project planner and contract administrator. Direct work cost may be only one part of the exposure. Prolongation, acceleration, disruption, temporary works, rework, and delayed procurement can be larger than the measured quantity itself.

Close the loop in the final account

The RICS guidance on final account procedures treats preparation as work carried out throughout the contract period. A variation is not controlled until it is closed in that account. Each item should end with a clear final status: agreed, withdrawn, rejected, superseded, included elsewhere, or still disputed. The final account should reconcile approved variations against the contract sum, payment certificates, outstanding claims, retention, and any unresolved deductions.

The close-out record should preserve the instruction, scope basis, measurement, rate support, agreement trail, and final value. If the team cannot explain why a variation moved from submitted value to approved value, the final account becomes harder to defend.

Common variation-control failures

• Work starts from informal direction without a written instruction or status record.
• The quotation includes broad lump sums with no measurable scope breakdown.
• Omissions are not deducted when replacement work is added.
• Daywork sheets are signed without checking entitlement or scope.
• Pending variations are excluded from the forecast until final agreement.
• The register mixes submitted, assessed, approved, and rejected values.
• Programme effect is claimed without a separate time-impact record.
• Final-account files do not contain the instruction and valuation evidence.

None of these failures is solved by a better spreadsheet alone. The register only works when the project team follows the approval route and records the evidence as the work happens.

Owner checklist before approving a variation

• Is there a valid instruction or contract basis for the change?
• Does the scope record show the original and revised requirement?
• Are quantities measured and traceable to drawings, site records, or agreed assumptions?
• Does the rate or price follow the contract valuation hierarchy?
• Are omissions, abortive work, preliminaries, taxes, and exclusions shown clearly?
• Has the programme or cash-flow impact been checked where relevant?
• Is the variation status reflected correctly in the forecast final cost?
• Will the final-account file contain enough evidence to close the item later?

Frequently asked questions

Is a contractor quotation enough to approve a variation?

No. A quotation is only one input. The owner should also see the instruction, scope definition, evidence, measurement, rate basis, exclusions, status, and forecast impact before relying on the number.

Can a variation be included in the forecast before it is agreed?

Yes, if it is a credible exposure. The forecast can show pending or assessed values separately from approved budget changes. That distinction helps the owner understand likely cost without pretending the item is already agreed.

Who decides whether a change is valid?

The contract defines the authority and process. The QS can assess cost and evidence, but entitlement, instruction authority, notices, certification, and dispute steps must follow the executed contract and project governance.

Set up the register before the next change arrives

Construction change management is strongest when the process is already in place before a difficult variation appears. The owner needs a live register, disciplined evidence capture, contract-led valuation, and a forecast that shows unresolved exposure early.

Ask GEMS to set up or audit your variation register and approval workflow. Explore our quantity surveying and contract-management services for clearer owner-side change control.