Variation Register vs Change Order Log: What's the Difference?
If you have worked on construction projects in different countries — or even just read guidance from different markets — you will have noticed that the terminology around tracking project changes is far from consistent. Some teams use a "variation register." Others call it a "change order log." You might also hear "variation schedule," "change register," "modification log," or half a dozen other terms. Are these all the same thing, or are there meaningful differences?
This guide breaks down the terminology, explains the regional and contractual context behind each term, and helps you understand what you actually need — regardless of what you call it.
The Core Concept Is the Same
At their heart, a variation register and a change order log serve the same fundamental purpose: they are structured records of every change to the original scope of works on a construction project. They track what changed, who instructed it, what it costs, how it affects the programme, and what the current status is. The differences are largely about terminology, regional conventions, and the specific contract form being used — not about the underlying function.
Variation Register: UK, Middle East, and Commonwealth Markets
The term variation register is predominantly used in the UK, the Middle East (particularly UAE and Saudi Arabia), Australia, and other Commonwealth countries. It aligns with the contract language used in NEC, JCT, and FIDIC, all of which use the word "variation" to describe changes to the scope of works.
Under NEC contracts, changes are processed through the compensation event mechanism, but the register that tracks these events is still commonly called a variation register or CE register. Under JCT, the Architect issues variation instructions, and the QS maintains a variation register to track each instruction and its valuation. Under FIDIC, the Engineer instructs variations, and the register tracks both the instruction and the Contractor's entitlement assessment.
In these markets, the term "variation" carries specific contractual meaning. It is not just informal language — it maps directly to defined terms in the contract. This is why commercial teams in these regions tend to be precise about using "variation register" rather than alternative terms.
Change Order Log: North American Markets
In the United States and Canada, the equivalent document is typically called a change order log or change order register. This reflects the contract terminology used in standard American contracts such as AIA (American Institute of Architects) and ConsensusDocs, which use "change order" rather than "variation" to describe amendments to the contract scope.
The US system also introduces a preliminary step called a Proposed Change Order (PCO) or Change Order Request (COR). This is essentially a notification and pricing stage before the formal Change Order is approved. A well-structured change order log in the US will therefore track both PCOs/CORs and approved Change Orders, along with their associated costs and schedule impacts.
The function is identical to a variation register — only the labels differ. If you are a UK-trained QS working on a US project (or vice versa), the adjustment is purely terminological.
Other Terms You Might Encounter
| Term | Typical Usage | Notes |
|---|---|---|
| Variation Schedule | UK, Australia | Often used interchangeably with "variation register." Some teams use "schedule" when the document is structured as a summary table attached to valuations. |
| Change Register | International projects | A neutral term sometimes used on projects with multinational teams to avoid confusion between "variation" and "change order" terminology. |
| CE Register | NEC projects | Specifically refers to a register tracking NEC compensation events. The columns and workflow are tailored to the CE process. |
| Modification Log | Engineering / industrial projects | Sometimes used in oil and gas, power, and heavy engineering where "modification" is the preferred term for scope changes. |
| Variation Log | General | Informal shorthand for a variation register. Same thing, less formal name. |
Does the Terminology Actually Matter?
In practice, what matters is not the name but the content and the process. Whether you call it a variation register, a change order log, or a CE tracker, the critical thing is that your document captures all the information needed to manage changes commercially: what changed, when, who instructed it, what it costs, what the time impact is, and where it stands in the approval process.
That said, there are two situations where terminology does matter. First, when your contract defines specific terms. If your contract uses "variation," your correspondence and records should use the same language to maintain contractual alignment. Second, when working with international teams. If your project has a UK client, a US contractor, and a Middle Eastern subcontractor, agreeing on consistent terminology early avoids confusion throughout the project lifecycle.
What Should Your Register Actually Track?
Regardless of what you call it, your register should include a unique reference number for each change, a clear description, the date raised, who instructed or requested the change, the relevant contract clause, estimated and agreed cost impacts, time impacts in days, the current status (from notification through to agreement), and references to supporting documents such as drawings, RFIs, or formal instructions.
If you are working under NEC, you will also want to track notification deadlines, PM response dates, quotation submission dates, and whether deemed acceptance applies. If you are working in the US under AIA contracts, you will want to track the PCO/COR stage separately from the approved Change Order. The core structure is the same — the details adapt to your contract form.
Choosing the Right Tool
For small projects with a manageable number of changes, a well- structured spreadsheet can do the job. We offer a free variation register template that you can download and customise to your project.
For larger or more complex projects — particularly those with multiple packages, international teams, or deadline-driven contract forms like NEC — a dedicated tool saves significant time and reduces risk. ChangeLog is a purpose-built variation register for construction teams. It works for teams that call it a variation register, a change order log, or anything in between. The function is what matters, and ChangeLog is built around that function.
Summary
A variation register and a change order log are fundamentally the same document with different names. The term you use depends on your region, your contract form, and your team's conventions. What matters is not the label but the practice: that every change on your project is recorded, tracked, valued, and resolved through a structured process. Whether you are managing NEC compensation events in London, FIDIC variations in Dubai, or AIA change orders in New York, the principle is the same — and getting it right is one of the most important things your commercial team does.