Buried on page 14 of a vendor agreement I inherited last year, there was this line: “Supplier shall provide quarterly business reviews including service level performance, root cause analysis of any incidents, and a forward-looking capacity plan.”

Nobody had ever asked for one. The contract had been signed nineteen months earlier. That’s six missed reviews. Six chances to catch problems early, gone. And when I emailed the account manager about it, he was genuinely surprised. “Oh, yeah, we can do that. Nobody ever asked.”

That’s contract obligation tracking in a nutshell. The promise is in writing. The promise is binding. And the promise is sitting in a PDF on a shared drive that nobody opens after signing day.

Why this keeps happening

Contracts get signed by one team and lived with by another. Procurement runs the negotiation, legal cleans up the language, the sponsoring department signs off, and then the document gets filed. The person who actually needs the quarterly review, the indemnification certificate, the data deletion confirmation, the price hold, the SLA credit, the renewal notice window, is usually three desks away from the signature.

Nobody is being lazy. The contract just doesn’t have a forwarding address.

I’ve seen this at a 40-person startup and at a company with 3,000 employees. The mechanics are the same. Once a contract is signed, the obligations inside it become invisible unless somebody deliberately makes them visible. The default is forgetting.

And forgetting is expensive. I wrote about this in 8.6% of Your Contract Value Is Disappearing, and obligation drift is a huge part of that number. You negotiated a service credit. You earned the service credit. You never claimed it because nobody was watching.

What obligation tracking actually means

Strip away the consulting language and it’s four things:

1. What did we promise, and what did they promise?
2. Who owns making sure it happens?
3. When is it due, and what does “done” look like?
4. What’s the follow-up if it doesn’t happen?

That’s the whole job. You can do it on a sticky note for one contract. You need a system for a hundred. But the four questions don’t change.

Most companies fail at question two. They can usually answer one and three with some digging. Four is a coin flip. But two, the owner, is where everything breaks. If nobody owns the promise, the promise doesn’t get kept.

Step 1: Pull the obligations out of the contract

Open the signed PDF. Read it. Yes, really. I know that sounds insulting, but I’d guess that at most companies, fewer than half of the active contracts have ever been read end-to-end by the person responsible for them.

Make a list of every commitment, on either side. Look for:

• Anything with a date attached (review meetings, audits, renewals, notice periods).
• Anything with a frequency (monthly reports, quarterly reviews, annual certifications).
• Anything conditional (if downtime exceeds X, then credit Y).
• Anything required for renewal (signed addendums, updated insurance, SOC 2 reports).
• Anything you have to do (provide forecasts, give notice, pay on time, keep data confidential).

You don’t need a fancy template. A four-column list in a spreadsheet works: obligation, party responsible, due date or trigger, evidence of completion. I’ve used a Google Sheet for a portfolio of 80 contracts and it was fine. Not elegant. Fine.

Step 2: Assign an actual human owner

This is the step everyone skips, and it’s the one that matters most.

“The legal team” is not an owner. “Procurement” is not an owner. “IT” is not an owner. An owner is a person with a name and an email address who, if asked, will say “yes, I know that’s mine.”

For each obligation, write down the owner’s name. Not their title. Their name. Then tell them. Out loud or in writing, but tell them. “Hey, Priya, you’re the owner of making sure we get the quarterly business review from Acme. First one is due August 15. Cool?”

If Priya says “uh, that’s not really my job,” you don’t have an owner. Keep looking until somebody nods.

Step 3: Define what “done” looks like

A surprising number of obligations get marked complete based on vibes. The vendor “sort of” sent a report. The customer “kind of” gave notice. The audit “more or less” happened.

For each obligation, write down what proof of completion looks like. Examples:

• Quarterly review: a meeting on the calendar plus a slide deck saved to the contract folder.
• Insurance certificate: a current COI on file, dated within the last 12 months.
• SLA credit: a credit memo applied to the next invoice.
• Data deletion: a written confirmation from the vendor’s compliance contact.

“Proof” doesn’t have to be heavy. It just has to be something you can point at. The test is: if a regulator or your CFO asked you to show that this obligation was met, could you?

Step 4: Put the deadline somewhere it will actually be seen

A deadline in a contract is invisible. A deadline on someone’s calendar is real.

The cheapest version of obligation tracking is calendar invites. For every dated obligation, put it on the owner’s calendar with a reminder set 30 days early. For frequency-based obligations, set up a recurring event. For conditional obligations (the “if X then Y” kind), put a quarterly check-in on the calendar to look at the trigger condition.

A spreadsheet with a date column will work too, as long as somebody is looking at the spreadsheet. The single most common failure mode I’ve seen is a beautiful tracker that nobody opens. A calendar invite that pops up in someone’s face is harder to ignore.

If you’re at the stage where calendars and a shared sheet aren’t keeping up, that’s when you start looking at software. Not before. I’ve watched companies buy a CLM with obligation tracking modules before they ever wrote down a single obligation by hand, and it goes exactly as well as you’d expect. The tool can’t track what you haven’t identified.

Step 5: Build a follow-up loop

When a deadline passes, somebody needs to look at the obligation and say one of three things:

• Done, here’s the proof, moving on.
• Late, here’s the nudge I’m sending right now.
• Not happening, here’s the escalation path.

That last one is the part most people don’t plan for. What do you actually do if the vendor blows off the quarterly review three times in a row? If you don’t know, you’ll do nothing, and the obligation will quietly die.

Decide upfront. Maybe it’s a polite email at 30 days late, a formal notice at 60, and a conversation with your account exec at 90. Maybe it’s a service credit claim. Maybe it’s a non-renewal flag. Whatever it is, write it down before you need it.

A real-world rhythm

Here’s what I do, with very little software, for a portfolio I inherited:

• Once a quarter: sit down with the obligation list and walk through every line. Mark what happened, what didn’t, and what’s coming up next quarter.
• Once a month: scan the next 60 days of obligations and ping owners to make sure they’re on it.
• Once a week: check anything that fell off last week and chase it.

That’s about three hours a month for 60 to 80 contracts. It’s not glamorous. It’s not a transformation initiative. But it catches the stuff that would otherwise rot.

What to do this week

Pick five contracts. Just five. The biggest by dollar value, or the ones that scare you most.

For each one: open the document, list the obligations, name the owners, put the dates on calendars, and write down what proof looks like.

You will find things. I have never done this exercise and not found at least one promise that nobody knew about. You’ll find a credit you can claim, a review you can ask for, a deadline you almost missed, or a clause that should have been triggering refunds for six months.

That’s the win. Not a system, not a platform, not a transformation. Just five contracts where the promises now have owners.

Do that this month and the next five next month and you’ll be ahead of most companies I’ve worked with.

---

I’m Dave, and I write about contract management the way it actually works. No jargon, no sales pitch, just what I’ve learned from 15+ years of doing this job. If this was useful, stick around.