Filing Verification Gateway for Melbourne Litigation Lawyers: One Pre-Lodgement Check Across Citations, Disclosure and Format
You’re filing into the Administrative Review Tribunal tomorrow morning. The brief draws on an expert report, a chronology your associate built with AI assistance, and a submission you’ve rewritten three times. Somewhere across those documents you need to confirm: every authority cited exists and matches the report, AI use is disclosed in the form the practice directions expect, formatting complies, and nothing flagged by the Federal Court’s GPN-AI has slipped through unverified. Doing that by eye, at 9pm, is how disclosure failures happen. The Filing Verification Gateway runs the battery for you before the document leaves your machine.
The problem
The Administrative Review Tribunal, which replaced the AAT in October 2024, publishes practice directions and guidance for practitioners — including directions touching expert evidence and the conduct of proceedings. Where AI is used to prepare any part of a filing, practitioners need to be confident the document satisfies whatever disclosure expectation applies in that forum, and that it doesn’t carry a downstream defect — a fabricated citation, an unattributed AI-generated passage, a mismatch between an expert’s report and how it’s described in submissions. Federal Court GPN-AI sets one set of expectations; ART practice directions sit alongside it for tribunal work; state Supreme Court rules layer on top for parallel matters.
A litigation lawyer running a mixed-forum practice in Melbourne needs each filing checked against the rules of the forum it’s headed to — not a generic checklist. AI-use disclosure non-compliance isn’t usually deliberate; it’s a draft passing through three people, AI assistance in one stage, and the disclosure step missed because no one owned it.
What the Filing Verification Gateway Agent does
The Filing Verification Gateway is the core orchestration layer of RuleCheck by Exegesis. It runs a battery of pre-lodgement checks on a draft filing in a single pass and returns a structured readiness report. The checks include:
- Citation verification against the Australian authority registry (Federal Court, Federal Circuit and Family Court, High Court, State Supreme Courts, AustLII) — every cited authority extracted and statused as verified, mismatched, or not found
- AI-use disclosure presence check against the forum the filing is headed to (Federal Court GPN-AI, ART practice directions, state Supreme Court rules)
- Format and structural checks tied to the lodgement forum
- Cross-document consistency (expert report citations vs how the report is described in submissions)
The architecture is deliberately narrow: deterministic checks against authoritative registries and rule sources, no external LLM inference on draft content, local-first processing.
How it works
- Upload your draft (and any expert report or annexures) as
.txtor.mdto the RuleCheck interface. - Select the lodgement forum — Federal Court, ART, Victorian Supreme Court, etc. The gateway loads the relevant rule set.
- The gateway runs the check battery in parallel: citation extraction and verification, disclosure-clause detection, format checks, cross-document consistency.
- You receive a single markdown readiness report listing every finding, its severity, the rule it ties to, and a recommended action.
- Archive the report alongside the matter file as an audit artefact of pre-lodgement verification.
Processing typically completes within seconds to a minute for documents under 10 pages.
Why this matters in Melbourne
Melbourne litigation practices commonly run mixed-forum workloads — Federal Court commercial matters, ART migration and NDIS reviews, Victorian Supreme Court proceedings, and Federal Circuit and Family Court family law work — often inside the same week, sometimes inside the same team. Each forum has its own rule set and its own evolving position on AI use. Federal Court GPN-AI is explicit about practitioner responsibility for AI-assisted content. The ART publishes practice directions and guidance that practitioners are expected to comply with on tribunal filings. Running a single pre-lodgement gateway — one that knows which rule set applies to which filing — is materially less error-prone than relying on each fee-earner to remember the disclosure posture of the forum they’re filing into that day.
Disclosure non-compliance, once flagged by a registrar or opposing counsel, is the kind of finding that follows a practitioner across files. The cheaper place to catch it is before lodgement.
Sources
- Administrative Review Tribunal — Practice Directions and Other Guidance: 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
- Federal Court of Australia — Rules, Acts & Regulations: https://www.fedcourt.gov.au/law-and-practice/rules-acts-and-regulations
- AustLII (Australasian Legal Information Institute): https://www.austlii.edu.au/
Exegesis capability references:
Join the waitlist
The gateway is live in beta as the orchestration layer of RuleCheck. We’re scoping pricing tiers — per-filing, per-user monthly, or firm-licence — based on how mixed-forum Melbourne practices actually want to consume it. Join the waitlist and what we hear from you will shape the tier you sit in.