How to Set Up Litigation Alerts and Notifications

How-To Guide · Litigation Alerts

Updated for 2026 · Claw Editorial

Missing a hearing date in India can mean an ex-parte order, a lapsed deadline, or an embarrassing call from a client who saw the cause list before you did. The problem is that Indian courts post cause lists, orders, and next-date updates across dozens of separate portals, and manually checking each one every morning is not practical for any team handling more than a handful of live matters. This guide explains what litigation alerts are, why setting them up correctly is harder than it looks, and how to configure them step by step, whether you use free court portals, a third-party tool, or a combination of both.

01Why missing a hearing is so easy in India

Indian litigation is spread across a fragmented court system where each court publishes its own cause list, through its own portal, on its own schedule. There is no single national system that aggregates updates in real time.

Many courts, many portals

India has the Supreme Court, 25 High Courts, hundreds of district courts, and dozens of tribunals. A team with matters in three different states is checking three different systems every day. There is no unified feed. The volume of portals grows further when you add consumer forums, NCLT benches, labour tribunals, and other specialised forums.

Cause lists change at the last minute

A matter listed for 10 a.m. can be pushed, pulled forward, or dropped from the board the evening before. If you pull the cause list in the afternoon and rely on it for the next morning, you may act on stale information. The risk is not just a missed appearance. It is an ex-parte order or a contempt situation that could have been avoided with one automated check.

Manual checking does not scale

An associate tasked with checking cause lists for 150 matters across five courts will either spend most of the morning on that task alone or will start cutting corners. Neither outcome is acceptable. Alerts fix this by pushing information to you rather than making you go looking for it.

02What a good alert setup actually does

A litigation alert is an automated notification that tells you something has changed in a case you are watching, in time for you to act before a deadline or hearing slips by.

A well-configured alert setup covers at least three types of event:

• Cause-list alerts: your matter has appeared on tomorrow's cause list for a named court.
• Order and judgment alerts: a new order or judgment has been uploaded in your case.
• Next-date alerts: the court has assigned a fresh hearing date for your matter.

More capable systems also push compliance reminders tied to what the court actually said in its order. If the court gave four weeks to file a reply, the reminder is created from the order date automatically, removing the manual diary step that most teams still rely on.

The goal of a litigation alert is simple: no matter should move in court without someone on your team knowing about it before the day is over.

03Step 1: Build a complete matter register

You cannot monitor what you have not listed. Before configuring any alert, compile a complete register of active matters. This is the step most teams skip, and it is why alert setups break down in practice.

For each matter, record the following:

• The court or tribunal name, including the bench if relevant.
• The official case number and year in the format the court uses (for example, W.P.(C) 1234/2024 or the CNR number for eCourts matters).
• The party names exactly as they appear in the court record, since name variations cause missed matches.
• The responsible advocate or team member who should receive alerts for that matter.
• The next known hearing date.

For large portfolios, tag each matter by court and by responsible lawyer. That tagging makes routing in Step 4 much more straightforward. A matter that is not in this register at this stage will be a silent gap in your coverage later.

For how larger in-house teams structure their matter registers and assign ownership systematically, see litigation tracking for in-house legal teams.

04Step 2: Use court portals for basic alerts

India's main court portals offer free basic case alerts. They are a reasonable starting point for very small portfolios, though they have real limitations at scale.

eCourts Services

The eCourts portal covers district courts and some High Courts. You can search by CNR number and register for SMS updates on case status. Visit ecourts.gov.in, enter your CNR number, and use the alert registration option on the case detail page.

Supreme Court of India

The Supreme Court website publishes daily cause lists and judgment uploads. There is no built-in push notification, so teams monitoring Supreme Court matters typically check the cause list directly at sci.gov.in each evening. A dedicated tracking tool (Step 3) automates this check.

High Court portals

Each High Court runs its own portal. Several of the larger High Courts publish daily cause lists and some offer case status SMS services, but coverage and reliability vary considerably between courts. Check the specific portal for every High Court where you have listed matters.

The honest limitation of court portals is that they are fragmented and cover only the courts they belong to. If you have matters across more than two or three courts, managing separate portal registrations becomes a burden faster than most teams expect. Step 3 is the practical answer to that problem.

05Step 3: Add a dedicated tracking tool

For any team with more than a handful of active matters across different courts, a dedicated litigation tracking tool is the practical answer. These tools aggregate cause list and case status data from multiple courts into one place and push alerts through your preferred channel without requiring separate portal registrations for each court.

When evaluating a tool, the key questions are:

• Court coverage: does it cover every specific court and tribunal where your matters are listed? Ask for the list, not just a headline number.
• Alert speed: how quickly does it detect a cause list update or order upload and dispatch the notification?
• Delivery channels: does it support the channels your team actually uses? WhatsApp is increasingly the practical choice for same-day cause list alerts in Indian legal teams.
• Bulk enrollment: can you import your full matter register at once, or must you add matters one by one?
• Compliance features: does it track the deadlines that flow from orders, or only the hearing dates?

Tools active in this space in India include Provakil, LegitQuest, Legalspace, and others. Each differs in court coverage, pricing, and feature depth. For broader context on what the market looks like, see the legal tools landscape in India.

06Step 4: Choose your alert channels

An alert is only useful if the right person sees it in time. The channel you use determines how reliably and quickly that happens.

WhatsApp

WhatsApp is the highest-read channel for Indian legal professionals. A cause list alert sent via WhatsApp the previous evening is typically read that night, giving the responsible lawyer enough time to prepare. For same-day alerts, WhatsApp is generally more reliable in practice than email because it is checked continuously rather than periodically.

Email

Email works well for non-urgent daily digests, order upload notifications, and deadline reminders that need a written record. Configure a consistent subject-line format per matter so alerts can be filtered and archived without manual sorting. Avoid relying on email as the only channel for time-sensitive cause list alerts on high-stakes matters.

In-app notifications

If your team uses a case management platform with a dashboard, in-app notifications give visibility to anyone actively logged in. They are not sufficient as a sole channel because they require the app to be open.

Routing alerts to the right person

For teams with multiple lawyers, configure alerts to go to the lawyer responsible for each matter directly, not to a shared inbox. Set a backup recipient (typically a senior partner or team lead) for matters where the primary person may be unavailable. Review routing every time team membership changes.

07Step 5: Set compliance reminders from court orders

Cause list alerts cover the hearing. Compliance reminders cover what comes after it. The obligations that flow from a court order, such as filing a reply, paying costs, or appearing on a specified date, are a separate tracking problem that many teams handle poorly.

When a court order lands, someone needs to read it, extract every obligation and its deadline, and create tracked reminders for each one. This is the step that most often falls through the cracks, particularly after a busy hearing day when dozens of orders arrive at once.

Manual approach

Log every compliance obligation into a shared calendar or task manager immediately after the order arrives. Assign it to the responsible person. Set at least two reminders: one at a comfortable distance before the deadline (for example, two weeks before a filing) and one close in (for example, two days before). Review the list at weekly team meetings. This works, but it depends on consistent discipline from everyone on the team.

Automated approach

Some advanced litigation management tools read a court order and automatically create reminders for the deadlines it contains. This removes the manual extraction step and reduces the chance of a one-line obligation buried in a long order going unnoticed.

Whichever approach you use, the principle is the same: every order that creates an obligation should generate a tracked reminder before the file is closed.

08Step 6: Test and maintain your setup

A common failure mode is setting up alerts once, never testing them, and only discovering a gap after a hearing is missed. Alerts need regular maintenance, not just initial configuration.

Test before you rely on it

When you first configure alerts, pick two or three matters where you already know the next listed date. Run the system for a week. Check that cause list alerts arrive when expected, on the right channel, to the right person. Confirm that name variations in court records are handled correctly. Indian name transliteration can vary (for example, Singh vs. Singha) and some systems miss matches because of this.

Weekly matter register check

Once a week, cross-check your active matter register against the matters enrolled in your tracking system. Any matter filed but not enrolled is a silent gap. Remove closed matters promptly to keep the list clean and avoid unnecessary alerts.

Monthly delivery check

At least once a month, check that alerts are actually reaching the right people. Ask each team member to confirm they received the last alert on at least one of their matters. Silent failures, where the tracking tool records an update but the notification was never sent, do happen and can go unnoticed for weeks.

Update routing immediately on team changes

When a team member changes phone number, email address, or role, update the alert routing the same day. A lawyer who left three months ago still receiving alerts on a dead number is one of the most common and avoidable failure points in any team's alert setup.

09Common mistakes to avoid

Most teams that struggle with litigation alerts are not making unusual errors. The same problems come up repeatedly.

• Monitoring by party name only: party name matching is imprecise. Names are often misspelled or transliterated differently across filings. Always add the official case number when you have it. Case numbers do not have spelling variations.
• Relying on a single delivery channel: if the only alert is an email digest checked once a day, a cause list update published at 9 p.m. may not be seen until after the morning hearing starts. Use at least two channels for high-stakes matters.
• No named owner per matter: alerts sent to a group inbox or a general team chat are easy to ignore because everyone assumes someone else has seen it. Ownership must be explicit.
• Single last-minute compliance reminders: one reminder the day before a filing deadline is too late if the work has not started. Set reminders in layers.
• Never testing the delivery: run a live test at setup and after any significant change to your team, your matter list, or your tool configuration.

For a broader look at what sets a strong litigation tracker apart from a basic one, see what a litigation tracker is.

10Where 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.

On the litigation alerts side specifically, Claw's case management module covers 8,457 courts across all Indian states, including district courts, tribunals, and the Supreme Court. It delivers automatic case updates, cause-list alerts, and daily cause lists over WhatsApp and email. Its AI auto-compliance feature reads a court order when it is uploaded and automatically creates the resulting deadline reminders, removing the manual diary step. This means Steps 3 through 5 in this guide can be handled within a single platform rather than across separate tools.

For teams that also do case research, the same subscription includes AI-based judgement search and Legal GPT, so tracking and research share one login. For context on how in-house legal teams typically structure their alert and tracking setup, see litigation tracking for in-house legal teams. For an overview of what a litigation tracker is and does, see what is a litigation tracker.

11Frequently asked questions