Sovereign AI for Australian Professional Sport

Athlete medical information is treated as the most sensitive data class in the deployment. It is processed only on infrastructure the club or code has contractual control of (single-tenant Australian sovereign cloud or on-premises), and is never disclosed to any third party — including the model provider, the cloud provider or any downstream service. Access to athlete medical content inside the model is role-aware: the medical and high-performance staff who would have access in the existing clinical system are the only people who can retrieve it through the AI. We can produce the architectural documentation that the club doctor, the integrity officer and the AFLPA/RLPA/PFA/ACA-equivalent representatives need to confirm the arrangement satisfies the relevant player-collective agreement.

No. Broadcast-rights contracts and the surrounding commercial material are typically subject to some of the strictest confidentiality clauses in the business. The deployment handles this material under tighter controls than other content: a single-tenant environment with no external network exposure for the contract-retrieval workload, role-aware access restricted to the commercial team and in-house counsel, and an immutable audit log of every interaction with broadcast-rights content. The model itself never sends the underlying contract content to a third party, and the trained model is yours — not a shared model. This is materially stronger than the alternative (the club’s commercial team using a public AI tool on contract drafts) which today is the more common quiet exposure.

Yes. The model holds the current AFL Total Player Payments rules, NRL salary cap and Top 30 squad rules, A-League cap and visa-player provisions, and NBL cap rules — whichever code is applicable — alongside your full player contract estate. Scenario modelling questions ("if we move this player and sign that one, what does our cap position look like in years one through four", "what is our list-aged profile if we draft three rookies this year and one next year", "which of our contracts have automatic-trigger clauses next September") get answered against your actual data in seconds. The list manager and salary-cap analyst still make the decisions; the modelling friction that today depends on dedicated spreadsheet work compresses to live conversation.

The model is given the Sport Integrity Australia frameworks, the World Anti-Doping Code as implemented through the National Anti-Doping Scheme, and the relevant code-specific integrity rules as ground truth. The integrity officer uses the model to draft TUE applications against the WADA International Standard for Therapeutic Use Exemptions, to check athlete supplement declarations against the club’s or code’s supplement policy, and to triage potential integrity incidents against analogous prior precedent. Athlete biological passport and TUE content is processed under the same tight athlete-medical-data controls described above — no third-party disclosure surface. The chain-of-custody implications for any subsequent SIA or Court of Arbitration for Sport proceeding are preserved.

Yes — in fact, national sporting bodies (Cricket Australia, the AFL, the NRL, the AOC, Sport Australia, the Australian Institute of Sport and the equivalent national federations for the Olympic sports) have an even broader use case. The same architecture extends across high-performance programmes, athlete-pathway management, anti-doping and integrity functions, commercial and partnership functions and member federation support. For the AIS specifically the deployment can support athlete management across multiple sports while respecting sport-specific access boundaries. For Sport Australia the deployment can support grant-program assessment, member-organisation governance support and the National Sport Plan implementation.

Yes, with the appropriate interface. The deployment is typically available through a club-controlled application that runs on the head coach’s preferred device (laptop, tablet, secured phone). On a typical match week the head coach uses it to retrieve opposition profile material, prior matchup analysis, the latest set-piece patterns the opposition has used, selection-paper material grounded in form and matchup data, and pre-match briefing pack assembly in the coach’s preferred format. On game day the high-performance team continues to use it for live data interpretation off the bench. The interface is built to the football department’s requirements rather than a generic dashboard.

For a single club a typical deployment runs ten to twelve weeks: two weeks of football, commercial and integrity scoping, six weeks of ingestion and fine-tuning across GPS, video-analytics, medical notes, commercial contracts, opposition-analysis archive and the relevant code regulation, then a four-week football-department pilot. The football department is doing useful retrieval inside the pilot window, with whole-of-club rollout following over the subsequent two to three months. For a code (AFL, NRL, A-League, Cricket Australia) the timeline extends to four to six months because the league has additional integrations (the league data layer, member club data exchange, integrity-related code-of-conduct material) and the governance pathway through the league’s technology, integrity and commercial committees is correspondingly longer.