Community Legal Orchestration Layer for Melbourne Boutique Firms: Run SRL Overflow Without Breaching AI-Use Disclosure
You’re a six-lawyer firm in Melbourne. You take pro bono referrals from a community legal centre, you carry a few NDIS and migration matters at reduced rates, and half the people you assist are self-represented in the Administrative Review Tribunal. The economics only work because you use AI to compress drafting time. The Tribunal’s practice directions on expert evidence and the Federal Court’s General Practice Note on AI now expect disclosure when generative AI materially contributes to a document — and your matter management system has no field for that, no audit log, and no consistent way for the junior solicitor to flag it. The Community Legal Orchestration Layer is the practice layer that sits between your matter system and the tribunal-facing work product.
The problem
Boutique firms carrying community legal centre overflow, SRL assistance work, and low-margin tribunal matters sit in a squeeze. The Administrative Review Tribunal’s practice directions and guidance for professionals set expectations around expert evidence and the conduct of representatives appearing before it. The Federal Court’s GPN-AI sets disclosure expectations for AI use in court documents. The Australian Solicitors’ Conduct Rules (Rule 19) require candour to the court and tribunal. None of these obligations relax because the matter is unpaid or reduced-fee.
What actually goes wrong is operational, not philosophical:
- The junior who drafted the statement of facts used an LLM for tone, didn’t note it on the file, and the principal signing off doesn’t know
- A volunteer working from the CLC partner uses a different tool stack than the firm
- The expert report for a low-cost NDIS review was summarised by AI before the principal read it, and there’s no record of which paragraphs were model-generated
- When the Tribunal or opposing party asks how the document was prepared, the firm cannot answer with precision
A boutique cannot afford a separate compliance officer for pro bono work. The orchestration layer has to make disclosure-correct conduct the default path.
What the Community Legal Orchestration Layer does
The Community Legal Orchestration Layer is a practice layer specifically scoped for firms running community legal centre overflow and low-cost matters alongside paid work. It sits above your existing matter management and:
- Tags every document by AI-contribution level (none, drafting assistance, substantive generation, summarisation of evidence)
- Maintains a per-matter AI-use log suitable for disclosure to the ART, the Federal Court, or opposing parties on request
- Routes draft tribunal documents through a pre-lodgement check (using RuleCheck, the open-source citation verifier at github.com/andrefabre/rulecheck) before they leave the firm
- Provides a standard disclosure footer template aligned with GPN-AI expectations, which the responsible solicitor can adopt or override
- Distinguishes CLC-referred work from paid matters in the audit trail, because the disclosure expectations are the same but the supervision model often differs
It is not a matter management system. It does not replace your existing PMS. It is the disclosure and AI-governance layer that wraps low-margin community-facing work so a six-lawyer firm can carry it without exposure.
How it works
- Matter onboarding. When a matter is opened (paid, pro bono, or CLC overflow), it inherits an AI-use policy template. SRL-assistance and tribunal matters default to stricter disclosure logging.
- Document tagging. As drafts move through the firm, each contributor records whether AI was used and at what level. The tag travels with the document.
- Pre-lodgement check. Before a document is filed at the ART or Federal Court, it runs through RuleCheck for citation verification and through the orchestration layer for disclosure-footer review.
- Disclosure artefact. On request from a tribunal, opposing party, or principal, the layer produces a structured AI-use log for that matter — what tool, what stage, who supervised.
- Periodic review. The principal receives a weekly summary of AI-use across all open matters, flagging any document filed without a recorded disclosure decision.
Why this matters in Melbourne
Melbourne boutique firms sit close to several community legal centres and carry a disproportionate share of Victorian ART work — migration review, NDIS, social services, veterans’ affairs. The ART’s published practice directions and guidance for professionals apply identically whether the representative is a Collins Street partner or a sole practitioner taking a CLC referral. The Federal Court sits in Melbourne and the GPN-AI applies to filings made here. A disclosure failure on a pro bono matter creates the same professional standards exposure as one on a paid matter — and arguably more reputational risk, because the SRL on the other side has less ability to absorb the consequences of a flawed filing.
Sources
- Administrative Review Tribunal — Practice Directions and other guidance for professionals and practitioners: https://www.art.gov.au/help-and-resources/professionals-and-practitioners/practice-directions-and-other-guidance
- Federal Court of Australia — Use of Generative Artificial Intelligence Practice Note (GPN-AI): https://www.fedcourt.gov.au/law-and-practice/practice-documents/practice-notes/gpn-ai
- Law Council of Australia — Australian Solicitors’ Conduct Rules: https://lawcouncil.au/policy-agenda/regulation-of-the-profession-and-ethics/australian-solicitors-conduct-rules
- AustLII (Australasian Legal Information Institute): https://www.austlii.edu.au/
- RuleCheck (open-source citation verifier by Exegesis): https://github.com/andrefabre/rulecheck
Join the waitlist
We’re scoping the orchestration layer with a small group of Melbourne boutiques running CLC overflow and ART matters. Pricing has not been set. Join the waitlist and the way you describe your current workflow will shape how the layer wraps it.