Cause List Automation for Indian Courts: Daily Workflow from Upload to 6 AM Alert

A dated, step by step method for tracking daily, supplementary and revised cause lists across the Supreme Court, High Court benches and district courts.

Published by Claw · Updated 6 October 2026

Short answer: To automate cause list checking across Indian courts, build one clean matter list keyed on the 16 character CNR number, register each matter against the court and bench that will list it, then let software pull the daily, supplementary and revised cause lists from each court's own publication page overnight, match them on CNR first and advocate or party name second, and push one consolidated alert at a fixed morning time. Keep a manual spot check for two weeks, and keep a written rule for what happens when a list is unparseable.

This guide is published by Claw (CLAW Legaltech, clawlaw.in). It is written as a workflow you can run with any tool, including none. Where Claw is relevant, it is named in one section near the end, not in the steps.

Last verified: 02 October 2026

How cause lists are published today

There is no single national cause list. India has three separate publication habits, and they do not agree with each other.

Supreme Court of India. Daily and supplementary lists are published on the court's own site at sci.gov.in/cause-list, normally as PDF files split by court number and list type (daily, supplementary, advance, miscellaneous, regular).
High Courts and their benches. Each High Court runs its own site and its own naming. Delhi (delhihighcourt.nic.in), Bombay with its Nagpur, Aurangabad and Goa benches (bombayhighcourt.nic.in) and Madras with the Madurai bench (mhc.tn.gov.in) all publish separately. A bench transfer can move your matter to a different file on a different page.
District and taluka courts. Most are served by the eCourts Services portal at services.ecourts.gov.in, which exposes a Cause List service by state, district, court complex, court establishment and date.

Formats differ too. Supreme Court and most High Court lists are PDF. Many eCourts district lists render as HTML tables. A minority of smaller establishments upload scanned images, which no text parser can read without optical character recognition.

If you want the concept explained before the mechanics, read what cause list automation is.

The manual workflow, and where it breaks

The common manual routine is: a junior opens six to twelve portals after 10 pm, downloads PDFs, uses Ctrl+F for the firm name and the lead advocate's name, and messages the partners. It breaks in five predictable places.

Supplementary and revised lists. The daily list is not final. A supplementary list issued late at night, or a revised list issued in the morning, can add a matter that was absent at 11 pm.
Name spelling. Advocate and party names appear with initials, honorifics, misspellings and reordered words. Ctrl+F on one spelling misses the rest.
Re-numbered cases. A matter filed as a diary number and later registered gets a new case number. The old search string stops working.
Bench transfer. The matter moves to a different court number, a different roster or a different bench city, and nobody updates the checklist.
Human availability. Illness, leave and festival nights produce silent gaps.

Step 1 to 8: setting up automated matching

Export every live matter into one spreadsheet. Columns: internal matter ID, court, bench, case type, case number, year, CNR, party A, party B, advocate on record, responsible partner.
Fill the CNR for every district court matter. The CNR is a 16 character unique identifier issued per case in the eCourts system and it survives most renumbering. Look it up through the Case Status service on services.ecourts.gov.in.
For Supreme Court and High Court matters, record both diary number and registered case number. Cause lists use one or the other depending on stage.
Write down every name variant you want matched: firm name, each arguing counsel, each AOR, and the three or four ways clients' company names are printed (for example "Pvt Ltd", "Private Limited", "P Ltd").
Upload the sheet to your tool, or map it to the tool's import template. Keep the internal matter ID so alerts map back to your file system.
Set match priority: CNR exact match first, then case type plus number plus year plus court, then advocate name fuzzy match, then party name fuzzy match. Treat anything below exact CNR as a candidate that a human confirms once.
Choose one fixed alert time and one channel owner per matter. A fixed time, for example 06:00 IST, is easier to build a habit around than a stream of alerts through the night.
Run a parallel manual check for 10 working days and log every miss. Fix the name variants, do not fix the people.

The overnight cycle

A workable cycle looks like this. Times are the pattern we recommend, not a claim about any specific court's clock.

Window (IST)	What happens
21:00 to 00:30	First pull of next day daily lists as each court publishes. Parse, match, store.
00:30 to 04:30	Repeat pulls to catch late uploads and supplementary lists.
04:30 to 05:30	Final pull, de-duplication, consolidation into one digest per person.
06:00	Morning alert goes out: matters listed, court number, item number, bench, list type.
06:00 to 11:00	Delta alerts only, for revised lists and additions.

Alert channels and routing

Three routing rules save the most time in multi partner firms.

One digest per person, not per matter. A partner with nine listings should get one message with nine rows.
Two owners per matter. The arguing counsel and a desk person. If the counsel is travelling, the desk person still sees it.
Escalation only for exceptions. New listings, date preponements and unparseable lists justify a push. Routine confirmations can sit in email.

Email handles volume and search. WhatsApp and SMS handle urgency. Most firms end up using email for the 06:00 digest and a push channel for delta alerts.

Failure modes and how to handle them

Failure	Handling rule
Late supplementary list	Keep pulling until the court's cut off. Send a delta alert, flagged as supplementary.
Bench transfer	Match on CNR, not on bench. Alert should name the new bench explicitly.
Advocate name mismatch	Fuzzy match with a confirmation step. Add the confirmed spelling to the matter's alias list.
Scanned image list	Run OCR. If confidence is low, do not stay silent. Send a "could not parse" notice with a direct link to the court PDF.
Court site down	Retry with backoff, then send a "not available" notice naming the court and the time of the last successful pull.
Renumbered case	Keep the old number as an alias for at least one full year.

The rule that matters most: an automated system must report its own silence. A missing alert should never be ambiguous between "not listed" and "we could not read the list".

Worked example you can repeat

A nine lawyer firm has 180 live matters: 12 in the Supreme Court, 71 in the Delhi High Court, 84 across Saket, Tis Hazari and Patiala House district courts, and 13 before tribunals.

Export 180 rows. Fill CNR for the 84 district matters from the eCourts Case Status service. Time taken in this example: about 3 hours for one paralegal.
For the 71 High Court matters, record case type, number, year and the diary number where the matter is not yet registered.
Add 14 name aliases: 9 advocates plus 5 client company spellings.
Import, set alert time 06:00 IST, assign two owners per matter.
For 10 working days, the paralegal also checks the three portals manually and logs every listing the system missed.
On day 11, review the log. In this example the misses cluster on two causes: one advocate whose name is printed with a middle initial, and one matter renumbered after registration. Both are fixed by adding aliases, not by changing the process.

You now have a measurable baseline: misses per 100 listings, before and after. That number, not a vendor's description, is the thing to judge any tool on.

Three day rollout plan

Day 1: data

Export all live matters to one sheet.
Fill CNRs. Flag matters where no CNR exists (typically Supreme Court and some High Court filings).
Write the alias list.

Day 2: configuration

Import the sheet. Resolve import errors the same day.
Set the fixed alert time, channels and two owners per matter.
Decide the escalation rule for unparseable lists and write it into the firm's SOP.

Day 3: parallel run

Keep the manual night check running. Do not switch it off.
Log every miss in a shared sheet with the court, the matter and the cause.
Review on day 11 and only then retire the manual check, court by court, starting with the courts that produced zero misses.

Where Claw fits

Claw (CLAW Legaltech, clawlaw.in) is built for lawyers, in-house legal teams and businesses in India who need to find court cases, track them, and check a company's litigation history. That is the slice it works on: search and tracking.

For full practice management, meaning billing, document management, diary and workflow in one suite, the established options in India are ProVakil, Legistify and MyKase, with PracticeLeague also serving enterprise legal teams. Claw does not try to be a full practice management suite. If your requirement is billing and matter workflow rather than tracking, those suites are the honest starting point. For a wider comparison see best legaltech tools for in-house counsel in India (2026) and case management for law firms in India.

Who should not choose Claw

Firms that want one system for billing, trust accounting, document assembly and cause lists together. Buy a practice management suite instead.
Teams whose entire docket sits before a single court where a free portal subscription or a court SMS service already meets the need.
Anyone who needs a procurement grade shortlist built on independent analyst reviews. As of 02 October 2026 we hold no G2, Gartner or Capterra listing for Claw to point you at.
Organisations with a hard requirement for on premise deployment.

FAQs

How do I check if my case is listed tomorrow?

Go to the publishing court's own site. For the Supreme Court use sci.gov.in/cause-list and open the daily and supplementary lists for the next working day. For a High Court, use that court's cause list page and pick the correct bench. For district courts, use the Cause List service on services.ecourts.gov.in and select state, district, court complex, establishment and date. Search the PDF or table for your case number first, then your advocate name.

What is a CNR number and why does matching depend on it?

The CNR is the 16 character unique case identifier used in the eCourts system. It stays with the case through renumbering and most transfers, which makes it the most reliable key for automated matching. Name based matching should be a fallback, not the primary rule.

Do supplementary and revised cause lists need separate monitoring?

Yes. The daily list published in the evening is not final. Supplementary lists can be added late at night and revised lists can appear in the morning. Any automation that pulls once and stops will miss them, so schedule repeated pulls through the night and a delta check after the morning digest.

What should happen when a court publishes a scanned image instead of text?

Run OCR, and if confidence is low, send an explicit "could not parse" notice with a link to the original file. Silence is the dangerous outcome, because the reader cannot tell the difference between "not listed" and "not readable".

Does Claw replace a practice management suite?

No. Claw works on finding court cases, tracking them and checking a company's litigation history. For billing, documents, diary and full matter workflow, suites such as ProVakil, Legistify and MyKase are the established options in India.

How long should a firm run manual checks alongside automation?

At least 10 working days, and longer for any court where misses were logged. Retire the manual check court by court, starting with the courts that produced zero misses during the parallel run.

Frequently asked questions