Some venues love using AI for incident narratives, monthly review summaries, and quick regulatory questions. Others prefer the platform without it. Venue Axis works cleanly either way — every AI feature is off by default, switched on per-feature with consent, and you can turn the lot off anytime. Patron names and IDs never reach the model. (One documented exception covers AI-assisted migration — see below.)
Two AI features process raw patron content by design: migration (read your existing spreadsheets, paper registers, certificate stacks and turn them into Venue Axis records) and KYC document extraction (read a driver licence or passport and pre-fill the CDD form). Both feed the AI raw images / files because extraction can't work without them. Both run on an Australian-hosted model so patron data does not leave Australia. Here's what we do for these paths.
AI assistance is available only where enabled, with human review before anything is saved or sent. For text features, patron names and IDs are scrubbed before any cross-border call. Vision features (migration, KYC document extraction) run on an Australian-hosted model so patron content stays in Australia. All seven are in production today.
The RGO speaks for thirty seconds. The system drafts a structured incident narrative in the format regulators expect. Staff reviews, edits, and submits. Never auto-files. The single most-used AI feature on the floor.
"How do I respond to a confirmed FRT match?" "What does enhanced CDD require?" Plain-English answers from your obligation library — every answer comes with citations back to the actual rule.
Floor and management feedback gets sorted automatically — bug, feature request, compliance question, support issue — and routed to the right queue. Voice option for staff who don't want to type.
Upload a PDF, Word document, or image up to 10MB. The system extracts structured fields — staff details, certificate expiry dates, AML controls, board minutes — for onboarding and migration. You review before anything is saved.
"Show me patrons with three or more $5k checks this month." "Which staff have expired RCG?" Plain-English in, your data out. Read-only — the system never modifies state.
Drafts the executive narrative for each section of the monthly board pack — incident trends, AML status, FRT accuracy, training compliance, upcoming deadlines. CEO reviews and approves before distribution.
Reads your AML controls and tells you where they fall short of AUSTRAC guidance, in plain English. The AI never invents a rule number — every reference traces back to a real source.
AI in Venue Axis runs inside specific tasks where the output can be checked. Here's what it won't do — and these aren't product decisions we'd revisit later, they're commitments we lock into the architecture.
AI processing is routed by feature. Every patron-bearing AI feature — both vision (migration, KYC document extraction) and text (incident narratives, board-pack commentary, AML controls interpreter, natural-language search) — runs on an Australian-hosted model, so patron data does not leave Australia. Patron identifiers are still scrubbed at the gateway for text features as defence-in-depth, even though the destination is on-shore. Help and feedback features carry no patron identifiers at all and remain on a US-hosted model.
Every AI feature is off by default; staff opt in per profile with consent recorded as an event. Daily call limits and the $20/month default budget cap apply per club. AI never auto-files records — a person signs every regulator-facing submission.