,

Litigation Portfolio Monitoring: Watch 20 Court Cases at Once With monitor_portfolio

How legal teams, lenders and law firms watch a whole litigation portfolio with the eCourtsIndia monitor_portfolio tool: key facts for up to 20 CNRs per call, stale warnings, latest orders and a weekly routine that scales to hundreds of matters.

Cover: watch a litigation portfolio, key facts for up to 20 Indian court cases in one call with monitor_portfolio

Watch a whole litigation portfolio, 20 cases at a time

Anyone responsible for many cases asks the same question every week: did anything change? The monitor_portfolio tool on the eCourtsIndia MCP server takes up to 20 CNRs and returns the key facts for each, so an assistant can tell you what moved, what is listed next and which records need a refresh.

Keep your portfolio as a list of CNRs. Run monitor_portfolio on batches of 20, compare with last week, and refresh or read only the cases that changed.

Live run on four commercial matters, 15 November 2026.

Last updated: 15 November 2026

Key takeaways

  • Up to 20 CNRs per call: status, filing date, last and next hearing, last order and its file, order and application counts, and a stale warning.
  • Fast: 2 to 10 seconds depending on the number of cases, because it reads our stored copy in parallel.
  • Stale warnings: a case whose next date has passed is flagged so you refresh it before you report on it.
  • Diffs are yours: the tool returns facts; you or your assistant compare them with the last run.
  • Scales by batching: 200 matters is ten calls.

What does monitor_portfolio return?

One structured record per CNR with the facts that change.

FieldWhat it tells you
title, court, judgesWhich matter and where
status, filingDatePending or disposed, and how old it is
lastHearingDate, nextHearingDateWhat happened last and what is next
lastOrderDate, lastOrderFileWhether a new order has been uploaded, and its filename
orderCount, iaCountActivity on the case, including interlocutory applications
staleWarning, dateModifiedWhether to refresh before relying on the record
monitor_portfolio fields as returned by the eCourts MCP server (v4.54) on 15 November 2026.

What did a real run show?

Four commercial matters at Patiala House, all listed for the same Monday, with very different histories.

We took four CNRs from the Patiala House docket for 16 November 2026 and ran them through monitor_portfolio in one call. All four were pending and listed for 16 November, and none carried a stale warning. Beyond that they had little in common. Two suits by banks, UCO Bank and Deutsche Bank AG, were filed in 2024 and had 12 and 10 orders. A suit against United India Insurance had been in the system since September 2003 with 41 orders, and a State Trading Corporation suit since October 2009 with 31.

That spread is the point of portfolio monitoring. A list of matter names says nothing about which ones are moving. A table of last order dates, order counts and filing years tells a general counsel in a minute which matters need attention and which are simply old.

What weekly routine works?

  1. Keep the portfolio as a list of CNRs with your own matter reference beside each.
  2. Every week, run monitor_portfolio in batches of 20.
  3. Refresh any case with a stale warning using the Case Refresh API or bulk_refresh_cases, then run it again.
  4. Compare with last week: new last order date, new next date, new status, more applications.
  5. For each changed case, read the newest order with the Court Order Summary API and write one line for the report.

With an assistant, the routine becomes a single prompt: “Here are our 60 CNRs. Check them, refresh any that are stale, and give me a table of what changed since last week with a one-line note on each new order.” Our general counsel portfolio guide shows a fuller version.

Who should use it?

  • In-house legal teams reporting litigation exposure to management or the board.
  • Lenders and collection agencies tracking recovery suits and cheque-bounce complaints.
  • Law firms giving clients a weekly status note without opening every case.
  • Individual advocates who want a Monday view of their own matters; the lawyer dashboard on ecourtsindia.com does the same without code.

How much changes in a portfolio in a month?

Less than people fear, but more than they track. Of the 8,37,52,146 records marked pending in our index on 15 November 2026, 1,34,46,692 (16%) had a hearing in the previous 30 days. At the other end, 1,08,98,781 (13%) had not had a recorded hearing for more than a year. In the same 30 days, our index recorded 4,29,292 cases as decided, a figure that keeps rising as court records are refreshed.

Pending records in our indexCountShare of pending
Hearing in the last 30 days (16 Oct to 15 Nov 2026)1,34,46,69216%
No recorded hearing for more than a year1,08,98,78113%
All records marked pending8,37,52,146100%
eCourtsIndia index, all court levels, read 15 November 2026. Decisions in the last 30 days: 4,29,292 recorded so far.

For a portfolio manager that suggests a useful rule of thumb. In a typical month, perhaps one case in six will have a hearing, and one in eight may have gone quiet for a year or more. The second group is the one that slips through: nobody checks a matter that never seems to move, until an ex parte order or a dismissal for default turns up.

What does weekly monitoring cost?

Portfolio sizemonitor_portfolio calls a weekCase reads a month (4 weeks)Monthly cost at the base rate
50 cases3200About ₹100
200 cases10800About ₹400
1,000 cases504,000About ₹2,000
5,000 cases25020,000About ₹10,000
Budgeted as case reads at ₹0.50 each at the Enterprise base rate, before GST. Add ₹0.05 for each stale case you refresh.

Refreshes add very little. If a third of a 200-case portfolio shows a stale warning each week, that is about 270 refreshes a month at ₹0.05, or ₹13.50. The order summaries for the cases that actually changed are the bigger line: at ₹2.50 each, 30 new orders a month cost ₹75.

What goes in the weekly report?

ColumnExampleWhy
Your matter referenceLIT-2024-118Links the court record to your internal file
CNR16-character case numberLets anyone open the same record
What changedNew order dated 12 Nov; next date moved to 9 JanThe only thing most readers need
One-line order note“Written statement taken on record; matter adjourned for evidence”From the order summary, checked against the order
Next date and stage9 Jan 2027, evidenceSo the team can plan
Action ownerCounsel or internal ownerSo something happens
A suggested report layout. Unchanged matters can go in a single line at the end.

Alert rules worth automating

  • New order uploaded: the last order date changed since last week. Summarise and send.
  • Status changed: pending to disposed, or the reverse after a restoration. Read the final order the same day.
  • Next date passed with no update: the stale warning. Refresh before anyone reports on it.
  • Gone quiet: no hearing for 180 days. Ask counsel why.
  • New interlocutory application: the application count went up. Someone has asked the court for something.

These rules are the same whether you run them through an assistant on the MCP server or in code on the REST API. For district courts, adding a daily listing check by CNR turns a weekly report into a same-day alert; our guide to cause-list integration for practice software shows how.

Turning the weekly view into a board report

Boards and audit committees rarely want a case list. They want exposure: how many matters, of what kind, at what stage, with what has changed since the last meeting. A quarterly roll-up of the weekly reports gives exactly that: counts by case type and court, matters filed and disposed in the quarter, the five oldest pending matters and why, and every new order that changed the company’s position. Because each line carries a CNR, the auditors can open the same record and check it, which is more than a spreadsheet maintained by hand can offer. For listed companies, our guide to litigation disclosure under SEBI LODR covers what has to be reported to the exchanges.

What does it cost, and what about code?

monitor_portfolio reads our stored case records, so budget for it as you would for case reads (₹0.50 per case at the Enterprise base rate on the REST API), plus refreshes at ₹0.05 for the stale ones. Developers who want the same routine without an assistant build it from the REST endpoints: case detail for each CNR, bulk refresh for stale ones and the CNR cause-list batch for upcoming district court listings. Check your exact charges in your account’s usage page, since MCP calls draw from the same credit balance as the API.

Sources and method

  • eCourts MCP monitor_portfolio on CNRs DLND010071122024, DLND010048502024, DLND010146062016 and DLND010000852009, 15 November 2026.
  • REST prices from ecourtsindia.com/api/pricing, read 15 November 2026. MCP pricing is not listed separately on that page.

Frequently asked questions

How can I monitor many court cases at once?

Keep a list of CNRs and run the eCourtsIndia monitor_portfolio tool on up to 20 at a time. It returns status, hearing dates, the latest order and a stale warning for each.

How many cases can monitor_portfolio check in one call?

Up to 20 CNRs. For larger portfolios, run it in batches of 20; 200 matters is ten calls.

Does it tell me what changed?

It returns the current facts. Your assistant or code compares them with the last run to find new orders, new dates and status changes.

What is a stale warning?

A flag on a case whose next hearing date has already passed. Refresh that case from the court before relying on the record.

Can I do the same without an AI assistant?

Yes. Use the REST API: case detail by CNR, bulk refresh for stale cases and the CNR cause-list batch for district court listings.

How often do pending cases get a hearing?

In our index, 16% of pending records had a hearing in the 30 days to 15 November 2026, and 13% had no recorded hearing for over a year.

What does it cost to monitor 200 cases every week?

About ₹400 a month at the Enterprise base rate, budgeted as case reads at ₹0.50, plus a few rupees for refreshing stale cases.

Which changes should trigger an alert?

A new order, a status change, a passed next date with no update, no hearing for six months, and a new interlocutory application.

Important: This guide is published by Billion Insights Ventures Pvt. Ltd., the company behind eCourtsIndia. It is not legal advice. Court data shown here is a copy of public court records as read on the date stated at the top of this page and is not a certified copy. A name match is not identity, a pending case is not guilt, and a disposed case is a status, not an outcome. Prices, limits, counts and examples were checked on that date and can change. eCourtsIndia is a private legal-technology platform and is not affiliated with any court, the e-Committee of the Supreme Court or the Government of India. Found an error? Write to support@ecourtsindia.com.

eCourtsIndia is a private legal-technology platform. It is not affiliated with, associated with, or endorsed by the Government of India, the Supreme Court of India or its e-Committee, or any court. Official case information is published on ecourts.gov.in. Always verify details against official court records or certified copies. This article is general information, not legal advice. Spotted an error? Write to support@ecourtsindia.com.

Search 35 crore+ Indian court case records, free

One search across the Supreme Court, all 25 High Courts, district courts and 18 tribunal and commission types. Hearing alerts, AI summaries and an API for developers.