How to Track Litigation Across Multiple Business Units in India

How To · Legal Operations

Updated for 2026 · Claw Editorial

When a company grows past one office, litigation stops living in one place. A manufacturing unit in Pune, a branch office in Kolkata, and a regional sales team in Hyderabad can each be facing their own cases, in their own courts, handled by their own local counsel, and the head office often finds out about a hearing only after it has happened. This guide sets out a practical way to build one reliable, company-wide view of litigation across business units, without depending on every unit remembering to report in.

01Why tracking litigation across business units gets hard fast

The moment a company has more than one business unit, location, or subsidiary, litigation visibility breaks down in a few predictable ways.

Ownership is fragmented

Each plant, branch, or regional office often engages its own local advocate, because that is who is closest to the local court. That is usually a sensible choice for the case itself, but it means the head office legal team has no single point of contact and no single source of truth. Every unit is doing its own thing, in its own way.

There is no single view

Without a shared system, the general counsel or legal head only sees the full picture when someone compiles it, usually by emailing every unit and waiting for replies. This is slow, it goes stale the moment it is sent, and it depends entirely on people remembering to report accurately.

Escalation happens too late

A show cause notice or an adverse order at a small regional matter can turn into a major exposure for the whole company. If that information sits in one unit's inbox and never reaches the head office, the company loses the chance to intervene early, brief senior counsel, or flag the matter to the board and auditors in time.

Compliance and reporting suffer

Board reporting, statutory disclosures, and insurance or audit requirements all need an accurate, current list of pending litigation across the group. If that list has to be manually stitched together from multiple units each time, it is almost always out of date by the time it reaches the board.

02What a good cross-unit tracking system looks like

Before picking a process or a tool, it helps to know what "good" actually looks like. A workable system has four properties.

• One shared record per matter: every case, wherever it sits, is logged in one place using a consistent format, not scattered across local files, WhatsApp threads, and personal notebooks.
• Automatic, not manual, updates: hearing dates, orders, and status changes should flow in without depending on a busy local advocate or unit head remembering to send an email.
• Roll-up visibility: the head office should be able to see litigation by business unit, by court, by exposure, or by stage, not just as one long undifferentiated list.
• Clear ownership and alerts: every matter has a named owner at the unit level, and the next action or deadline should trigger a reminder automatically, so nothing depends purely on memory.

The real risk in multi-unit litigation is not any single case. It is the one matter that never gets reported up until it is too late to act on.

03Step-by-step: building the tracking process

Here is a practical sequence for building this from scratch, or fixing a process that has grown messy over time.

Step 1: List every business unit and its local counsel

Start with a simple inventory: every plant, branch, subsidiary, and regional office, and who represents the company legally at each one. This sounds basic, but in many companies this list itself does not exist in one place, and building it is often the first useful outcome of the whole exercise.

Step 2: Standardise how a matter gets logged

Agree on a single format for recording a case: case number, court, business unit, subject matter, opposing party, current stage, next hearing date, and the person responsible. If every unit records this information differently, or not at all, a roll-up view is impossible later.

Step 3: Pull existing matters into one central record

Ask every unit to submit their current pending matters against the standard format, and consolidate them centrally. This first pass will usually be incomplete and it will take follow-up, but it establishes the baseline the ongoing process builds on.

Step 4: Set up automatic status and hearing updates

This is the step that most manual processes fail at. Relying on a unit to email an update after every hearing does not scale once you have more than a handful of units. Automated case tracking that pulls hearing dates and orders directly from court records, and pushes alerts to the responsible person, removes the dependence on manual reporting.

Step 5: Build the roll-up views the business actually needs

Once matters are logged centrally, set up the views leadership actually uses: litigation by business unit, by exposure value, by stage, and matters with a hearing in the next two weeks. A single flat list is not useful to a general counsel managing risk across a group; a filtered, current view is.

Step 6: Put a review cadence in place

A tracking system only stays accurate if someone owns it. Set a monthly or quarterly review where each unit's open matters are checked against the central record, so drift gets corrected before it becomes a real gap.

04Common pitfalls to avoid

• Treating this as a one-time exercise: a spreadsheet built once and never updated is worse than no system, because it creates false confidence.
• Letting each unit keep its own format: if the data is not standard, it cannot be rolled up or compared, and someone ends up manually re-typing everything anyway.
• No named owner per matter: a case with no clear owner at the unit level is the one most likely to be missed at the next hearing.
• Relying only on local counsel to report in: local advocates are focused on their own matter, not on your company's group-wide reporting needs. Build the process so updates do not depend solely on them remembering.

Getting these basics right is largely a legal operations problem, not a legal one. For a broader look at how legal operations functions in Indian companies, see what legal operations means in India.

05Manual process vs a unified system

Companies typically move through three stages as the number of business units grows.

The pattern is consistent: the more business units a company has, the more a manual, email-based process costs in missed updates and late escalations, and the more a purpose-built system pays for itself.

06Where Claw fits

Claw is an all-in-one legaltech platform for Indian advocates, law firms, and corporate legal teams, combining AI-based case search, an AI legal assistant (Legal GPT), case management, and compliance automation across all Indian courts and tribunals.

For the specific problem in this guide, Claw's case management and tracking covers 8200 plus courts across India, including all states, tribunals, and district courts, alongside the Supreme Court. That matters directly for multi-unit litigation, because it means matters filed by different local counsel in different courts can still be pulled into one central view without asking every unit to manually report in. Claw tracks matters automatically, sends hearing and deadline alerts by WhatsApp and email, reads court orders to schedule the next action automatically, and produces MIS-style reports that a general counsel can use for exactly the kind of roll-up view described in Step 5 above. For teams building out this kind of central legal operations view more broadly, see how litigation intelligence supports legal operations.

07Sources and further reading

Background references used in this guide:

• Ministry of Corporate Affairs (corporate filings and compliance context): mca.gov.in
• Supreme Court of India (official case and cause list reference): sci.gov.in
• Claw: clawlaw.in

08Frequently asked questions