The Contract Register Everyone Owns and Nobody Reads
Every business I go into has something they call a contract register. It’s usually a spreadsheet. Sometimes it’s a page in a legal folder. Occasionally it’s a proper module in a piece of software that somebody remembered to buy but nobody has kept updated.
If I ask who owns it, the answer depends on who I ask. Finance say procurement. Procurement say legal. Legal say it should really be finance. Nobody is actively unhappy with the arrangement, because for most of the time it doesn’t matter. It only matters when a supplier is about to auto-renew for another three years, or when a compliance question comes up, or when the FD wants to know exactly how much notice we have to give on a contract everyone thought was up in eighteen months and is actually up in six.
At that point, the register is opened, and it turns out to have half the contracts in it, some of the terms wrong, three suppliers who left in 2022 and one who’s been on last year’s rates for the past two.
The register that isn’t really a register
The problem with most contract registers isn’t that businesses don’t have one. It’s that the one they have was built as a filing exercise rather than a governance one. It records that a contract exists, gives it a name, sometimes attaches a PDF. What it doesn’t do is answer any of the questions the business will actually need to answer at some point.
What’s the notice period, and when does the notice window open. Which of these auto-renew, and at what price. Which contain price escalation clauses, and how are those calculated. Which have exit costs, and how much are they. What’s the actual annual value based on the last twelve months of invoices, rather than the assumed spend from when the contract was signed. Who inside the business is meant to be managing the supplier, and does that person still work here.
A contract register that doesn’t answer those questions is doing something, but it isn’t governance. It’s an inventory of paperwork.
Ownership is where most of it falls over
The other thing that tends to kill a contract register is the ownership question. If nobody clearly owns the register, everybody assumes somebody else is keeping it current. If everybody owns the register, the same thing happens with different vocabulary.
In practice, contract registers that stay useful tend to have a single owner with a specific responsibility. That’s usually procurement, or somebody in procurement, and it is usually somebody senior enough to have a view across categories rather than a junior buyer trying to keep the file tidy alongside their day job.
That person doesn’t have to do all the work themselves. Category owners still keep their own contracts current. Legal still flags terms that need attention. Finance still reconciles spend. But there is a single point of accountability for the register being current, complete and accurate, and a routine for making sure it stays that way.
Once that is in place, the register starts to do the thing it is supposed to do. Somebody spots the auto-renewal window three months in advance rather than three weeks after. The FD asks about exposure to a supplier and gets an answer that afternoon. Legal knows which contracts need updating when the GDPR requirements shift or a new sanctions regime lands. Procurement can see the value at risk if a supplier fails. That is procurement governance working. It is not exciting, but it prevents the kind of surprise that keeps FDs awake.
What good looks like when it’s built properly
There is no single template for a contract register that works. It depends on the size of the business, the number of contracts, the sectors involved and how much of the spend is regulated. The ones that do their job tend to have a few things in common.
They are live. Updates land within days of a contract being signed, not months. There is a workflow that catches new contracts and makes sure they are logged with the right metadata, not just filed.
They are cross-referenced. You can look at a supplier and see every contract in place with them. You can look at a category and see the contract landscape across it. You can look at a spend threshold and see everything above or below it. The register doesn’t just record contracts one at a time.
They connect to something. In good setups, the contract register talks to the spend data, to the supplier risk data, and to the calendar. So renewal dates end up in an actual diary, not just a column in a spreadsheet, and value at risk is calculated using the real spend rather than the contract headline.
And the registered data is trusted. That last one is harder than it sounds. The register is only useful if the people using it believe what it says. Once it has been out of date for a year, or contains contracts that don’t reflect what’s actually been signed, people stop referring to it and start asking questions the long way round. Rebuilding that trust takes months and usually means going back through the whole register from scratch.
Worth the effort for who
Contract registers that get built and maintained properly are worth the effort in almost any business with more than a handful of suppliers of any material scale. The cost of not having one shows up in auto-renewals nobody wanted, exits that turn out to cost more than expected, and the FD finding out about supplier exposure after something has already gone wrong.
For businesses with a smaller supplier base or a lower risk profile, a lighter-touch approach works fine. Even so, having a single spreadsheet that somebody genuinely maintains, with the notice periods, values and renewal dates in it, will save the average business more than it costs several times over.
If your business has a register that hasn’t been trusted for a while, the honest answer is usually to start again. Rebuilding it properly, once, is quicker than trying to patch what’s there. It is also a decent way to work out how much supplier due diligence is really being done on the arrangements that matter most.
Happy to talk it through if you are thinking about that route.