“We need you to tell us what our contract with Vendor X actually says.”

I stared at the email from the client’s in-house legal team. Attached were dozens of files: Word documents, PDFs, scanned signatures, unsigned drafts. The subject line read “Vendor X Agreement. Consolidation Needed URGENT.”

I opened the first file. Framework Agreement, dated seven years ago. Then the amendments started. Amendment 1, Amendment 2… I kept scrolling. Amendment 15, Amendment 23, Amendment 38, Amendment 61.

Sixty-one amendments.

At least, that was the highest number I could see. Whether there were more lurking in those files, I honestly couldn’t tell you.

The Problem

The in-house team didn’t have time to figure it out themselves. They needed to amend the contract again, something about expanding the scope of services, but nobody could say with confidence what the current terms actually were. What were the payment terms? Who owned what IP? What were the termination rights?

Nobody knew.

So they did what most organisations do when faced with this kind of mess: they sent it to external counsel. Me.

The Process (or: How I Spent 70 Hours of My Life)

First, I had to understand what I was working with. I counted the files:- Original framework agreement- 61 amendments (or possibly more)- Some signed, some unsigned- Some in Word, some in PDF- Some fully executed, some partially executed- Some that appeared to be drafts, but maybe weren’t- At least three that contradicted each other

My first step was converting everything to Word format. Every PDF, every scanned document, every partially illegible signature page. I needed to be able to work with the text, search it, manipulate it, compare it.

Then came the consolidation itself.

I created a master document starting with the original framework agreement. Then I went through each amendment, in chronological order, incorporating the changes into the master. To keep track of what came from where, I used a different coloured font for each amendment and noted the colour coding in the footer.

Amendment 1: blue text. Amendment 2: green text. Amendment 15: purple text. By Amendment 40, I was running out of distinguishable colours.

Seventy hours later, I had a consolidated contract.

And what a contract it was.

What I Found

Errors Everywhere

Amendments that referenced clause numbers that didn’t exist (because earlier amendments had renumbered everything). Defined terms that were used inconsistently or not at all. Obligations that had been “superseded” by three different amendments but never actually deleted, leaving it unclear which version applied.

In one particularly delightful section, an amendment added a termination right referencing “Section 8.4” which had been deleted by a previous amendment and replaced by what was now “Section 9.2,” but nobody had updated the cross reference.

Inconsistencies

Payment terms that varied depending on which part of the contract you read. Some amendments extended the term, some didn’t mention it at all, leaving it genuinely ambiguous when the contract was actually supposed to end. Liability caps that had been changed four times, with no clear indication which one governed.

Amendments That Never Should Have Been Agreed

This is the part that made me wince. Whoever had negotiated some of these amendments hadn’t understood the original framework they were amending. New obligations had been added that directly contradicted existing protections. Scope changes that fundamentally altered the risk allocation without anyone apparently noticing.

One amendment tried to dovetail a cloud services agreement into what was originally a framework for hardware supply. The legal and operational frameworks for these two services are completely different. They have different risk profiles, different liability structures, different IP considerations. Trying to govern both under one contract was like trying to wear a suit jacket with tracksuit bottoms. Technically possible, but deeply uncomfortable for everyone involved.

The Time Problem

This contract had been around for over seven years. It had outlived multiple commercial teams, several in-house lawyers, and at least two reorganisations. Nobody who had negotiated the original framework still worked at the company. Most of the people who’d negotiated the amendments were gone too.

Institutional knowledge had walked out the door, leaving behind a contract that nobody fully understood but everyone relied on.

The Real Cost

Let me be clear about what this cost:

My time: 70 hours at external counsel rates. You can do the maths.

The client’s time: Countless hours of their in-house team trying to figure this out before giving up and escalating. More hours responding to my questions about what various amendments were supposed to achieve. Even more hours reviewing my consolidated version.

Opportunity cost: Whilst I was consolidating this contract, I wasn’t doing other work. Whilst the in-house team was dealing with this, they weren’t focusing on strategic priorities.

Risk: For seven years, decisions had been made based on what people thought the contract said. Some of those decisions, I’m fairly certain, were wrong. What liability had the company unknowingly taken on? What rights had they failed to enforce? What obligations had they missed?

We’ll never know.

Why This Happens

Here’s the thing: nobody sets out to create a 61 amendment nightmare. It happens gradually, one small decision at a time.

Year 1: “We just need a quick amendment to add this one service. No need to redraft the whole agreement.”

Year 2: “Can we do another quick amendment? It’s only three clauses.”

Year 3: “I know we’ve amended this a few times, but it’s still easier than renegotiating the entire framework.”

Year 5: “I know the contract’s getting complex, but we’re too busy to consolidate it now. Maybe after this project.”

Year 7: “Does anyone actually know what this contract says?”

Each individual amendment seems reasonable at the time. Each one is faster than redrafting. Each one is “just one more.” Until suddenly you’re at 61 amendments and nobody can tell you what you’ve agreed to.

The Lessons

1. Consolidate After Every Third Amendment (Maximum)

If you’re amending a contract more than twice, it’s time to create a consolidated, restated version. Yes, it takes time. Yes, it costs money. But it costs far less than 70 hours of external counsel time years later.

2. Someone Must Own the Contract

Not just negotiating it. Not just signing it. Someone must own knowing what’s in it, tracking amendments, and maintaining the institutional knowledge. When that person leaves, the knowledge must transfer.

3. Question Whether You Should Amend at All

Sometimes the right answer isn’t “let’s do a quick amendment.” Sometimes it’s “this change is substantial enough that we should renegotiate the entire agreement.” Yes, that’s harder. But shoving incompatible services into an unsuitable framework is harder still.

4. Post-Signature Management Matters

This isn’t a novel insight to me anymore, but it was certainly reinforced by this experience. The real work on a contract starts after signature. Tracking obligations. Managing performance. Understanding what you’ve agreed to. Maintaining the contract as a living business tool, not an archived document.

The Aftermath

After 70 hours, I delivered a consolidated contract to the client. It was technically accurate, fully cross referenced, and properly colour coded. They could now see exactly what their current obligations were.

They used it to negotiate Amendment 62.

I wish I could tell you they learnt their lesson and consolidated regularly after that. But I can’t, because I don’t know. I moved on to other matters. The in-house team moved on to other crises.

But I never forgot that contract. It crystallised something I’d been observing throughout my career: the massive gap between what organisations negotiate and what they actually capture. The silent value leakage that happens when contracts are signed, filed, and forgotten.

That 61 amendment contract became the catalyst for Consolidocs. Because I kept thinking: there has to be a better way.

AI can’t negotiate your contracts for you. But it can absolutely consolidate 61 amendments in minutes instead of 70 hours. It can extract the current state of obligations without colour coding in 47 different fonts. It can flag inconsistencies and undefined terms automatically.

The technology exists. The problem is that most organisations don’t realise they have a problem until they’re staring at 61 amendments and nobody knows what they’ve agreed to.

The Question Worth Asking

How many of your contracts are at Amendment 15? Amendment 23? How many have been around for five, seven, ten years with multiple amendments and no consolidation?

How confident are you that your team knows what’s actually in them?

If the answer is “not very,” you’re not alone. This isn’t a failure of competence. It’s a failure of systems. Good people, doing their best, constrained by tools and processes that weren’t designed for the complexity of modern contracts.

The 61 amendment contract wasn’t an outlier. It was just the most extreme version of a problem I saw everywhere.

And that’s the problem worth solving.

Have you dealt with a contract consolidation nightmare?

I’d love to hear your story. Reply via the contact form or connect with me on [LinkedIn](https://linkedin.com/in/tina-fernandez-techlawyer).

Want to learn more about post-signature contract management?

Subscribe to my newsletter for monthly insights on contract performance, AI governance, and building better systems for the hard parts of legal work.

Disclaimer: Details have been modified to protect client confidentiality. But the 61 amendments? Those were real. And the 70 hours? Also real.

About the Author:
Tina Fernandez is a contract performance expert, speaker, and founder of Consolidocs. After 20+ years in technology law, including countless hours consolidating amended contracts, she’s building AI native tools to solve post-signature performance challenges. When she’s not speaking at conferences or building software, she’s learning to fly a Cessna 152 and proving that 60 is exactly the right age to start a tech company.

es_MXSpanish