Agentic AI for legal practice · case study

How an agent fleet runs the back office of a law & mediation practice

A real multi-agent system built for a family-law and mediation firm. It takes the routine admin — intake, conflict checks, drafting, scheduling, billing — while every safety call and legal judgment stays with the practitioner. Here's exactly how it works, in diagrams.

Diagram 1 · The architecture

One coordinator, five specialists

A coordinator agent reads every incoming message, runs a safety check first, then delegates to the specialist built for that job. Each specialist has a narrow scope — least-privilege by design.

◆ Coordinator

Reads every message · runs the safety check before anything else · routes to the right specialist

SAFETY GATE RUNS HERE FIRST
Intake & Triage

Classifies the matter, judges urgency, opens the file

Conflict & Safety

Conflict checks + family-violence screening; shuttle vs joint

Drafting

First drafts, every one marked needs review

Scheduling

Books sessions, writes reminders, safety-aware formats

Billing

GST invoices, trust/office separation, arrears

Each specialist reports back to the coordinator, which synthesises the next step for the practitioner.

Diagram 2 · Safety, before anything else

Every message is screened by fixed code — before the AI sees it

The safety check is plain, deterministic code, not an AI decision. It can't be talked around, it's logged, and it works even if the AI is switched off. This is the part most AI tools get wrong.

Client message

Any inbound enquiry

Safety screen (deterministic code)

Scans for risk signals before any AI processing

● Critical

Threat to life, weapon, child in danger, self-harm AI blocked. Shows 000, 1800RESPECT, Lifeline, DCJ. Flags a person.

● High

AVO, assault, coercive control, stalking flags for review, defaults to shuttle, won't join parties without sign-off.

● Clear / Elevated

No critical flags routed to the AI specialists. Elevated factors quietly noted and re-screened as the matter develops.

The safety net is written into the system's foundations, not its personality — testable, logged, always on.

Diagram 3 · Where the human stays in control

The 70% principle — two questions decide everything

For every task the system asks: can it be undone, and can the outcome be checked? The answer places it in one of four boxes — and only the green box runs without a human.

 
Outcome easy to check
Outcome needs expertise
Easy to undo
Automate

Agent acts on its own. e.g. drafting a reminder, classifying a matter.

Assist

Agent drafts; you review. e.g. an engagement letter or parenting plan.

Can't be undone
Gate

Agent prepares; you approve before it acts. e.g. sending a client message.

Human only

Agent surfaces info; you decide. e.g. issuing a s 60I certificate, advising on settlement, a safety call.

What the system never owns

Legal advice or predicting court outcomes · issuing a s 60I certificate or signing a document · the client relationship — trust, empathy, the hard conversation · any safety judgment about a real person. The system flags and escalates; the practitioner decides.

Diagram 4 · A matter, end to end

What it looks like in a working day

A high-risk enquiry arrives. Here's the path it takes before the practitioner has even opened their inbox.

"My ex won't return the kids and there's an AVO because he pushed me."
1

Coordinator

Reads it, runs the safety screen — flags High risk immediately.

2

Intake & Triage

Classifies as a parenting matter, marks it urgent, opens the file.

3

Conflict & Safety

Conflict check clears; recommends shuttle sessions, no joint meeting.

4

To the practitioner

A briefed summary + recommended next steps land for your review.

Every step above is written to a timestamped audit log — nothing happens invisibly.

Diagram 5 · Built for a regulated practice

Auditable, sovereign, resilient

The qualities that make an agentic system safe to run inside a regulated profession.

Full audit trail

Every screen, draft and invoice logged with a timestamp. Nothing invisible.

Key in a vault

The AI key lives in a secure vault, never written into the code.

Checked locally

Client text is safety-screened on-system before anything is sent to the AI.

Fails safe

Safety + admin logic is plain code — it keeps working even if the AI is down.

A foundation, not a finished product

Before it touches a real client file, three things take a practitioner's sign-off: the document templates, the trust-accounting and costs-disclosure flow (against the Uniform Law), and the privacy/storage setup. The system is built so each is a review step — not a rebuild.

The back-office capacity of a much larger firm

Every judgment, every safety call, and every client relationship stays exactly where it belongs — with the practitioner. This is the pattern BIFF AI builds across every domain.

See the full agentic showcase How agents work