Verification Load Balancing Orchestrator for Perth In-House Counsel: Spread the AI-Output Verification Load Before It Snaps

You run legal for a Perth-based business. You have three external panel firms, two in-house lawyers, and a commercial team that discovered ChatGPT eighteen months ago. Drafts now arrive on your desk that nobody can confidently say were — or weren’t — generated, summarised, or “polished” by a model. The Australian Solicitors’ Conduct Rules still apply to every solicitor touching that work, in-house and external. Verification of AI-influenced output has become a bottleneck sitting on one or two people. The Verification Load Balancing Orchestrator is built to redistribute that load before something slips through.

The problem

Shadow AI use inside a firm — or inside the business units your in-house team supports — isn’t a single discrete event. It’s a steady stream of contracts, board papers, advice memos, and external counsel drafts where the provenance of any given paragraph is unclear. Western Australia adopted the Legal Profession Uniform Law on 1 July 2022, bringing WA solicitors under the Legal Profession Uniform Law Australian Solicitors’ Conduct Rules 2015. Those Rules — covering candour, competence, supervision and the duty not to mislead — apply to in-house solicitors holding a practising certificate just as they apply to firm partners. When verification of model-influenced output piles up on one senior lawyer, two things go wrong: items get rubber-stamped under deadline pressure, or the queue stalls and business stakeholders route around legal entirely. Both are governance failures the General Counsel ends up wearing.

What the Verification Load Balancing Orchestrator does

The Verification Load Balancing Orchestrator distributes verification workload across the partners and reviewers available to your legal function — internal counsel, external panel partners, and contracted reviewers — so that no single person becomes the choke point for AI-output sign-off. It treats verification as a routable workflow: each incoming document is classified by risk, matched to a reviewer with appropriate seniority and capacity, and tracked through to a recorded sign-off. The orchestrator does not make the legal judgement — a human solicitor does that — but it does the routing, queueing, escalation, and audit-trail work that otherwise lives in someone’s inbox.

How it works

1. Intake. A draft (contract, advice, submission, board paper) is submitted to the orchestrator with metadata: matter, originator, AI-use disclosure, urgency, and risk tier.
2. Classification. The orchestrator tags the document by verification depth required — full citation check, clause-by-clause review, factual-claim verification, or light-touch sanity check — based on configured firm rules tied to ASCR obligations (candour, competence, supervision).
3. Routing. It assigns the document to the reviewer with the right seniority, capacity, and conflict-clear status. Panel firms, in-house seniors, and contracted reviewers all sit in the same routing pool with configurable weights.
4. Verification step. The assigned reviewer completes the check (often supported by RuleCheck for citations and rule references) and records a structured sign-off — verified, amended, or rejected — against the document.
5. Audit log. Every routing decision, reviewer assignment, and sign-off is recorded in an immutable log the General Counsel can produce on request, including for professional standards or regulator queries.

Why this matters in Perth

WA solicitors have been operating under the Legal Profession Uniform Law and the Uniform-law version of the ASCR since 1 July 2022. For an in-house team in Perth, that means your practising-certificate-holding lawyers carry the same conduct obligations as a partner at a national firm — including the supervisory duties under the ASCR for work product they put their name to, regardless of whether a model touched it first. The Law Council’s 2026 review of the ASCR is also live, with proposals around solicitors’ duties when acting on client instructions and reporting obligations under the Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth) regime commencing 1 July 2026. The compounding effect — AML/CTF reporting obligations layered on top of unresolved AI-verification load — is exactly the kind of governance pressure a Perth GC needs a defensible workflow for, not a heroic individual.

Sources

• Law Council of Australia — Australian Solicitors’ Conduct Rules: https://lawcouncil.au/policy-agenda/regulation-of-the-profession-and-ethics/australian-solicitors-conduct-rules
• RuleCheck by Exegesis (open-source pre-lodgement checker): https://github.com/andrefabre/rulecheck

Join the waitlist

Join the waitlist — be the first to know when the Verification Load Balancing Orchestrator opens for Perth in-house legal teams

The Orchestrator is in design partner phase. We’re working with a small number of in-house functions to calibrate routing rules, reviewer-pool configurations, and audit-log formats against real ASCR supervision and candour obligations. Join the waitlist and we’ll be in touch as access opens — and what we hear from you will shape how routing logic is configured for teams like yours.