Readiness is a state you are in, not a project you run.
All three 2025 instruments are loaded clause by clause. You work them on a schedule, attach evidence against each obligation as it is produced, and see at any moment which parts of your registration you could defend today.
Your Standards are already loaded when you arrive.Every obligation carries the documents that satisfy it and the date they stop being current.
Traced back to the clause
The problem
The evidence exists. Finding it is the job.
Most RTOs are more compliant than they can prove. The mapping was done, the validation happened, the trainer's currency was checked — but the artefacts are spread across a shared drive, three inboxes and one person's memory, and none of them are attached to the obligation they satisfy.
So readiness becomes a project. Six weeks before an audit somebody starts a spreadsheet, and the organisation spends those weeks re-finding work it already did. That cost is invisible on any budget line, and it is paid every single time.
The Standards, loaded
Clause by clause, not chapter by chapter.
The 2025 instruments are in the platform at clause level, with the performance indicators underneath each one. That granularity is what makes everything else possible: evidence attaches to an obligation, a review question maps to an obligation, and a finding names an obligation.
When an obligation has no evidence against it, the gap is visible now rather than in an audit report. That is the whole difference between knowing where you stand and hoping.
- Performance indicators sit under each clause, so a gap names itself precisely
- Evidence carries its own validity date and is flagged before it lapses
- An obligation with nothing against it is visible now, not in an audit report
Compliance review schedule
A review activity is a piece of work with a date and an owner.
You plan compliance review activities across the year rather than running one enormous internal review nobody has time for. Each activity covers a defined set of obligations, uses a checklist built from seeded question templates, and belongs to somebody by name.
Answer a question No and it becomes a non-compliance on the spot, carrying the clause it came from. Nothing is retyped, and nothing is lost between the review and the work that follows it.
- Seeded question templates
- Gap analysis
- The non-compliance report
- Six scope items have no current strategyDetected 2 hours ago · affects 6 of 19 scope itemsBuild TAS
- Two industry licences expire within 30 daysTrainers notified · managers copiedReview
- A recurring finding was raised against Standard 1.3Second occurrence this schedule · linked to RP-011-04Open plan
What this replaces
The work does not disappear. The scramble does.
- A readiness spreadsheet rebuilt from scratch before every auditA standing picture of which obligations you could defend today
- Evidence spread across a shared drive, three inboxes and one person's memoryEvidence attached to the obligation it satisfies, with its validity date
- One enormous internal review nobody has time to run properlyReview activities planned across the year, each with an owner and a date
- Findings retyped from a review document into a separate action listA failed question that becomes a non-compliance carrying its clause
Traceable to the Standards
Every review question, every piece of evidence and every finding on this page names the obligation it belongs to, so the work is defensible in the terms the regulator uses.
Where this connects
Findings that close themselves
A failed question becomes a rectification plan, a task, and a record.
Read moreAssessment validation
A stated sampling policy, eligible validators, recommendations that land.
Read moreTraining products
Scope synchronised from training.gov.au, strategies under version control.
Read more
Find out what your last audit would have looked like with a system behind it.
14 days, no credit card, and the Standards are already loaded when you sign in.