Client/Firm Privilege Boundary Orchestrator for Melbourne Boutique Firms: Stop Privilege Bleeding Between Matters

You run a seven-lawyer shop in the Melbourne CBD. Two partners are on opposite sides of a commercial dispute that’s threatening to land in the Administrative Review Tribunal. One of your juniors has been using the firm’s shared AI assistant to draft chronologies for both matters — same model, same workspace, same retrieval index. You don’t know what context the model is pulling from when it answers a prompt for Matter A. Neither does the junior. The ART’s expert evidence practice direction expects expert material to be the witness’s own independent work; your own ASCR obligations require you to maintain confidentiality between clients with adverse interests. The Privilege Boundary Orchestrator is built to make those boundaries enforceable at the tool layer, not just on a wall planner.

The problem

Boutique firms run lean. A single shared AI workspace — whether a Copilot tenant, a Claude project, or a self-hosted RAG stack — usually contains material from every active matter, because nobody has time to spin up a new environment for each engagement. That convenience produces three failure modes that show up specifically in firms under ten lawyers:

The Australian Solicitors’ Conduct Rules — Rule 9 (confidentiality) and Rule 10 (conflicts concerning former clients) — apply whether a breach happens through a paralegal’s filing cabinet or a model’s vector store. The ART’s practice direction on expert evidence assumes the expert’s report reflects their own opinion; AI-assisted preparation that touches conflicted material undermines that assumption.

What the Client/Firm Privilege Boundary Orchestrator does

The Orchestrator sits between your lawyers and the AI tools they use. It manages privilege boundaries between client work and firm-internal use of AI by:

The Orchestrator does not replace your conflict check at intake. It enforces the conflict decisions your firm has already made, at the layer where they most often fail in practice.

How it works

  1. Matter intake binding. When a new matter opens, the Orchestrator captures the matter ID, the parties, declared adverse parties, and any ethical walls. This becomes the access policy for that matter.
  2. Workspace partitioning. Each matter’s documents, prompts, and retrieval indices are tagged and partitioned. Lawyers see a single interface; the Orchestrator enforces which slices are reachable from which context.
  3. Prompt-time enforcement. Every prompt is evaluated against the matter context the lawyer is working in. Retrieval from conflicted partitions is blocked and logged.
  4. Expert evidence mode. When a workflow is flagged as supporting expert preparation, the Orchestrator restricts retrieval to material the expert has been formally briefed on and produces a separate audit trail.
  5. Audit export. A per-matter access log is exportable as a Markdown or PDF report, time-stamped, suitable for governance review or production in response to a privilege challenge.

Why this matters in Melbourne

Boutique firms in Melbourne handle a disproportionate share of ART-bound matters — migration review, NDIS, taxation, veterans’ affairs — alongside Supreme Court of Victoria commercial work where the same parties recur across years. Concurrent representation and successive representation issues are routine, and the cost of an enforced conflict is high enough that firms invest heavily in intake screening. That intake screening is undermined the moment a shared AI workspace pools material across matters without enforcement. The ART’s expert evidence practice direction adds a second front: where your firm briefs experts who give evidence before the Tribunal, you need to be able to show that AI tools used in preparation did not blur the line between the expert’s own analysis and material from other firm matters. A Melbourne boutique typically cannot afford a dedicated information governance team — the Orchestrator is built to enforce the rules a larger firm would staff a team to enforce manually.

Sources

Exegesis capability references:

Join the waitlist

Join the waitlist — be the first to know when the Privilege Boundary Orchestrator opens to Melbourne boutique firms

The Orchestrator is in design partner conversations with boutique firms now. We’re sizing the right deployment model — single-tenant hosted, self-hosted on firm infrastructure, or hybrid — and pricing structure based on what design partners actually need. Join the waitlist and we’ll bring you into that conversation early.