24 March 2026
Written by Sajid Fense, Founder
What is a contract variation register, and does a small business need one?
It is a single list of every departure from your standard terms that you have agreed to, and you need one as soon as you have agreed to two.
Standard terms stop being standard the first time somebody negotiates. That is not a failure: a customer worth having will sometimes ask for a change worth making. The failure is that the change is agreed in an email thread, applied to one document, and then forgotten by everyone including the person who agreed it.
A variation register is the list that stops that happening. It is one row per departure from standard, and it is maintained by whoever administers the document set rather than by whoever negotiated the deal.
What goes in it
Six columns is usually enough.
| Column | What it holds |
|---|---|
| Counterparty | Who you agreed it with |
| Document | Which document and which version |
| Clause | Where in the document the departure sits |
| Departure | What was agreed instead of standard, in one sentence |
| Approved by | The role that agreed it |
| Date | When it was agreed |
The column that gets left out and should not is clause. Without it, the register tells you that something was varied but not where, which means finding it still requires reading the whole document. With it, the register is usable in ten seconds.
The column people over-engineer is departure. One sentence, in plain words, describing what is different. Not the drafted wording: the register points at the document for that. The register exists to make things findable, not to reproduce them.
Why you need one sooner than you think
The threshold is two. Once you have agreed two departures, you have a set, and sets that are not written down get forgotten in a specific order: the oldest first, and the ones agreed by people who have since left.
Three things go wrong without one.
The same concession gets given twice without anyone deciding to. A customer asks for a longer payment period. Somebody agrees, reasonably. Eighteen months later a different customer asks and a different person agrees, also reasonably. Neither knows about the other, so nobody ever gets to ask whether this should just be standard.
Renewals get done on the wrong basis. A contract comes up for renewal and gets processed against current standard terms, quietly removing a variation the customer thought they had. That is a bad conversation to have and an avoidable one.
Nobody can answer how far you have drifted. The genuinely useful question (of our forty customers, how many are on standard terms) is unanswerable without a register, and it is the question that tells you whether your standard terms are actually standard or merely aspirational.
Who maintains it
Not the person who negotiated. This is the single most common design mistake.
The negotiator is the worst-placed person to maintain the register because their job ends when the deal closes, and the register entry is created at exactly the moment they have moved on to the next thing. Registers maintained by negotiators are complete for about four months.
It should be maintained by whoever administers the document set: the person who issues the document, files the executed copy, and would notice its absence. The register entry becomes part of closing the file, not part of doing the deal.
The practical mechanism: the executed document does not get filed until the register row exists. That coupling is what keeps it current, because filing is a step somebody actually wants to complete.
What a good one looks like after a year
A useful register is boring and mostly empty in one respect: most of your customers should not appear in it. If half your customer list has a row, you do not have standard terms with variations, you have bespoke terms with a template, and that is a different and more expensive way to run a business.
It should also show patterns. When four customers have all varied the same clause in a similar direction, that is the clause telling you something. Either your standard position is wrong for your market, or it is right and you are conceding it too easily. Both are worth knowing and neither is visible without the register.
The boundary
A variation register records what you agreed. It does not tell you what any variation does, whether it should have been agreed, or how it interacts with the rest of the document. Those questions go to your own external adviser.
What the register changes is the cost of asking. A question that begins "here are the eleven departures we have agreed across forty customers, grouped by clause" is bounded and answerable. The same question without the register starts with somebody reading forty contracts.