Education Administration /Drafting live field guide · 8 min

Compliance Evidence Assembler

Drafts an ASQA/AVETMISS-style evidence pack against the regulator's template from records kept current, flagging every gap — so audit prep is review-and-sign-off, not a weekend of hunting.

Open the live demo

theater/demos/edu-admin_compliance-evidence-assembler.html · sandbox · read-only

Open

FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads the regulator's evidence request, maps every requirement to the records you already hold, drafts the portfolio with each source attributed, and lays out every gap for a compliance officer to verify and approve before anything goes to ASQA.

Input 01

The request + your records

An ASQA performance-assessment evidence request for a sampled qualification, plus the records you already hold — training and assessment strategy, assessment tools and validation records, the trainer/assessor matrix, student files, and the complaints register.

Agent 02

Maps, attributes, tags

Maps each requirement to the document that evidences it, attributes the source on every line, and tags each requirement fully evidenced, partial, or a gap — with a concrete rectification action where it falls short.

Output 03

A draft pack, gaps flagged

A portfolio assembled to the regulator's structure with its working shown, every gap surfaced for a compliance officer to verify, close, and approve before it is submitted to ASQA.

Where it works well

It does the requirement-by-requirement cross-check every time, in full, and attributes every source.

Done by hand it is days of hunting per qualification — and the requirements that get skimmed are the ones that fail the audit.
Best for a compliance or quality officer at an RTO or TAFE preparing for a performance assessment, re-registration, or pre-audit self-assessment.
Run continuously, gaps surface as records go stale, so the recaptured days go back into fixing evidence — not assembling it under deadline.

The slow, invisible cost of an audit is the tracing — walking every requirement back to the one document that evidences it, across student files, validation records and a trainer matrix that all live in different systems. That work is what gets compressed into the fortnight before the performance assessment.

Where it works badly

It is confidently wrong when it maps a stale or superseded document to a requirement — and the pack looks complete either way.

Weak where evidence is judgement, not a document — whether an assessment tool actually meets the rules of evidence, or whether validation was genuine. It should flag for review, not declare it met.
If your records live as scanned PDFs and email threads with no index, the map is only as good as what it can find, and a missing document reads the same as one that does not exist.

The honest test

If you cannot say, right now, that every document this pack cites is the current, signed-off version — this tool makes your audit submission faster, not safer.

Point it at last year's training and assessment strategy, a validation record that was never signed off, or a trainer file missing current industry currency, and it assembles a clean, well-attributed portfolio that evidences requirements with documents that would not survive scrutiny. That is the trap.

What it doesn't do — and shouldn't

It drafts the pack and flags the gaps. A compliance officer approves. That boundary is deliberate.

WHAT IT DOES

Surfaces the document it mapped to each requirement, with its source attributed

Tags every requirement fully evidenced, partial, or a gap

Drafts a rectification action for each gap and flags it for review

WHAT IT WON’T

Submit the portfolio to ASQA

Certify that the RTO is compliant

Judge whether an assessment tool or validation actually meets the rules of evidence

An evidence portfolio is what a performance assessment is decided on, and the consequences of a wrong submission — rectification, conditions, or cancellation of registration — land on the RTO and its CEO, not on a tool. ASQA assesses against the Standards for RTOs; the accountable person stays on the decision because the regulator holds them, not the software, responsible.

What your data has to look like

Your records held as identifiable, current documents — and a way to know which version is the one in force.

Typical readiness

across orgs we see, before the first job

Training and assessment strategy, current version

Usual weak point

Assessment validation records, signed off

Needs shaping

Trainer and assessor matrix with currency

Needs shaping

Student records and AQF certification issuance

Usual weak point

Complaints and appeals register

Usually ready

The real first job

The validation records and the trainer matrix are usually the weak point — held in someone's head, an unsigned spreadsheet, or a folder nobody owns. Fixing how that evidence is captured and kept current is usually the real first job — larger and more valuable than the assembly layer on top. Once the records are in order, every audit after that is an export, not a fire drill.

Right fit if…

You face ASQA performance assessments, re-registration, or course accreditation on a recurring cycle

You hold a large or multi-site scope where keeping evidence audit-ready is a continuous workload

Your records live in systems you can point to — SMS, validation schedule, trainer matrix

You want pre-audit self-assessment running continuously, not a fortnight before the deadline

Walk away if…

Your evidence lives as unindexed scanned PDFs and email threads

Your validation records are unsigned or held informally in people's heads

You need a tool that certifies you compliant rather than assembles the evidence

You run a tiny single-qualification scope where a spreadsheet already keeps you ready

Open questions

The worried-buyer questions, answered straight

It can map a stale or unsigned document to a requirement and make the pack look complete — which is exactly why nothing is submitted on its say-so. It attributes the source on every line, tags each requirement as fully evidenced, partial, or a gap, and flags where it could not match cleanly. A compliance officer verifies each one before approving. The tool assembles and shows its working; the accountable person stands behind the submission to ASQA.

It works from records it can identify and read — a current training and assessment strategy, signed validation records, the trainer matrix, student data from the SMS. Where evidence is an unindexed scan or buried in an email thread, a missing document reads the same as one that does not exist, and the map is only as good as what it can find. Getting that evidence indexed and current is usually the first piece of work — and the piece that pays off across every audit after.

No. It removes the hunting and the cross-referencing — the days of tracing each requirement back to a document — so the officer spends their time on the judgement: whether an assessment tool actually meets the rules of evidence, whether validation was genuine, whether a gap is real. The portfolio is still theirs to approve. The capacity it frees goes back into closing real gaps before the regulator finds them.

Current to the version in force. A training and assessment strategy gets revised, validation gets re-run, and trainer industry currency lapses — and ASQA assesses what was in force at the time of delivery. Point it at a superseded document and it evidences a requirement with something that would not survive scrutiny. The honest test: can you say, today, that every document the pack cites is the current, signed-off version?

Student records, USIs and trainer files are personal information under the Privacy Act 1988 and the Australian Privacy Principles, and AVETMISS data carries its own handling obligations. Any deployment runs against your own systems and data handling, not a shared pool — we scope where the data sits and who can see it as part of the build. The demo here runs entirely on fabricated data; RTO 21455 and its records are not real.

It maps against whichever framework is in force for your assessment, and the regulator’s requirements change. The 2025 Standards for RTOs commenced on 1 July 2025 and replaced the 2015 Standards, restructuring the requirements into Outcome Standards, Compliance Standards and the Credential Policy. The clause-to-document mapping is configured to the standard that applies to you — and re-checked when the framework changes — rather than hard-coded once and left to drift.

What it takes to build

4–6 weeks · 4 phases

Reused from template~65%

Bespoke to this skin~35%

stack · Claude · private RAG · structured data store

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Considering this for your RTO?

The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where audit prep hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work