Forum-Aware Disclosure Router for Melbourne Boutique Firms: Get the Right AI-Use Disclosure Into the Right Document

You run a six-lawyer boutique out of the Melbourne CBD. This week your matters cross the Administrative Review Tribunal, the Federal Court, and a Supreme Court of Victoria proceeding. Each forum has its own posture on AI-assisted work — different disclosure expectations, different practice directions, different thresholds for what has to be flagged. You don’t have a precedent bank the size of a top-tier firm, and you don’t have a knowledge-management partner whose only job is to track practice notes. The Forum-Aware Disclosure Router exists so that the disclosure attached to a filing matches the forum it’s being lodged in — not the last template someone happened to copy.

The problem

AI-use disclosure is no longer a single, generic paragraph. The Administrative Review Tribunal’s practice directions and other guidance for professionals and practitioners set expectations specific to ART proceedings, particularly around expert evidence. The Federal Court of Australia’s General Practice Note on the use of generative AI (GPN-AI) sets a separate set of expectations for matters in that jurisdiction. State Supreme Courts are publishing their own guidance, with variation in scope and trigger. For a boutique firm running a mixed forum list, the failure mode is mundane: a Federal Court-style disclosure paragraph dropped into an ART filing, or an outdated template that pre-dates the current practice direction. The Australian Solicitors’ Conduct Rules (Rule 19, candour to the court) treat misleading the tribunal as a professional obligation issue irrespective of the source of the error.

What the Forum-Aware Disclosure Router does

The router takes a filing draft plus the forum it is destined for, identifies the AI-use disclosure language attached (or notes its absence), and routes the document to the compliance template that matches the forum. It is built around a deterministic mapping between forum and the current practice direction or practice note governing AI-use disclosure in that forum — Federal Court (GPN-AI), Administrative Review Tribunal (Practice Directions and Other Guidance), state Supreme Courts where applicable. The output is a draft with a disclosure block that matches the destination forum, plus a short report identifying what was changed and why.

How it works

  1. Upload the draft and select the forum. Federal Court, ART, Supreme Court of Victoria, and other supported forums are selectable from a dropdown. The router treats forum as the controlling input.
  2. The router parses the draft for any existing disclosure language. It flags generic or mismatched disclosures (for example, a Federal Court-style GPN-AI paragraph attached to an ART filing).
  3. The forum-specific compliance template is selected from the router’s mapping, which is keyed to the current practice direction or practice note for that forum.
  4. A revised disclosure block is inserted into the draft, and a change report is generated showing the previous text, the new text, and the primary source the template is derived from.
  5. The output is returned for human review. The router does not file documents and does not substitute for the practitioner’s independent verification of the disclosure against the current practice direction.

Why this matters in Melbourne

A Melbourne boutique typically runs work across federal jurisdictions sitting in the city (Federal Court, Federal Circuit and Family Court, ART) alongside Supreme Court of Victoria and VCAT matters. That mix is exactly where forum-specific disclosure mistakes happen: a template built for one forum gets reused for another because the practitioner’s time is on the substantive argument, not on which paragraph governs disclosure. The ART’s practice directions for professionals and practitioners are published and updated separately from the Federal Court’s GPN-AI, and the two forums do not share a single disclosure standard. The router’s job is to remove the manual step of remembering which template belongs where.

Sources

Exegesis capability references:

Join the waitlist

Join the waitlist — be the first to know when the Forum-Aware Disclosure Router opens for Melbourne boutique firms

The router is in build. We’re scoping pricing tiers for boutiques (per-matter, per-user monthly, or firm-licence) based on demand from firms running mixed federal and state lists. Join the waitlist and we’ll be in touch as access opens.