Filing Verification Gateway for Brisbane In-House Counsel: One Check Before Anything Leaves the Legal Team

Your commercial team drafted the response. External counsel reviewed it. A paralegal ran a clean-up pass through a model to tighten the language. Now it’s sitting in your inbox at 4:50pm, due for lodgement tomorrow, and you are the last set of eyes before it goes out under your in-house team’s name. You don’t have time to re-verify every citation, re-check every disclosure obligation, or audit which paragraphs were touched by AI. The Filing Verification Gateway is the single pre-lodgement checkpoint built for that moment.

Why it matters now

The Australian Solicitors’ Conduct Rules apply to solicitors employed in-house as much as they do to private practitioners. Rule 19 (duty to the court — candour) and Rule 4 (duty to act with honesty and integrity) extend to any filing or correspondence produced under a solicitor’s name, irrespective of who actually drafted the text or what tools were used. Where any part of a document has been generated, summarised, or rewritten by a language model, the solicitor of record remains responsible for its accuracy and for whatever disclosure obligations attach in the jurisdiction or forum the document is going to. In Queensland, the ASCR were adopted in June 2012 and remain the operative conduct framework for solicitors, including in-house counsel. The Law Council’s 2026 review of the ASCR signals that the rules are actively being calibrated to new ethical pressures — AI use sits squarely in that space. Disclosure non-compliance is rarely deliberate; it is almost always the product of a workflow that never had a single, enforced verification step before lodgement.

The 5-minute view

• AI-use disclosure non-compliance is the risk that a document drafted, edited, or summarised with AI is filed without the verification, disclosure, or audit-trail steps required by the relevant rules or court practice notes
• ASCR Rule 19 (candour) and Rule 4 (honesty and integrity) attach to the solicitor of record regardless of who or what produced the text
• In-house teams typically lack a structured pre-lodgement gate — the document moves from drafter to filer with no enforced verification step in between
• Manual checks across citations, disclosures, formatting, and authority references are not feasible at the pace of in-house workload
• The Filing Verification Gateway runs a battery of deterministic checks on a draft filing in a single pass and returns a structured readiness report
• It is the orchestration layer over RuleCheck’s individual verification agents (citation verification, disclosure checks, authority cross-reference, format checks)
• The gateway runs locally — draft content is not sent to external LLMs

What Exegesis is building

The Filing Verification Gateway is the core orchestration feature of RuleCheck by Exegesis — a local-first, deterministic, no-external-LLM pre-lodgement filing checker. RuleCheck is live in beta at rulecheck.onrender.com and accepts .txt or .md filing drafts. The gateway runs each verification agent in sequence against the draft — citation verification against the Australian authority registry, disclosure-clause detection, internal cross-reference checks, and formatting checks — and returns a single consolidated readiness report. The architecture is intentionally narrow: it does not generate new legal content, does not store filing drafts beyond the configured retention period, and does not transmit content to external services. For an in-house team, that posture matters — privileged commercial content stays inside your environment.

How it works

1. Upload the draft. Submit the .txt or .md filing or correspondence draft through the RuleCheck interface.
2. Gateway orchestration. The Filing Verification Gateway invokes each verification agent in sequence against the document — no model inference, no external calls.
3. Per-check findings. Each agent returns its own findings: citations (verified / mismatched / not found), disclosure-clause presence, authority cross-references, format issues.
4. Consolidated readiness report. The gateway returns a single Markdown report with a top-line readiness status and per-section detail.
5. Archive. The report is suitable for archiving alongside the matter file as evidence of the pre-lodgement verification step.

Why this matters in Brisbane

Queensland adopted the ASCR in June 2012 and they remain the operative conduct rules for solicitors practising in the state, including in-house counsel employed by Queensland-based corporates, government entities, and statutory bodies. In-house teams in Brisbane often sit at the intersection of multiple lodgement environments — Queensland Supreme Court filings, federal regulatory submissions, ASX disclosures routed through legal — and each carries its own verification expectations under ASCR Rule 19 and Rule 4. A single pre-lodgement gateway is the simplest way to make the verification step a workflow artefact rather than an act of trust.

Sources

1. Law Council of Australia — Australian Solicitors’ Conduct Rules: https://lawcouncil.au/policy-agenda/regulation-of-the-profession-and-ethics/australian-solicitors-conduct-rules
2. 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
3. AustLII (Australasian Legal Information Institute): https://www.austlii.edu.au/

Exegesis capability references:

• RuleCheck by Exegesis — live beta
• Filing Verification Gateway Agent spec

Join the waitlist

Join the waitlist — be the first to know when access tiers open for Brisbane in-house legal teams

The Filing Verification Gateway is live in beta as part of RuleCheck. We’re scoping the right access structure (per-filing, per-user monthly, or in-house team licence) based on demand from corporate legal teams. Join the waitlist and we’ll let you know when access opens — and what we hear from you will shape how the tier you sit in actually works.