Litigation management software is a system that tracks a firm's court cases, hearing dates, and case status in one place, pulling updates from Indian court records so no next date of hearing slips. MyKase is litigation management software built for Indian practice, syncing cause-lists and case status from the eCourts and NJDG ecosystem across the country's court hierarchy.
Most firms start looking for a litigation tracker after a scare: a matter that moved on the cause-list while nobody was watching, an ex-parte order, a client asking why the firm did not appear. The buying question is rarely "what does it do". It is narrower and more anxious. Will it actually stop us missing a date? Does it read Indian courts, or was it built for American ones? What happens to our client data?
This guide answers the questions firms raise in real demo calls, in the order they raise them. It reinforces what the MyKase litigation tracking page covers rather than repeating it, going deeper on the decisions that decide the purchase: how automatic date capture works, where global tools break on Indian court structure, what to check on security, and how pricing usually lands.
What is litigation management software, and how is it different from a spreadsheet?
Litigation management software is the system of record for every case a firm runs: parties, court, case number, stage, next date of hearing, assigned advocate, documents, and history. A spreadsheet holds the same fields, but it is a static list. Someone has to open the court website, read the cause-list, and type the new date in. That manual step is where dates die.
The real difference is direction of update. Litigation tracking software pulls status from court records and pushes alerts to the people who need them. When a matter is listed, when an order is passed, when the next date changes, the software surfaces it instead of waiting for a clerk to check. On MyKase this lives as one case list tied to its legal case management software, so tracking, documents, and tasks share a single record rather than three disconnected files.
How does litigation tracking software prevent missed court dates?
Missed dates almost always trace to a broken chain: the court updated, the firm did not, and no alarm fired. Litigation tracking software closes that chain by reading the next date of hearing straight from the court's own record and alerting the responsible advocate before the hearing, not after the order.
The mechanics are plain once you separate capture from alert. The software reads the case status and next date from the eCourts and NJDG ecosystem, so the date in the system is the date the court set. It then pushes that hearing to the advocate appearing, with enough lead time to prepare. MyKase ties each tracked matter to a reminder and an owner. An unacknowledged date escalates instead of sitting silent.
Why does litigation tracking in India need cause-list and NDOH support specifically?
Indian litigation runs on two artefacts a foreign tool does not model natively: the daily cause-list and the NDOH, the next date of hearing. The cause-list is the court's published schedule of matters listed for a given day. The NDOH is the date the court fixes for the matter to come up again. Miss either and you miss the case.
A tracker built for Indian practice has to read the cause-list to know a matter is listed today, and capture the NDOH to know when it returns. These are not generic "event" fields. They map to how Indian courts actually schedule work through the eCourts platform and the National Judicial Data Grid. MyKase reads the cause-list and treats the next date of hearing as a first-class field, the way Indian courts publish them, not the way a US docketing tool assumes a court behaves.
Can litigation software track cases across all Indian courts?
India runs one of the largest court systems on earth. The eCourts ecosystem and the National Judicial Data Grid span the Supreme Court, High Courts, and district and taluka courts, though each tier reports through a separate NJDG portal rather than one combined dashboard. Under eCourts Phase II, the Department of Justice reports 18,735 district and subordinate courts computerised and interconnected, so a litigation tracker is only as useful as the share of that hierarchy it can actually read.
Coverage is the question to press hardest in a demo. Ask which court levels a tool reads, whether it handles High Court and district court case status, and how it deals with tribunals and specialised forums. The NJDG district-courts dashboard showed roughly 4.99 crore cases pending at district and taluka level when accessed in July 2026, a figure the dashboard itself last reviewed in August 2025, with the Supreme Court and High Court tiers tracked on their own separate NJDG portals. A firm of any size is likely spread across multiple court types. MyKase pulls status across the Supreme Court, High Courts, and district and taluka courts the eCourts system exposes.
What features actually matter in a litigation tracker?
Feature lists blur together in demos, so it helps to separate what prevents harm from what is merely convenient. The harm-preventers are automatic status capture, next-date-of-hearing alerts, cause-list monitoring, and a clear owner per matter. Without those, the tool is a prettier spreadsheet. The convenience layer, useful but secondary, includes document storage, billing hooks, reporting, and client updates.
Two features quietly decide daily usability. One is a single case record that ties tracking to documents and notices, so an advocate is not stitching context from three systems before a hearing. The other is role-based visibility, so partners see the whole portfolio and associates see their own matters. On MyKase the tracked case, its documents from document management for legal practice, and its statutory notices from the notice management solution share one record, so an advocate reads context in one place before a hearing.
How is Indian litigation software different from global tools like the ones built for US firms?
Global practice tools are excellent at what they were built for: American dockets, US billing conventions, and Western court calendars. They were not built to read an Indian cause-list, capture an NDOH, or map the Supreme Court, High Court, and district court structure that the eCourts platform exposes. Bolting Indian court data onto a foreign schema usually means manual re-entry, which reintroduces the missed-date risk the firm was trying to remove.
There is a compliance dimension too. Data handling for an Indian firm sits under the Digital Personal Data Protection Act 2023, and billing sits under Indian GST rules for legal services. A tool built abroad rarely accounts for either out of the box. MyKase reads the cause-list and captures the NDOH as native fields, maps the Supreme Court, High Court, and district hierarchy the eCourts platform exposes, and carries Indian statutory context, rather than a US docketing tool with Indian data bolted on.
How does automatic case status update actually work?
The value of a litigation tracker rises or falls on how it gets fresh status. The strong model is direct capture from the court's published record: the software reads the case status and next date of hearing from the eCourts and NJDG data for that matter, then reflects any change in the firm's case list. The date in the system is the date the court set, without a clerk retyping it and without a window where the court has moved on and the firm has not noticed.
What to verify is the update loop, not just the claim of automation. Ask how often status is refreshed, what happens when a court publishes a new listing, and whether a change triggers an alert to the matter owner. A tracker that captures the date but stays silent has solved half the problem. MyKase pairs automatic status capture with reminders on the same record, so a new next date of hearing becomes a notification, not a fact buried in a case file.
Does a litigation tracker integrate with eCourts, Tally, and firm ERP systems?
A tracker rarely lives alone. It has to read from the court source and write to the tools a firm already runs its money and its files through. On the court side, the load-bearing integration is the eCourts and NJDG ecosystem, the published record the tracker pulls case status and the next date of hearing from. Ask a vendor exactly which court data it connects to, because that link is what separates automatic capture from manual re-entry.
On the back-office side, two integrations come up in most Indian firms. Accounting sits in Tally for a large share of practices, so billing that ties to a tracked matter should reconcile cleanly with the firm's ledger rather than force double entry. Larger firms may also run a practice ERP or a document store the tracker must feed. MyKase keeps litigation tracking, documents from document management for legal practice, and case management on one platform, so the court-side eCourts link and the firm's own records connect through a single case record instead of a chain of exports.
Is litigation tracking software secure enough for confidential case data?
Case files hold privileged, sensitive material, so security is a buying criterion, not a footnote. The Digital Personal Data Protection Act 2023, Section 8(5) provides that "A Data Fiduciary shall protect personal data in its possession or under its control, including in respect of any processing undertaken by it or on its behalf by a Data Processor, by taking reasonable security safeguards to prevent personal data breach." That duty was enacted in 2023, and its obligations are phasing in: the DPDP Rules 2025, notified in November 2025, set most substantive compliance, including the security-safeguard duty, to take effect by 13 May 2027. The Act is not yet fully enforceable, so the practical point for a firm is to prepare now rather than treat it as settled law.
Practitioners and commentators have argued that this duty reaches a vendor's technical controls too, since the section expressly covers processing carried out on the Data Fiduciary's behalf by a Data Processor, which makes those controls relevant to the firm's own compliance posture. The checklist worth running is concrete. Where is data hosted, who can access it, how is it encrypted, and what access controls exist per user and per role? A cloud litigation tracker should give partners portfolio-wide visibility while limiting associates to their own matters. MyKase documents its hosting, access control, and encryption on its cloud and data security page, the controls a firm needs as it prepares for its own DPDP obligations.
Does litigation software handle billing and Indian GST for legal services?
Tracking and billing meet at the matter, so many firms want the case record to feed invoicing. That raises a specifically Indian question: how the tool handles GST on legal services. Under the GST Scheme of Classification of Services, legal advisory and representation services sit under SAC 998211 for criminal law and SAC 998212 for advisory and representation in other fields of law, which covers civil and commercial litigation, while SAC 998213 is the separate code for intellectual-property-related documentation and is not the general litigation code. Under GST Notification 13/2017-Central Tax (Rate), legal services supplied by an advocate or firm of advocates to a business entity fall under reverse charge, so the recipient accounts for the tax rather than the advocate.
That reverse charge is not universal. It applies where the recipient business entity's turnover exceeds the GST registration threshold, which is Rs 20 lakh, or Rs 10 lakh for special-category states. Under Notification 12/2017-Central Tax (Rate), legal services to a non-business entity, to a business below that registration threshold, or to government are exempt. So a small-firm client below the threshold may carry no GST at all. The practical test is whether invoicing understands the right SAC classification and reverse-charge treatment for legal services, rather than applying a generic tax line. MyKase is built for Indian legal practice, so billing that ties to a tracked matter reflects the GST framework Indian advocates work under instead of a foreign tax model that does not fit.
How much does litigation management software cost in India?
Pricing for litigation software in India tends to take one of a few shapes in the quotes firms actually receive: per-user monthly, per-firm tier, or a bundled practice suite where tracking is one module among case management, documents, and billing. The cheapest sticker is not always the cheapest outcome, because a tool that tracks poorly re-imports the missed-date cost the firm was paying before.
The number to weigh a quote against is the cost of one missed hearing: an ex-parte order, and the client asking why nobody appeared. Against that, a per-user subscription is small. When you compare, hold coverage, automatic date capture, and security constant, then look at price, rather than the reverse. MyKase publishes its plans on its pricing page, so a firm can size litigation tracking within a full practice suite instead of stitching point tools together. To see it on your own matters, you can book a demo.
How do you switch to a new litigation tracker without losing case history?
Migration fear keeps many firms on a spreadsheet longer than they should stay. The concern is real: years of case history, hearing records, and documents cannot be lost or re-keyed by hand. A good rollout imports existing matters, maps them to their court records, and reconnects each case to its next date of hearing so nothing goes dark during the switch.
The switch is easier when tracking, documents, and notices live in one system rather than several. Consolidating onto a single case record means the firm migrates once, not repeatedly across disconnected tools. MyKase brings litigation tracking, document management for legal practice, and case management onto one platform, so moving off scattered files becomes a single migration into one system of record rather than a series of fragile hand-offs.
What should a firm ask a vendor, and expect in the first month, before buying?
The strongest buyers walk into a demo with a short, pointed list rather than a feature wish. Ask which Indian court levels the tool reads, how it captures the cause-list and NDOH, and how often status refreshes. Ask what triggers an alert and who receives it, because a captured date that no one is told about is not prevention. Ask how the tool handles the DPDP Act 2023 security duty under Section 8(5) and where data is hosted, and whether the tracker connects to documents, notices, and billing or sits alone.
Then look past the sale to the first month, because buying is one decision and adoption is the harder one. A firm that signs but never fully loads its matters keeps living on the old spreadsheet in parallel, which defeats the purchase. Ask who imports the existing matters, how long the mapping to court records takes, and when the alerts go live. The first month should move the whole active docket into the system, assign an owner to each matter, and switch alerts on. MyKase runs litigation tracking, documents, and notices on one record, so onboarding loads the docket once and the whole team works from a single case list from the first week.
India-built vs global litigation tracking: capability comparison
| Capability | India-built tracker (e.g. MyKase) | Global tool retrofitted for India |
|---|---|---|
| Cause-list monitoring | Reads daily cause-lists from the eCourts ecosystem | Not modelled; manual entry |
| Next date of hearing (NDOH) | Captured automatically as a first-class field | Mapped to a generic event field, often re-keyed |
| Court coverage | Supreme Court, High Courts, district and taluka courts (eCourts/NJDG hierarchy) | Built for US/foreign dockets |
| Automatic case status | Pulled from eCourts and NJDG records | Manual updates or none |
| Data compliance | Built for the DPDP Act 2023 context (Section 8(5) security duty, phasing in to 2027) | Foreign privacy frameworks by default |
| Legal billing | SAC 998211/998212/998213 and GST reverse-charge aware | Generic tax lines, not Indian GST |
Buying litigation management software comes down to a few honest questions: will it stop us missing a date, does it read Indian courts through the eCourts and NJDG ecosystem, and can we trust it with client data as the DPDP Act 2023 obligations phase in toward 2027? A tool built abroad struggles on cause-lists, NDOH capture, and Indian court structure. MyKase reads Indian courts natively, tying automatic case status, next-date alerts, documents, and notices to one record. Run a demo on your own matters and press the coverage and security questions before you sign.
Frequently Asked Questions
A litigation tracker is software that monitors a firm's court cases, capturing case status and the next date of hearing from Indian court records so nothing is missed. MyKase tracks matters across the eCourts and NJDG hierarchy and alerts the responsible advocate before each hearing.
Automatic court case status works by reading a case's status and next date directly from the eCourts and NJDG record, then flagging changes. MyKase captures this on the matter record and turns a new listing into an alert instead of a manual website check.
The best fit is the tool that reads Indian courts natively, captures cause-lists and NDOH, and helps a firm prepare for the DPDP Act 2023 security duty. MyKase reads the eCourts and NJDG hierarchy directly, not a US docketing tool with Indian data bolted on.
It reads the next date of hearing from the court's published record and pushes a reminder to the advocate appearing. MyKase captures the NDOH automatically per matter and links it to reminders, so a fixed date becomes a notification the firm cannot overlook.
Yes, if it reads the eCourts and NJDG hierarchy, which spans the Supreme Court, High Courts, and district courts. MyKase tracks case status and hearing dates across the Indian court structure so a spread-out portfolio stays on one list.
It can be, when the vendor maintains the reasonable security safeguards the DPDP Act 2023 requires of a Data Fiduciary under Section 8(5), a duty phasing in toward 2027. MyKase documents hosting, encryption, and role-based access on its cloud and data security page.
Many suites tie billing to tracked matters. The Indian question is GST: legal services fall under SAC 998211 or 998212 with reverse-charge treatment above the registration threshold. MyKase is built for Indian practice, so billing linked to a matter reflects that framework rather than a generic foreign tax model.
