02 / Unit audit

The other job assessors do.

Not marking student work, but reading a unit’s own documents against each other. Two assessors once spent fifteen hours each on a single unit. Apollo does the reading in minutes, for cents.

The check

Every document, read against every other

Marking guide, task briefs, templates, knowledge questions, cross-read together the way an auditor does. Where a task asks for something the guide never assesses, it stops and says so.

The report

Findings you can take to the page

Each mismatch names the documents it sits between, so a reader goes straight to the paragraph. The report states what was examined, so the review itself is inspectable.

The fix

From findings to a correction plan

The next build turns each finding into the fix: what to change, in which document, and why. An assessor still reviews and acts on everything.

What it catches

The gaps an auditor would find, before an auditor finds them.

Three mismatches account for most of what turns up in a validation meeting.

01

Tasks that don’t match the guide

A task asks for something the marking guide never assesses, or the guide expects evidence the task never requests.

02

Criteria with nowhere to land

Performance criteria that no task gathers evidence for. It is the first gap an ASQA auditor looks for.

03

Drift between versions

A template updated without the guide, or instructions that contradict the sample answer.

NEXT / Your data Where student work goes, what is stripped before it leaves, and what is never stored. Download Apollo