Case trackingEight court systems

One record,
from the court server
to the audit.

A case enters from the court’s own system, becomes a single record, and everything after it — tasks, filings, orders, notes, the audit trail — attaches to that record rather than living beside it.

ISO 27001 certified · MeitY empanelled · Deployable on-premise

01Intake

Search the court’s system.
Not your spreadsheet.

Find a matter by CNR, case number, or party name against the forum that holds it, and open the record from the court’s own data rather than retyping it.

District Courts

eCourts

High Courts

eCourts

Supreme Court

SCI

NCLT

Company law

NCLAT

Appellate

DRT

Debt recovery

DRAT

Appellate

Consumer

Jagriti

CNR · case number · party name

Or enter a matter with no court linkage at all — arbitrations and internal files take the same record shape.

02The record

Everything hangs
off one row.

Parties, forum, filing and listing dates, acts, and any fields your department needs that the court doesn’t have — on one record, with access mapped to your reporting hierarchy so each officer sees their jurisdiction.

Add your own columns to the case list and they persist as part of the record, not as a local view.

Find it again in seconds — live search across registration, party, and filing number, filters for court, collaborator, listing window, and tag, and status tabs that keep a running count as matters move.

W.P.(C) 8842/2024Pending
Forum
High Court · Principal Bench
Next listing
12 Sep 2026
Assigned
3 officers · 1 external counsel
Attached
14 documents · 6 tasks · 9 orders
Every field change logged with actor and timestamp
03What attaches

Six surfaces,
one parent record.

The case record

Tasks

Work items carry the case id, so open, completed, and overdue counts roll straight back onto the record.

votum_tasks.case_id

Documents

A folder is created with the case, so filings and correspondence land on the record instead of an inbox.

auto-created on intake

Orders & hearings

Orders and listing history are fetched from the court and stored against the case as a dated timeline.

/ecourts/store_orders

Notes

Case notes with @mentions, editable only by their author — so a note is attributable to a person.

author-scoped

Audit trail

Every change to the record is logged with the actor and timestamp, and reads back as one activity list.

recent_activity

Bookmarks

Flag a hearing or a filing for quick recall, newest first, without leaving the record to find it again.

votum_cases.bookmarks

Research arrives the same way

The browser extension reads a judgment from the tab you’re on, summarises it, and saves it against a case — so case-law research lands on the record instead of in a bookmark folder.

Chrome · side panel
04The loop

The court updates.
The record follows.

This is the one edge that runs backwards. Cause lists are read on a schedule and the next listing date is written onto the case, so the date on the record is the court’s date — not a transcription of it. Any case can also be refreshed on demand.

01

Read

Cause lists and case status are pulled from the forum on a schedule.

02

Write

The next listing date and any new orders are written onto the case record.

03

Surface

The updated date shows on the record and across every filtered case view.

Continuous · no manual portal checks

05Out

Then it comes
back out whole.

01

Export any view

Filter to what you need — court, collaborator, listing window, tag — then export those rows with only the columns you chose visible.

02

Full case history

Produce the record's complete timeline for an audit, an RTI response, or a court filing without reconstructing it from email.

03

Hearing visibility

Next listing dates stay current on the record and across the case list, so the date is read from one place.

06Around all of it

Governed at
every edge.

The graph above is only useful if each hop is controlled. Access follows your hierarchy, deletion is restricted and reversible, and the whole record can sit inside your own perimeter.

  • Role-based access mapped to your reporting hierarchy
  • Admin-only deletion, with the record soft-deleted rather than dropped
  • ISO 27001 certified information security management
  • MeitY empanelled — procurement-ready for government buyers
  • On-premise and sovereign deployment, data resident in India

Follow one case end to end.

Bring a live matter to the briefing and we’ll walk it through the whole graph — intake to export — on your own data.

ISO 27001 certified · MeitY empanelled