How to Track Contract Obligations and Renewals (Before They Cost You)

A contract does not finish its job when everyone signs it. Signing is where the promises inside it come into existence, not where they get kept. Every "shall deliver," "shall notify," "shall renew unless," and "shall maintain insurance of" is a live commitment someone now has to track, act on, and prove was met, months or years later. Most businesses have a decent process for getting a contract signed. Very few have one for what happens after, and that gap is where real money gets lost: an auto-renewal nobody meant to trigger, a missed report that lets a vendor's failures go unchecked, an SLA credit nobody claimed because nobody was watching the date.

Adira, which publishes this guide, sells contract management software built to automate this tracking, so we have a commercial interest in how you answer the question below. This guide is written to get a small or mid-size team a working, mostly manual process first, on a spreadsheet, before you need to buy anything.

This is the practical follow-up to what obligation management actually is: the six-step process, a template you can build today, and the one deadline that causes more losses than everything else on this list combined.

Why obligations need active tracking, not just careful drafting

Indian contract law is blunt about what a signature actually creates. Section 37 of the Indian Contract Act, 1872 says:

"The parties to a contract must either perform, or offer to perform, their respective promises, unless such performance is dispensed with or excused under the provisions of this Act, or of any other law." Source: Section 37, Indian Contract Act, 1872, Indian Kanoon

A promise does not get easier to keep just because it was drafted well. A perfectly drafted contract with nobody watching its dates is exactly as exposed as a badly drafted one. The law does not track deadlines for you, and reading the contract once at signing does not either.

Step 1: Extract every obligation and key date before you file it

Before you can track anything, you need a list: what has to happen, by when or on what trigger, under which clause, for both sides. This is extraction, not tracking, and deserves its own process. Our companion guide on how to extract key dates, obligations, and amounts from a contract has a manual Ctrl+F checklist and an AI-assisted approach with a verification pass. Do this at the point you file the contract, not in a backlog months later, or a rushed pass will miss exactly the obligations, buried in a schedule, reached only by cross-reference, that cause the most damage.

Step 2: Find the real deadline, the renewal-notice window, not the renewal date

Of every mistake on this list, one causes more losses than all the others combined: tracking a contract's renewal or expiry date, and missing the earlier, separate deadline that actually lets you stop it.

Most contracts with an auto-renewal (evergreen) clause do not simply end on the expiry date. They renew automatically unless one side gives written notice inside a defined window before it, commonly 30, 45, or 60 days out. Miss that window by even a day, and the contract renews anyway, often for a full further term, sometimes at a higher price. Our full explainer on auto-renewal clauses works through the notice-window arithmetic. For a tracker: never store only the expiry date, calculate and store the notice deadline as its own field, and set the reminder against that date, not the anniversary everyone thinks of first.

Step 3: Assign a named owner to every obligation

An obligation without a named person attached belongs to nobody, and nobody misses a deadline on purpose, they miss it because it was never clearly theirs. Assign a real name or role, not "the team" or "legal": procurement for a delivery date, finance for a payment milestone, the account manager for an SLA report, legal for a renewal-notice deadline. When the person who negotiated the deal changes roles or leaves, obligations tied only to them go silent, so reassign ownership as part of any offboarding, not as an afterthought.

Step 4: Set reminders with real lead time

A reminder set for the day a deadline falls due is a record of what you already missed. Cascade reminders, with more lead time for higher-stakes obligations:

• Renewal-notice deadline: 90 days out, then 30, then a final alert at 7.
• Recurring reporting or payment: 5 to 7 days ahead, since the action is routine.
• Insurance or compliance certificate: 30 days ahead of the underlying policy's renewal, since replacement cover takes time to arrange.

Match lead time to how long the action actually takes, not a single default applied to everything.

Step 5: Keep evidence, not just a memory, of compliance

Meeting an obligation and being able to prove you met it, months or years later, are two different things. "We definitely sent that notice" carries far less weight than a dated email, delivery receipt, or signed acknowledgment tied to the specific clause it satisfies, attached to the tracker row itself, not a separate inbox someone has to search later.

This matters legally, not just operationally. Under Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 (the successor to Section 65B of the Evidence Act), an electronic record generally needs a certificate about how it was produced and maintained before a court will admit it. A tracker with an evidence trail, and a record of who created each piece, gives you something to certify later. A tracker with no evidence field gives you a claim nobody can back up.

Step 6: Review the tracker every quarter

A tracker only opened when a deadline is about to hit is a to-do list, not a management process. Set a standing quarterly review: every active contract represented, owners still correct after team changes, past reminders actually fired, closed contracts moved out of the active view. This is also where extraction errors, a date misread, a clause missed, get caught before they cause a real miss.

What the law actually does when a deadline is missed

Two things decide how expensive a missed deadline gets: whether the contract treats it as a strict condition, and how long you have to act on a breach at all.

Indian courts take a stated notice deadline seriously once the contract makes it a condition, not a formality. In M/s. Sonell Clocks and Gifts Ltd. v. The New India Assurance Company Ltd., (2018) 9 SCC 784, the Supreme Court upheld an insurer's rejection of a fire-loss claim because the policyholder gave notice roughly four months after the loss instead of within the fifteen days required, holding:

"The fulfillment of the stipulation in Clause 6 of the general conditions of the policy is the sine qua non to maintain a valid claim under the policy." Source: M/s. Sonell Clocks and Gifts Ltd. v. The New India Assurance Company Ltd., Supreme Court of India, 2018, AdvocateKhoj

This held even though the insurer had already appointed a surveyor; the Court rejected the argument that this waived the notice condition. The lesson carries over to any contract with a stated notice period, for a renewal, a claim, or a right to cure a breach: if the clause is drafted as a condition, a court is likely to enforce the stated number of days literally.

The clock runs against you too. Under Article 55 of the Schedule to the Limitation Act, 1963, a suit for compensation for breach of contract must generally be filed within three years of the breach, or, for a continuing breach, within three years of it ceasing. See the Limitation Act, 1963. A tracker that watches only your own obligations, not the other side's, is missing half the point: if a counterparty quietly stops meeting theirs and nobody notices for three years, your right to do anything about it may already be gone.

A simple obligations tracker you can build today

You do not need software to start. A spreadsheet with these columns, filled in as each contract is filed, covers most small and mid-size teams.

Column	What goes here	Example
Contract	Short contract name or ID	Acme-MSA-2026
Counterparty	The other party	Acme Logistics Pvt Ltd
Obligation	What has to happen, in your own words	Submit monthly SLA report
Clause reference	Where it comes from in the document	Clause 8.2, Schedule 3
Trigger date / frequency	The exact date, or the recurring rule	5th business day of each month
Owner	A named person, not a team	Priya Menon, Account Management
Reminder lead time	How far ahead the alert fires	5 days before due date
Evidence	Where proof of compliance lives, linked	Email thread #4521, filed in /evidence
Status	Open, Done, Overdue, or Escalated	Done, 3 Sept 2026

Add one more column for any contract with an auto-renewal clause: a renewal-notice deadline, calculated from the clause and stored apart from the expiry date. That single extra column is the one most likely to save you real money. Conditional formatting to colour any row entering its reminder window turns this into a working tracker, no purchase required.

Red flags in how obligations get written and tracked

Normal	Red flag	Why it matters
Renewal-notice deadline stored as its own field	Only the expiry or renewal date is tracked	The real, earlier deadline lapses silently; the single most common costly slip
A fixed date or measurable trigger for every obligation	Vague timing: "in due course," "periodically"	No date to set a reminder against; falls to whoever happens to remember
A named person as owner	"The team," "legal," or left blank	Nobody is clearly on the hook; obligations get orphaned when roles change
Reminders cascaded ahead of the deadline, by stakes	A single reminder set for the due date itself	No time left to act once the alert fires
Evidence attached to the specific obligation it proves	A general sense that "we usually do this"	Nothing to show a court or counterparty if compliance is disputed
A quarterly review that catches drift and errors	Tracker only opened when a deadline is imminent	Extraction mistakes go uncaught until they cause a real miss
The other side's obligations tracked too	Tracker covers only what you owe	You may miss the other side's breach before Article 55's three-year window runs out

A bad obligation clause, rewritten

Bad: "The Vendor shall maintain adequate insurance cover throughout the Term and shall provide evidence of the same to the Client upon request."

What is wrong: "adequate" has no checkable number, "upon request" gives no trigger date to set a reminder against, and there is no stated consequence if cover lapses.

Better: "The Vendor shall maintain professional indemnity insurance of not less than Rs 1 crore per claim, and public liability insurance of not less than Rs 50 lakh per occurrence, throughout the Term. The Vendor shall provide a certificate of currency for each policy to the Client's designated contract owner within 5 business days of each policy's renewal date, and in any event no later than 30 days before the expiry of the then-current certificate. Failure to provide a valid certificate shall entitle the Client to treat this as a material breach under Clause [Termination for Cause]."

What changed: "adequate" became two checkable numbers, "upon request" became two fixed trigger dates for a tracker, and a stated consequence gives the obligation real teeth.

When manual tracking breaks, and it is time to tool up

A spreadsheet with named owners, cascaded reminders, and an evidence column genuinely works, for a while. It breaks down at a predictable point: past a few hundred active obligations across dozens of contracts, more than one or two people editing the same sheet, or owners changing roles often enough that reassignment becomes a task nobody owns. A reminder that should have fired silently doesn't, because someone archived a row instead of updating it; a renewal-notice deadline calculated once is never recalculated after an amendment quietly changes the notice period.

None of that means the manual process was wrong to start with, it was the right place to start. It means the job has outgrown a spreadsheet's ability to enforce its own rules. If you have crossed into that territory, our guide to managing contract renewals at scale covers what changes once volume, not diligence, is the limiting factor.

You can extract and mark up the obligations in a single contract for free in Weave, no purchase needed. Adira's paid CLM plans (Practice at $89 to $109 per seat per month, Firm at $179 to $219, Enterprise on custom pricing, all with a 7-day trial, as published on adiralaw.com, last verified 4 September 2026) build this pipeline into an ongoing system across a full portfolio, for teams that have genuinely outgrown the spreadsheet stage.

US and global contrast

The mechanics, extract, assign, remind, keep evidence, do not change much by geography; a missed SLA report causes the same damage anywhere. What differs is how strictly courts read a missed deadline. Indian courts, as Sonell Clocks shows, enforce a clearly worded condition-precedent notice period literally, while Section 55 separately asks whether a deadline was meant to be "of the essence." US practice leans more heavily on treating a stated deadline as binding by default, so a drafter carrying that over unexamined can be caught out.

FAQ

What is the single biggest mistake in tracking contract obligations? Tracking the renewal or expiry date instead of the earlier, separate renewal-notice deadline. By the time a team notices the renewal date approaching, the window to stop it, usually 30 to 60 days earlier, has often already closed.

How much lead time should a reminder have? It depends how long the action takes. A renewal decision needing multi-person sign-off deserves 60 to 90 days; a routine recurring report needs only 5 to 7.

Can a spreadsheet actually work for obligation tracking, or do I need software? Yes, for a small number of contracts with disciplined owners and named reminders. It reliably breaks down past a few hundred active obligations, multiple editors on one sheet, or frequent owner turnover.

What counts as evidence that an obligation was met? Anything dated and tied to the specific clause: a sent email, a courier receipt, a signed acknowledgment, a payment confirmation, attached to the tracker row itself, not scattered across personal inboxes.

Do I need to track the other side's obligations too, or just my own? Both. Under Article 55 of the Limitation Act, 1963, you generally have three years from a breach to sue for compensation. Only tracking your own obligations means you may miss the other side's breach in time to act.

How often should the tracker itself be reviewed, separately from individual deadlines? Quarterly, at minimum: owners still correct, past reminders actually fired, and extraction errors from when a contract was first filed caught before they cause a real miss.

This guide gets you a working process for tracking obligations and renewals, and the columns to start a tracker today. It does not tell you whether a specific notice clause in your contract is a strict condition precedent, or what remedy you are entitled to if a counterparty's obligation lapsed. Those depend on your contract's exact wording and facts, and are not legal advice. Talk to a lawyer before you rely on, or write off, a deadline that genuinely matters.