How It Works

Uploading Your Assessment Tools

From upload to report: minutes, not days.

Submit the trainer and assessor guide(s) for the unit being validated — the practitioner-facing document that contains the assessment tasks, observation checklists, marking guides, model answers, and assessor instructions. However many files make up that package for a given unit.

That’s the entire input. No configuration. No manual mapping. No setup.

Trainer and assessor guide files being uploaded for validation

How Validation Is Applied

Five independent reviews

Validation360 pulls the complete, official Unit of Competency directly from training.gov.au. From it, the system constructs a hierarchical compliance benchmark.

Every element. Every performance criterion. Every nested sub-criterion. Every knowledge evidence sub-bullet. Every foundation skill, performance evidence requirement, and assessment condition — each decomposed into an independent test point.

Five independent reviews then run in parallel against the submitted assessment materials.

  • The performance criteria analyst examines every criterion across all three evidence dimensions — assessment instructions, marking guide, and assessment instrument.
  • The performance evidence analyst tests sufficiency against ASQA’s Rules of Evidence.
  • The foundation skills specialist maps reading, writing, oral communication, and numeracy to the specific tasks where each is demonstrated.
  • The knowledge evidence reviewer maps every knowledge evidence item to the sub-bullet level.
  • The assessment conditions examiner tests assessor requirements, industry expert involvement, simulation rigour, and consistent performance.

Every compliance requirement examined

Every requirement checked. No sampling. No assumptions. No spot checks. Gaps are not missed because they fell outside a sample.


Cross-checking designed to surface hidden gaps

  • Parallel analysis across components (instrument to benchmark to mapping to evidence)
  • Independent checks across different compliance requirements (to reduce opinion drift)
  • Cross-referencing against unit requirements (performance evidence, knowledge evidence, assessment conditions)
  • Testing design-to-evidence alignment (does the task actually produce the evidence the benchmark is judging)

The objective is not speed alone. It is consistency and rigour — so the outcome is defensible.

Why This Stays Consistent

No Fatigue

No fatigue

The same rigour applied to the first unit reviewed and the fiftieth. Validation quality doesn’t drop as volume increases or as the year gets busier.

No familiarity bias — the system has no prior relationship with the tools

No familiarity bias

The units a team knows best are the ones most likely to carry blind spots. Familiarity and genuine independence are structurally incompatible. The system has no prior relationship with the tools.

No pressure to make it pass — the same standard enforced regardless of timing or context

No pressure to make it pass

Where deadlines or workload pressure exist, validation can drift toward close enough. The same standard is enforced every time, regardless of timing or context. No softened findings.

No single reviewer or interpretation — five independent reviews cross-confirmed before anything reaches the report

No single reviewer or interpretation

Five independent reviews run before the final validator cross-examines all five — each review blind to the others. Instead of hinging on one reviewer’s judgement or one consultancy’s interpretation of the Standards, conclusions are cross-confirmed from multiple independent angles before anything reaches the report.

What the System Identifies

Role-mix error: a task asks the learner to explain a procedure when the unit requires demonstrated performance

Role-mix errors

A performance criterion requires a learner to physically perform an action. The assessment task only asks them to explain, describe, or identify it.

The task exists. It maps to the right criterion. It looks like evidence.

Under ASQA’s evidence hierarchy, demonstrating knowledge of a procedure is not the same as demonstrating performance of it.

Role-mix errors are among the most consistently present failures across all qualification areas — and among the least frequently caught by internal validation.

Mapping inconsistencies between knowledge evidence sub-bullets and assessment questions

Mapping inconsistencies

Knowledge evidence items in the UoC are frequently structured with nested sub-requirements.

Internal validation maps at the heading level. The heading gets a question, and the sub-bullets are assumed covered.

Each sub-bullet is a discrete requirement. They often aren’t covered. Validation360 treats each one independently.

A question asking a learner to define informed consent, dignity of risk, or mandatory reporting satisfies none of the knowledge evidence requirements that follow from the definition.

The UoC requires demonstrated understanding of application in practice, impact, and consequences. A definition question tests recall.

The gap is invisible on a surface read — because a question exists for every knowledge area.

  • Unit requirements marked as covered but not clearly assessed
  • Tasks assessing content that is not mapped (or does not belong)
  • Assessment conditions not reflected in the tool design
Evidence and benchmark gaps where unit requirements specify plural or range performance

Evidence and benchmark gaps

A UoC may specify performance with clients (plural), a range of equipment, at least three different situations, or on multiple occasions.

Every one of those specifications is a discrete compliance requirement.

Assessment tasks requiring a single demonstration against a plural or range requirement are non-compliant — regardless of how many delivery cycles the tool has been through.

Observation checklists not broken down per performance criterion, and marking guides without observable behaviour descriptors for practical demonstration, are also identified here.

ASQA will ask how the assessor determined competence. Most checklists cannot answer that question.

Questions We Hear From Compliance Teams

Most RTOs do.

The question isn’t whether a process exists. It’s whether it achieves genuine independence at the requirement level, consistent rigour across every unit in scope, and a defensible audit trail.

The structural limitations of internal validation — familiarity, volume, time pressure — apply regardless of the quality of the process or the capability of the people running it.

Validation360 isn’t a replacement for compliance expertise. It’s what the process looks like when it runs without the constraints that make internal validation inconsistent.

It doesn’t need to.

The methodology that drives Validation360 was built by experienced practitioners over a decade.

The system applies that methodology more consistently, more completely, and without the time pressure and familiarity bias that cause even experienced practitioners to miss things.

The question isn’t whether the system matches an expert on their best day. It’s whether it outperforms an expert on a pressured day — with twelve other clients, a deadline, and a qualification they’ve reviewed a hundred times before.

The report doesn’t replace human sign-off. It replaces the analytical work that precedes it.

A compliance manager who reviews the Validation360 output, exercises professional judgement on the findings, and approves the rectification plan has performed a more defensible validation process than one who completed internal review manually under time pressure.

The report is the analysis. The compliance professional is still the decision-maker.

What changes is the quality of the evidence they’re making that decision from.

The free test resolves this.

Run the system against a unit the team has already validated internally. The output either finds something they missed — or it doesn’t.

If it finds something, the trust question answers itself. If it doesn’t, the team has confirmation.

Either outcome is useful. Neither requires prior trust.

What You Receive

What the system finds, the report makes actionable.
Every finding traced to a specific task, criterion, or evidence requirement — so the work that remains is the fix, not the analysis.

The compliance status dashboard

Five colour-coded domain charts — green, yellow, red. Showing the proportion of requirements that Fully Map, Partially Map, or Do Not Map. One view of the risk profile across all five compliance domains, readable in under a minute.

Compliance status dashboard with five colour-coded domain charts showing fully map, partially map, do not map proportions

Clear rectification guidance

Every finding traced to an exact task number, question reference, or form identifier.

Every recommendation specific to the gap it addresses.

The analysis work lifts. What’s left to do is the fix — requirement by requirement, task by task, where practitioner judgement actually matters.

Rectification guidance traced to exact task number, question reference, and form identifier

Professional, RTO-branded, audit-ready reports

Delivered in minutes. Branded to the RTO. Formatted and ready for internal compliance records and validation evidence.

The full report includes a requirement-by-requirement analysis across all three evidence dimensions, a dedicated assessment conditions analysis, and a cross-reference matrix mapping every performance criterion against every form of supporting evidence on a single page.

RTO-branded validation report with requirement-by-requirement analysis and cross-reference matrix

See what the system finds in your own assessment tools.