Limitation Period Tracking for Litigation

Why limitation period tracking is the silent killer of litigation portfolios

A time-barred claim is not a loss you can appeal your way out of. It is a right that has quietly extinguished itself while the file sat in a drawer. Unlike an adverse order, there is no counsel to blame and no strategy that could have saved it - only a date that passed. For general counsel, this is uniquely dangerous because the failure is invisible until it is fatal. A dispute can look perfectly healthy in a case-management system right up to the moment someone realises the window to file closed months earlier.

The exposure is magnified by the sheer variety of limitation periods that coexist in an Indian portfolio. A simple money recovery on a breach of contract carries a three-year period; a suit to recover possession of immovable property runs to twelve years; a challenge to an arbitral award under Section 34 of the Arbitration and Conciliation Act must be brought within three months, extendable by only a further thirty days at the court's discretion. Each of these starts from a different trigger, and a team that applies the wrong period - or the wrong start date - to the wrong claim is building silent liability into its own portfolio.

There is also a reputational and fiduciary dimension. When an in-house team lets a recoverable receivable lapse into time-bar, it is not just a legal miss; it is a write-off the board will ask hard questions about. Limitation discipline is therefore not a back-office chore but a core control that protects the balance sheet.

• A time-barred suit is dismissed under Section 3 regardless of merit and even if the defendant never pleads limitation.
• Different claim types carry radically different periods, from 30 days for certain appeals to 12 years for immovable property.
• The failure is invisible in most tracking systems until the deadline has already passed.
• Lapsed recoverable claims convert directly into balance-sheet write-offs the board will scrutinise.

The anatomy of a limitation period under the Limitation Act 1963

Effective tracking starts with understanding what a limitation period actually is made of. Every period in the Schedule to the Limitation Act 1963 has three moving parts: the description of the suit, application or appeal; the prescribed period of time; and the point from which that time begins to run. Get any one of these wrong and the computed deadline is wrong. The Act also supplies interpretive rules - how to exclude the day from which the period is reckoned, how to treat the last day falling on a court holiday, and when the time consumed in obtaining certified copies is excluded for appeals.

Two mechanisms deserve particular attention because teams routinely misapply them. The first is Section 5, which allows condonation of delay for appeals and applications where sufficient cause is shown - but crucially does not apply to suits. A litigation team that assumes it can always beg forgiveness for a late filing is mistaken the moment the matter is an original suit. The second is Section 18, under which a fresh period of limitation begins each time the debtor makes a written, signed acknowledgment of liability before the original period expires. This is a powerful lever for keeping recovery claims alive, but only if the acknowledgment is captured, dated and proven.

• Every limitation period combines a claim description, a prescribed duration and a start trigger.
• Section 5 condonation covers appeals and applications, not original suits.
• A signed written acknowledgment before expiry restarts the clock under Section 18.
• Part-payment of a debt or interest can also give a fresh period under Section 19.

Cause of action: the trigger that starts the clock

The hardest part of limitation tracking is almost never the arithmetic - it is identifying when the cause of action actually arose. The prescribed period is fixed in the statute, but its start date is a question of fact and law that turns on the specific events of each dispute. For a breach of contract, time typically runs from the date of breach, not the date of the agreement. For recovery of money lent, it may run from when the loan was made or when repayment was demanded, depending on the terms. For a continuing wrong, a fresh cause of action arises each day the wrong continues.

This is where portfolios go wrong at scale. Teams anchor the clock to a convenient, visible date - the invoice date, the contract date, the date a complaint was internally logged - rather than the legally correct accrual event. A dishonoured cheque under Section 138 of the Negotiable Instruments Act is a good illustration of how tightly sequenced these triggers can be: the cause of action for prosecution crystallises only after the statutory demand notice is served within the prescribed window and the drawer fails to pay within the stipulated period, after which the complaint itself must be filed inside a narrow one-month window. Miss the internal sequence and the complaint is liable to be thrown out.

• The prescribed period is fixed by statute, but the start date is fact-specific and often contested.
• Anchoring to the invoice or contract date instead of the true accrual event is the most common tracking error.
• Section 138 NI Act claims require a precisely sequenced notice-and-default chain before the filing window opens.
• Continuing wrongs generate fresh causes of action and need periodic re-assessment.

Where limitation tracking breaks down in real portfolios

In most organisations the failure is not ignorance of the law but the absence of a reliable operating system for it. Limitation dates live in spreadsheets that only one person updates, in email threads with outside counsel, or in the tacit knowledge of a senior partner. When that person is on leave, changes roles or simply overlooks a file, the deadline travels with them. The larger the portfolio and the more it spans jurisdictions, forums and claim types, the more fragile this informal arrangement becomes.

Hand-offs are the classic point of failure. A dispute originates with a business team, moves to internal legal, and is then briefed to an external firm - and at each transfer the accrual date and the computed deadline are re-derived, or worse, assumed. Documents that would establish the true trigger, such as the delivery challan, the last acknowledgment of debt, or the date an award was received, are scattered across inboxes and physical files. Nobody owns the single authoritative deadline, so nobody is accountable when it slips.

The consequences are quantifiable even if rarely measured. Recoverable dues lapse into time-bar and become write-offs; challenges to adverse awards are lost because the ninety-day-plus-thirty window closed; appeals are filed late and burn management attention on condonation applications that should never have been necessary. Each of these is preventable with instrumentation that most teams simply do not have yet.

• Deadlines held in one person's spreadsheet or memory disappear when that person is unavailable.
• Every hand-off between business, in-house and external counsel re-derives or assumes the accrual date.
• Source documents that prove the trigger are scattered and rarely linked to the deadline.
• No single owner of the authoritative deadline means no accountability when it slips.

Building a defensible limitation tracking system

A robust system rests on one principle: every deadline must be computed from documented facts and be reconstructable by anyone who reviews it later. That means capturing, for each claim, the accrual event and the evidence that fixes its date, the applicable limitation provision, the computed expiry, and any events - acknowledgments, part-payments, exclusions - that alter it. When all four are stored together, the deadline stops being a mystery number and becomes a defensible calculation.

The second principle is layered, early warning. A single alert on the expiry date is close to useless, because litigation preparation takes weeks. Effective systems escalate through tiers - an early advisory when a window opens, an operational reminder well before filing must begin, and a hard alert as the margin narrows - with each tier routed to a named owner rather than a shared inbox that everyone assumes someone else is watching. Ownership must be explicit and must survive personnel changes.

The third principle is periodic portfolio review. Latent claims that have not yet been actioned are the ones most likely to lapse, so the system should surface not only imminent deadlines but dormant matters whose windows are quietly closing. A monthly limitation review, driven by a live report rather than a manual trawl, converts limitation from a reactive scramble into a governed process.

• Store the accrual event, its supporting evidence, the applicable provision and the computed expiry together for every claim.
• Use tiered alerts - advisory, operational and hard-deadline - routed to a named owner.
• Recompute deadlines automatically when acknowledgments, part-payments or exclusions are recorded.
• Run a scheduled portfolio review that surfaces dormant claims approaching time-bar.
• Make deadline ownership explicit and ensure it survives staff transitions.

How legal AI transforms limitation and cause-of-action tracking

The reason limitation tracking has resisted automation for so long is that the hard part - identifying the accrual event - is buried in unstructured documents. It sits in the wording of a contract's breach clause, the date stamped on a dishonoured cheque return memo, the covering letter that accompanied an arbitral award, or the last signed acknowledgment in a ledger. Legacy on-premise systems and generic case-management tools track the dates you type into them; they cannot read a document and tell you what date should have been typed.

This is precisely where modern legal AI changes the economics. An AI layer can ingest the underlying documents in a matter, extract the events that plausibly trigger a cause of action, propose the applicable limitation provision, and compute a candidate deadline - all with the source passage linked for a lawyer to verify. Instead of a junior manually reading hundreds of files to find accrual dates, the system surfaces them and asks a qualified reviewer to confirm. The judgment stays with the lawyer; the drudgery and the risk of an overlooked file move to the machine.

Critically, this is augmentation, not replacement. Limitation questions can be genuinely contested, and no responsible team would file or abandon a claim on an unreviewed machine output. The value is in coverage and consistency: nothing slips through unread, every deadline carries its reasoning and its source, and the whole portfolio can be re-scanned the moment a new document - say, a fresh acknowledgment of debt - resets a clock.

• AI extracts candidate accrual events from unstructured documents that manual tracking cannot reach at scale.
• Each computed deadline is linked to the source passage for lawyer verification.
• Judgment on contested limitation questions stays with qualified counsel.
• The portfolio is continuously re-scanned as new documents reset or open limitation windows.

Governance, audit trails and board-level defensibility

For a general counsel, limitation is ultimately a governance question: can you demonstrate to the board, the auditors or a regulator that the organisation has a system to protect its legal rights from lapsing? A defensible answer needs more than good intentions. It needs an audit trail - who computed each deadline, on what basis, who verified it, when it was reviewed, and what alerts were issued and acknowledged. This record turns limitation from an area of unquantified exposure into a controlled process with evidence behind it.

This matters well beyond litigation. Time-barred receivables affect financial reporting; abandoned claims against defaulters intersect with recovery strategy and, in the case of corporate debtors, with the three-year period that governs applications under the Insolvency and Bankruptcy Code. A limitation system that produces clean, reviewable records feeds directly into provisioning decisions, audit responses and board reporting. The same instrumentation that stops a deadline slipping also gives the organisation a truthful, current picture of the enforceability of its entire claim portfolio.

Done well, limitation tracking stops being a source of anxiety and becomes a quiet competitive advantage: the organisation pursues every enforceable right in time, writes off nothing it could have recovered, and can prove at any moment that it is in control of its own litigation clock.

• Maintain an audit trail of who computed, verified and reviewed every deadline.
• Feed limitation status into provisioning, audit responses and board reporting.
• Recognise the three-year period governing IBC applications against corporate debtors.
• Convert limitation from unquantified exposure into a documented, defensible control.