Construction Variation Register Template

Track every variation from notice to approval and payment — protect your margin and keep a clean contractual record.

Untracked variations are lost margin. This register gives contracts administrators and project managers one place to log every variation, its status, value and supporting references, so nothing slips and claims are substantiated.

What's inside

Variation number, description and date raised
Cause/origin and supporting references (RFI, instruction, drawing)
Claimed value, approved value and variance
Status (notified / submitted / approved / rejected / paid)
Time impact (days) to link variations to EOT claims

Columns

VO No.	Date Raised	Description	Origin / Cause	Supporting Ref	Claimed ($)	Approved ($)	Time Impact (days)	Status	Date Approved
VO-001	2026-06-10	Additional waterproofing to plant room	Client instruction CI-07	RFI-031, Dwg A-204 RevC	8400	8400	0	Approved	2026-06-18
VO-002	2026-06-14	Rock excavation - latent condition	Latent condition	Geo report, Site photos	23500	0	5	Submitted

How to use it

Raise the notice within the time bar in your contract — late notice is the most common reason variations are rejected.
Attach the supporting evidence at the moment you log it, not weeks later.
Record the time impact even when it's zero — it's how you build an EOT case if the variations stack up.

Frequently asked

What should a construction variation register include?

Each variation's number, date raised, description, cause, supporting references, claimed and approved value, time impact and current status. Keeping value and time impact together lets you see both the commercial and programme exposure at a glance.

Why are variation claims rejected?

Most often because notice was given outside the contractual time bar, or the claim lacks evidence linking the work to an instruction, latent condition or change. Logging the supporting reference when you raise the variation prevents both.

From template to system

This template captures the data by hand. Alloovium reads it straight from your project documents, keeps it current, and checks it against your compliance gate automatically.

See how it works