RTO Validation and Evidence Collection: A Practical Guide

Validation is where most RTOs quietly lose ground with ASQA. Under the Standards for RTOs 2025, the Training and Assessment Quality Area requires you to plan, conduct and record systematic validation of assessment — but the Standards don't hand you a template. This guide walks through a practical validation model we use with our clients: what to validate, how often, who should be in the room, and the exact evidence to collect so the file stands up to audit.

What validation actually means

Validation is a quality review of your assessment system, not a re-marking exercise. It answers two questions:

1. Does the assessment tool produce evidence that meets the Principles of Assessment (fair, flexible, valid, reliable) and the Rules of Evidence (valid, sufficient, authentic, current)?
2. Did the assessor apply that tool consistently and defensibly across the sample?

Most non-compliance findings against the Training and Assessment Quality Area come from RTOs treating validation as an internal moderation meeting with no documented outcomes. ASQA wants to see judgement, sampling logic, and rectification actions — not a signed attendance sheet.

Your validation schedule

The Standards for RTOs 2025 expect each training product on scope to be validated on a planned, risk-based cycle, with priority given to newly added, high-enrolment and high-risk training products. In practice we recommend:

• High-risk qualifications (new to scope, high enrolments, funded delivery, third-party arrangements): annually.
• Medium-risk: every two years.
• Low-risk (small cohorts, mature delivery, no complaints): every three years, never longer.

Maintain a single validation plan showing every unit of competency across your scope, the last validation date, the next scheduled date, and the assigned lead validator. Auditors ask for this document first.

Building your validation panel

The Standards require that validators are independent of the person who developed or delivered the assessment being validated, and that the panel collectively holds vocational competency, current industry skills, and assessment expertise (TAE credentials). In small RTOs this is the hardest requirement to meet honestly. Options:

• Rotate assessors across validation panels so no one validates their own work.
• Engage an external industry expert on a per-session basis — a written engagement letter and their CV are enough evidence.
• Use a validation partner for specialist qualifications where you lack an independent assessor.

The RTO validation checklist

Before the session, gather:

• The training and assessment strategy (TAS) for the qualification.
• The unit of competency and its assessment requirements.
• The full assessment tool (instructions, tasks, marking guide, mapping).
• A representative sample of completed student evidence (minimum 6 or 10% of the cohort, whichever is greater; adjust for risk).
• Records of any previous validation outcomes and rectification actions.

During the session, the panel reviews each item against a validation instrument that covers:

1. Mapping — does every performance criterion, performance evidence and knowledge evidence map to an assessment task?
2. Principles of Assessment — is the tool fair, flexible, valid and reliable?
3. Rules of Evidence — does the collected evidence meet validity, sufficiency, authenticity and currency?
4. Assessor judgement — was the marking guide applied consistently, and is the "satisfactory / not yet satisfactory" decision defensible from the evidence retained?
5. Reasonable adjustment — where applied, was it documented, appropriate and did it preserve the competency standard?

VET evidence collection: what to keep

The most audited part of validation is the evidence file. Retain:

• The validation plan showing this session was scheduled.
• The signed validation report with panel members' names, roles, qualifications and vocational currency evidence.
• The completed validation instrument for each tool reviewed.
• The student sample list (de-identified is fine) with a clear sampling rationale.
• Rectification actions with owners, due dates and evidence of completion.
• A version-controlled updated assessment tool (or a documented decision that no change is required).

Store all of this against the qualification and unit codes in a way you can retrieve within minutes during an ASQA audit. Scattered evidence across email threads and personal drives is the single most common cause of avoidable non-compliances.

ASQA validation requirements: the audit view

When ASQA reviews validation under the Standards for RTOs 2025, they look for a pattern — evidence that validation is systematic, planned, independent and results in improvements to training and assessment. A single well-documented session on one unit will not satisfy them if the overall scope shows gaps. If you've inherited an RTO with weak historical validation, the fastest path back to compliance is:

1. Build a multi-year validation calendar covering every unit on scope.
2. Prioritise units delivered in the last 12 months for immediate validation.
3. Document a "validation catch-up plan" showing dated milestones and present it proactively at your next audit.

When to bring in help

Most RTOs can run internal validation successfully once the system is in place. Bring in an external consultant when you:

• Have received an ASQA non-compliance relating to assessment, validation or assessor decisions.
• Are adding new qualifications to scope and need the initial validation done independently.
• Deliver in a specialist industry where you can't source an independent vocationally competent panel member.
• Need an audit-ready validation catch-up plan built and executed inside 90 days.

RTO Intelligence runs validation sessions across every training package — as a one-off catch-up, as part of a compliance rebuild, or as an ongoing quarterly service. If you want a hand mapping your scope and building a defensible schedule, book a discovery call and we'll walk through your situation.

Frequently asked questions about RTO validation

How often must an RTO validate assessment? The Standards for RTOs 2025 require a planned, risk-based cycle rather than a fixed five-year rule. We recommend annually for high-risk training products (new to scope, high enrolment, funded or third-party delivery), every two years for medium risk, and never longer than three years for low-risk products.

What is the difference between validation and moderation? Moderation happens before or during marking to align assessor judgements. Validation is a documented quality review of the assessment tool and completed judgements after the fact. ASQA looks for validation records; moderation alone is not a substitute.

How many student samples do you need to validate? Use a minimum of six completed student files or 10% of the cohort, whichever is greater, and increase the sample where risk, complaints or previous non-compliance exist. Always document your sampling rationale.

Who can sit on a validation panel? Validators must be independent of the person who developed or delivered the assessment being validated. Collectively the panel needs vocational competency, current industry skills and assessment expertise (TAE credentials). External industry experts can be engaged per session with a CV and engagement letter as evidence.

Can a sole trader or small RTO validate its own assessments? Yes, but independence must still be demonstrated. Small RTOs typically rotate assessors, engage an external validator, or use a consultant for specialist qualifications.

What evidence does ASQA ask for at audit? The validation plan, signed validation report with panel credentials, completed validation instruments, the de-identified student sample list with rationale, rectification actions with owners and due dates, and the version-controlled updated tools.

What happens if validation has not been done? Build a dated validation catch-up plan covering every unit on scope, prioritise products delivered in the last 12 months, and present the plan proactively. Demonstrating a systematic, resourced catch-up is far stronger than an unexplained gap.

How long should validation records be kept? Retain validation records for the life of the training product on scope plus your standard record-retention period, and keep them retrievable within minutes by qualification and unit code.