Why Your Contract Obligations Spreadsheet Stops Working at 40 Contracts
Your contract obligations spreadsheet does not stop working because you crossed 40 contracts. It stops working for four specific reasons, and all four of them are about people rather than volume.
I should say up front that I am not here to tell you spreadsheets are bad. I have built plenty of them, and a couple were rather good. The problem is not the tool. The problem is that a spreadsheet is a passive object, and passive objects lose to active work every single time.
Here is the short version, so you do not have to read 1,400 words to get it.
A contract obligations spreadsheet works beautifully while one person maintains it, that person gets something out of maintaining it, and the consequences of ignoring it for a month are survivable. Break any one of those three conditions and the register starts to rot, whether you have 12 contracts or 200.
Forty is simply where most people notice.
Every obligations register is immaculate in month one
You know the one. Colour coded. Owners assigned. Dates in the right format. Somebody has used conditional formatting and is quietly rather proud of it.
Now ask to see the same register in month seven.
The tab is still there. The dates are historic. Three of the named owners have left the business. Nobody has touched column G since March, and there is a row near the bottom that just says "TBC with Dave".
I am not being unkind about anyone. I have built that spreadsheet. More than once, and with the conditional formatting.
What is going on there is not laziness and it is not a failure of discipline. It is a structural property of the instrument, and if you understand which of the four thresholds you have crossed, you can usually buy yourself another year without spending anything.
The four thresholds that actually break a contract obligations spreadsheet
One: more than one person has to update it
This is the big one, and it arrives far earlier than 40 contracts.
The register lives with you. The truth lives with delivery, engineering, finance and whoever is running the depot. So maintaining it requires you to extract status from people who did not build it, do not use it, and get precisely nothing from updating it.
That works for a while, on goodwill.
Goodwill has a half-life of about a quarter.
The CCM Institute's 2025 benchmark work puts clarity of responsibilities as one of the two most severe capability gaps in the discipline, scoring 3.0. That is not a filing problem. It is the same problem showing up on a survey.
Two: one list has to serve several different cycles
A register sorted by clause reference is a table of contents. Useful for lookup, useless for management, because managing is a time-based activity and clause 14.3 has no opinion about what you should do this week.
When your monthly review has to wade through the annual insurance certificates to reach the six items that actually need attention, people stop reading it. Not because they are difficult, but because you have wasted their time twice in a row and they have adjusted.
Fixing this does not need software. It needs the register sorted by how often each item needs attention rather than by where it sits in the document, which I have written out properly in the guide to tracking contract obligations.
Three: nothing happens if everyone ignores it
A spreadsheet does not chase. It does not ring anyone. It sits there, exactly as accurate as whoever last touched it, and no more current than that.
Which means the whole system depends on your memory, and your memory is competing with 40 other agreements and an inbox that has opinions.
A register you have to remember to check has not solved the problem. It has moved the problem into your head and made it look tidy.
Four: it can no longer prove anything
This is the threshold nobody sees coming.
Ask yourself what you would hand over if a regulator, an auditor or the other side's solicitor asked tomorrow for your last two years of contract oversight. If the honest answer is "an inbox and a spreadsheet that has been overwritten 300 times", you have already crossed it.
A spreadsheet has no version history worth the name, no audit trail, and no way of demonstrating that an obligation was raised in March rather than reconstructed in November. That is fine right up until the afternoon it is the only thing that matters.
Worth flagging the asymmetry here. Sell side usually feels this first, because you are the one being asked to evidence performance, often at short notice, often by someone building a case. Buy side tends to discover it later and more expensively, because nobody audits the buyer until the buyer tries to enforce something and cannot show a consistent history of raising it.
So where does 40 come from?
It is arithmetic rather than a rule.
A properly triaged agreement has somewhere between 20 and 40 actively managed obligations. Not the 300 lines that come out of a control-F sweep, the ones that genuinely need a human being. Multiply that by 40 contracts and you are holding something in the order of a thousand live items across perhaps a dozen owners in four functions.
At that point all four thresholds arrive within about a quarter of each other, and the register goes from tired to fictional in a single reporting cycle.
If your portfolio is 15 contracts but they are spread across six owners who have never met you, you will hit the wall sooner. If you have 90 contracts and 80 of them are low-value repeat agreements on identical terms, you may never hit it at all. Count the owners and the cycles, not the contracts.
The month seven test
Put this in your diary for seven months after you build any register. It takes an afternoon and answers the question honestly.
When was the last time somebody other than me updated this?
How many of these named owners still work here?
Which items have I quietly stopped reviewing?
If I were hit by a bus tomorrow, could my replacement run this contract from what is written here?
If the answers are uncomfortable, that is not failure. That is the normal decay curve of a management tool. Catching it at month seven costs you an afternoon. Catching it at month 30 costs considerably more and usually involves a letter.
Three things to do before you buy anything
I sell contract management software, so treat the following with appropriate suspicion. It is still true.
Start with the calendar. Every dated obligation gets a diary entry, set early enough to actually act, assigned to the named owner as well as to you. This costs nothing, takes an afternoon, and addresses the single largest cause of value leakage in post-award contract management. If you do nothing else on this list, do this one.
Then restructure what you already have. A well-built register sorted by cadence with a person's name on every line, sitting somewhere everyone can see it, comfortably beats a badly implemented platform. Name a person, not a function. Functions do not update spreadsheets.
Then find out what your organisation already owns. A remarkable number of businesses have bought a CLM platform and use about 15% of it. There may be an obligations module sitting there unused because nobody was ever trained on it and the person who ran the procurement has moved on. Ask before you buy a second one.
Only after those three does buying something make sense, and there is a reason for the order. Technology amplifies whatever process you already have. If your obligations are badly triaged, automating them gives you 300 automated alerts, which people will switch off within a fortnight. If nobody owns anything, a system will not create ownership. It will tell you, in a well-designed interface, that nobody owns anything.
How TermHive helps once the spreadsheet has run out of road
TermHive exists for the point where the four thresholds have all arrived and the honest answer to the month seven test is bleak.
Contracts and schedules go into the Library once, so there is one version rather than five inboxes and a shared drive nobody trusts. Track turns each agreement into individual obligations, each with a named owner and a due date, so the register is not a document that decays but a record that updates as people do the work. Alerts does the chasing your spreadsheet cannot, which is the whole difference between a system that pushes and a file you have to remember to open. ROI reports what the exercise recovered, for the day finance asks why the licence exists.
What it does not do: draft your contracts, negotiate them, or handle e-signature. It also will not triage your obligations for you. That judgement is the job, and a platform that claimed otherwise would be lying to you.
If the chasing is the part that has broken, start with Alerts.
Frequently asked questions
How many contracts can you manage in a spreadsheet? There is no fixed number, which is why nobody sensible quotes one. A spreadsheet holds up while one person maintains it and the consequences of neglecting it for a month are survivable. In practice that tends to break somewhere between 30 and 50 contracts, but portfolios with many obligation owners break far earlier and portfolios of near-identical low-value agreements can run much longer.
Is Excel good enough for contract management? For a small portfolio managed by one person with a disciplined calendar, yes, and anyone telling you otherwise is selling something. Excel fails at three specific jobs: chasing people without being asked, surviving a change of owner, and evidencing what was raised and when. If those three do not matter yet, keep the spreadsheet.
What is the difference between a contract tracking spreadsheet and an obligations register? A tracking spreadsheet usually holds contract metadata: counterparty, value, start date, renewal date. An obligations register goes a level deeper and holds the individual promises inside each agreement, on both sides, each with an owner and a cadence. Most spreadsheets described as contract trackers are really renewal-date lists, which is why they miss most of the value.
Why do obligations registers stop being updated? Because updating them benefits the person who built the register rather than the people being asked to update it. Nothing happens if they ignore it, and the request competes with work that has consequences attached. That is a design problem rather than an attitude problem, and it is covered in more detail in the guide to contract obligation management.
When should you move from a spreadsheet to contract management software? When you can no longer maintain it alone, when you need it to chase people without your involvement, or when you would struggle to evidence a year of oversight from it. Before that point, a calendar and a well-structured register will get you most of the way. Software that automates a broken process just produces the same failure faster and with better graphs. Have a look at the Library when you get there.
Comments