Recognition of Prior Learning

---

RPL and Outcome Standard 1.6

What is RPL?

Recognition of Prior Learning (RPL) is a formal assessment pathway. It evaluates a candidate’s existing skills, knowledge and experience, gained through work, life or informal training; against the requirements of a unit of competency or qualification. Where the evidence is sufficient, the candidate is assessed as competent without repeating training they have already, in effect, completed. It is not a credential shortcut; it is a full assessment, just run against a different evidence base than a training-then-test pathway.

Why it matters: Outcome Standard 1.6

RPL is explicitly referenced in the RTO Standards 2025. Standard 1.6 sits in Quality Area 1, Division 3 (RPL and Credit Transfer), alongside Standard 1.7. It requires RTOs to:

• Give every VET student the opportunity to seek RPL for the qualifications and units they’re enrolled in or seeking to enrol in — and to actively tell them this, at enrolment, in the student handbook and in pre-training information. Availability can’t rest on the student happening to ask.
• Base every RPL decision on valid, sufficient, authentic and current evidence — the same rules of evidence and principles of assessment that apply under Standard 1.4 apply here too. RPL is held to the same rigour as any other assessment, not a lighter-touch version of it.
• Produce transparent, defensible and documented decisions, so an auditor (or the candidate) can see how the call was made.
• Reflect any reduction in volume of learning that results from RPL in the student’s Training and Assessment Strategy.

For the candidate, RPL is a matter of fairness and efficiency- it avoids making people sit through training for what they can already demonstrate. For the RTO, it’s a heightened ASQA risk area precisely because it’s easy to get informal: verbal claims, resume reviews and “reputation” assessments don’t meet the standard, and inconsistent or thin RPL decisions are a recurring audit finding.

What happens in an RPL assessment

1. Application and information — the candidate is informed RPL is available and applies against a specific unit or qualification.
2. Evidence gathering — the candidate (often with assessor guidance) assembles evidence: work samples, references, prior qualifications, statements, third-party reports, etc.
3. Mapping to evidence requirements — each piece of evidence is mapped against the performance evidence (PE) and knowledge evidence (KE) of the relevant unit(s), checking it meets the rules of evidence (valid, sufficient, authentic, current).
4. Gap identification — where the evidence doesn’t fully cover a PE/KE item, that becomes a gap. Gaps are typically converted into a targeted interview, practical demonstration or supplementary task rather than a full unit of training.
5. Assessor judgement and signoff — the assessor makes and records a competency decision against the full unit, datestamps it and signs it, the same as any other assessment judgement.
6. Record and report — the mapping, evidence references (including where physical evidence is held) and the final outcome are compiled into an RPL record for the student file and for audit.

The RPL Assessor Companion

The RPL Assessor Companion RPL Assessor companion is a tool that I have built in my Homelab that supports exactly this process. Evidence is logged as individual “evidence cards,” each tied to a single PE or KE item and carrying a descriptor and tags. The candidate (or assessor) drags evidence cards onto a mapping document against the unit’s requirements, and a gap check identifies any PE/KE items not yet covered. Those gaps are automatically turned into separate interview tasks so the assessor knows exactly what still needs to be evidenced. Each mapping is date stamped and logged against the assessor’s name, and the process finishes with a signed-off, printable RPL record — with physical evidence files retained on SharePoint and referenced on the final report. It’s designed as a standalone companion to the broader RTO Standards Companion rather than a module within it, since the RPL record it produces is the point of the tool.