Common ASQA audit findings and their process cause
Eight findings that recur across Australian RTOs, each traced back to the workflow that produced it — because findings are symptoms, not causes.
THE SHORT ANSWER
- Nearly every recurring finding is a process failure, not a knowledge failure.
- Assessment and validation findings usually trace to a mapping document nobody maintains.
- Evidence findings trace to collection happening at audit time instead of at delivery time.
- Fix the workflow and the finding stops recurring; fix the document and it returns next cycle.
Symptoms versus causes
A rectification response that edits a document closes the finding. It does not stop the finding. The same gap reappears at the next audit because the process that produced it is untouched — usually a manual step that depends on one person remembering something at the right moment.
| FINDING | PROCESS CAUSE | PROCESS FIX |
|---|---|---|
| Assessment tool does not cover all criteria | Mapping maintained by hand, versions diverge | Automated mapping with citations |
| Validation not conducted as scheduled | Schedule lives in a spreadsheet nobody owns | Register with due-date alerts |
| Insufficient evidence retained | Evidence collected at audit time, not at delivery | Collection triggered by delivery events |
| Inconsistent assessor decisions | No sampling between formal moderation rounds | Continuous sampling, exception review |
| Trainer credentials not current | Matrix checked manually, irregularly | Monitored register with expiry alerts |
| Superseded unit still in use | Training package updates tracked by email | Change monitoring and impact analysis |
| Student records incomplete | Re-keying between forms and the SMS | Validation at point of entry |
| Improvement actions not closed out | Actions recorded without owners or dates | Task tracking with accountability |
How to use this at your next rectification
For each finding, write the sentence "this happened because our process requires a person to ___ at the right moment". If you can complete that sentence, you have found the automation candidate. If you cannot, the finding is genuinely about capability or documentation, and should be treated that way.
WORKED EXAMPLE
An RTO received a finding that validation had not occurred for six units within the required period. The document fix was a revised schedule. The process fix was a register that flags units approaching their due date and assigns an owner — after which the finding did not recur, because nobody had to remember.
The uncomfortable pattern
Providers with the most recurring findings are rarely the ones with weak trainers or bad intent. They are the ones running a compliance system on institutional memory. Automation is valuable here precisely because it is unforgetful, not because it is clever.
Frequently asked questions
Recurring themes include assessment tools not covering all performance criteria, validation not conducted as scheduled, insufficient evidence retained, inconsistent assessor decisions, trainer credentials not current, superseded units still in use, incomplete student records, and improvement actions left open.
Because rectification usually edits a document while leaving the workflow that produced the gap unchanged. If the process still depends on a person remembering something at the right time, the finding returns at the next audit.
By removing the memory dependency: due-date registers, evidence collection triggered by delivery events, continuous sampling, credential expiry alerts and change monitoring all fire whether or not anyone remembers.
Rectify as required, then write the one-sentence process cause for each finding. That sentence tells you whether you are looking at an automation candidate, a documentation gap or a capability issue.
Turn findings into process fixes
Bring your last audit report to the free process audit.