Validation Is Not a Meeting: Why Standard 1.3 Demands Pre-Validation and How RTOs Are Getting It Wrong

April 14, 2026 Sukh Sandhu

A detailed examination of the distinction between pre-validation and post-validation under the Standards for RTOs 2025, the persistent myths that undermine assessment quality, and a practical seven-step process for building compliant, rigorous pre-validation into every RTO’s assessment system

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, it is now explicitly non-compliant.

The 2025 Standards introduce a regulatory architecture that distinguishes clearly between two different forms of validation, each governed by a different standard, each serving a different purpose, and each requiring a different approach. Outcome Standard 1.3 mandates pre-validation: the rigorous review of assessment tools before they are used with learners, to ensure they are fit for purpose and aligned with the training product. Outcome Standard 1.5 mandates post-validation: the systematic review of assessment practices and judgements after assessments have been conducted, to ensure consistency and quality of outcomes over time.

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 conducts post-validation diligently but neglects pre-validation is not half compliant. It is non-compliant with Standard 1.3, because it allows structurally flawed tools to be used with learners before any quality assurance has been applied to the tool itself.

This article examines what Standard 1.3 actually requires, why the persistent myth 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 compliant pre-validation 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 states that an RTO’s assessment system must be fit for purpose and consistent with the training product. This is not a general aspiration. It is a specific regulatory requirement with defined performance indicators. Standard 1.3(b) requires that assessment tools be rigorously reviewed prior to use to ensure they align with the Principles of Assessment (fairness, flexibility, validity, and reliability) and the Rules of Evidence (validity, sufficiency, authenticity, and currency). Standard 1.3(c) requires that the outcomes of these reviews result in tangible, documented changes to the assessment tools.

The language is deliberate. The Standard says “prior to use,” not “at some point.” It says “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.

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 after assessments have been completed. This is the process that examines completed student evidence, evaluates the consistency of assessor judgements, identifies drift or inconsistency in how competency decisions are being made, and drives improvements to both tools and assessor practice based on what the evidence reveals.

Post-validation under Standard 1.5 is essential. It provides the ongoing quality assurance feedback loop that ensures assessment integrity over time. But it operates after the fact. It reviews what has already happened. By the time a post-validation session 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.

Pre-validation under Standard 1.3 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 processes.

Dimension	Pre-Validation (Standard 1.3)	Post-Validation (Standard 1.5)
Purpose	Ensure assessment tools are fit for purpose and aligned with the training product BEFORE any learner is assessed	Evaluate the quality and consistency of assessment judgements and outcomes AFTER assessments have been conducted
Regulatory Basis	Outcome Standard 1.3(b): assessment tools must be reviewed prior to use to ensure alignment with the Principles of Assessment and the Rules of Evidence	Outcome Standard 1.5: assessment practices and judgements must be validated systematically, using a risk-based approach, across a five-year cycle
Timing	Before the assessment tool is used with learners, triggered by new tool development, scope additions, training package updates, or contextualisation changes	After assessments have been completed; scheduled according to a risk-based validation plan across the five-year cycle
What Is Reviewed	The assessment tool itself: task design, mapping to unit requirements, clarity of instructions, marking guides, sufficiency of evidence gathered, contextualisation to the learner cohort and delivery mode	Completed assessment evidence and the judgements made by assessors: consistency of decisions, quality of evidence collected, alignment between judgements and the Rules of Evidence
Who Should Be Involved	Assessment designers, subject matter experts, trainers and assessors who will use the tool, and, where possible, industry representatives who can verify workplace relevance	Validators with collective industry competence and current practice, may include assessors from other RTOs, industry representatives, and quality/compliance staff
Key Output	A documented review record showing findings, identified issues, and revisions made to the tool before it enters use; Standard 1.3(c) requires documented changes	Validation reports documenting findings, actions taken, improvements implemented, and evidence that outcomes have improved as a result
Risk If Neglected	Learners are assessed using flawed tools that may not validly measure competency; the RTO issues qualifications based on structurally inadequate evidence; and non-compliance at audit	Assessment drift goes undetected; inconsistent judgments across assessors; the RTO cannot demonstrate that its assessment system produces reliable, valid outcomes over time

The Critical Distinction

Pre-validation (Standard 1.3) checks the tool BEFORE it is used.

Post-validation (Standard 1.5) checks the outcomes 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 persistence of the “validation is just a meeting” myth 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 participating in the meeting genuinely believe they are doing what compliance requires.

But a meeting, in itself, is not validation. Validation is an analytical process. It requires the systematic evaluation of assessment tools 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 the meeting is structured around rigorous, evidence-based evaluation, if the participants have the expertise and the time to conduct that evaluation properly, and if the outcomes are documented and result in tangible changes to the tools.

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 their 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 has a good answer for.

This is not validation. It is the performance of validation. It satisfies the form without achieving the function. And under the 2025 Standards, which explicitly require pre-use review, documented changes, and evidence of fit-for-purpose tools, the performance is no longer enough.

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-validation requirement, and they share a common origin: a superficial, tick-box approach to assessment quality assurance that treats validation 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 assessment tools are deployed without a pre-use review to check whether they are contextualised for the RTO’s specific learner cohort, delivery mode, industry context, and assessment conditions	A purchased tool may technically map to unit requirements but use workplace scenarios irrelevant to the RTO’s learners, set unrealistic conditions, or gather insufficient evidence for certain performance criteria; without pre-validation review, these gaps only surface during audit or, worse, after qualifications have been issued
Failing to document the review	A review discussion takes place, but the findings are not recorded, the revisions are not documented, and the connection between what was found and what was changed is not evidenced	Standard 1.3(c) explicitly requires that the outcomes of the review result in documented changes; a conversation without documentation is, from a regulatory perspective, a conversation that did not happen
Excluding industry voices	Validation and pre-validation are conducted entirely by internal compliance or training staff, without involvement from industry representatives, workplace supervisors, or subject matter experts with current industry practice	Assessment tools that are reviewed only by educators may satisfy academic logic but miss practical workplace realities: current equipment, updated procedures, industry-specific safety requirements, or emerging competency expectations that only people working in the industry can identify
Confusing pre-validation with post-validation	The RTO relies entirely on post-assessment validation (Standard 1.5) to catch errors, meaning structurally flawed tools are used to assess learners before any quality control has been applied to the tool itself	Post-validation reviews completed assessments and judgements; it cannot retrospectively fix a tool that was fundamentally flawed from the outset; learners assessed with unchecked tools may have been judged competent or not yet competent on the basis of invalid evidence
Treating validation as an annual event	Validation is scheduled as a single annual meeting, often timed to precede an expected audit, rather than embedded as an ongoing quality process triggered by tool changes, scope additions, training package updates, or performance data	A once-a-year approach means tools can operate unchecked for months, accumulating mapping gaps, outdated content, unclear instructions, and assessment tasks that no longer reflect current industry practice; by the time the meeting occurs, the damage to assessment quality may already be extensive
Using generic validation checklists	The RTO uses a single, generic validation form that asks whether the tool is “satisfactory” without requiring reviewers to evaluate specific elements: mapping accuracy, task clarity, evidence sufficiency, marking guide specificity, and alignment with the Principles of Assessment	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 of competency 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 validation 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 pre-validation with post-validation, because the annual meeting is the only validation activity that occurs. An RTO that excludes industry voices is also likely to fail to contextualise its tools, because the people reviewing the tools do not have current workplace knowledge. The failure patterns are systemic, not isolated, and addressing them requires systemic change, not incremental fixes.

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, and rely on purchased tools without review, and fail to document changes. The fix is not to address each failure separately, but to redesign the validation process from the ground up, embedding pre-validation as an operational requirement triggered by tool changes, not as a scheduled administrative event.

4. Building a Compliant Pre-Validation Process: Seven Steps

If the meeting model is insufficient, what should replace it? The answer is a structured, documented, evidence-based review process 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 panel	Identify the people 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 panel 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 assessment 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 assessment task as if you were the learner: are the instructions clear and unambiguous? Are the tasks set 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 will produce 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 judgments 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 an assessor 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 competency judgement; consider whether the volume, variety, and depth of evidence meet the Rules of Evidence	Sufficiency is not about word counts or page numbers; it is about whether the combination of evidence types (knowledge questions, practical tasks, workplace observations, third-party reports) provides a complete, defensible picture of competency
6	Contextualise for the cohort	Check that the tool has been 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; it is a requirement that the assessment conditions and scenarios reflect the actual environment in which learners will demonstrate competency
7	Document findings and changes	Record every finding from the review: what was checked, what was found, what was changed, who made the changes, and when the revised tool was approved for use; this documentation must be retained as evidence	Standard 1.3(c) requires documented changes; the documentation is not just an audit trail but proof that the RTO’s quality assurance process is active, rigorous, and produces tangible improvements to assessment quality

This process does not need to be elaborate or time-consuming. For a simple assessment tool with a 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 Pre-Validation Should Be Triggered

One of the most common misconceptions about pre-validation is that it 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 that fitness or consistency should trigger a new pre-validation review.

At a minimum, pre-validation should be triggered when a new assessment tool is developed or acquired, including purchased resources that have not previously been 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-based 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 be appropriate for another. And it should be triggered when post-validation findings from Standard 1.5 identify systemic issues with a tool’s design that require structural revision rather than minor adjustments.

This trigger-based approach transforms pre-validation from a scheduled event into an embedded quality practice. It ensures that 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 be months before or after the change actually occurred.

6. The Relationship Between Pre-Validation and Post-Validation

Pre-validation and post-validation are not competing processes. They are complementary elements of a continuous assessment quality cycle. Pre-validation checks the tool before use. Post-validation checks the outcomes after use. Together, they create a feedback loop in which the assessment system is continuously improving: pre-validation catches structural flaws before they affect learners, post-validation catches performance issues that only become visible through actual assessment practice, and the findings from each inform the other.

When post-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 (a marking guide that is too vague, a task that is ambiguous) or in assessor practice (insufficient moderation, different interpretations of the standard). If the issue is tool design, the response should include a pre-validation 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, but the tool itself may not need revision.

This integrated approach is exactly what the 2025 Standards envision. 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 processes around it will not only achieve compliance but will 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.

Conclusion: Quality Control, Not Compliance Theatre

The distinction between pre-validation and post-validation under the Standards for RTOs 2025 is not a technical refinement. It is a fundamental reframing of what validation means and what it is for. Validation is not a meeting. It is not a scheduled event. It is not a form to be filled in. It is a quality control process, 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 the review must have the expertise to evaluate whether the tool does what it claims to do. And the evidence of this process must be retained, retrievable, and defensible at audit.

For RTOs that have been treating validation as a meeting, this requires a fundamental shift in practice. It requires moving from a reactive, calendar-driven approach to a proactive, trigger-based approach. It requires moving from generic checklists to structured, criterion-referenced evaluation. It requires moving from internal-only review to panels that include industry expertise. It requires moving from undocumented discussions to documented findings and evidence-based changes. And it requires understanding that pre-validation and post-validation are different processes, serving different purposes, governed by different standards, and both are 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: ensure that assessment tools work before using them, and ensure that assessment outcomes are consistent and valid after using them. This is not compliance theatre. This is quality control. And it is the minimum that learners, employers, and the sector as a whole deserve.

Summary: From Meetings to Quality Control

Pre-validation (Standard 1.3) and post-validation (Standard 1.5) are different processes with different purposes. Both are required. Neither replaces the other.
Assessment tools must be reviewed BEFORE use, with documented findings and documented changes. A discussion without documentation is not compliance.
Pre-validation should be triggered by tool changes, scope additions, training package updates, delivery mode changes, and cohort changes, not by calendar dates.
The review panel must include people with industry competence and current practice, not just internal compliance staff.
Purchased tools must be pre-validated to the same standard as internally developed tools. Buying from a reputable supplier is not a substitute for review.
Generic checklists that produce generic answers must be replaced with structured, criterion-referenced evaluations against the Principles and Rules of Evidence.
Pre-validation and post-validation form a continuous quality cycle: findings from each should inform the other, driving ongoing improvement in assessment quality.