Explainer · Continuous Monitoring
What Continuous Litigation Monitoring Is (2026)
Most people search the courts the way they search anything: once, when they need an answer. Continuous litigation monitoring is a different habit. Instead of asking "what cases exist against this name today" and moving on, it asks the same question again and again, on a schedule, and tells you only what has changed since last time. The word that matters is continuous. The search does not stop when you get the first answer; it keeps running, so a case filed next month is caught next month, not whenever someone happens to look again. This explainer, for risk, credit, legal and compliance teams in India, sets out what continuous litigation monitoring actually is, the parts that make it work, who relies on it, and how it differs from a one-off search and from watching the courts by hand. Last verified October 2026.
- What it is: scheduled re-searching of a fixed set of names across the courts, reporting only what has changed since the last scan.
- "Continuous": reliably repeating on a schedule, not a live feed; a case surfaces once the portal publishes it and the next scan runs.
- Five components: a watchlist, a baseline, a cadence, a comparison, and alerts.
- Who uses it: lenders, buyers, legal teams, investors and insurers, anyone with exposure that lasts beyond one transaction.
- Honesty: not real-time, bounded by coverage and names, and a risk input, not a credit score or legal advice.
01The short answer
Continuous litigation monitoring is the ongoing practice of searching a fixed set of names across the courts and tribunals on a repeating schedule and reporting only what has changed since the last scan. It turns a one-time question (what cases exist against this name) into a standing one (what has changed since I last looked). The point is to catch a new case, a new order or a disposal as it appears, rather than discovering it late at an occasional manual check.
It is built from a small set of parts: a watchlist of names, a baseline of what already exists, a cadence for how often to re-scan, a comparison that spots the change, and alerts that deliver it. Remove any one and it stops being continuous monitoring and becomes a repeated manual search.
02What "continuous" means here
"Continuous" does not mean a live feed that pings the instant a case is filed. Indian court data does not work that way; filings become findable only once a court portal publishes them. What continuous means in practice is reliably repeating: the same search runs on a set schedule, without someone remembering to do it, so the gap between a case appearing and you knowing about it is short and predictable rather than long and accidental.
That distinction matters. A relationship you entered a year ago, a loan, a supply contract, a portfolio holding, keeps generating legal risk the whole time it lasts. Continuous monitoring is what keeps your picture of that risk current, instead of frozen at the moment you last happened to check. For the contrast with a single search, see monitoring versus a one-time search.
03The components that make it work
Continuous monitoring is an assembly of five parts, each doing one job:
| Component | Its job |
|---|---|
| Watchlist | The fixed set of names being monitored, including related parties |
| Baseline | The starting picture of what already exists, so new can be told from old |
| Cadence | How often the search re-runs: daily, weekly or monthly |
| Comparison | Lining up each scan against the last to find the difference |
| Alerts | Delivering the change to the person who can act on it |
The baseline is the part people forget. Without it, the first scan has nothing to compare against, so every existing case looks new. For how the comparison catches a filing, see how constant monitoring catches new filings.
04Who uses it
Continuous monitoring is for anyone whose exposure to a name lasts beyond a single transaction:
- Lenders, watching borrowers and guarantors for recovery suits and insolvency across a live loan book.
- Buyers and procurement teams, watching key suppliers and distributors for disputes and solvency stress.
- Legal teams, tracking their own portfolio of cases for new orders and hearings.
- Investors and insurers, watching portfolio companies and insured parties over the life of the exposure.
If your exposure to a name lasts, a one-time search goes stale the day after you run it. Continuous monitoring is what keeps it from going out of date.
05How it differs from manual watching
Many teams already "monitor" by having someone re-check a few portals every so often. Continuous monitoring differs in three ways that matter:
- It is reliable. The scan runs on schedule whether or not anyone remembers, so names do not slip through because a person was busy.
- It scales. A person can re-check a handful of names; a monitoring setup can re-check thousands, each across many forums, on the same schedule.
- It reports only change. Instead of re-reading whole case lists, the team sees a short list of what is new, changed or closed, which is the only part that needs attention.
The result is the same question answered far more often and far more consistently than a human can sustain, which is the whole value of making it continuous.
06The honest limits
Continuous monitoring narrows blind spots; it does not remove them:
- Not real-time. A case surfaces on the next scheduled scan after the portal publishes it. Detection lag is the portal delay plus the time to the next scan.
- Bounded by coverage and names. It catches a case only in a forum it searches, under a name on the watchlist. "Nothing new" means nothing matched, not that nothing was filed.
- A risk input, not a verdict. A new filing is an allegation to look into, a common-name hit needs a human check, and the output is not a credit score or legal advice.
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 risk intelligence service, and its Constant Monitoring is continuous litigation monitoring assembled in one place. The first pass records your baseline across 9,102 courts, benches and forums plus insolvency filings at the NCLT and NCLAT in a dated, scored Excel workbook: a Summary with a risk band (Clean, Low, Moderate or High), a Matters sheet, a Related parties sheet that widens the watchlist to directors, promoters and guarantors, and a Coverage sheet showing what was searched. From then on it re-scans the watchlist on a daily, weekly or monthly cadence, compares each scan against the stored state, and reports only what is New, Changed or Closed, with alerts. Every finding carries a match confidence, 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 watchlist or documents to train its AI models. Constant Monitoring is priced at Rs 300, Rs 600 or Rs 3,000 per entity per month by cadence and depth, with one-time searches from Rs 500. "Nothing new" means nothing matched your watchlist in the forums covered on the scan date, a common-name hit needs a human check, and the output is a risk input, not a regulated credit score and not legal advice.
To record the baseline that continuous monitoring tracks against, run a case search across Indian courts by name across every forum at once.
08Sources and further reading
- eCourts (court case status): ecourts.gov.in
- National Judicial Data Grid (official pendency data): njdg.ecourts.gov.in
- Insolvency and Bankruptcy Board of India (insolvency records): ibbi.gov.in
- Claw: clawlaw.in
This explainer is general information, not legal advice. Confirm any matter that affects a decision against the official court record before you act.
09Frequently asked questions
What is continuous litigation monitoring?
It is the ongoing practice of searching a fixed set of names across Indian courts and tribunals on a repeating schedule and reporting only what has changed since the last scan. It turns a one-time question into a standing one, so new cases, orders and disposals surface as they appear rather than at an occasional manual check.
Does "continuous" mean real-time alerts?
No. Court data becomes findable only once a portal publishes it, so continuous means reliably repeating on a schedule, not instant. A new case surfaces on the next scheduled scan after the portal publishes it, which keeps the gap between filing and knowing short and predictable rather than long and accidental.
What are the parts of a monitoring setup?
A watchlist of names including related parties, a baseline of what already exists so new can be told from old, a cadence for how often to re-scan, a comparison that finds the difference between scans, and alerts that deliver the change. The baseline is the part most often forgotten, and without it every existing case looks new on the first scan.
How is it different from re-checking the courts myself?
It is reliable, because it runs on schedule whether or not anyone remembers; it scales, because it can re-check thousands of names across many forums rather than a handful; and it reports only change, so the team reads a short list of what is new, changed or closed instead of re-reading whole case lists. It is the same question answered far more often and consistently.
What are the limits of continuous monitoring?
It is not real-time, so detection lags the portal publishing delay plus the time to the next scan. It only catches a case in a forum it searches under a name on the watchlist, so "nothing new" means nothing matched, not that nothing was filed. And a new filing is an allegation to look into; the output is a risk input, not a credit score or legal advice.