Build it with AI
Create an operational matter tracker without replacing legal judgment.
Build a focused system for matter status, deadlines, document requests, owners, and administrative workflow.
Introduction
What a law firm case tracker has to hold.
Most teams end up with a law firm case tracker the same way: matter folders, a diary of deadlines, and fee-earner knowledge of where each case stands. Matter administration held in one fee earner’s head works while their caseload is small. It fails when cover is needed, because the state of a matter — what is outstanding, what date is next — is not written anywhere a colleague can read.
The deadline diary and the matter file are separate, so a date is only as safe as whoever last checked both. There is no single view of outstanding items across matters, no visibility of administrative deadlines before they are close, and no record of what was requested from a client and never received.
What follows covers building a law firm case tracker: the records it holds (matters, clients, deadlines, documents, responsible fee-earner, and stage), the systems it reads (Google Drive and Gmail), and what it does not fix.
The problem
Matter status distributed across a practice management system, a mailbox, and a diary.
Practice management systems model time recording and billing thoroughly, and matter progress weakly, which is why the progress lives in email. General project tools have no concept of a matter, a limitation date, or a conflict check.
The records are matters, clients, deadlines, documents, responsible fee-earner, and stage, and the authoritative copy of most of them already lives in Google Drive or Gmail. The matter file says documents requested, the client says they sent them three weeks ago, and both are looking at different mailboxes.
The cost is not the inconvenience: a limitation date is met by memory rather than by system.
You're likely here because
- Covering someone else’s matter starts with reading their email
- The deadline diary and the matter file are separate, so a date is only as safe as whoever last checked both.
- When it is wrong, a limitation date is met by memory rather than by system
What gets built
Launch builds it, Grow operates it.
Built in Launch
- • Matter tracker
- • Deadline views
- • Document request workflow
Operated through Grow
- • Client follow-up
- • Scheduling
- • Referral tracking
Systems it reads
- • Google Drive
- • Gmail
- • Google Calendar
The record model
What a matter record has to carry.
- Administrative state
- Held separately from any legal analysis. This system tracks dates, documents, and ownership, and the separation is the design rather than a disclaimer.
- Outstanding items with age
- Across matters rather than per matter. Per-matter information already exists somewhere; the aggregate does not, and that is where the failures hide.
- Key date with its preparatory steps
- Surfaced in advance rather than on approach, which is the difference between a plan and a scramble.
- Responsible fee earner and supervisor
- Because supervision is a regulated obligation and a cross-matter view that omits it is not usable by the firm.
- Client correspondence received
- Observed from the mailbox, so what a client says they sent and what the file records can be reconciled without an argument.
- Confidentiality and information barrier scope
- Enforced per matter, since the firm may operate barriers and a cross-matter view is exactly where they get breached.
- Retention and destruction rule
- Per your regulator and the firm’s policy rather than a general default, because file retention here is a regulated obligation with dates attached.
How it runs
From scattered matter admin to one tracked state.
Step 01
Describe what a law firm case tracker has to do
Model the administrative lifecycle of a matter — the states, the outstanding items, the dates — as distinct from the legal work. This system tracks the first and does not touch the second.
Step 02
Connect the systems of record
Email supplies client correspondence and what has been received, the document store holds files, and the calendar holds the dates. Reading them makes outstanding items observable rather than remembered.
Step 03
Build the operating surface
A matter record with administrative state, outstanding document requests, key dates with owners, and a view across the caseload rather than per matter.
Step 04
Start narrow
Outstanding document requests across all matters, with age. It is the highest-volume administrative failure in most firms and is invisible without a cross-matter view.
Step 05
Route the exceptions
An administrative date approaching without the preparatory step complete surfaces to the responsible fee earner and to a supervisor, because the cost of missing one is not proportionate.
Step 06
Measure deadlines identified more than a week ahead rather than in the final days
Measure outstanding requests older than their expected turnaround, and administrative dates met without a late scramble. Both are countable and neither touches legal work.
Implementation path
Tracking matters without touching legal judgement.
- 01
Separate administrative tracking from legal analysis in the design and say so explicitly. This system holds dates, documents, and status; it does not advise.
- 02
Baseline outstanding document requests and their age across the caseload. Most firms have never seen this number and find it uncomfortable.
- 03
Start with the cross-matter view rather than per-matter detail. Per-matter information already exists somewhere; the aggregate does not, and that is where the failures hide.
- 04
Have supervision and file-retention requirements reviewed by whoever is accountable before go-live, since both are regulated and neither is a software default.
- 05
Build the narrowest useful version first: matters with an approaching deadline and no recorded activity, surfaced to the responsible fee-earner.
- 06
Separating administrative tracking from legal analysis in the design, in writing, comes first. The cross-matter outstanding-items view is two weeks and is where the value concentrates. Supervision and retention requirements need review by whoever is accountable before go-live; that review is a prerequisite rather than a final sign-off.
- 07
After the outstanding-items view, add key dates with their preparatory steps surfaced in advance. Client-facing status comes later and only where confidentiality has been assessed for it.
Controls
Controls that matter.
Control 01
A hard boundary against legal advice, analysis, or anything that substitutes for professional judgement — this tracks administration only
Control 02
Confidentiality and access control enforced per matter, including information barriers where the firm requires them
Control 03
Retention and destruction handled per your regulator’s requirements and the firm’s policy, rather than by a general default
Examples
Three administrative failures that stop recurring.
The document requested and never chased
A cross-matter view of outstanding requests by age turns a per-matter oversight into a visible queue, which is the only form in which it gets cleared.
Covering a colleague’s caseload
Administrative state on the matter rather than in a mailbox means cover starts from a readable position rather than from an afternoon of reading correspondence.
The date that arrived sooner than expected
Key dates with the preparatory steps attached, surfaced in advance rather than on approach, is the difference between a plan and a scramble.
How it goes wrong
Three ways matter tracking goes wrong.
The system starts summarising documents and suggesting next steps, and has moved from administration into analysis.
Hold the boundary. Anything touching legal judgement stays with the qualified professional, and the drift happens through individually reasonable features rather than a decision.
A limitation date is tracked here and the existing diary control is retired.
Keep it as a supporting record alongside your existing controls. The consequence of a missed limitation date is severe enough that a single point of reliance is inappropriate regardless of the system.
A cross-matter view is built without information barriers, and a fee earner can see a matter they are screened from.
Scope access per matter from the first version. A cross-matter view is precisely the artefact most likely to breach a barrier, and it does so invisibly.
Limitations and considerations
What this deliberately does not do.
- This tracks administration and must not be used for legal advice, analysis, or any judgement reserved to a qualified professional. That is the design boundary rather than a disclaimer.
- Limitation periods and court deadlines carry consequences that no tracking system should be solely relied upon for. Treat it as a supporting record alongside your existing controls, not as a replacement for them.
- Client confidentiality, conflicts, information barriers, and file retention are regulated obligations that vary by jurisdiction. Configuration can support them; the assessment belongs with whoever is accountable at the firm.
- If one fee earner holds a small caseload and never needs cover, this is overhead. If the practice management system already surfaces the cross-matter view, use it — the gap this fills is usually a gap in aggregation rather than in data.
- Connector coverage varies: Google Drive, Gmail, Google Calendar are representative rather than guaranteed, and the fields exposed depend on your workspace permissions.
FAQ
Build a law firm case tracker with AI: common questions.
Does this give legal advice?
No, and it is designed so that it does not. It tracks administrative state — outstanding items, dates, documents, ownership — and every question of legal analysis remains with the qualified professional handling the matter.
Can we rely on it for limitation dates?
Not solely. Use it as a supporting record alongside the controls you already have. The consequence of a missed limitation date is severe enough that a single point of reliance is inappropriate regardless of the system.
How does it handle confidentiality between matters?
Access is scoped per matter and supports information barriers where the firm operates them. Whether a given configuration satisfies your regulator is an assessment for whoever is accountable, and it should happen before go-live.
Will it work alongside our practice management system?
That is the usual arrangement. Practice management stays authoritative for time recording and billing; this holds the administrative matter state those systems model weakly and that currently lives in email.
What should the first version contain?
Matters with an approaching deadline and no recorded activity, surfaced to the responsible fee-earner. Everything else waits until that one is genuinely used.
How will we know whether it worked?
Measure deadlines identified more than a week ahead rather than in the final days against the baseline taken before anything changed.
Related pages
Keep exploring
Start with ARIA
Ask ARIA to build it.
Describe the website, application, workflow, or operating surface you need. ARIA plans, connects, builds, tests, and keeps refining it — inside the permissions you set.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Build a law firm case tracker around the process you actually run.
Build the cross-matter view of outstanding items first, keep the boundary against legal judgement explicit, and have retention reviewed before go-live.