THE VARIATION REGISTER
Maintaining a Live Register and Managing the Open-to-Agreed Pipeline

Introduction
The variation register is one of the most practical commercial documents on any construction project. It is not a form; it is a live management tool. When maintained correctly, it provides a real-time picture of the financial exposure arising from instructed changes: how many variations have been instructed, what quantum has been submitted, what has been agreed, and what remains in dispute or under assessment. When it is neglected populated only at month-end, missing key instructions, or lacking status clarity it becomes a liability at final account.
On fast-track projects in Saudi Arabia mall renovations with live trading, hospital fit-outs to accelerated programmes, or Design & Build high-rise towers where the contractor’s design evolves monthly the volume of variations can be substantial. On a complex fit-out contract, it is not uncommon to have 100 or more open variation items at any stage of the project. Without a disciplined register, the commercial team loses track of instructions, misses submission deadlines, and enters the final account negotiation without a clear picture of its own position.
The variation register is the single source of truth for the project’s commercial position on changes. Both the employer’s QS and the contractor’s QS should maintain one and reconciling the two registers is one of the most productive activities in any commercial meeting.
WHAT YOU WILL LEARN
- What a variation register must contain to be genuinely useful as a commercial management tool
- The distinction between open, submitted, assessed, and agreed variations and why it matters
- How to manage the pipeline from instruction to agreement efficiently
- Common failures in variation register discipline that cost contractors money at final account
- How the register feeds into the CVR and interim payment applications under FIDIC
What the Register Must Contain
A variation register is only as useful as its data. Each row must capture enough information to manage the variation through its full lifecycle from instruction to agreement. Minimum fields for an effective register:
- Variation reference number and description of instruction
- Date of instruction and source document reference (site instruction, RFI response, engineer’s letter)
- Instructed by (engineer, employer, architect) and basis of instruction
- Scope category: additional works, omission, substitution, or employer risk event
- Contractor’s submitted amount and date of submission
- Engineer’s or employer’s assessed amount and date of assessment
- Agreed amount and date of formal agreement
- Status: Instruction Received / Submission Pending / Submitted / Under Assessment / Agreed / Disputed
- Time impact: EOT sought, EOT agreed, programme reference
- Comments and reference to any dispute or formal reservation of rights
➤ A register with submission amounts but no agreed amounts is not a commercial tool — it is a wish list.

Open vs Agreed: The Pipeline Management Discipline
The distinction between open and agreed variations is where commercial management adds or destroys value. An “open” variation is one that has been instructed but where the cost has not yet been formally agreed. An “agreed” variation is one where both parties have formally confirmed the cost — in writing, typically through a signed variation order or an agreed commercial minute.
The open-to-agreed pipeline must be actively managed:
- Open variations over 60 days without submission should trigger an internal review — is the data available? Are there notice issues to resolve?
- Submitted variations over 90 days without engineer response should trigger formal follow-up — under FIDIC Clause 3.5, the engineer must determine within a reasonable time
- Variations where the contractor’s submission and the engineer’s assessment diverge by more than 15% represent a commercial risk requiring escalation
- Variations related to programme-critical events should be agreed before the programme moves on — not deferred to final account
On Saudi Arabia projects, final account negotiation is often the first time employer and contractor reconcile their variation registers — and the gap can be significant. The contractor who has maintained a live, disciplined register is in a far stronger commercial position.

Common Register Failures
The most common variation register failures observed on contracts in the Middle East:
- Instructions captured informally (by email or verbal) not logged until weeks later
- Submissions prepared in isolation without reference to the register — creating numbering gaps and duplications
- Status not updated after engineer’s responses so the register still shows “Submitted” for items assessed three months ago
- No link between the variation register and the interim payment application — so agreed variations are not claimed in the next IPC
- Time impact column left blank until EOT submission by which time the programme data has been lost
➤ The variation register is not a filing system for old instructions. It is a live commercial control document that must reflect the project’s actual position at any point in time.
PRACTICAL QS APPROACH
The experienced QS updates the register weekly, not monthly. Every site instruction is logged within 24 hours of receipt. Submissions are tracked by internal deadline. Agreement is not assumed it must be documented in writing.
The register is shared with the client’s QS at each commercial meeting with an explicit request to reconcile status. Any discrepancy in instructed scope, submitted amounts, or agreement status is resolved before the commercial meeting closes.
- Log all instructions within 24 hours — assign a register number and status immediately
- Set internal submission deadlines — 21 days for standard variations, 7 days for programme-critical items
- Review the open pipeline weekly and escalate items exceeding target duration
- Reconcile with the engineer’s records at every monthly commercial meeting
- Feed all agreed variations directly into the next interim payment application without delay
FINAL THOUGHT
The variation register is proof that the commercial team is managing the project not just recording it. A disciplined register accelerates agreement, reduces final account disputes, and ensures that nothing the contractor has earned is left unclaimed.
Because in reality:
- An instruction without a register entry does not exist commercially it will not appear in the final account
- The gap between a contractor’s open register and its agreed register is the gap between its potential final account and its actual recovery
