Guide
How to build a litigation case tracker in Notion: chronology, issues, evidence and hearings
Build a litigation case tracker in Notion: chronology, issues, evidence register, orders and hearings, linked so every issue shows its support.
By Raghav R Handa, practising lawyer18 min read
TL;DR
- A litigation tracker is seven related databases under one Matter: Chronology, Issues, Evidence, Witnesses, Filings and orders, Discovery and Hearings.
- The power is in the relations: link each piece of evidence to the events it proves and the issues it supports, and every issue shows what supports it and what is missing.
- Notion tracks the case; it is not an e-discovery platform, and it does not calculate court deadlines.
- Keep privileged and work-product material on restricted pages and label it.
A litigation tracker in Notion is seven related databases under one Matter: a Chronology, an Issues list, an Evidence register, Witnesses, Filings and orders, Discovery, and Hearings. The power comes from the relations: link each piece of evidence to the events it proves and the issues it supports, and you can open any issue and see what you have, and what you lack. Notion tracks the case; it does not replace e-discovery software or calculate court deadlines. This is a structure guide, not legal advice. It gives the schemas, the views, the formulas, a worked example and the routines that keep a case file honest.
What a litigation file has to hold
A contested matter generates information of several kinds that must be connected: what happened (events), what must be proved (issues), what proves it (evidence and witnesses), what the court has done and required (filings, orders, hearings) and what each side owes (discovery). Most case files fail because these live in separate places, so nobody can answer, quickly, "what supports issue 3?" Relations answer it.
The seven databases and how they connect
| Database | One row is | Relates to |
|---|---|---|
| Chronology | An event | Matter, Issues, Evidence, Witnesses |
| Issues | A legal or factual question to be decided | Matter, Chronology, Evidence, Witnesses |
| Evidence | A document, exhibit or item | Matter, Chronology, Issues, Witnesses (as author or custodian) |
| Witnesses | A person who can give evidence | Matter, Chronology, Issues, Evidence |
| Filings and orders | A pleading, application or order | Matter, Issues, Deadlines, Hearings |
| Discovery | A request, response or obligation | Matter, Evidence, Filings and orders |
| Hearings | A court appearance | Matter, Issues, Evidence, Witnesses, Filings and orders |
The schemas in full
Chronology
| Property | Type | Why |
|---|---|---|
| Event | Title | A short factual statement |
| Date | Date (with an 'approximate' checkbox) | When it happened; flag uncertain dates |
| Description | Text | More detail |
| Source | Relation to Evidence | What shows it happened |
| Issues | Relation to Issues | What it bears on |
| Witnesses | Relation to Witnesses | Who can speak to it |
| Agreed or disputed | Select: Agreed, Disputed, Unknown | Where the parties stand |
| Confidence | Select: Documented, Witness only, Inferred | How strong the support is |
| Privileged | Checkbox | For internal notes |
| Matter | Relation | Which case |
Issues
| Property | Type | Why |
|---|---|---|
| Issue | Title | Stated as a question |
| Type | Select: Law, Fact, Mixed, Remedy | How to approach it |
| Burden | Select: Ours, Theirs, Shared | Who must prove it |
| Our position | Text | A sentence or two |
| Status | Select: Open, Strong, Weak, Conceded, Won, Lost | Where it stands |
| Authorities | Relation to your knowledge base | The law relied on |
| Evidence count | Rollup (count of Evidence) | How much support exists |
| Verified evidence count | Rollup (count where Verified is checked) | How much is checked |
| Support gap | Formula | Flags issues with no verified support |
Evidence
| Property | Type | Why |
|---|---|---|
| Title | Title | Following your naming rule |
| Type | Select: Document, Email, Photo, Recording, Expert report, Pleading, Other | Filtering |
| Date | Date | Document date |
| Author or custodian | Relation to Witnesses | Authentication path |
| Exhibit number | Text | Cross-reference to bundles |
| File link | URL | In your document system |
| Verified | Checkbox | You have read and checked it |
| Privileged | Checkbox | Excluded from sharing and production |
| Events, Issues | Relations | What it proves |
| Disclosed | Select: Not yet, Disclosed, Withheld (privileged) | Discovery status |
Witnesses
| Property | Type | Why |
|---|---|---|
| Name | Title | Person |
| Role | Select: Client, Opposing party, Fact witness, Expert, Other | How they fit |
| Can speak to | Relation to Events | Topics |
| Contact and availability | Text | Logistics |
| Statement status | Select: Not taken, Draft, Signed, Served | Progress |
| Credibility notes | Text (privileged) | Internal assessment |
Filings and orders
| Property | Type | Why |
|---|---|---|
| Title | Title | For example, Defence, Order of [date] |
| Type | Select: Pleading, Application, Order, Judgment, Correspondence with court | Filtering |
| Filed or made on | Date | When |
| Document | URL | The file |
| Creates deadlines | Relation to Deadlines | Orders create dates; record trigger and rule |
| Issues | Relation | What it bears on |
Discovery
| Property | Type | Why |
|---|---|---|
| Item | Title | Request or obligation |
| Direction | Select: We request, They request, Court-ordered | Who owes whom |
| Due | Date | Tracked, calculated elsewhere |
| Status | Select: Open, Responded, Disputed, Complete | Progress |
| Related evidence | Relation | Documents involved |
| Owner | Person | Who acts |
Hearings
| Property | Type | Why |
|---|---|---|
| Hearing | Title | Type and date |
| Date and time, Court | Date, Text | Logistics |
| Purpose | Select: Case management, Interim, Trial, Appeal | Preparation level |
| Issues in play | Relation | What is being argued |
| Evidence and witnesses | Relations | What you will rely on |
| Preparation checklist | Page template | Standard tasks |
| Outcome | Text | Record afterwards |
Build it in order
- Chronology first. It is the spine. Enter events as you learn them, with the source. A view sorted by date is your master timeline.
- Issues next. Start with the pleaded issues, then add others as the case develops. Track status and your current position in a sentence.
- Evidence register. Relate each item to the events and issues it supports. A rollup of evidence per issue shows thin spots immediately.
- Witnesses. Link people to the events they can speak to, so witness preparation follows the chronology.
- Filings and orders, with deadlines. Record each order and the deadlines it creates. Calculate dates in a rules-based tool and record them with trigger and rule. See can Notion calculate court deadlines?
- Discovery and hearings. Track what is owed, and prepare each hearing from a template.
Views that turn the data into case management
| View | Database | Filter and display | What it tells you |
|---|---|---|---|
| Master timeline | Chronology | Sorted by date; group by year or phase | The story in order |
| Disputed events | Chronology | Agreed or disputed is Disputed | Where the fight is |
| Events without a source | Chronology | Source is empty | Facts you cannot yet prove |
| Issue support matrix | Issues | Table with evidence count and verified count | Strength by issue |
| Unsupported issues | Issues | Verified count is 0 and status is Open | Gaps to fill |
| Evidence not linked to any issue | Evidence | Issues is empty | Documents with no purpose, or missing links |
| Unverified evidence | Evidence | Verified is unchecked | Reading still to do |
| Witness by event | Witnesses | Grouped by role; show events | Preparation plan |
| Open discovery | Discovery | Status not Complete; sort by due | What is owed |
| Next hearings | Hearings | Date within 30 days; show readiness | What to prepare |
Formulas that help (they display, they do not decide)
// Support gap on an Issue: open but no verified support
if(and(prop("Status") == "Open", prop("Verified evidence count") == 0),
"No verified support", "")
// Days to hearing
dateBetween(prop("Date"), now(), "days")
// Hearing readiness: all checklist tasks done?
if(prop("Open prep tasks") == 0, "Ready", "Preparing")A worked example: a commercial supply dispute
A distributor claims a supplier delivered defective goods and withheld payment. Over the first month the file fills in like this:
| Database | Sample rows |
|---|---|
| Chronology | Contract signed (documented); first delivery (documented); first complaint email (documented); phone call about replacement (witness only, disputed); payment withheld (documented) |
| Issues | Was the contract breached by delivery of defective goods? Did the distributor give proper notice? What loss resulted? Was withholding payment justified? |
| Evidence | Contract; delivery notes; inspection report; the complaint email; payment records; the supplier's reply |
| Witnesses | The distributor's warehouse manager (can speak to delivery and inspection); the supplier's account manager (can speak to the call) |
| Filings and orders | Claim; defence; an order setting directions with dates |
| Discovery | Request for inspection records; the supplier's request for correspondence |
| Hearings | Case management conference; a later interim application |
The issue support matrix then shows that "proper notice" has one verified document (the email) and one disputed call with a single witness: a visible weakness to address in witness evidence before the hearing.
Hearing preparation checklist (template)
- Confirm date, time, court and any remote-hearing arrangements.
- Confirm the issues in play and your position on each.
- Assemble the evidence relied on; confirm each item is verified and in the bundle.
- Prepare witnesses; confirm availability.
- Check outstanding orders and deadlines affecting the hearing.
- Prepare and exchange documents as directed; confirm service.
- Prepare the skeleton or outline; check authorities are verified.
- Brief the client; agree instructions on settlement.
- Record the outcome and new triggers afterwards, the same day.
Privilege and confidentiality
Litigation files hold the most sensitive material a firm has. Add a Privileged checkbox to Evidence, Chronology and Witnesses, keep credibility notes and strategy on restricted pages, decide what stays outside Notion (the documents themselves, if your document system is stronger), keep AI and integrations away from the case, and think before sharing with experts or co-counsel. See privilege and Notion.
What not to ask of Notion
- Bulk document review, Bates numbering or production: use a purpose-built platform.
- Calculating filing deadlines: use rules-based calendaring and a second check.
- Storing the only copy of anything: keep originals in your document system.
- Real-time court filing: use the court's system and record the reference.
Common mistakes
- Building the tracker after the case is already complicated; start at instruction.
- Not recording the source of an event, so it cannot be proved.
- Evidence not linked to issues, so you cannot see gaps.
- Letting the chronology go stale after the first month.
- Putting privileged strategy on broadly shared pages.
For the surrounding setup see Notion for litigation lawyers, matter management, limitation period tracking and the best way to use Notion for lawyers.
Frequently asked questions
Can Notion be used to manage a litigation file?
Yes, for tracking: a chronology, issues, an evidence register, witnesses, filings, discovery and hearings, all related to the matter. It is not an e-discovery or document review platform, and it does not calculate court deadlines, so use dedicated tools for those.
How do I build a chronology in Notion?
Create a Chronology database with a date, a description, a source document and a relation to the matter. Add a view sorted by date, and relate each event to the issues and evidence it affects and the witnesses who can speak to it.
Can Notion handle discovery or disclosure?
It can track requests, responses and due dates, but bulk document review, Bates numbering and production belong in a purpose-built platform. Use Notion to track what is owed and who is doing what.
How do I see which issues lack evidence?
Relate Evidence to Issues and add a rollup that counts the evidence on each issue. A view of issues with a count of zero, or only unverified evidence, shows your gaps.
How do I prepare for a hearing in Notion?
Create a Hearings database with a preparation checklist template, relate it to the issues in play, the evidence to be relied on and the witnesses, and build a view of the next hearings with their preparation status.
Is it safe to keep privileged litigation material in Notion?
It can be if you tier it, restrict access, label it, keep AI and integrations away from it and review who can see it. Consider keeping the documents themselves in your document system and linking to them. See the privilege guide.
Can I share the tracker with co-counsel or experts?
Share only the pages needed, with named access, and consider privilege and confidentiality consequences before sharing with anyone outside your firm. Prefer a filtered view or export for external experts.
How do I keep the chronology current?
Make recording events a habit: a new document arrives, create or update the event the same day. Add a weekly scan of each matter for new triggers, and a view of events missing a source.
Related guides
- Contract lifecycle management in Notion: a lightweight CLM for small legal teams
- An engagement letter and fee agreement tracker in Notion: no work without a signed scope
- Legal project management in Notion: phases, budgets, scope and status reports
- Legal knowledge management in Notion: a precedent bank and firm wiki that stays current