# Your contract obligations are buried in email: build an obligation register **TL;DR:** Most Indian businesses sign a contract, file the PDF, then run the actual relationship over email and WhatsApp, so the real obligations, the waivers, and the deadlines that matter live scattered across threads nobody reads until a dispute starts. Build an obligation register: one sheet with every obligation, its owner, its clause reference, its trigger and due date, and its consequence of breach, pulled from both the signed document and the email trail that varied it. The two highest-value things this piece covers are how an email exchange can legally vary a written contract under the Contract Act 1872 and the Bharatiya Sakshya Adhiniyam 2023, and how Section 18 of the Limitation Act 1963 can reset your limitation clock the moment the other side acknowledges a debt in writing, even in an email. --- ## On this page - [What an obligation register actually is](#what-an-obligation-register-actually-is) - [The columns your register needs](#the-columns-your-register-needs) - [The clause types that get missed](#the-clause-types-that-get-missed) - [Why the email trail is legally dangerous](#why-the-email-trail-is-legally-dangerous) - [Getting the email trail into court](#getting-the-email-trail-into-court) - [Waiver and estoppel: how silence costs you the deadline](#waiver-and-estoppel-how-silence-costs-you-the-deadline) - [Limitation: the clock, and what resets it](#limitation-the-clock-and-what-resets-it) - [Building the register in one week](#building-the-register-in-one-week) - [Who owns it and the review cadence](#who-owns-it-and-the-review-cadence) - [Using AI for the first pass](#using-ai-for-the-first-pass) - [A worked example register](#a-worked-example-register) - [Frequently asked questions](#frequently-asked-questions) --- ## What an obligation register actually is A signed contract is a snapshot. The relationship that runs after signature is not. A vendor asks for two extra weeks on a delivery and you reply "sure, no problem." A client emails that they will pay in three tranches instead of one, and you go along with it for eighteen months. A renewal window opens and closes without anyone in either company noticing, because the only person who read the contract left the company fourteen months ago. None of that gets filed anywhere. It sits in an inbox, split across three people's mailboxes, half of it on WhatsApp, and it stays invisible until a dispute forces someone to go back and reconstruct what actually happened. By then the reconstruction is adversarial, expensive, and often wrong, because memory fills gaps that the record should have filled instead. An obligation register is the fix. It is a single sheet, usually a spreadsheet or a lightweight database, that lists every ongoing obligation under a contract in one row each: what has to happen, who has to make it happen, which clause creates the duty, what triggers it, when it falls due, and what happens if it is missed. It is built once from the signed document, then kept alive by folding in every material email that varies, waives, or reinterprets a term. It is not a summary of the contract. It is an operational tool that a non-lawyer on your team can open on a Monday morning and know exactly what is due that week, without re-reading forty pages of legalese or scrolling back through two years of correspondence. This matters more in India than the drafting textbooks suggest, because Indian commercial relationships run heavily on relationship and adjustment. A counterparty who is late is usually not sued immediately; they get an email, a phone call, an accommodation. That flexibility is often the right commercial call. It is also exactly how obligations quietly drift away from what the signed contract says, and exactly why, when a real dispute finally arrives, both sides discover they have been operating under a contract that exists only partly on paper. [AI contract drafting](/blog/ai-contract-drafting) tools have made it faster to produce the first document. Almost nothing in that stack helps you track what happens to the document after both sides sign it. This piece is about that second, longer, and more consequential phase. --- ## The columns your register needs Keep the register flat. One row per obligation, one obligation per row, even if that means the same clause spawns three or four rows because it creates recurring duties. A register that tries to be clever with nested categories stops getting updated within a month. | Column | What goes in it | |---|---| | Obligation | Plain-English description of what has to happen, not a clause paraphrase | | Owner | The named individual on your side responsible for acting, not a department | | Counterparty owner | Who on the other side you would notify or chase, by name if you have it | | Clause reference | Exact clause and sub-clause number in the executed document | | Source | "Contract" or the specific email/date if the obligation was created or varied outside the document | | Trigger | The event that starts the clock: signing, delivery, invoice, renewal window opening | | Due date | Calculated actual date, not "30 days from delivery" | | Notice period required | How much advance notice either side must give, and by what method | | Evidence of performance | What you would produce to prove you did it: delivery receipt, email confirmation, payment record | | Consequence of breach | Penalty, termination right, indemnity trigger, or none stated | | Status | Open, done, waived, disputed, overdue | | Last reviewed | Date someone actually checked this row was still accurate | Two columns do most of the work that a plain contract summary cannot do. "Source" is what forces you to go looking in email for obligations the document itself never mentions, the payment schedule that got renegotiated by reply-all, the delivery date that moved twice. "Consequence of breach" is what stops the register from becoming a to-do list; it tells you which missed rows are a minor annoyance and which ones expose you to termination or an indemnity claim. Resist the temptation to add a "priority" or "risk score" column at the outset. It looks useful and becomes stale within a quarter, because risk changes with context that a static field cannot capture. A clean, current register with accurate due dates does more for you than a colour-coded one that nobody trusts. --- ## The clause types that get missed Some obligations announce themselves: the payment clause, the delivery schedule. Others sit quietly in boilerplate that nobody reads a second time after signature, and those are precisely the ones that cost money when they are missed. Work through this list against every commercial contract you hold. ### Notice and cure periods Almost every termination-for-breach clause is conditioned on a notice, a defined cure period, and only then a right to terminate. Terminating without giving the contractual cure window, even where the other side is genuinely in default, can itself become a repudiatory breach on your part. Put the exact number of days, the method of notice required (registered post, email to a named address, courier), and the earliest date you could lawfully terminate, in the register as its own row. ### Renewal and auto-renewal windows Auto-renewal clauses usually give a narrow window, often 30 or 60 days before the renewal date, to give notice of non-renewal. Miss it and you are locked in for another term on the existing pricing, sometimes for a year you did not intend to commit to. This is the single most common obligation-register failure in SaaS and vendor contracts, because the window opens and closes silently unless someone calendars it against the actual signature date rather than the date someone remembers signing. ### Exclusivity An exclusivity clause restricts you (or the other side) from dealing with competitors, sourcing the same category elsewhere, or operating in a defined territory. These are easy to breach inadvertently when a new business line launches or a new vendor gets onboarded by a different team that has never seen the contract. Register the scope precisely: product category, territory, and duration, not just "exclusivity applies." ### Minimum commitments and take-or-pay A minimum purchase commitment or take-or-pay clause obliges you to pay for a threshold volume whether or not you actually consumed it. These usually run on a defined measurement period, quarterly or annual, and the shortfall payment often has its own separate due date distinct from ordinary invoicing. Track the running consumption against the threshold in the register, not just the existence of the clause, or the shortfall becomes a surprise at period-end. ### Change of control A change-of-control clause typically gives the other party a right to terminate, renegotiate, or demand consent if you are acquired, merge, or undergo a defined ownership change. This is easy to miss because it sits dormant for years and then becomes acutely relevant during a fundraise or acquisition due-diligence process, exactly when you have the least time to negotiate a waiver. ### Audit rights Many vendor and licensing contracts give the counterparty a right to audit your usage, records, or compliance, usually on a defined notice period and frequency limit. If you never track this, the first audit request feels like an ambush rather than a contractual entitlement you agreed to. Register both your obligation to cooperate and any limit on frequency you negotiated, since that limit is your protection against a hostile counterparty running repeated audits as a pressure tactic. ### Indemnity notification deadlines An indemnity clause almost always conditions the indemnifying party's obligation on prompt notice of the claim, sometimes with an explicit number of days. Miss that notification window and you can lose the indemnity entirely, even where the underlying claim is genuine and the indemnifying party would otherwise have covered it. This is one of the costliest misses in the whole register because it is triggered by a third-party event, a customer complaint or a regulatory notice, that your team may not immediately connect to the contract at all. ### Insurance maintenance Contracts frequently require one or both parties to maintain specified insurance cover, sometimes naming the other party as an additional insured, for the term of the contract and sometimes beyond it. Policies lapse on renewal dates that have nothing to do with the contract's own calendar, so this needs its own tracked due date tied to the insurance policy, not the contract anniversary. ### Data protection obligations under the DPDP Act 2023 Where a contract involves sharing personal data, especially a vendor processing data on your behalf as a Data Processor for your Data Fiduciary obligations under the Digital Personal Data Protection Act 2023, the contract should specify security safeguards, breach notification timelines to you, data return or deletion obligations on termination, and any restriction on further sub-processing. These obligations are becoming standard contractual terms as India's DPDP compliance timeline plays out; [DPDP compliance deadlines for 2026 and 2027](/blog/dpdp-compliance-deadlines-2026-27) sets out what is coming into force and when, and the vendor contracts you sign now should already be written for that horizon. If your existing vendor contracts predate the DPDP Rules 2025, check whether they were ever amended to reflect them; [the DPDP Rules 2025](/blog/dpdp-rules-2025) is the primary reference for what those obligations actually require in practice. ### The arbitration clause's pre-conditions Many Indian commercial contracts do not give either party an immediate right to invoke arbitration. They condition it on a mandatory negotiation period, sometimes escalating through named senior representatives, or a defined mediation step, before arbitration can formally begin. Skip that pre-condition and a tribunal, or a court asked to appoint an arbitrator, can find the arbitration invocation premature. Register the exact pre-arbitral steps and the minimum time that must elapse, because in a genuine dispute this is usually the first thing opposing counsel checks for a technical objection. [Arbitration in India](/blog/arbitration-in-india) covers how the arbitration framework fits together, and [the Mediation Act 2023](/blog/mediation-act-2023) is relevant where the pre-arbitral step is a mediation requirement rather than plain negotiation. --- ## Why the email trail is legally dangerous The reason you cannot build this register from the signed document alone is that Indian contract law does not treat the signed document as the final word on what the parties agreed. It treats it as the starting point, capable of being varied by what the parties actually did afterward. Section 62 of the Contract Act 1872 says that if the parties to a contract agree to substitute a new contract for it, or to rescind or alter it, the original contract need not be performed. There is no requirement in the Act that this substitution or alteration be in any particular form. An exchange of emails in which one party proposes a changed delivery date and the other confirms it is, in substance, an agreement to alter the contract, and Indian courts have repeatedly treated correspondence in this way as capable of creating or varying binding obligations. The Supreme Court, in *Trimex International FZE Limited v. Vedanta Aluminium Limited*, held that a concluded contract can come into existence through an exchange of emails even where the parties never got around to signing a formal, signed agreement, once the essential terms were mutually accepted. The same logic runs the other way: if a signed contract can be formed by email exchange without a formal signed document, a signed contract can equally be varied by a later email exchange without a formal amendment being executed. This is reinforced by the Information Technology Act 2000. Section 4 gives legal recognition to electronic records, so a requirement under any law that information be in writing is satisfied if it is rendered in electronic form and remains accessible for future reference. Section 10A, inserted by the 2008 amendment, goes further and specifically addresses contracts: it states that a contract shall not be deemed unenforceable solely on the ground that electronic form or means was used for the communication of the proposal, its acceptance, the revocation of a proposal or acceptance, or any other communication relevant to the formation of a contract. Between the two, an email proposing a variation, an email confirming acceptance of that variation, and an email confirming performance under the varied term, form a chain that Indian law treats as legally effective, not as informal chatter that a court will disregard because it never made it into a signed amendment. Section 11 of the IT Act deals with attribution: an electronic record is attributed to the originator if it was sent by the originator, by someone with authority to act on the originator's behalf, or by an information system programmed to operate automatically on the originator's behalf. This matters because it is the section that lets you hold a counterparty to an email sent by their procurement manager or their operations lead, without needing to prove the company's board separately authorised that specific message. It is also why you should register, for every material email in your obligation trail, who sent it and in what capacity, since attribution disputes usually turn on exactly that. What makes an email a valid signature is a narrower and more specific question than most people assume. An email is not automatically a "digital signature" in the technical sense the IT Act defines for that term, which involves a defined authentication process using asymmetric cryptography and an electronic signature certificate. But a typed name, a sign-off, or even a functional signature block at the end of an email can, depending on the facts, satisfy a requirement of "signature" under other statutes, because Section 3 of the General Clauses Act 1897 and the interpretation clauses of many commercial statutes define "sign" broadly enough to include marks made with the intention to authenticate a document, and courts have applied this reasoning to typed names in emails where the sender clearly intended it as an authentication of the content. Do not assume this by default for every clause; where a contract explicitly requires a "signed" amendment for validity, treat that requirement as meaningful and get an actual signed amendment, not just an email trail, for the obligations that matter most. The practical implication for your register is direct. Every material email exchange that changes a delivery date, a price, a scope item, or a performance standard is a candidate variation of the contract, whether or not either party thought of it that way at the time. If you are not capturing those emails in the "source" column, your register describes a contract that no longer matches what either party is actually bound by. This is exactly the fact pattern behind [a freelance contract formed and varied entirely over email](/blog/freelancer-unpaid-source-code-ownership), where the deliverables and the IP ownership terms both ended up defined by a thread rather than a signed statement of work. --- ## Getting the email trail into court Recognising that an email varies your contract is only useful if you can actually put that email before a court or tribunal when it matters. This is where most businesses fail, not because the email does not exist, but because nobody preserved it in a form the Evidence law will accept. Under the Bharatiya Sakshya Adhiniyam 2023, which replaced the Indian Evidence Act 1872, Section 63 governs the admissibility of electronic records, replacing the old Section 65B of the Evidence Act. The substance carries forward: an electronic record is treated as a document and is admissible without requiring the original device to be produced in court, provided the conditions in the section are satisfied and a certificate is furnished under Section 63(4). That certificate has to identify the electronic record, describe the manner in which it was produced, give particulars of the device involved, and deal with the conditions of admissibility set out in the section, and it must be signed by the person occupying a responsible position in relation to the device and, under the BSA's dual-certification requirement, by an expert as well. The practical takeaway is that a screenshot of an email, or a forwarded copy pasted into a WhatsApp message, is not by itself the kind of evidence a court will accept as proof of the original electronic communication. If an email in your obligation trail is important enough that you might need to rely on it in a dispute, note in the register which emails you would need a Section 63 certificate for, and keep the original mailbox, export, or a properly preserved copy, rather than relying on a printed copy years later when the original account may no longer be accessible. [Section 63 electronic evidence under the BSA](/blog/bsa-section-63-electronic-evidence) covers the certificate mechanics in full, and [the BSA-Evidence Act section mapping](/blog/bsa-evidence-act-section-mapping) is the reference for translating old Section 65B case law and practice to the new numbering, which matters because most of the reported case law on this subject was decided under the old section and remains persuasive on how courts read the new one. Two failure modes are common. The first is discovering, only at trial, that nobody preserved the original email account and only a printout survives, which weakens the evidentiary weight even where the content is not genuinely disputed. The second is producing the email but no certificate at all, which several reported decisions have treated as a fatal defect in admissibility, not a mere technicality that can be cured later. Build the habit now, while the relationship is healthy: export and archive contract-relevant email threads with headers intact, and note in the register which threads you have preserved this way. [How to preserve evidence properly before you call a lawyer](/blog/preserve-evidence-before-calling-lawyer) covers the same discipline in more general terms and applies directly to keeping a contract email trail admissible. --- ## Waiver and estoppel: how silence costs you the deadline The most common way a business loses a right it clearly had on paper is not by signing it away. It is by not insisting on it, repeatedly, until the law treats that pattern as a choice. Section 63 of the Contract Act 1872 allows a promisee to dispense with or remit, wholly or in part, the performance of a promise made to them, and to accept any satisfaction they think fit instead of actual performance. Where a buyer accepts late delivery three times running without protest, or a licensor keeps taking reduced royalty payments without objection, that conduct can be read as a waiver of the strict contractual timeline or amount, at least going forward, even without any written amendment. A related and separate doctrine, promissory estoppel, can prevent a party from later going back on a representation, made by words or by conduct, that the other side relied on to their detriment, even where there is no formal consideration for that representation. This is exactly why the register's "status" column has to distinguish "waived" from "done." If a due date was missed and you let it pass without comment, that is not the same as the obligation having been performed. It is a live risk that your own conduct may be read as accepting the departure from the contract, which can then be difficult to reverse if you later decide you want the original deadline enforced strictly again. Two phrases exist precisely to prevent this drift, and they should appear in your outgoing correspondence whenever you accept a departure from the contract but do not want that acceptance read as a permanent change. "Without prejudice" attached to a communication signals that what follows is part of a genuine attempt to settle or accommodate a dispute, and it is generally not admissible against the sender as an admission if the matter later goes to litigation, though it does not make the underlying facts disappear. "Under protest" attached to an acceptance, for example accepting a late or partial payment "under protest and without prejudice to our rights under clause X," is a direct signal that you are not waiving the right, only accepting the immediate practical reality while reserving your position. Courts have repeatedly given weight to this kind of contemporaneous reservation as evidence against a claim of waiver, because it shows the accepting party never intended to give up the underlying right. Put both phrases into your team's standard vocabulary for exactly the situations the register is meant to catch: a missed delivery date accepted for commercial reasons, a partial payment accepted to keep the relationship moving, a scope change agreed informally under time pressure. The discipline costs one sentence in an email. The alternative, discovered only when you actually need to enforce the original term, can cost you the right entirely. | Email phrase you sent | Legal effect | What to write instead | |---|---|---| | "No worries, take your time" | Reads as unconditional acceptance of delay; risks waiver of the deadline going forward | "We accept this revised date under protest and without prejudice to our rights under clause [X] for future deliveries." | | "That's fine, we'll adjust" | Can be treated as agreement to vary the term by conduct under Section 62, Contract Act 1872 | "We agree to this adjustment for this instance only, without amending the schedule in clause [X]." | | Silence after a late invoice or short payment | Repeated silence over time strengthens a waiver argument against you | Acknowledge receipt and expressly reserve rights, even briefly, each time: "Received, rights under clause [X] reserved." | | "Let's discuss and sort this out informally" (skipping the notice clause) | May be read as an agreed departure from the formal notice mechanism, weakening your later claim that notice was defective | Send the formal notice in parallel, then add "without prejudice to the above, happy to also discuss informally." | | "We'll get the amendment signed later" | Nothing wrong in principle, but if "later" never arrives, you are relying entirely on the email exchange as your variation | Confirm the exact terms agreed in the email itself, and calendar a hard follow-up date for the signed amendment | | "Confirmed, invoice as discussed" on a changed price | Can constitute acceptance of a price variation under Section 62, binding going forward | If the change is meant to be one-off, say so explicitly: "Confirmed for this invoice only; base pricing under clause [X] unchanged." | --- ## Limitation: the clock, and what resets it This is the paragraph in the whole register-building exercise that most affects whether you can actually recover anything once a dispute is real, so read it slowly. Under the Limitation Act 1963, a suit for breach of contract generally has to be filed within three years, and Article 55 of the Schedule to the Act, which governs suits for compensation for breach of a contract, runs that period from the date of the breach. This is the single most dangerous fact for a business that manages its counterparty relationships informally: the clock does not run from when you discover the loss, or from when negotiations to resolve it break down. It runs from the date the breach happened, whether or not you noticed it, and whether or not you were still trying to sort it out amicably in the meantime. A business that spends two years trying to resolve a dispute commercially, exchanging emails, extending informal deadlines, hoping the relationship survives, can wake up to find the underlying claim is now time-barred, because none of that goodwill stopped the limitation clock. Courts applying the Civil Procedure Code have consistently held that a plaint filed after limitation has expired is liable to rejection, and [order 7 rule 11 CPC](/blog/order-7-rule-11-cpc) is the specific mechanism a defendant uses to get exactly such a suit thrown out at the threshold, before the merits are ever heard. This is where Section 18 of the Limitation Act 1963 becomes the highest-value provision in this entire piece. Section 18 provides that where, before the expiry of the prescribed limitation period, a person against whom a right is claimed makes an acknowledgement of liability in respect of that right, in writing and signed by that person, a fresh period of limitation begins to run from the date of that acknowledgement. It does not extend the original period. It resets it, starting the three years over again from the acknowledgement date. Two conditions make or break a Section 18 acknowledgement, and both are exactly the kind of thing your email trail either proves or fails to prove. First, the acknowledgement has to be made before the original limitation period expires. An acknowledgement received after the clock has already run out does not revive a dead claim; it is simply too late. This means the moment you suspect a breach, even one you intend to handle informally, you should be actively watching for and, where possible, prompting a written acknowledgement from the other side, precisely because every month that passes without one brings you closer to a claim you can no longer enforce. Second, the acknowledgement has to show a clear recognition of a subsisting liability or right; it does not need to include an express promise to pay, but it does need to go beyond vague or evasive language. An email that says "we know we owe this, we're arranging funds" is a strong acknowledgement. An email that says "let's discuss further" or "we'll look into it" generally is not, because it does not clearly recognise the liability itself. This is why the register should flag, for every payment obligation currently in dispute or running late, whether you hold a genuine written acknowledgement of the amount owed, dated within the current limitation window, and if not, whether you can reasonably prompt one before the window closes. The practical discipline this creates: whenever a counterparty is behind on payment or performance and you are managing it commercially rather than litigating immediately, try to secure something in writing, even a short email, that clearly recognises the outstanding obligation. A payment plan proposal from the debtor, a partial payment with a covering note referencing the balance, or a simple "we acknowledge we owe [amount] under the [date] invoice" email is exactly the kind of document Section 18 is built around. Track the date of the last such acknowledgement for every open obligation in your register, and calculate the fresh limitation deadline from that date, not from the original breach. [Condonation of delay](/blog/condonation-of-delay) covers the separate, harder question of what happens if you miss the limitation window entirely and need a court's discretion to excuse the delay under Section 5 of the Limitation Act, which is a much less certain path than simply keeping the clock reset through timely acknowledgements in the first place. [Written statement and limitation under the CPC](/blog/written-statement-limitation-cpc) covers how a limitation defence gets raised and tested once litigation has actually started. --- ## Building the register in one week The register does not need a long project. It needs a focused week, a clear division of labour, and a willingness to leave gaps marked rather than guessed at. **Day 1: pull the document apart.** Read the executed contract clause by clause and list every obligation it creates, on either side, with its clause reference. Do not chase emails yet. Get the document's own obligations into rows first. **Day 2 and 3: mine the email trail.** Search each party's relevant mailboxes for the contract name, key terms, and the counterparty's domain, across the full life of the relationship. Pull out every thread that agrees a date, changes a price, waives a term, or acknowledges a debt or delay. This is the slowest and most valuable part of the exercise, and it is the part almost every business skips, which is exactly why the register is worth building in the first place. **Day 4: reconcile.** Match email-sourced obligations against document-sourced ones. Where an email varies a document term, mark the document row as superseded and add the varied row with the email as its source. Where an email creates a genuinely new obligation the document never addressed, add it as its own row. **Day 5: verify and calculate.** Convert every relative trigger ("30 days from delivery," "60 days before renewal") into an actual calendar date. Flag every row where you cannot find clear evidence of performance. Flag every open payment obligation where you do not currently hold a written acknowledgement within the current limitation window. Treat gaps as findings, not failures. A row you cannot fully substantiate is more valuable flagged as uncertain than filled in with a guess that later gets relied on as fact. --- ## Who owns it and the review cadence A register with no owner decays within a quarter. Assign it to a specific role, not a department, whether that is the commercial lead who manages the relationship day to day or, for contracts material enough to warrant it, the in-house legal or contracts function. [Legal research for in-house counsel in India](/blog/legal-research-in-house-counsel-india) covers the broader workflow question of how a lean in-house team stretches across everything it is asked to own, and a maintained obligation register is one of the highest-leverage things that team can produce, because it turns contract risk from something only legal understands into something the whole commercial team can act on. Keep in mind that most of the advice given inside that same email trail by an in-house lawyer is not privileged; [privilege for in-house counsel in India](/blog/in-house-counsel-privilege-india) explains why, and what that means for how candidly you should write about a disputed obligation before a dispute is real. Set a review cadence tied to the contract's own rhythm rather than an arbitrary calendar date. A monthly check for anything with a payment or delivery obligation due in the next 60 days. A quarterly full review of every open row for accuracy. A mandatory review triggered by any of three events: a renewal window opening, a material email exchange touching the contract, or the first sign of a dispute. That last trigger matters most, because the moment a relationship turns adversarial is exactly when the register stops being a convenience and becomes the evidentiary backbone of your position. --- ## Using AI for the first pass Reading a forty-page contract clause by clause and cross-referencing it against two years of email correspondence is exactly the kind of first-pass extraction work that AI tools handle well and humans find tedious enough to skip. Use an AI drafting or extraction tool to produce the initial obligation list from the executed document, and to search and summarise the relevant email threads for candidate variations. This will cut the week described above down meaningfully, particularly on the email-mining step, which is the one most businesses never do properly by hand. Do not skip the human verification step, and do not treat the AI-generated register as final without it. Extraction tools miss cross-references between clauses, misread conditional language as unconditional obligations, and can confuse a defined term used loosely in an email with its precise contractual meaning. A human reviewer, ideally the person who actually manages the relationship, should check every row against the source document or email before the register goes live, and should personally verify every date calculation and every consequence-of-breach entry, since those are the two fields most likely to matter in an actual dispute. [Legal verification workflow for AI output](/blog/legal-verification-workflow-ai-output) sets out a general discipline for this kind of check that applies directly here, and [how to vet legal AI citation accuracy](/blog/how-to-vet-legal-ai-citation-accuracy) is relevant wherever the extraction tool is also pulling in statutory references, since a wrong section number in your own register is exactly the kind of error that propagates silently until someone relies on it. Where the dispute has already started and you need to check whether a precedent you are relying on for a waiver or limitation argument is still good law, a legal research tool that shows the citing paragraph rather than a bare headnote is faster than running the same search manually across multiple databases. Niyam is built for exactly that kind of targeted, cited check once a specific legal question, rather than the broad extraction pass, is what you need answered. --- ## A worked example register The table below is a realistic obligation register for a mid-sized Indian SaaS vendor contract, six rows drawn from clauses that would exist in a typical enterprise software agreement plus a live email trail. | Obligation | Owner | Clause ref | Source | Trigger | Due date | Notice period | Evidence of performance | Consequence of breach | Status | |---|---|---|---|---|---|---|---|---|---| | Pay quarterly minimum commitment shortfall | Finance (buyer) | Clause 4.3 | Contract | End of measurement quarter | 15 days after quarter end | None specified | Payment confirmation, usage report | Vendor may suspend access after 30 days overdue | Open, due next quarter | | Give non-renewal notice or auto-renew for 12 months | Contracts lead (buyer) | Clause 12.1 | Contract | 60 days before renewal date | 60 days before anniversary | 60 days, in writing to named address | Sent notice with delivery confirmation | Contract auto-renews at then-current pricing | Open, window opens in 6 weeks | | Maintain cyber-liability insurance, buyer as additional insured | Vendor | Clause 9.2 | Contract | Continuous | Policy renewal date (not contract anniversary) | 15 days' notice of any lapse | Certificate of insurance | Vendor in breach, indemnity may be affected | Open, verify current certificate | | Notify buyer of any data breach involving buyer's personal data | Vendor | Clause 15.4 (DPDP rider) | Contract | Any breach event | 72 hours from vendor's discovery | Immediate written notice | Incident report, notification email | Separate indemnity clause triggered | Standing, no incident to date | | Revised delivery date for phase 2 integration | Vendor PM | Varies clause 3.1 | Email, 14 Feb 2026 thread | Original date missed | 15 Mar 2026 (revised) | None, accepted informally | Email confirmation from both sides | Original clause 3.1 penalty was waived for this instance | Done, accepted under protest | | Acknowledgement of outstanding invoice #INV-2209 | Vendor finance | N/A, payment obligation | Email, 3 Jun 2026 | Invoice due date passed | Fresh limitation runs from 3 Jun 2026 under Section 18, Limitation Act | N/A | Email stating "we acknowledge the outstanding amount of Rs 4,20,000 under invoice INV-2209" | Fresh 3-year limitation period from acknowledgement date | Open, payment plan pending | Notice how the last two rows exist only because someone mined the email trail. Neither would appear in a register built from the contract document alone, and the sixth row is precisely the kind of entry that determines whether a claim is still enforceable three years from now. --- ## Frequently asked questions ### Does an obligation register replace the need for a lawyer to review the contract? No. The register is an operational tracking tool built from what a lawyer, or an AI-assisted first pass followed by a lawyer, has already identified as the contract's obligations. It does not replace legal interpretation of ambiguous clauses, and any row where the underlying obligation is genuinely disputed should still go to a lawyer rather than being resolved by whoever is filling in the spreadsheet. ### What if the counterparty sends a formal legal notice instead of another email? Once a legal notice arrives, the relationship has moved from informal adjustment to a formal dispute posture, and the register becomes your primary evidence source for the response. [Legal notice, police notice, and summons: how they differ](/blog/legal-notice-vs-police-notice-vs-summons) explains what each of these communications actually requires of you, since the register's clause references and evidence-of-performance rows are exactly what your lawyer will need first when a notice sets a response deadline. ### Can WhatsApp messages vary a contract the same way emails can? In principle, yes. The Contract Act 1872 does not require any particular medium for an agreement to vary a contract, and the IT Act's recognition of electronic records is not limited to email. In practice, WhatsApp evidence is harder to preserve and authenticate cleanly for a Section 63 BSA certificate, since messages can be edited, deleted, or lost with a phone change far more easily than an email account. Treat anything agreed over WhatsApp as provisional and confirm it by email as soon as practical, precisely because the email is easier to preserve and certify later. ### What if the contract has an entire agreement clause saying no email can vary it? An entire agreement clause, sometimes combined with a "no oral or informal variation" clause, is meant to prevent exactly the kind of drift this piece describes, and courts generally give weight to such clauses. But Indian courts have also recognised that parties can, by their subsequent conduct, be found to have varied even a contract containing such a clause, particularly where one party's conduct would make it unfair to let them rely on the clause against the other. The safer practice is still to treat the clause as meaningful and route genuine changes through a signed amendment, while using the register to flag any informal variation as a live risk rather than assuming the clause makes it disappear. ### How long should we keep the email archive for a contract that has ended? At minimum for the full limitation period applicable to any claim that could arise from the contract, which is generally three years from the relevant breach under the Limitation Act 1963, and longer if any acknowledgement under Section 18 has reset that clock, or if the contract involves a longer specific limitation period, such as for a suit on a registered instrument. For contracts with ongoing indemnity or warranty obligations that survive termination, keep the archive for as long as those survival clauses run. ### Who should own the obligation register if we do not have in-house legal? Assign it to whoever owns the commercial relationship day to day, typically the account manager, operations lead, or finance contact who is closest to the actual performance of the contract. That person does not need to interpret ambiguous legal language alone; they need to flag anything uncertain for a lawyer's review rather than guessing. What matters most is that one named person is accountable for keeping the register current, not which department they sit in. ### Does accepting a late payment "under protest" actually work, or is it just wording? It is more than wording, but it only works if it is genuine and contemporaneous. Courts assessing a waiver argument look at the conduct as a whole, and a party that repeatedly writes "under protest" while otherwise behaving exactly as though the right had been waived, for example never actually enforcing the original term when it mattered, will find the phrase carries less weight. Used consistently and followed through when the stakes are real, it is a strong and simple piece of evidence against a waiver claim. ### What is the difference between a notice period and a cure period? A notice period is how much advance warning a party must give before taking a step, such as terminating or invoking an audit right. A cure period is the window given to the defaulting party, after being notified of a breach, to fix it before the other side can act on it, such as terminate the contract. A termination clause commonly requires both: notice of the breach, then a defined cure period, and only after that period expires without a fix does the termination right actually arise. ### If we never had a formal amendment signed, is the varied term unenforceable? Not necessarily. As the Supreme Court's reasoning in cases like *Trimex International FZE Limited v. Vedanta Aluminium Limited* shows, a contract, and by extension a variation of one, can be formed and evidenced through an exchange of correspondence including emails, without a formal signed document, provided the essential terms were mutually and clearly accepted. Whether a specific variation is enforceable without a signed amendment depends on the facts, including whether the original contract required variations to be in a specific signed form, so treat this as a fact-specific question rather than a blanket rule either way. ### Do we need a Section 63 certificate for every email we might rely on? You need one for any electronic record you intend to produce as evidence in a proceeding where the content of the communication, rather than merely its existence, is disputed. For day-to-day register management, you do not need to prepare certificates in advance for every email. You do need to preserve the originals properly so that a certificate can be prepared later if a dispute actually reaches that stage, since reconstructing an email trail years after the fact, once mailboxes have changed or accounts have closed, is far harder than archiving it while the relationship is live. ### How does a mandatory pre-arbitration negotiation clause interact with the limitation clock? The pre-arbitral step does not, by itself, extend or pause the underlying limitation period for the substantive claim under the Limitation Act 1963, unless the contract or a specific statutory provision says otherwise. This is precisely why businesses that spend months in mandatory negotiation before invoking arbitration need to watch the limitation clock in parallel, and why securing a Section 18 acknowledgement during that negotiation period is valuable even while a formal dispute resolution process is technically still pending. ### Should the register include obligations that run in our favour, not just ones we owe? Yes, and this is often the more commercially valuable half of the exercise. Tracking what the other side owes you, including renewal notice rights you can exercise, audit rights you hold, and payment obligations running in your favour, is what lets you actually enforce the contract rather than only defend against being accused of breaching it. A register that only tracks your own obligations misses half of what the document is worth. ### Can AI reliably extract obligations from a contract without missing anything? AI extraction tools are genuinely useful for a fast first pass across a long document and a large email archive, and they consistently outperform a rushed manual read for coverage. They are not reliable enough, on their own, for the final version of a register you intend to rely on in a dispute, particularly for cross-referenced conditional clauses and for correctly interpreting whether a given email actually varies the contract or is just discussion. Use AI to build the draft register quickly, then have a human who understands the relationship verify every row before it becomes the version of record.