# How to track Supreme Court case status by case number in 2026 _Published 2026-04-01T09:00:00.000Z · Updated 2026-05-11T15:47:11.323Z · By Aniruddh Atrey_ Canonical: https://www.courtnetra.com/blog/track-supreme-court-case-status Category: Practice management Tags: NDOH, hearing diary, Supreme Court, case tracking, eCourts --- > A practical 2026 guide for Indian advocates to track Supreme Court of India case status by diary number or case type — manually via the SC portal, and automatically via auto-fetch tools like CourtNetra. ![Lady Justice statue holding scales — symbol of the Indian judiciary](https://images.unsplash.com/photo-1505664194779-8beaceb93744?w=1600&h=900&q=80&auto=format&fit=crop) Tracking a Supreme Court of India case is, on paper, a solved problem — the SC's integrated case-management portal publishes case status, daily cause lists, and order copies. In practice, every advocate has the same complaint: doing it across more than a handful of matters is a daily drain. This post covers the manual workflow, the auto-fetch alternative, and the failure modes you should anticipate. ## What the Supreme Court portal exposes The SC portal ([https://www.sci.gov.in](https://www.sci.gov.in)) and its case-status pages provide: - **Case status by diary number** — the unique reference assigned at filing. - **Case status by case type and year** — Civil Appeal, Criminal Appeal, SLP, Writ Petition, Transfer Petition, etc. - **Case status by party name** — fuzzy match across petitioner and respondent. - **Daily cause lists** — published the previous evening (typically by 6 PM IST) for the next working day. - **Judgment text** — published once an order is finalised; some judgments have a 24-hour delay between pronouncement and online publication. Each of these is a separate query against a separate URL pattern. There is no single "track this matter" workflow on the portal — you query, read, and remember. ## Manual workflow: what working advocates actually do The pattern most counsel teams follow: - **Set a recurring calendar reminder** to check the cause list the evening before. Most teams check at 7 PM IST daily. - **Maintain a matter list** in Excel, Google Sheets, or a hand-written diary with diary numbers and case types. - **Walk through each matter** on the cause list — search for the diary number, read the bench, note the time slot. - **Forward to the team** — typically a WhatsApp group with the next day's listing. - **Cross-reference with the previous day's order** — to know if anything was directed. This workflow scales to maybe 20-30 matters per advocate. Beyond that, it breaks. ## The auto-fetch alternative What auto-fetch tools (CourtNetra and similar) do: - You add a matter to the dashboard once — diary number, case type and year, or CNR. - The tool polls the SC portal on a fixed schedule — typically every 4-6 hours during the working day. - When the cause list updates, the matter timeline is updated automatically. - Notifications go out — WhatsApp, email, and dashboard — for every change. - The next morning's hearing diary aggregates all listings across all matters in your list. The time savings are significant. A senior counsel with 200 matters across the SC, three High Courts, and the NCLT was previously spending 90 minutes a day on cause-list reconciliation. With auto-fetch, that became 10 minutes of reviewing the digest. ## Failure modes you should anticipate Auto-fetch is not magic. The portals do fail; the integrations do break. Realistic expectations: **Portal outages.** The SC portal goes down occasionally — usually for short windows during midnight maintenance. During an outage, no fetch returns useful data; matters show a transient error indicator. Plan for fallback to manual checking on outage days. **Cause-list timing variance.** Most cause lists are published by 6 PM IST the previous evening, but delayed publications (sometimes 9 PM, occasionally 11 PM) happen. If you fetch at 6 PM and find nothing, the previous-day cause list might not be published yet — re-check at 9 PM. **CNR mismatch.** District Court matters use a CNR (Case Number Record). The SC and HCs use different identifiers. If a District Court matter is migrated to the SC on transfer, the CNR is replaced by an SC diary number; the auto-fetch needs to follow that re-keying. **Bench reconstitution.** When the Chief Justice reconstitutes a bench (e.g. mid-week roster change), pending listings move; the auto-fetch sees them as cancellations and re-listings. Read the matter timeline rather than the alert headlines on bench-change days. **Order publication delay.** A bench can pronounce an order on Day 1 and the order text appears on Day 2 or later. The auto-fetch knows the listing happened but won't have the order text until the portal publishes it. ## What "good" looks like For a working SC practice, the practical bar is: - **Same-day awareness** of every cause-list update on every matter - **No-tab-checking morning routine** — the daily digest is enough - **Mobile-first alerts** — WhatsApp because that's where every Indian advocate already works - **Bilingual support** — Hindi for the senior counsel who reads Devanagari more comfortably - **A search backstop** — when something looks wrong in the auto-fetch, you can still do a manual cause-list search to verify That's the bar CourtNetra builds against. The tool is one of several in the market; what matters is the workflow being achievable, with or without a particular product. ## Specific Supreme Court case-tracking patterns A few patterns that are unique to the SC and worth knowing: **Diary number vs case number.** The SC issues a diary number on filing — that's the queryable identifier on the portal. Once the matter is registered (after defects are cured), it gets a case number. The diary number stays valid as a query key throughout. Use the diary number for tracking until you have a registered case number; switch then. **Daily Order vs Reportable Judgment.** Most SC orders are recorded as Daily Orders. Reportable Judgments are a smaller subset, marked as such by the bench and indexed for citation. The portal distinguishes them — track both, but for citation purposes only the Reportable subset matters. **SLP vs Civil Appeal numbering.** A Special Leave Petition (Civil) is filed under Article 136. If leave is granted, it's converted to a Civil Appeal with a new number. The matter timeline should track both numbers — the SLP number for filing-stage history, the Civil Appeal number once leave is granted. **Transfer Petitions.** Filed under Article 139A or Section 25 CPC. Handle distinctly because the originating court matters — auto-fetch needs to know the High Court the matter was transferred from to surface the pre-transfer history. ## The bottom line Tracking SC matters is not difficult; tracking many SC matters reliably and across a team is. The right answer in 2026 is auto-fetch with a manual backstop — you don't replace the portal, you augment it with structured polling, alerts, and a unified diary. For Indian advocates managing 50+ matters across the SC, HCs, and tribunals, the time saved is on the order of hours per week. For a chamber, it's days per month. For the larger firms, it's a non-question — they've already moved. CourtNetra's auto-fetch covers the SC alongside all 25 High Courts, eCourts District Courts, and seven tribunals. The 7 AM IST daily digest is sent over WhatsApp and email, bilingual. There's a 3-day free trial without a card — you can add a real matter and see the auto-fetch run on your data before deciding.