Law firms still run on paper diaries, spreadsheets and WhatsApp groups. AdvoAI brings matters, hearings, orders and delegation into one web app — and in v2 it reads court orders, so the team confirms changes instead of retyping them.
Legal work was scattered across diaries, spreadsheets, WhatsApp and folders — priorities and hand-offs got lost, and every court order meant retyping dates by hand.
Research, information architecture, flows, wireframes, UI and a reusable component system for every role in a chamber.
Priority flows from the 05 Oct 2026 brief: capture an order and confirm what changes, Today by role, hearing outcomes and onboarding — as a clickable prototype.
How might we give a legal team one workspace to organise work and collaborate — without adding complexity?
Confirmed where we agreed, challenged where testing or the brief’s own principles pointed elsewhere.
Today, Matters, Calendar, Tasks and Clients — with search, + Add and notifications on every screen.
“+ Add” means Add order / document: the most frequent, most valuable task gets the main button.
A right panel on every matter tab — never a tab or a second sidebar.
Never typed on a matter; it changes only when an outcome is recorded or a hearing is added.
Hearing date, order date, filing deadline, the other side’s deadline, limitation.
The same Today page, with a different emphasis for each role.
Today leads with — sign-offs and drafts to review
Needs — to know what changed overnight, without chasing
Today leads with — drafts, orders to capture and hearings to prepare
Needs — to hand work up for review cleanly
Today leads with — the whole board — printable on A4
Needs — to save hearing dates without waiting on an advocate
Uploads become — “Waiting for an advocate” drafts in the right queue
Needs — work that never disappears
Every court order meant retyping dates, tasks and stages by hand.
Upload, paste or photograph an order. AdvoAI proposes the changes on a confirm card — next date, tasks, reminders, stage — each linked to its source paragraph.
The team confirms instead of types, and every change can be checked against the order.
A confident-looking extraction error is worse than a gap.
Low-confidence fields are amber and unticked by default, with the reason and a link to the source.
People check exactly the fields that need checking.
Seniors, juniors and clerks start the day needing different things.
The same page leads with sign-offs for seniors, drafts and capture for juniors, and the whole board for clerks.
One product to learn, with the right work on top for each role.
A clerk can’t confirm tasks or stages, so the whole card used to stop.
Task and stage rows show as disabled — “Needs an advocate” — while the clerk can still save the hearing date.
The date lands on time; the advocate signs off the rest.
An answer a lawyer can’t verify is a liability in court.
Ask AI cites the matter’s documents, opens the source beside the panel, and declines questions outside them.
Every answer can be checked before it is used.
Final designs — Today, Matter overview, Ask AI with cited sources, and the order confirm card
A Daily Brief, a scannable matters table, a calendar that makes busy days obvious, and roles and consent in the open — on one component library.
The capture → read → confirm flow with every edge case (low confidence, no match, duplicate, couldn’t read), Today by role, hearing outcomes and onboarding.
A clickable prototype with five starting points, built for sessions with 3–5 advocates and a clerk.
The hard part was deciding what not to show on each screen.
Measure how often confirm cards are accepted unchanged, and which fields people correct.
Making AI‑drafted legal citations verifiable.