The Standards for RTOs 2025, in force since 1 July 2025, draw a sharp line between two obligations the sector has long blurred: the review of assessment tools before they are used with learners under Outcome Standard 1.3, and the systematic validation of assessment practices and judgements across a five-year, risk-based cycle under Outcome Standard 1.5. Treating either as a single annual meeting no longer satisfies the regulator. This article examines what Standard 1.3 actually requires, the six failure patterns auditors keep finding, and a practical seven-step process for getting it right, and what it means for RTOs, assessors and the learners whose qualifications depend on it.
The Most Misunderstood Word in VET Compliance
If there is a single word in the Australian VET compliance vocabulary that is used more often than it is understood, it is validation. Every RTO uses the word. Every compliance officer talks about it. Every auditor asks about it. And yet, across the sector, validation continues to be treated as something it is not: a meeting. A scheduled event. An annual or biannual exercise in which a group of trainers and assessors sit around a table, review a handful of completed student assessments, fill in a form, and move on. The meeting gets ticked off. The compliance calendar is updated. And nothing fundamentally changes about the quality of the RTO's assessment tools or the integrity of its assessment judgements.
This understanding of validation has always been inadequate. Under the Standards for RTOs 2025, an RTO that never reviews its assessment tools before using them is non-compliant with Outcome Standard 1.3, no matter how diligently it runs its annual validation meeting.
The 2025 Standards establish a regulatory architecture that separates two different obligations, each governed by a different Outcome Standard, each serving a different purpose, and each requiring a different approach. Outcome Standard 1.3 requires that the assessment system is fit for purpose and consistent with the training product, and that assessment tools are reviewed prior to use. Outcome Standard 1.5 requires that assessment practices and judgements are validated systematically over time, using a risk-based approach, with every training product validated at least once every five years.
These are not interchangeable processes. They are not two names for the same activity. They operate at different points in the assessment lifecycle; they review different things, and they produce different types of evidence. An RTO that validates diligently after the fact but never reviews a tool before it is used is not half compliant. It is non-compliant with Standard 1.3 because it allows unreviewed tools to determine learners' competency before any quality assurance has been applied to the tool itself.
This article examines what Standard 1.3 actually requires, why the persistent belief that validation is just a meeting continues to damage assessment quality across the sector, the specific failure patterns that auditors consistently identify, and a practical, seven-step process for building a compliant pre-use review into every RTO's assessment system.
1. The Regulatory Architecture: Standard 1.3 and Standard 1.5
1.1 What Standard 1.3 Requires
Outcome Standard 1.3 requires that an RTO's assessment system is fit for purpose and consistent with the training product. This is not a general aspiration. It is a specific regulatory requirement. Standard 1.3 provides that assessment tools are reviewed prior to use to ensure that assessment is conducted in accordance with the principles of assessment and the rules of evidence at Standard 1.4, and that the outcomes of those reviews result in changes to the tools where changes are needed. The principles of assessment are fairness, flexibility, validity and reliability. The rules of evidence are validity, sufficiency, authenticity and currency. They sit at Standard 1.4, and the Standard 1.3 review is the mechanism that checks a tool against them before it is used.
The language is deliberate. The Standard says tools are reviewed prior to use, not at some point. It contemplates documented changes, not a discussion. It says fit for purpose, not purchased from a reputable supplier. The regulatory intent is clear: no assessment tool should be used to determine a learner's competency until it has been critically reviewed, found to be structurally sound, and, where necessary, revised to address any gaps, ambiguities or alignment failures identified during the review.
A point of terminology matters here because the sector routinely gets it wrong. The 1.3 review is commonly called pre-validation. That is convenient shorthand, but it is not the regulator's language, and the difference is not trivial.
|
What ASQA Actually Calls It |
|
The term "pre-validation" is sector shorthand, not the regulator's wording. ASQA has clarified that the 2025 Standards do not refer to "pre-use validation." Standard 1.3 requires that assessment tools are reviewed prior to use, and ASQA has confirmed that this review does not refer to a validator or validation team, so the reviewer does not need to hold specific validator credentials. The obligation is real, and it must be documented. The label matters less than the discipline behind it: review the tool, in writing, before a learner is assessed with it. This article uses pre-use review and pre-validation interchangeably, while keeping the regulator's distinction in view. |
1.2 How Standard 1.5 Differs
Outcome Standard 1.5 governs what most RTOs have traditionally understood as validation: the systematic review of assessment practices and judgements to ensure the assessment system produces judgements that are consistent with the training product. Under the 2025 Standards, this validation looks across the whole assessment system over time, examining completed student evidence, evaluating the consistency of assessor judgements, identifying drift or inconsistency in how competency decisions are made, and driving improvements based on what the evidence reveals. It uses a risk-based approach, with every training product on scope validated at least once every five years, and more frequently where the RTO becomes aware of risks, changes to the training product, or relevant feedback.
This validation is essential. It provides the ongoing quality assurance feedback loop that protects assessment integrity over time. But it operates after the fact. It reviews what has already happened. By the time a validation activity identifies that an assessment tool is structurally flawed, learners have already been assessed using that tool. Competency decisions have already been made. Qualifications may already have been issued. The damage, if there is damage, has already occurred.
The Standard 1.3 review is designed to prevent that damage from occurring in the first place. It is a proactive quality control mechanism, not a reactive one. The following table maps the key differences between the two. For clarity, this article frames the 1.3 review as pre-validation and the 1.5 activity as post-validation, while recognising that the Standards themselves reserve the word validation for Standard 1.5.
|
Dimension |
Pre-validation: the 1.3 pre-use review |
Post-validation: validation under Standard 1.5 |
|
Purpose |
Ensure assessment tools are fit for purpose and consistent with the training product before any learner is assessed |
Evaluate the quality and consistency of assessment practices and judgements after assessments have been conducted |
|
Regulatory basis |
Standard 1.3: the assessment system is fit for purpose, and tools are reviewed prior to use against the principles of assessment and rules of evidence at Standard 1.4 |
Standard 1.5: assessment practices and judgements are validated systematically, using a risk-based approach, across a five-year cycle |
|
Timing |
Before the tool is used; triggered by new tool development, scope additions, training package updates, or contextualisation changes |
After assessments are completed; scheduled according to a risk-based validation plan across the five-year cycle |
|
What is reviewed |
The tool itself: task design, mapping to unit requirements, clarity of instructions, marking guides, sufficiency of evidence, contextualisation to cohort and delivery mode |
Completed assessment evidence and assessor judgements: consistency of decisions, quality of evidence, alignment with the rules of evidence |
|
Who is involved |
The reviewer, who does not need validator credentials, ideally a subject matter expert with current industry competence and, where possible, an industry representative |
Validators with collective industry competence and current practice may include assessors from other RTOs, industry representatives and compliance staff |
|
Key output |
A documented review record showing what was checked, what was found and what was changed before the tool enters use |
Validation reports documenting findings, actions taken, improvements implemented, and evidence that outcomes have improved |
|
Risk if neglected |
Learners are assessed using flawed tools that may not validly measure competency; qualifications rest on structurally inadequate evidence; non-compliance at audit |
Assessment drift goes undetected; judgements vary across assessors; the RTO cannot demonstrate reliable, valid outcomes over time |
|
The Critical Distinction |
|
The pre-use review under Standard 1.3 checks the tool before it is used. Validation under Standard 1.5 checks the practices and judgements after assessments are completed. They are not interchangeable. An RTO that conducts only post-validation is not half compliant. It is non-compliant with Standard 1.3 because it has allowed unreviewed tools to determine learners' competency outcomes. |
2. The Myth: "Validation Is Just a Meeting"
The belief that validation is just a meeting is one of the most damaging features of Australia's VET compliance landscape. It survives because it is convenient. Scheduling a meeting feels manageable. It has a start time, an end time, and a form to fill in. It produces a document that can be filed. It allows the RTO to say, with apparent sincerity, that validation has been conducted. And in many cases, the people in the meeting genuinely believe they are doing what compliance requires.
But a meeting, in itself, is not validation, and it is certainly not the pre-use review that Standard 1.3 demands. Both are analytical processes. They require the systematic evaluation of assessment tools, or of completed evidence and judgements, against defined criteria: the principles of assessment, the rules of evidence, the unit of competency requirements, the assessment conditions, and the practical realities of the workplace context in which competency will be applied. A meeting can be the forum in which this analysis takes place, but only if it is structured around rigorous, evidence-based evaluation, only if the participants have the expertise and the time to conduct that evaluation properly, and only if the outcomes are documented and result in tangible changes.
What typically happens in practice is different. The meeting is scheduled at the last available moment, often in response to an upcoming audit or a compliance calendar reminder. A handful of completed student assessments are brought to the table. Participants, who are often the same trainers and assessors who designed and used the tools, spend an hour or two reviewing them. The forms are completed with phrases like "tools are satisfactory" or "no changes required." The meeting ends. Everyone returns to the delivery schedule. The tools remain unchanged. The same structural issues, the mapping gaps, the ambiguous task instructions, the generic marking guides, the insufficient evidence requirements, persist until the next audit, or the next complaint, or the next time an external validator asks a question that nobody can answer.
|
The Performance of Validation |
|
This is not validation. It is the performance of validation. It satisfies the form without achieving the function. It produces a record that something happened, and no record that anything changed. Under the 2025 Standards, which require tools to be reviewed prior to use, changes to be documented, and the assessment system to be demonstrably fit for purpose, performance is no longer enough. The record of a superficial review does not protect the RTO at the audit. It becomes the evidence against it. |
3. How RTOs Are Getting It Wrong: Six Consistent Failure Patterns
When auditors review RTOs against Standard 1.3, a consistent set of failure patterns emerges. These are not obscure edge cases. They are the most common ways in which RTOs fall short of the pre-use review requirement, and they share a common origin: a superficial, tick-box approach that treats assessment quality assurance as a compliance exercise rather than a quality control process.
The following table maps the six most common failure patterns, what happens in practice, and why each matters from both a regulatory and a quality perspective.
|
Failure pattern |
What happens |
Why it matters |
|
Blindly trusting purchased resources |
Off-the-shelf tools are deployed without a pre-use review to check whether they are contextualised for the RTO's learner cohort, delivery mode, industry context and assessment conditions |
ASQA has been explicit that buying materials described as "pre-validated" does not remove the obligation to review and contextualise them; generic resources that are not tailored to the provider can themselves be a source of non-compliance |
|
Failing to document the review |
A review discussion takes place, but the findings are not recorded, the revisions are not documented, and the link between what was found and what was changed is not evidenced |
The Standard contemplates that the review results in documented changes; from a regulatory perspective, a conversation without documentation is a conversation that did not happen |
|
Excluding industry voices |
The review is conducted entirely by internal compliance or training staff, without input from industry representatives, workplace supervisors, or subject matter experts with current practice |
Tools reviewed only by educators may satisfy academic logic but miss workplace realities: current equipment, updated procedures, industry-specific safety requirements, or emerging competency expectations that only people working in the industry can identify |
|
Confusing the pre-use review with validation |
The RTO relies entirely on post-assessment validation under Standard 1.5 to catch errors, so structurally flawed tools are used to assess learners before any quality control is applied to the tool |
Validation reviews completed assessments and judgements; it cannot retrospectively fix a tool that was flawed from the outset; learners assessed with unchecked tools may have been judged on the basis of invalid evidence |
|
Treating validation as an annual event |
Validation is scheduled as a single annual meeting timed to precede an expected audit, rather than embedded as an ongoing process triggered by tool changes, scope additions, training package updates or performance data |
The 2025 Standards moved away from fixed annual quotas towards a risk-based five-year cycle; a calendar-driven approach misreads Standard 1.5 and leaves tools operating unchecked for months under Standard 1.3 |
|
Using generic validation checklists |
The RTO uses a single generic form that asks whether a tool is "satisfactory" without requiring reviewers to evaluate mapping accuracy, task clarity, evidence sufficiency, marking guide specificity and alignment with the principles and rules |
A generic checklist produces generic answers; it does not force the critical analysis required to identify whether a tool genuinely produces valid, sufficient, authentic and current evidence for each performance criterion, element and knowledge requirement |
These failure patterns are not independent. They interact and reinforce each other. An RTO that blindly trusts purchased resources is also likely to use a generic checklist because the checklist is designed to produce a satisfactory result rather than a critical analysis. An RTO that treats validation as an annual event is also likely to confuse the pre-use review with validation, because the annual meeting is the only quality activity that occurs. An RTO that excludes industry voices is also likely to fail to contextualise its tools because the people reviewing them do not have current workplace knowledge.
|
The Systemic Nature of Validation Failure |
|
Validation failures are rarely isolated. An RTO that treats validation as a meeting is also likely to use generic checklists, exclude industry voices, rely on purchased tools without review, and fail to document changes. The fix is not to address each failure separately. It is to redesign the process from the ground up, embedding the pre-use review as an operational requirement triggered by tool changes, not as a scheduled administrative event. Fix the system, not the symptom. |
4. Building a Compliant Pre-Use Review: Seven Steps
If the meeting model is insufficient, what should replace it? The answer is a structured, documented, evidence-based review that operates as a quality gate: no assessment tool enters use until it has passed through the gate and been confirmed as fit for purpose. The following seven-step process provides a practical model that any RTO, regardless of size, can adapt to its context.
|
Step |
Action |
What it involves |
Why it matters |
|
1 |
Assemble the review group |
Identify who will review the tool: the assessment designer or lead assessor, a subject matter expert with current industry competence, and, where possible, an industry representative or workplace supervisor |
The group must collectively hold the expertise to evaluate whether the tool measures what it claims to measure, in conditions that reflect actual workplace practice |
|
2 |
Check the mapping |
Review the mapping matrix against the unit of competency requirements: every performance criterion, every element, every foundation skill, every knowledge evidence requirement and every assessment condition must be addressed |
Mapping gaps are the single most common structural flaw in assessment tools; if the mapping does not cover every requirement, the tool cannot produce sufficient evidence of competency |
|
3 |
Evaluate task design and clarity |
Read every task as the learner would: are the instructions clear and unambiguous? Are the tasks pitched at the right level? Do the scenarios reflect realistic workplace situations? Are the conditions of assessment specified? |
A task that is confusing, unrealistic or poorly worded produces unreliable evidence regardless of the learner's competence; task clarity is a validity issue, not a formatting preference |
|
4 |
Review the marking guide |
Examine the marking guide or benchmark answers: are the expected responses specific enough to ensure consistent judgements across different assessors? Are the criteria for satisfactory performance defined, not assumed? |
Without a specific marking guide, two assessors reviewing the same evidence may reach different judgements; this is a reliability problem that originates in tool design, not assessor competence |
|
5 |
Assess evidence sufficiency |
Determine whether the tool, taken as a whole, gathers enough evidence across enough methods to support a valid judgement; weigh the volume, variety and depth of evidence against the rules of evidence |
Sufficiency is not about word counts or page numbers; it is about whether the combination of evidence types provides a complete, defensible picture of competency |
|
6 |
Contextualise for the cohort |
Check that the tool is contextualised for the RTO's specific learner cohort, delivery mode and industry context; a tool designed for classroom delivery may not work for online or workplace-based assessment without modification |
Contextualisation is not optional decoration; the conditions and scenarios must reflect the actual environment in which learners will demonstrate competency |
|
7 |
Document findings and changes |
Record every finding: what was checked, what was found, what was changed, who made the changes, and when the revised tool was approved for use; retain this as evidence |
The Standard contemplates documented changes; the record is not just an audit trail but proof that the quality assurance process is active, rigorous and producing tangible improvements |
This process does not need to be elaborate or time-consuming. For a simple tool with clear mapping and straightforward tasks, the review may take an hour. For a complex, multi-method assessment across a full qualification, it may take longer. The point is not the time spent, but the rigour applied. Every step has a defined purpose, every step produces evidence, and the outcome is a tool that has been critically evaluated, found to be fit for purpose, and documented as such before any learner is assessed with it.
5. When the Pre-Use Review Should Be Triggered
One of the most common misconceptions is that the pre-use review is a one-time event: review the tool before first use, and the obligation is satisfied. This misreads the Standard. The requirement is that tools are fit for purpose and consistent with the training product. Any change that could affect the fitness or consistency should trigger a fresh review.
At a minimum, the review should be triggered when a new tool is developed or acquired, including purchased resources not previously reviewed by the RTO. It should be triggered when an existing tool is substantially revised, including changes to task design, marking guides, mapping or assessment conditions. It should be triggered when a training package is updated, because changes to unit requirements may invalidate an existing tool's mapping. It should be triggered when the delivery mode changes, because a tool designed for classroom assessment may not produce valid evidence in an online or workplace-based context. It should be triggered when the learner cohort changes significantly, because a tool contextualised for one industry sector or demographic may not suit another. And it should be triggered when validation under Standard 1.5 identifies systemic issues with a tool's design that require structural revision rather than minor adjustment.
This trigger-based approach transforms the pre-use review from a scheduled event into an embedded quality practice. It ensures the review occurs at the point where it matters, when something changes that could affect assessment quality, rather than at an arbitrary calendar date that may fall months before or after the change actually occurred.
6. The Relationship Between the Two Reviews
The pre-use review and validation are not competing processes. They are complementary elements of a continuous assessment quality cycle. The pre-use review checks the tool before use. Validation checks the practices and judgements after use. Together, they create a feedback loop in which the assessment system continuously improves: the pre-use review catches structural flaws before they affect learners, validation catches performance issues that only become visible through actual assessment practice, and the findings from each inform the other.
When validation under Standard 1.5 identifies that assessors are making inconsistent judgements on a particular tool, the question is whether the inconsistency originates in the tool's design, such as a marking guide that is too vague or a task that is ambiguous, or in assessor practice, such as insufficient moderation or differing interpretations of the standard. If the issue is tool design, the response should include a fresh pre-use review of the revised tool before it re-enters use. If the issue is assessor practice, the response may involve moderation, professional development or supervision, and the tool itself may not need revision.
This integrated approach is exactly what the 2025 Standards envisage. The regulatory architecture does not treat assessment quality as a single obligation satisfied by a single process. It treats it as a system, with multiple control points, each serving a specific function. RTOs that understand this architecture and design their quality assurance around it will not only achieve compliance but also produce genuinely better assessment outcomes. RTOs that continue to treat validation as a meeting will find themselves increasingly unable to satisfy either Standard 1.3 or Standard 1.5, because the meeting model is structurally incapable of delivering what either Standard requires.
7. What This Means for RTOs
The shift required is practical, and it can be approached in a clear order of priority.
First, build the gate. Replace the generic validation form with a structured, criterion-referenced pre-use review that no tool can bypass before it reaches a learner. The review checks mapping, task clarity, marking guides, evidence sufficiency and contextualisation, and it produces a record of what was changed. This single step closes the most common Standard 1.3 gap at the audit.
Second, make it trigger-based, not calendar-based. Tie the pre-use review to the events that actually change a tool's fitness for purpose: new or purchased tools, substantial revisions, training package updates, delivery mode changes and cohort changes. A review that fires when something changes will always be more defensible than one that fires on a date.
Third, connect the two reviews and bring in the industry. Feed validation findings under Standard 1.5 back into the pre-use review, and make sure both draw on people with current industry competence rather than internal staff alone. The pre-use review confirms the tool is sound before use; validation confirms the judgements are sound over time; industry input keeps both anchored to real workplace practice. Together, they are the evidence base on which self-assurance under the 2025 Standards depends.
8. Conclusion: Quality Control, Not Compliance Theatre
The distinction between the pre-use review under Standard 1.3 and validation under Standard 1.5 is not a technical refinement. It is a fundamental reframing of what assessment quality assurance means and what it is for. It is not a meeting. It is not a scheduled event. It is not a form to be filled in. It is quality control: a rigorous, evidence-based mechanism for ensuring that the tools used to determine learners' competency are fit for purpose, aligned with the training product, and capable of producing valid, sufficient, authentic and current evidence.
Standard 1.3 makes this explicit. Assessment tools must be reviewed before use. The review must be documented. The review must result in changes where changes are needed. The people conducting it must have the expertise to evaluate whether the tool does what it claims to do, even though they need not hold validator credentials. And the evidence of the process must be retained, retrievable and defensible at audit.
For RTOs that have been treating validation as a meeting, this requires a genuine shift in practice. It means moving from a reactive, calendar-driven approach to a proactive, trigger-based one. It means moving from generic checklists to structured, criterion-referenced evaluation. It means moving from internal-only review to groups that include industry expertise. It means moving from undocumented discussions to documented findings and evidenced changes. And it means understanding that the pre-use review and validation are different obligations, serving different purposes, governed by different Standards, and both essential to a functioning assessment quality system.
The 2025 Standards do not ask RTOs to do more for the sake of doing more. They ask RTOs to do what quality assurance actually requires: make sure assessment tools work before using them, and make sure assessment outcomes are consistent and valid after using them. That is not compliance theatre. It is quality control. And it is the minimum that learners, employers and the sector as a whole deserve.
|
Summary: From Meetings to Quality Control |
|
1. The pre-use review under Standard 1.3 and validation under Standard 1.5 are different obligations with different purposes. Both are required, and neither replaces the other. 2. "Pre-validation" is sector shorthand; ASQA's language is that assessment tools are "reviewed prior to use," and the reviewer does not need validator credentials. 3. Assessment tools must be reviewed before use, with documented findings and documented changes. A discussion without documentation is not in compliance. 4. The pre-use review should be triggered by tool changes, scope additions, training package updates, delivery mode changes and cohort changes, not by calendar dates. 5. Validation under Standard 1.5 is now risk-based across a five-year cycle, not an annual quota, and looks at the whole assessment system over time. 6. The review should involve people with current industry competence, not just internal compliance staff. 7. Purchased tools must be reviewed and contextualised to the same standard as internally developed tools; "pre-validated" off-the-shelf materials do not discharge the obligation. 8. Generic checklists that produce generic answers must be replaced with structured, criterion-referenced evaluation against the principles of assessment and rules of evidence at Standard 1.4. 9. The pre-use review and validation form a continuous quality cycle: findings from each should inform the other. 10. The record of a superficial review does not protect the RTO at audit; it becomes the evidence against it. |
References and Further Reading
ASQA (2025). 2025 Standards: Frequently Asked Questions (Versions 2.0 and 3.0). Australian Skills Quality Authority.
ASQA (2025). Practice Guide: Assessment. Australian Skills Quality Authority.
ASQA (2025). Practice Guide: Validation of assessment. Australian Skills Quality Authority.
ASQA (2025). Standards for Registered Training Organisations 2025. Australian Skills Quality Authority.
Department of Employment and Workplace Relations (2025). Policy Guidance: 2025 Standards for RTOs, Outcome Standards. DEWR.
Federal Register of Legislation (2025). National Vocational Education and Training Regulator (Outcome Standards for NVR Registered Training Organisations) Instrument 2025.
Government of Western Australia (2025). Fact Sheet: Assessment Validation.
