00 — Overview

Queensland Audit Office (QAO) reference application. This is a demonstration prototype modelled on the Queensland Audit Office's public-facing documentation, reports, guidance and activities. It is not an official QAO system and holds no real audit information — every entity, request, allegation, finding and decision in the demo data is fictional and illustrates the data model and workflow only.

What ARIM is

The Audit Request & Investigation Manager turns the handling of audit requests and investigations into a structured, integrity-controlled record. A finding isn't "made" because someone concluded it — it stands when the request was triaged and assessed for jurisdiction and conflict, the investigation gathered evidence with a chain of custody, the finding is linked to that evidence and tested by procedural fairness, and an authorised decision and complete closure record follow. ARIM holds every one of those links so the integrity of a case is always demonstrable.

The domain

Audit offices receive requests and disclosures, decide which to investigate, and must conduct investigations that withstand scrutiny — with conflicts managed, evidence defensible, and subjects given a fair chance to respond before findings are settled. The hard parts are triage (accept / refer / decline?), evidentiary integrity (custody and issue linkage), and procedural fairness (natural justice). ARIM models all three, keeping outcomes anchored to evidence and process.

The 22 models by area

Intake & Triage (7) - Entity — an organisation (subject / accountable). · AuditRequest — a request or disclosure received. - RequestIssue — a discrete allegation/issue. · TriageAssessment — the accept/refer/decline triage. - JurisdictionAssessment — in-scope determination. · ConflictAssessment — conflict-of-interest check. - InformationRequest — a request for more information.

Investigation (2) - Investigation — the investigation itself. · InvestigationPlan — its versioned plan.

Evidence (5) - EvidenceItem — a piece of evidence. · EvidenceIssueLink — links evidence to an issue (supports/contradicts). - ChainOfCustody — a custody event for evidence. · Interview — an interview. · ChronologyEvent — a dated event in the case chronology.

Findings & Fairness (3) - Finding — a finding against an issue (substantiated?). · FindingEvidenceLink — links a finding to its evidence. - ProceduralFairnessResponse — a natural-justice response to a finding.

Outcomes & Closure (5) - Recommendation — a recommendation. · Referral — a referral to another body. - Decision — an authorised decision. · ClosureRecord — the closure with completeness checklist. - StatusHistory — the request's lifecycle trail.

(The source pack's DomainEvent outbox is Phase 2 — see page 03.)

The demo scenario

A QAO-style case: a public official's protected disclosure alleging procurement irregularities at the Department of Regional Development:

  • Intake & triage: two issues (an undisclosed conflict of interest and alleged split purchasing); triaged ACCEPT_FOR_ASSESSMENT; jurisdiction IN_SCOPE (with a referral flagged); lead investigator conflict-clear; an information request answered.
  • Investigation: an approved plan; evidence (evaluation records, an email chain) with issue links and a chain of custody; two interviews; a three-event chronology.
  • Findings & fairness: the conflict finding SUBSTANTIATED (evidence-linked), split purchasing NOT_SUBSTANTIATED; procedural fairness completed (finding unchanged).
  • Outcomes: a recommendation to DRD, a referral to the CCC, an approved decision, and a complete closure record.

36 rows across all 22 models — a full, defensible case from disclosure to closure.