Vidhilekha
One file, properly kept, for every matter you carry.
Vidhilekha keeps hearings, documents and client updates in a single record — so nothing depends on a WhatsApp thread or a diary that only you can read.
The case file lives in five places, and none of them talk to each other.
A hearing date sits in a diary. An update goes out on WhatsApp. A document is on someone's laptop. Vidhilekha exists to put all of it back in one place — the file itself.
Hearing dates slip
Cause lists change, courtrooms shift, and a missed update costs a client's trust — or worse.
Updates scatter
What was said at a hearing lives in someone's memory or a chat thread that gets deleted.
Juniors start from zero
Preparing for a hearing means re-reading everything, every time, with no structured brief to work from.
From intake to the next hearing, in order.
This is the actual sequence a matter follows once it's in the system — not a feature list, a workflow.
A case is opened, once
Client, court, case type and the advocate of record are captured up front, in the same format the courts themselves use for the case number.
Hearings and cause lists stay current
Every hearing date, the appearing advocate, and the outcome are logged against the matter — so "what happened last time" is never a guess.
A hearing brief is ready before the morning
The night before a listed hearing, Vidhilekha assembles a structured brief from the case history — so preparation starts from a summary, not a stack of notes.
Documents attach to the matter, not to a chat
Filings, orders and correspondence sit against the case they belong to, visible to everyone on the matter with access to see it.
The client hears it from the file, not secondhand
Case updates reach the client directly, in plain language — closing the loop without another manual phone call.
Every part of practice, kept in one register.
Vidhilekha is built around the actual departments of a chambers — firm, case, intelligence and reference data — not a generic set of "modules."
Teams & designations
Admins and advocates work under one account, each with a designation and the access their role allows — nothing more.
A client login of their own
Clients see only their own matters through a read-only view — status, hearings and documents, without a phone call.
Case register
Court, case type, status and the advocate of record — filed under a case number in the same format the courts use.
Hearings & cause lists
Every listed date, the appearing advocate and the outcome, logged against the matter as it happens.
Case timeline
Updates, hearings and documents in a single chronological record — what happened, in order, without digging.
Document vault
Filings, orders and correspondence stored against the matter, not a device — with size tracked toward the firm's quota.
Document requests
Ask a client for a specific paper and track it through to received — no more "did you send that yet?"
Parties & links
Opposing counsel, co-parties and related matters cross-referenced, so the full picture of a dispute stays visible.
Nightly hearing brief
An AI-assembled prep note lands before every listed hearing — drawn from the matter's own history, not a template.
Note-to-update parser
A scribbled hearing note becomes a structured case update in seconds — no manual re-typing after court.
Bring your own AI key
Firms that want it can plug in their own model key — encrypted at rest, and nothing routes through a shared one.
Court directory
Six Bengaluru court complexes mapped down to the courtroom, kept current as a shared reference — not re-typed per matter.
Statute database
BNS, BNSS, BSA and 35+ Acts, cross-referenced back to the IPC, CrPC and Evidence Act sections advocates still think in.
Firm dashboard
What's listed this week, what's overdue, what's pending documents — a firm-wide view instead of case-by-case checking.
Full audit trail
Every write is recorded with the actor, their IP and a timestamp — case changes, team changes, AI key changes, all of it.
Strict tenant isolation
Every request is scoped to your firm's own account at the token level — another firm's file is never a query away.
Grounded in Bengaluru's courts and India's current criminal codes.
Vidhilekha starts from how matters actually move through Indian courts — not a generic case-management template with local labels bolted on.
Every court complex in Bengaluru is live today. We're rolling out to other major cities next, one at a time.
The statute engine, as an API.
The same concordance that assembles a hearing brief is queryable directly — look up an Act, search a section by keyword, or resolve an old IPC/CrPC/Evidence Act section to its BNS/BNSS/BSA equivalent. Same JWT your firm already uses; no separate key.
{
"data": [
{ "code": "BNS", "name": "Bharatiya Nyaya Sanhita, 2023" },
{ "code": "BNSS", "name": "Bharatiya Nagarik Suraksha Sanhita, 2023" },
{ "code": "IPC", "name": "Indian Penal Code, 1860" },
{ "code": "NI", "name": "Negotiable Instruments Act, 1881" }
]
}
{
"data": [
{
"act": "IPC",
"section": "420",
"title": "Cheating and dishonestly
inducing delivery of property",
"maps_to": { "act": "BNS", "section": "318" }
}
]
}
35+ Acts, old code and new code cross-referenced
- Bharatiya Nyaya Sanhita, 2023 — was IPC, 1860
- Bharatiya Nagarik Suraksha Sanhita, 2023 — was CrPC, 1973
- Bharatiya Sakshya Adhiniyam, 2023 — was Evidence Act, 1872
- Negotiable Instruments Act, 1881
- Protection of Children from Sexual Offences Act, 2012
- Narcotic Drugs and Psychotropic Substances Act, 1985
- Prevention of Corruption Act, 1988
- SC/ST (Prevention of Atrocities) Act, 1989
- Protection of Women from Domestic Violence Act, 2005
- Juvenile Justice (Care & Protection of Children) Act, 2015
- Information Technology Act, 2000
- Code of Civil Procedure, 1908
- Indian Contract Act, 1872
- Transfer of Property Act, 1882
- Specific Relief Act, 1963
- Limitation Act, 1963
- Indian Succession Act, 1925
- Hindu Marriage Act, 1955
- Arbitration and Conciliation Act, 1996
- Companies Act, 2013
- Consumer Protection Act, 2019
- Motor Vehicles Act, 1988
Plus the rest of the 35+ Acts in the database — growing as new matters need them.
Built to assist research and prep — not replace judgement.
Every AI feature in Vidhilekha is grounded in your own case record and India's statute books, opt-in, and billed transparently. Nothing files itself — AI output is always a draft an advocate reviews before it goes anywhere.
Hearing brief, assembled overnight
Before every listed hearing, Vidhilekha reads the matter's own timeline — past orders, notes, documents — and drafts a structured brief. It's cached once generated, so it's fast and doesn't repeat calls for the same hearing.
Note-to-update parsing
Paste in what happened at a hearing and it's parsed into status, outcome and next date automatically. If the parse ever comes back malformed, the raw note is kept as the outcome — it never fails silently.
Statute & section search
Full-text search across every Act in the database, with old-code-to-new-code resolution built in — search "cheating" or "IPC 420" and get back the matching BNS section. See the Statute API.
Bring your own model key
Firms can plug in their own Anthropic key — encrypted at rest, never shown again after saving. Set, and platform AI credits stop being touched entirely; usage stays visible per advocate either way.
Precedent & case-law search
Surfacing judgments and citations relevant to a matter's actual facts, not just keyword hits — in planning, not yet available.
First-pass draft assist
A starting draft for routine applications — adjournment, bail, vakalatnama — grounded in the matter file, for an advocate to edit and file. In planning, not yet available.
{
"raw_notes": "Witness examined. Case adjourned to 1 Sep 2026."
}
→ 200 OK
{
"parsed": {
"status": "adjourned",
"outcome": "Witness examined.",
"next_date": "2026-09-01",
"next_court": null
}
}
Create your firm's account.
Vidhilekha is live for early-access firms. Head to the app and register your chambers directly — no waitlist form to fill out.
Prefer a walkthrough first? Write to info@vidhilekha.com