Operations · Litigation Monitoring · Risk Teams
How to Build a Litigation-Monitoring Process (2026)
A one-time litigation check at onboarding tells you about a counterparty on the day you looked. A monitoring process tells you about them over the whole relationship, which is where most of the risk actually lives. A supplier can be clean when you onboard it and a defendant in an insolvency petition a year later. Building a monitoring process means deciding, in advance, what you watch, how often, who acts on a hit, and how you record it, so the work does not depend on one person remembering to search. This page is a practical guide for a risk, credit or procurement team in India to stand up that process. Last verified October 2026.
- The idea: turn a one-time check into a standing control that watches your active counterparties over the whole relationship.
- The five steps: define the watch list, set the search scope, set a risk-based cadence, assign ownership and escalation, and record every cycle.
- Weight it: watch high-exposure relationships closely and the long tail lightly, with an event-driven re-check before renewals and credit increases.
- Honesty: confirm identity on every hit, remember "nothing on record" is not a clean chit, and keep the log as evidence that the control ran.
01Why a process beats a one-time check
Litigation is not a fixed fact; it is a stream of events. New cases are filed, hearings move, orders are passed and matters are disposed, every day, across thousands of forums. A single check captures one frame of that stream. The risk you care about, a lender sliding into insolvency, a vendor hit with a fraud complaint, a borrower's guarantor facing recovery, usually arrives after you onboarded them.
A monitoring process turns the check from an event into a standing control. It also makes the work auditable: you can show what you watched, how often, and what you did when something changed, which matters when a decision is questioned later.
02Step 1: define the watch list
Start with who you watch, not how you search. A good watch list is scoped by relationship, not by convenience:
- Active counterparties that carry live exposure: borrowers, key suppliers, large customers, channel partners, tenants.
- The people behind them, directors, promoters and guarantors, because the risk often attaches to individuals.
- Group and connected entities, where a dispute against a sister company signals trouble.
Record the exact legal names and identifiers, so the search runs against the right identity and not a namesake. Tier the list, so your largest or riskiest relationships get watched more closely than the long tail. For the before-the-deal side of this, see how to add litigation screening to vendor onboarding.
03Step 2: set the scope of the search
Decide which forums you search and which matters you care about. Monitoring everything equally wastes attention, so weight the scope to the exposure:
| Signal | Why it matters | Where it sits |
|---|---|---|
| Insolvency (IBC) | A counterparty in insolvency can stop paying or performing | NCLT and NCLAT |
| Recovery and SARFAESI | Financial pressure from lenders | DRT and DRAT, civil courts |
| Criminal and economic offences | Fraud and conduct risk | Criminal and special courts |
| Large civil and commercial suits | Disputes that can disrupt the business | Civil and commercial courts, arbitration |
| Regulatory and tax matters | Sector and compliance risk | Tribunals and authorities |
Coverage across forums is the thing to get right, because a matter filed in a court you do not watch is invisible to you. See what good litigation-search coverage looks like.
04Step 3: set the cadence
Cadence is how often you re-run the search. The right answer is risk-based, not uniform:
- High-exposure relationships (large borrowers, critical suppliers) warrant frequent scans, for example daily or weekly.
- Medium exposure can be monthly.
- The long tail can be quarterly, with an event-driven re-check before a renewal, a credit increase or a new order.
The point of cadence is to catch a new filing before it becomes your problem, so tie the frequency to how fast a change would hurt you. For the detail, see how often to re-screen counterparties.
05Step 4: assign ownership and escalation
A process without an owner is a to-do that never gets done. Decide, in writing:
- Who runs the scans and keeps the watch list current as relationships start and end.
- Who triages a hit, confirms it is the right party, and decides if it is material.
- Where a material hit goes, the escalation path to credit, legal or management, and how fast.
Build in a confidence check at the triage step, because a hit on a common name is not yet a fact. For the escalation path, see how to escalate a high-risk litigation finding.
06Step 5: record and review
Keep a record of what you did, because monitoring is also a defence. For each cycle, log the list searched, the forums covered, the date, the hits found, and the action taken. That record lets you show a regulator, an auditor or a court that you had a control and that you ran it.
Review the process itself on a schedule: is the watch list current, is the cadence matched to risk, are hits being triaged and escalated on time? A process that is never reviewed drifts out of date.
Monitoring is not just early warning. Done properly, it is also the evidence that you had a control in place and acted on what it found.
07Where 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.
ClawScore (at clawscore.clawlaw.in) is Claw's litigation and criminal-risk intelligence service, and its Constant Monitoring is built for exactly this process. You give it a watch list of counterparties and their directors, promoters and guarantors, and it scans them across 9,102 courts, benches and forums on a daily, weekly or monthly cadence, reporting New filings, Changed movement and Closed disposals so your team sees what moved since the last cycle. Each name can be pulled as a scored Excel workbook with a Summary and a ClawScore risk band (Clean, Low, Moderate or High), a Matters sheet, a Related parties sheet and a Coverage sheet showing what was searched, and every finding carries a match confidence so a common-name hit is flagged for a human check rather than assumed. Results return in under 5 seconds, judgment search spans 30 crore+ judgments with Supreme Court decisions from 1950 and High Court decisions from 1990, and Claw does not use your searched names or documents to train its AI models. The output is a risk input, not a verdict: "nothing on record" means nothing was found in these registries on the date searched under the names searched, a pending or criminal matter is not proof of guilt, and the workbook is not legal advice and not a credit score.
To build the search layer under your monitoring process, start with a case search across Indian courts by party name across every forum at once.
08Sources and further reading
- eCourts (district and High Court case status): ecourts.gov.in
- National Judicial Data Grid (official pendency data): njdg.ecourts.gov.in
- Insolvency and Bankruptcy Board of India: ibbi.gov.in
- Claw: clawlaw.in
This page is general information for an Indian B2B audience, not legal advice. A monitoring process supports a risk decision; it does not replace counsel on any specific matter.
09Frequently asked questions
Why is a monitoring process better than a one-time litigation check?
A one-time check captures a counterparty on the day you looked, but most risk arrives afterwards: a supplier is clean at onboarding and a defendant in an insolvency petition a year later. A process watches active relationships over time, catches new filings early, and leaves an auditable record that you had a control and acted on it.
Who should be on the watch list?
Your active counterparties that carry live exposure, such as borrowers, key suppliers, large customers, channel partners and tenants, plus the directors, promoters and guarantors behind them and any group or connected entities. Record exact legal names and identifiers so the search runs against the right identity, and tier the list by risk.
How often should the search run?
Make the cadence risk-based, not uniform. Scan high-exposure relationships frequently, for example daily or weekly, medium exposure monthly, and the long tail quarterly, with an event-driven re-check before a renewal, a credit increase or a new order. Tie the frequency to how fast a change would hurt you.
Who acts on a hit?
Assign it in writing. One role runs the scans and keeps the watch list current, one triages each hit by confirming it is the right party and judging whether it is material, and a defined escalation path sends material hits to credit, legal or management within a set time. Build a confidence check into triage so a common-name hit is verified before it is treated as fact.
What records should the process keep?
For each cycle, log the list searched, the forums covered, the date, the hits found and the action taken. That record is the evidence that you had a monitoring control and ran it, which matters to auditors, regulators and courts. Review the process itself on a schedule so the watch list and cadence stay matched to risk.