In most Indian boardrooms the litigation update is a single slide near the back of the pack. It carries a count of pending matters, a total claim value that everyone privately believes is inflated, and a short list of significant cases with a one line status. It is presented in four minutes, generates two questions, and is approved. Nobody in the room, including the person presenting it, treats it as a live risk instrument. It is a compliance artefact.
Then a quarter arrives where it matters. An arbitral award goes against the company for an amount nobody had provisioned. A regulator passes an order that the auditors want disclosed. A dispute that appeared on the slide as pending, next date awaited turns out to have been decided nine weeks earlier. At that point the board asks a question the general counsel has to answer immediately and precisely: what else is on this list that we do not actually understand.
This article is about building a litigation report that can survive that question. Not a longer report. A report with a stated basis, a register that is genuinely current, and an honest treatment of the gap between what the company has provided for, what it has disclosed as contingent, and what it simply does not yet know.
The argument
A litigation register goes stale because it is maintained by asking people. Business heads are asked once a quarter, external counsel are asked before the board meeting, and the answers are compiled by someone with no independent way to check them. The court record moves continuously and the register moves quarterly, so the register is wrong by construction, not by negligence. Automation has made that gap closable, which is precisely what turns a stale register from an operational nuisance into a governance failure.
What the Board Is Actually Asking
Boards do not want a case list. Directors are not going to read four hundred rows, and presenting them is a way of appearing thorough while communicating nothing. A board has four questions, and a good report answers those four in order.
Could any of this hurt us badly
Is there a single matter, or a correlated group of matters, capable of a loss that would be material to the balance sheet, disrupt operations, or affect the ability to continue a line of business. This is a question about tail risk, not about totals, and a report organised by claim value will usually bury it.
Is the picture getting better or worse
Direction over time, not a snapshot. Filings against the company per quarter, disposals per quarter, the age profile of the portfolio, and external spend. A flat count can conceal a portfolio that is turning over rapidly or one that has not moved in three years.
Are we provisioned honestly
How the accounting treatment lines up with the legal assessment, where the two diverge, and why. This is where the board's interest and the auditor's interest converge, and where a report that avoids the subject is most conspicuous.
Is anything about to require disclosure
For a listed company especially, whether any matter is approaching an event that triggers a market disclosure obligation or a Board's report item, so that the board is not learning about it at the same time as the market.
A report built around those four questions is shorter than the one most companies produce and considerably harder to write, because it requires judgement rather than compilation.
Materiality That Is Stated, Not Assumed
Every litigation report applies a materiality filter. Very few state it. That is the most common defect in the entire exercise, because an unstated threshold cannot be challenged, cannot be applied consistently by whoever produces the report next quarter, and cannot be defended afterwards when someone asks why a matter was not escalated.
Materiality for litigation reporting is not one number. It is a set of tests, and a matter reaches the board if it crosses any of them.
- Quantitative. A claim value threshold, ideally expressed against a base the board already uses, such as a percentage of turnover, net worth or profit, rather than an absolute rupee figure that ages badly. For listed entities, align this deliberately with the quantitative materiality framework the company has adopted for its disclosure policy under the listing regulations rather than inventing a parallel standard.
- Qualitative regardless of value. Any criminal proceeding naming a director or key managerial person. Any matter challenging a licence, approval or the right to operate. Any regulatory or enforcement proceeding. Any matter where an injunction affects operations. Any dispute with a customer or supplier who is individually material to revenue or supply.
- Precedential. A small claim that will decide an issue replicated across many similar contracts, employees or customers. A one lakh rupee dispute that governs a clause in four thousand agreements is a material matter that no value threshold will catch.
- Reputational. Matters likely to attract public attention, involve allegations about conduct rather than commercial disagreement, or concern subject matter the company has publicly committed itself on.
- Aggregate. A cluster of individually immaterial matters arising from the same root cause, reported as one item with a count, because that is what it actually is.
Write the threshold down and apply it to the exclusions too
A materiality basis is only useful if the report also says what it excluded. A line stating that the report covers all matters above the stated thresholds and that a further stated number of routine matters below them are tracked in the register is worth more than three extra pages of detail. It tells the board what it is not seeing, which is the only way a board can decide whether it wants to see it.
The Provisioning Conversation With Finance and the Auditors
Litigation is one of the few areas where the legal function's judgement enters the financial statements directly. Under Indian accounting standards, a present obligation arising from a past event that is probable and can be reliably estimated is provided for, while an obligation that is possible rather than probable, or that cannot be reliably measured, is disclosed as a contingent liability. Both descriptions rest on an assessment that only the legal team can supply, and auditors are required to perform their own procedures around litigation and claims, which in practice means asking legal for a written view and, frequently, seeking confirmation from external counsel.
The friction is structural. Legal is trained to avoid characterising a matter as likely to be lost, because that assessment can surface in the proceeding itself and because litigators are professionally reluctant to concede outcomes. Finance needs a probability characterisation to close the books. Auditors need evidence supporting whichever characterisation was used. The result, in many companies, is a stand-off resolved by everyone agreeing that everything is possible rather than probable, which produces a clean provision line and a contingent liability note that grows every year without explanation.
A contingent liability note that only ever grows is not a disclosure. It is an admission that nobody is assessing outcomes.
The workable answer is to separate the internal assessment from the external position. The legal team maintains a candid internal view for each material matter, held with appropriate confidentiality, expressing a range rather than a point estimate and the key uncertainty driving it. Finance works from that. What appears in the accounts follows the accounting standard, and what appears in the board pack explains where legal and accounting judgement diverge and why. A board that understands that a matter is carried as contingent because quantification is genuinely unreliable, rather than because nobody wanted to make the call, is a board that has been properly informed.
| Category | What it means in practice | What the board pack should say |
|---|---|---|
| Provided for | The company assesses an outflow as probable and can estimate it reliably. The number is in the accounts. | The amount, the basis of the estimate, and whether it has moved since the last report, with the reason for any movement. |
| Contingent, quantified | An outflow is possible but not probable, or probable but not reliably measurable, and a claim amount exists. | The claim value alongside the realistic exposure, which is often far lower. A claim as pleaded is an assertion, not an assessment. |
| Contingent, unquantified | The claim seeks unspecified damages, an injunction, or relief that resists valuation. | The nature of the relief and the operational consequence if granted. Value is the wrong lens for an injunction against your main plant. |
| Recoverable | Exposure covered by insurance, an indemnity from a counterparty, or a back to back contractual position. | The gross exposure and the net, separately, with an honest note on the strength of the recovery. An indemnity from a distressed counterparty is not a recovery. |
| Not yet assessed | Matters recently filed or served, where no view has been formed. | The count and the age. A category that grows quarter on quarter is a resourcing signal, and it belongs in front of the board rather than in a footnote. |
Keeping the Register Current
Everything above assumes the underlying register is accurate. In most companies it is not, and the reasons are consistent enough to list.
The common thread is that the register is maintained by asking. Every entry depends on a human being remembering to report an event to someone else. That works for large matters with senior attention and fails everywhere else, which is why registers are usually accurate about the five matters the board already knows and unreliable about the four hundred it does not.
Define the reporting perimeter as entities, not as matters
Write down every legal entity in the group, including dormant ones, joint venture vehicles, and entities acquired in the last three years that may still litigate under a former name. The perimeter is the thing you monitor. A matter-based register can only ever contain what someone already told you about.
Reconcile the register against the public record, at least quarterly
Search the perimeter across the forums your business actually touches and compare the result against the register. Expect the first reconciliation to be uncomfortable. The matters it surfaces are not new risks, they are risks you already had and did not know about, which is a materially better position than the alternative.
Put continuous monitoring on the entities, not on individual cases
Tracking known matters catches updates. Monitoring the entity catches the filing you have never heard of, which is the one that damages a board relationship. New filings should reach the general counsel when they appear in the source registries, not at the next quarterly cycle.
Assign a single owner to the register and a single owner to each material matter
The register needs one accountable person who is not the same person as the board pack author, so that accuracy is maintained continuously rather than reconstructed before a meeting. Each material matter needs a named internal owner who holds the assessment, not just a firm name.
State the as-at date and the coverage on the report itself
Every litigation report should carry the date the underlying data was refreshed, the entities covered, and the forums searched. This is not defensive paperwork. It is what allows a director to calibrate how much weight the page can bear, and it is what protects the person who wrote it.
The Disclosure Interface
For a listed company, litigation reporting has a second audience. Material developments in litigation and regulatory proceedings can trigger disclosure obligations to the stock exchanges under the listing regulations, on short timelines, judged against the company's own materiality policy. Separately, the Board's report is required to record details of significant and material orders passed by regulators, courts or tribunals that impact the going concern status and the company's operations, and the auditor is required to report on whether the impact of pending litigation on the financial position has been disclosed. The precise contours of each obligation should be confirmed against the provisions and the company's own policy as they currently stand.
The practical consequence is a timing problem rather than a drafting problem. A disclosure clock can start when an order is passed, and an order can be passed on a day when nobody from the company was in court and external counsel is travelling. A company whose knowledge of its own proceedings depends entirely on being told is a company whose disclosure timeline starts whenever the telling happens. That is a governance exposure of a quite different character from the underlying dispute, and it is one of the strongest practical arguments for monitoring the record directly.
The failure that ends careers, and the one that does not
Losing a case is a business outcome. Boards absorb business outcomes. Telling a board that a matter is pending when it was decided against the company two months earlier is a different kind of failure, and it is the one that permanently changes how every future report from the legal function is read. The distinction is worth being blunt about internally, because it explains why register hygiene deserves budget and attention that the underlying matters may not.
Where CourtMesh Fits
The reconciliation and monitoring steps above used to be disproportionate for anything but the largest legal teams, because they meant searching a dozen portals per entity per quarter. CourtMesh reduces that to a query. Unified search covers the Supreme Court, all 25 High Courts, the District Courts and the tribunals over a corpus of roughly 310 million cases drawn only from official government portals, so a group's entity perimeter can be run as one exercise rather than forum by forum.
A private organisation-scoped watchlist is the piece that changes the register from a quarterly reconstruction into a live record. Monitor your own entities and be alerted when a new matter surfaces against them in the source registries. Only your team sees what you are watching. AI case analysis helps with reading the volume of orders a large portfolio generates, which is where the time goes once retrieval stops being the bottleneck. And counterparty litigation and insolvency screening answers the adjacent question a board increasingly asks, which is whether the parties on the other side of your material disputes and contracts are themselves under stress.
Two limits, said plainly. Indian court publication is uneven and often late, so no system can promise that every matter is present, and a nil result is never proof of a clean record. And none of this produces the assessment: a tool can tell you an order was passed, it cannot tell you what to provide for. The judgement stays with the general counsel, which is exactly where a board wants it.
Bring a register the board can rely on
A litigation report is only as good as the register underneath it, and a register maintained by asking people once a quarter is stale before it is printed. CourtMesh lets an in-house team reconcile its entity perimeter against the public record across the Supreme Court, all 25 High Courts, the District Courts and the tribunals, and keep a private watch so that new filings surface when they appear rather than at the next board cycle. It will not tell you what to provide for. It will make sure the page in front of your directors describes the portfolio you actually have.
Explore CourtMesh
