Validation Under the New Standards: Why the Data Is Now the Hardest Part
John Liddicoat5 March 20264 min read
Validation has always been complex. Under the old standards, an RTO had a single five-year validation cycle — every training product validated at least once within that period. Linear. Predictable. Manageable, at least in theory.
The single most important change you need to understand
Under the new standards, every single training product has its own independent five-year validation cycle — its own schedule, its own risk profile, its own drumbeat. You no longer have one cycle. You have a rolling matrix of cycles.
One RTO. Five Qualifications. Five Separate Cycles.
Take a simple example. An RTO delivers five qualifications. Under the new approach, that RTO now has five separate five-year cycles running simultaneously — each with its own risk-based frequency.
5
Separate 5-Year Cycles
per five qualifications on scope
5
Independent Schedules
each driven by last validation event
5
Risk Profiles
high, medium, or low per product
Variable
Validation Drumbeats
annual to once-per-cycle
The 'drumbeat' is the frequency of validation within each five-year window. A high-risk product may require annual validation. A stable, low-risk product may only require validation once in five years. Any identified issue may trigger earlier revalidation — resetting that product's individual clock.
The Rolling Matrix — Visualised
Here's what this looks like in practice for a typical RTO with five qualifications across different risk profiles. Notice how each row runs to a different rhythm — and how a single compliance issue can trigger an unscheduled validation that throws the cycle forward.
Validation cycle matrix
Each product runs an independent 5-year cycle. Circles mark validation events; a marked circle shows revalidation triggered by findings.
Note the Diploma of Hospitality Management row. After the initial validation, issues were identified — triggering an unscheduled revalidation at Year 2. The cycle then resets from that point. This is how a single finding can reshape an entire validation schedule.
Two Types of Validation — and They're Not Interchangeable
As if managing multiple rolling cycles wasn't enough, the new standards require RTOs to distinguish between two fundamentally different types of validation. They require different lenses, different data, and often different validators.
Practice Validation
Are we doing what we said we would do? This is about system integrity — validating that delivery matches your Training and Assessment Strategy.
- Is delivery aligned to the Training and Assessment Strategy?
- Are trainers implementing assessment as designed?
- Are workplace requirements being met?
- Is industry expectation reflected in practice?
Judgment Validation
Are assessment tools and decisions valid? This is about assessment defensibility — whether your tools and outcomes can withstand scrutiny.
- Do tools fully address unit requirements?
- Is evidence sufficient, authentic, current and valid?
- Does sampling support competency decisions?
- Are mapping and marking guides accurate?
Then Add Sampling Complexity
Judgment validation isn't a single action — it's a process that generates a trail of defensible data. Each step must be documented and each finding tracked to resolution.
- Determine a sampling methodology and justify it
- Select student files based on that methodology
- Record how many files were reviewed and why
- Capture all findings against specific requirements
- Document corrective actions and track to closure
- Assess whether findings trigger earlier revalidation
Validator Governance Is Now Part of the Data
Validation effectiveness is heavily influenced by who conducts it. The regulator expects RTOs to demonstrate that validators were suitable — which means capturing and retaining evidence of governance, not just outcomes.
- Who participated in each validation exercise
- Why they were suitable — qualifications, vocational competency, industry currency
- How independence was managed — particularly for judgment validation
- What contribution they made to findings and decisions
What This Creates: A Significant Data Ecosystem
For even a modest RTO, the new validation environment doesn't just require more effort — it requires managing a genuinely complex data ecosystem. Every category below must be captured, retained, and retrievable at audit.
Cycle Management
- Per-product 5-year cycles
- Risk-based frequency decisions
- Next-due dates per product
- Cycle reset triggers
Practice Validation Records
- Delivery vs TAS alignment evidence
- Trainer implementation records
- Workplace requirement checks
- Industry currency evidence
Judgment Validation Records
- Sampling methodology rationale
- Student file selection records
- Tool review findings
- Evidence sufficiency assessments
Corrective Action Tracking
- Findings linked to specific clauses
- Corrective actions assigned
- Closure evidence captured
- Continuous improvement linkage
Validator Governance
- Validator credentials on file
- Vocational competency evidence
- Industry currency records
- Independence documentation
Revalidation Triggers
- Issue-triggered revalidation records
- Trigger justifications
- Revised cycle schedules
- Outcome evidence from triggered reviews
What ASQA Will Actually Ask at Audit
The Australian Skills Quality Authority is increasingly focused on maturity — not whether validation happened, but whether it was governed. These are the kinds of questions a mature audit will surface.
At audit, the regulator will not simply ask 'Did you validate?' They will ask:
- Why did you validate this product at this frequency?
- Why did you consider it low or high risk?
- How did you determine your sampling rate?
- What happened when issues were found?
- How do you know the improvements were implemented?
- How does this validation link to your continuous improvement framework?
- How does it connect to your broader self-assurance framework?
The Real Risk: Manual Systems Can't Handle This
Validation doesn't fail because it wasn't done
It fails because it cannot be proven to have been governed. Reconstruction of five years of rolling decisions at audit — from scattered spreadsheets, shared folders, and email trails — is where RTOs fall over.
Many RTOs attempt to manage this with spreadsheets, folder-based evidence storage, and calendar reminders. The approach doesn't fail because people are careless. It fails because the volume and interdependency of data points becomes too complex to reliably manage manually — particularly across staff changes and version drift.
- Staff turnover resets institutional knowledge of cycle status
- Version control inconsistencies create conflicting records
- Next validation dates drift without automated tracking
- Corrective actions sit in meeting minutes without systemic follow-up
- Validator governance evidence is scattered across email and HR systems
The Strategic Question
The question has changed
The question for RTO leaders is no longer 'Are we validating?' It is: 'Do we have a validation management system capable of sustaining multiple rolling cycles, variable drumbeats, governance oversight, and defensible record-keeping over time?' That distinction will show at audit.
Octossure is built specifically for this environment — to manage rolling validation cycles, distinguish practice from judgment validation, track sampling and corrective actions, capture validator governance, and surface compliance status to leadership at a glance. Validation complexity is now structural. The system managing it needs to be equally structured.