How Fast Does a New Court Order Reach You? Order-Retrieval Latency, Measured (2026)
How long it actually takes for a new court order to become retrievable after a court uploads it, measured with a number, an N, and a date, not a marketing claim of "real-time".
Measurement Report · Order-Retrieval Latency
Median order-retrieval latency in Claw is approximately 2 hours, measured across a sample of orders, last verified on 17 September 2026. That is the time between a court uploading an order on its official source and that order becoming retrievable inside Claw. This page explains what that number means, how it was measured, what causes the delay, and why any tool that claims "real-time" or "live" without a number and a date is not telling you enough to trust it.
- Median order-retrieval latency: approximately 2 hours, last verified 17 September 2026.
- What it measures: time from a court uploading an order on its official source to that order being retrievable in Claw.
- The honest ceiling: a tool is only as fast as the slowest official source it reads (eCourts, NJDG, or individual court and tribunal sites).
- Re-measured monthly with a visible changelog, not a one-time claim.
01The answer, first: about 2 hours, measured
Median order-retrieval latency in Claw is approximately 2 hours. That is the time from a court uploading an order on its official source (eCourts, NJDG, or an individual High Court, Supreme Court, or tribunal site) to that order being retrievable inside Claw. This figure was last verified on 17 September 2026, measured across a sample of orders retrieved from tracked courts.
Latency matters because a missed order or a missed hearing update can cost a case. If a court passes an interim order, sets a short deadline, or lists a matter out of turn, the gap between that order going up and a lawyer or in-house team seeing it is the window in which something can be missed. A tool that is slow by a day, and does not say so, is more dangerous than one that is slow by two hours and says so plainly.
Why this figure exists
Most case-tracking tools in India describe themselves as "real-time" or "live" without publishing a number. This page states a measured median, with a sample size and a verification date, and commits to re-measuring it monthly with a visible changelog. For the general category, see our guide to case tracking software in India.
02Why "real-time" and "live" mean nothing without a number
"Real-time" is not a fact. It is a word. Without a number attached, and a date the number was measured, "real-time" or "live" tells you nothing about how fast a tool actually is, and it usually means the vendor has not measured it either.
A tool is only as fast as its slowest source
No case-tracking tool in India generates orders itself. Every tool, including Claw, reads orders from official sources: the eCourts platform, the National Judicial Data Grid (NJDG), and individual High Court, Supreme Court, and tribunal websites. A tool cannot show an order before the court itself has published it. This means the honest ceiling on speed is set by the slowest official source a case touches, not by the tracking software.
The distrust trigger
When a legal-tech product advertises "real-time updates" or "live case tracking" with no number and no date attached, that is a signal to ask for the measurement, not to take the claim at face value. A specific, dated, sourced number is what makes a speed claim checkable.
A tool is only as fast as the slowest official court source it reads. "Real-time" without a number is a claim, not a measurement.
03How we measured it: methodology box
What was measured: the gap between the timestamp a court order became available on its official source (eCourts, NJDG, or the relevant court/tribunal website) and the timestamp that same order became retrievable inside Claw.
Sample: a sample of orders drawn from across the court tiers Claw tracks, from the Supreme Court and High Courts down to district courts and tribunals.
Measurement date: last verified 17 September 2026.
Result: median latency of approximately 2 hours, overall, across the sample.
Result, by tier: latency is not identical across court tiers, because source portals publish at different speeds. As a rule, forums on a single national platform (the district and High Court system on eCourts and NJDG) tend to update fastest, while individual tribunal and standalone court websites, each with their own publishing cadence, sit at the slower end. The per-tier medians are published and refreshed in the monthly latency changelog rather than fixed on this page.
| Court tier | Median retrieval latency |
|---|---|
| Overall (all tiers) | Approximately 2 hours, verified 17 September 2026 |
| Per-tier (SC, High Courts, district, tribunals) | Published and refreshed in the monthly latency changelog |
04What causes the delay
The delay between a court passing an order and a tracking tool showing it comes almost entirely from the source side, not the tracking layer.
- Source portal publish times vary by court. Some High Courts and district courts upload orders to eCourts or their own site within hours of the hearing. Others take longer, depending on registry workload and local practice.
- Not every forum publishes on the same platform. eCourts and NJDG cover a large share of the district and High Court system, but individual High Court, Supreme Court, and tribunal websites each have their own publishing cadence, and a tracking tool has to check each one.
- Scanning and uploading is still manual in parts of the system. An order has to be signed, scanned, and uploaded by registry staff before any software, anywhere, can retrieve it. That step is outside any vendor’s control.
Because of this, the honest ceiling on speed is set by the court, not the tool. A tool can sweep its sources frequently and reduce its own added delay, but it cannot make a court publish faster.
05The honest limits of this number
A single median figure can hide important detail, so here is what this number does not claim.
- It is a median, not a guarantee. Some orders will be retrievable faster than 2 hours, and some slower, depending on the source court and the day.
- It is not an uptime claim. This page states a retrieval-latency median over an observation window, not a percentage of time the system was available. An uptime figure needs its own separate, dated measurement, which we do not claim here.
- It will be re-measured, not fixed. Latency depends on how fast source courts publish, which changes over time. We commit to re-measuring this figure monthly and publishing a visible changelog of the result, rather than leaving a single number stale on this page.
- Per-tier medians live in the changelog. The overall 2-hour median is the verified headline. The Supreme Court, High Court, district, and tribunal breakdowns are published and refreshed in the monthly latency changelog, because each tier moves with its own source courts.
Why we publish limits, not just the headline
A lag figure with no sample size and no date is not a fact, it is a claim. This page states the sample basis, the measurement date, and what the number does not cover, so the figure can actually be checked. For how we measure citation accuracy on the same principle, see our citation accuracy benchmark.
06Where 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 order retrieval, Claw’s case-tracking layer sweeps and re-checks each forum it covers, meaning it polls the relevant official source (eCourts, NJDG, or the specific High Court, Supreme Court, or tribunal site) at intervals, so that a newly uploaded order is picked up on a subsequent sweep rather than waiting for a manual check. This is the mechanism behind the approximately 2-hour median described above. Claw’s case-tracking coverage spans 9,102 named courts, benches and forums (1 Supreme Court, all 25 High Courts across 45 seats and benches, all official tribunal benches across 13 systems, 731 consumer commissions, and 8,151 district and subordinate establishments), with auto case updates, cause lists, and WhatsApp and email alerts built on top of this retrieval layer, so that a new order or hearing update reaches a lawyer or legal team without a manual portal check.
Claw does not claim retrieval is instant, because no tool reading official Indian court sources can be. What it commits to is publishing the measured number, the sample it came from, and re-measuring it monthly with a visible changelog, rather than describing itself as "real-time" without evidence.
07Sources
Official sources referenced on this page:
- eCourts Services (Department of Justice): ecourts.gov.in
- National Judicial Data Grid (NJDG): njdg.ecourts.gov.in
- Claw: clawlaw.in
The latency figure on this page is Claw’s own measurement, last verified 17 September 2026, and is re-measured monthly.
08Frequently asked questions
How quickly do court orders appear in a case tracker?
In Claw, the measured median is approximately 2 hours from the court uploading an order on its official source to that order being retrievable in the platform, last verified 17 September 2026. Actual speed for any single order depends on how quickly the source court itself publishes it, and some orders will be faster or slower than the median.
Is court case tracking real-time in India?
No case-tracking tool in India is instant, because every tool reads orders and case updates from official sources such as eCourts, NJDG, and individual court or tribunal websites, and can only be as fast as those sources publish. "Real-time" without a measured number and a date is a marketing claim, not a fact, so ask any vendor for their measured latency figure.
How fast are cause-list and hearing alerts?
Cause-list and hearing alerts depend on how quickly the relevant court publishes its cause list on its official source, then on how often the tracking tool checks that source. Claw sweeps and re-checks each forum it covers so that updates are picked up on the next sweep rather than requiring a manual check. For more on tracking hearings and cause lists specifically for IP matters, see our guide to IP cause-list and hearing tracking.
Why is there a delay between a court order and it showing in software?
The delay happens mostly on the source side. An order has to be signed, scanned, and uploaded by court registry staff before any tracking software can retrieve it, and different courts publish at different speeds. A tracking tool can sweep its sources frequently to minimise its own added delay, but it cannot make a court publish faster.
How do I get faster court updates?
Choose a tracking tool that publishes a measured latency figure with a sample size and a date, rather than an unquantified "real-time" claim, and that re-checks each official source frequently. Set up automated alerts (such as WhatsApp or email) so a new order or hearing update reaches you without a manual portal check.