RPL — Obligations Checklist¶
The acceptance surface for the RPL tile. Every line is something an RTO must be able to demonstrate. The tile is not done until each line is answered by a modelled, clause-bound surface — or carries a principled out-of-scope / deferral decision.
This is move 2 of the Legislation-to-Tile Method for the RPL tile. It follows the pattern People set (people-00-obligations).
Authority (read first)¶
Per the method, the instrument is the authority; the practice guide is Layer 3 commentary (example activities, known risks, self-assurance questions). Anchors are written clause / instrument; PG = practice-guide-qa1.
Two adjacent standards live here, and they are distinct mechanisms — the tile must not blur them:
- Standard 1.6 — Recognition of Prior Learning. RPL is an assessment process: assessment of an individual's relevant prior learning and experience (formal and informal) to determine the extent to which they meet the training-product requirements. Evidence is gathered and judged. This is the tile's heart.
- Standard 1.7 — Credit Transfer. CT is not an assessment: it recognises and awards credit for prior successful completion of an equivalent unit or module. No evidence-of-competency judgement — an equivalence match against a completed, recognised result. Lighter, different workflow. Launch inclusion is a model-move decision (§7).
The single most load-bearing fact for the whole tile: RPL is assessment, so the judgement is the assessor's. The rules of evidence (Standard 1.4) apply in full. The engine may anchor the assessor; it never decides. Every design constraint below flows from that.
Standard 1.6 — Recognition of prior learning (anchor: 1.6 / F2025L00354)¶
Outcome: VET students with prior skills, knowledge and competencies are supported to seek RPL to progress through the relevant training product. The RTO must be able to demonstrate each line.
The offer (PI a — RPL as a proactive obligation, not a passive tool)¶
| # | Obligation — the RTO must be able to demonstrate | Anchor | RPL tile's role |
|---|---|---|---|
| 1.6-1 | Students are offered the opportunity to seek RPL and are made aware of the RTO's RPL policy and process | 1.6 / F2025L00354 (PI a) | Core — the invite/offer surface is this discharge |
| 1.6-2 | Students are made aware of their right to have prior learning recognised (except where an industry regulator or licensing requirement prevents it) | 1.6 / F2025L00354 (PI a); PG | Core — the offer carries the right + the licensing caveat |
| 1.6-3 | The approach accommodates the variety of experiences and learning pathways students present | 1.6 / F2025L00354 (PI a); PG | Core — intake accepts heterogeneous evidence, not a fixed form |
| 1.6-4 | Where a third party plays a role in RPL assessment, the student is made aware of it | 1.6 / F2025L00354 (PI a); PG | Evidence-hold — third-party disclosure recorded (third-party RPL is day-two) |
The decision — evidence-based, same rigour as the assessment system (PI b)¶
| # | Obligation | Anchor | RPL tile's role |
|---|---|---|---|
| 1.6-5 | RPL decisions are based on evidence of prior skills, learning and experience, gathered and judged | 1.6 / F2025L00354 (PI b) | Core — evidence intake + the judgement surface |
| 1.6-6 | RPL is conducted in accordance with the RTO's assessment system — same policies, processes and rigour as ordinary assessment, not a lighter path | 1.6 / F2025L00354 (PI b); PG "same rigour as your assessment system" | Core — the tile embodies assessment-grade rigour, structurally |
| 1.6-7 | Evidence is judged against the rules of evidence (validity, sufficiency, authenticity, currency) and the principles of assessment | 1.4 + 1.6 / F2025L00354 (PI b); PG | Core — see the rules-of-evidence sub-table below |
| 1.6-8 | Decisions are consistent with, and maintain the integrity of, the training-product requirements | 1.6 / F2025L00354 (PI b/c); PG | Core — the unit's requirements are the bar the evidence is judged against (rto-nrt-db) |
| 1.6-9 | The assessor responsible for judging RPL evidence (including any engaged through a third party) meets the credential requirements of Standards 3.2 and 3.3 | 1.6 / F2025L00354 (PI b); PG; 3.2–3.3 / F2025L00354 | Source — assessor identity + credentials read from People |
The record — documented, fair, transparent, consistent, retained (PI c)¶
| # | Obligation | Anchor | RPL tile's role |
|---|---|---|---|
| 1.6-10 | Decisions are documented and are transparent, defensible | 1.6 / F2025L00354 (PI c); PG | Core — the sealed judgement record + provenance |
| 1.6-11 | Decisions are fair, transparent and consistent among students | 1.6 / F2025L00354 (PI c) | Core — same rubric, same engine anchor, per-leaf trace for every candidate |
| 1.6-12 | RPL assessment records are retained to the assessment-record-retention requirement — the evidence the judgement rested on is held, not discarded | 1.6 / F2025L00354 (PI b/c); PG known risk "not upholding assessment record retention requirements" | Core — the sealed R2 evidence vault; retention floor = the audit window |
| 1.6-13 | Where evidence identifies gaps, the RTO works with the student on the gap training required — its amount, delivery and any cost | 1.6 / F2025L00354; PG | Core — the engine's per-leaf not-yet-traced map is the gap map; feeds the gap-training conversation |
Assurance of the RPL process itself¶
| # | Obligation | Anchor | RPL tile's role |
|---|---|---|---|
| 1.6-14 | The RTO validates and assures its RPL practices to be confident decisions are made in accordance with the Standards | 1.6 / F2025L00354; 1.5 / F2025L00354; PG | Source — RPL judgements enter the assessment-validation cycle (read by Record) |
| 1.6-15 | Staff understand that granting RPL where the student does not meet the requirements has serious consequences (public safety, industry confidence, sector reputation) — and the system provides that assurance | 1.6 / F2025L00354; PG | Core — the tile is built so wrongly granting is structurally resisted (see §5) |
The rules of evidence, as they bind RPL (anchor: 1.4 / F2025L00354)¶
RPL evidence is judged against the four rules of evidence. This is where the UCCA engine's capability boundary maps exactly onto the law — the engine holds what it is permitted to hold; the two it cannot hold are the two the assessor must own.
| Rule | What it requires of RPL evidence | Who holds it |
|---|---|---|
| Validity | The evidence genuinely relates to the unit's requirements — the trace from evidence to competency holds | Engine anchors (the per-leaf demonstrated / not-yet trace with a verified span) → assessor confirms |
| Sufficiency | The quality and quantity of evidence is enough to judge competence | Assessor decides — an aggregate judgement the engine is constitutionally barred from making |
| Authenticity | The assessor is assured the evidence is the student's own genuine work | Assessor + adapter + candidate attestation — the candidate attests authenticity at intake; the engine (text) does not judge provenance |
| Currency | The evidence reflects current skills/knowledge against current training-package requirements | Adapter recency check + assessor — tested against the live rto-nrt-db requirement |
The rule the whole tile is built to honour: the engine may raise a hand on validity and surface gaps; it never rules on sufficiency or authenticity, and it never grants. That is not a limitation to engineer around — it is the anchor-not-decide constitution meeting the rules of evidence, and it is what keeps the RTO (and us) off ASQA's RPL-mill radar (§5).
Standard 1.7 — Credit transfer (anchor: 1.7 / F2025L00354)¶
Outcome: VET students who have completed an equivalent training product are supported to obtain a credit transfer. Distinct from RPL — an equivalence match on a prior recognised completion, no evidence-of-competency assessment.
| # | Obligation | Anchor | RPL tile's role |
|---|---|---|---|
| 1.7-1 | Students are offered credit transfer and given the CT policy | 1.7 / F2025L00354 (PI a); PG | Core (if in scope) — CT offer |
| 1.7-2 | Credit is awarded for prior successful completion of an equivalent unit/module, evidenced by an authenticated transcript / recognised result | 1.7 / F2025L00354; PG "authenticating transcripts" | Core (if in scope) — equivalence match on rto-nrt-db supersession/equivalence lineage |
| 1.7-3 | CT decisions are documented and the transcript authenticated | 1.7 / F2025L00354; PG | Core (if in scope) — lighter record; no evidence vault |
Model-move decision (§7): CT is cheaper than RPL — the equivalence data already lives in rto-nrt-db (supersedes / superseded_by), and there is no evidence bundle to vault. But it is a distinct workflow, not a sub-case of RPL. The model decides whether CT ships in the launch RPL tile as a light second mode, or is day-two.
§5 — The RPL-mill posture: risks the tile must structurally prevent¶
The practice guide's known-risks list is, in effect, ASQA's enforcement brief against RPL. Each is a design constraint — the tile is built so the risk is resisted by construction, not by policy alone. This is the regulatory hard line the engine's anchor-not-decide rule exists to satisfy.
| Known risk (PG) | The tile's structural answer |
|---|---|
| Automatically granting RPL for a higher AQF qualification in the same industry | The engine never auto-grants. No path issues an RPL outcome without an assessor's recorded judgement. The findings contract carries no pass/fail/competent vocabulary. |
| Cutting corners / business models that issue RPL cheaply → unqualified people in critical roles (aged care, disability, ECEC) | RPL runs at assessment-grade rigour (1.6-6); the mode-switch demo proves depth by contrast, never by shortcut. |
| Promoting RPL as an easy, quick or guaranteed path | Product language and UX never promise an outcome; the outcome is an assessor judgement, surfaced as such. (A positioning + copy constraint, carried into the spec.) |
| Not upholding record-retention requirements | The sealed R2 evidence vault (1.6-12), retained to the audit-window floor. Custody is the default, not an option. |
| Failing to verify authenticity of submitted evidence | Candidate authenticity attestation at intake + assessor authenticity judgement (rules-of-evidence table). The engine does not fake this — authenticity is never the engine's to assert. |
| Inadequate inquiries / non-genuine students or agents using RPL as a vehicle | Intake captures identity (candidate self-attested), and — where the context expects it — government photo ID and a recorded session as authenticity anchors (optional, consent-gated; see the intake pipeline). |
| Outsourcing to unregulated third parties who don't apply the Standards | Third-party RPL is day-two; at launch RPL is conducted on the RTO's own assessor identity (People, 1.6-9). When third-party lands, it carries the same-rigour monitoring obligation (1.6-14). |
| Not robust enough for high-risk work licensing thresholds | The bar is the unit's requirements (rto-nrt-db); licensing-gated units carry their threshold. Flagged for the model where a unit is licence-linked. |
| Overseas qualifications/competencies not mapped to Australian legislative/regulatory requirements | Flagged for the model — overseas-evidence handling (incl. WHS and industry-law mapping) is a distinct evidence path; likely day-two, named now so it isn't assumed handled. |
| Not testing evidence for currency against training-package requirements | Currency check against live rto-nrt-db (rules-of-evidence table); no assumed-current evidence. |
| Insufficient systems for identifying/addressing gaps | The engine's per-leaf not-yet-traced map is the gap-identification system (1.6-13); gaps feed the gap-training conversation. |
§6 — Cross-tile seams¶
- People (source). The RPL assessor's identity and credentials (must meet 3.2/3.3, obligation 1.6-9) are read from People. RPL does not re-implement assessor credentialling — it consumes People's verdict.
- The engine (tool, not decider). The engine anchors validity and surfaces gaps (evaluative mode on the existing core — per the received UCCA capability crossing, cited in the model). It never rules sufficiency/authenticity, never grants. The seam is anchor-not-decide.
- Record (evidence + validation). RPL judgements are assessment judgements — they enter the assessment-validation cycle (1.6-14, Standard 1.5) and the audit evidence record. The sealed evidence vault is RPL-domain custody; the outcome (units credited) is an audit artefact Record and the outcome-export carry.
- Candidate-identity / intake pipeline (shared substrate). The offer→invite→self-complete→capture→queue→adjudicate→outcome pipeline is shared with LLND and built once. RPL is its first consumer; the candidate record it binds to is the shared invisible identity store (beside People, never inside it).
- Student Management System (outside the fence). The outcome leaves to the SMS (or an importable export where no SMS exists); custody of the evidence and judgement stays with RTOpacks.
student_identifierhas the meaning of the Student Identifiers Act 2014 — the USI is a verified, specially-handled identifier, not free text.
§7 — What this checklist tells the next moves¶
Discharging events (for NO ORPHAN GRAINS / the audit ledger) fall out of the Core rows: 1. RPL offered / student made aware (discharges 1.6-1/2) — the invite. 2. RPL application opened against a candidate + target training product. 3. Evidence submitted + sealed (the vault landing; carries the authenticity attestation). 4. Engine anchor run — per-leaf validity trace + gap map produced (an anchor, not a verdict). 5. Assessor judgement recorded — the sufficiency/authenticity/currency ruling, the outcome (the signing act; assessor identity per People). 6. Gaps → gap-training determination (where not-yet-competent). 7. Outcome exported / pushed to the SMS. 8. (CT, if in scope) Equivalence match + transcript authenticated.
The model (move 3) must hold: the candidate identity (shared store), the RPL application (candidate × target product × units), the evidence bundle (sealed custody + authenticity attestation), the engine-anchor findings (per-leaf trace + gaps, subject-locked), the assessor judgement (the decision, on People's credentialled assessor), the gap-training determination, and the outcome/export. The dual-mode (human-shell / engine-assisted) is a mode over one judgement surface, not two systems.
Two model decisions flagged, not decided here: (1) CT launch inclusion (§4); (2) overseas-evidence handling (§5) — both likely day-two, both named so they aren't silently assumed in scope.
The tall pole is not the workflow — it is the trust proof. The human RPL loop (invite → evidence → assessor dashboard → decision → audit export) clears the incumbent's workflow bar and is launch-buildable on the spine substrate (People, Record, the vault). The engine cognition layer rides on the UCCA evaluative mode (confirmed reachable, no re-engineer — see the received crossing, cited in the model), with the evidence-normalisation adapter as the real our-side build. Multimodal (image/video evidence) is out of v1; text + documents (OCR for scans) is the launch path.
Move 2 artefact (draft — the model, rpl-01-model, will answer it). Built from F2025L00354 (Standards 1.4, 1.5, 1.6, 1.7, 3.2, 3.3) and practice-guide-qa1.md (RPL & Credit Transfer; Assessment), read as primary / Layer-3 sources 2026-07-06. The RPL tile name is ruled (frozen-launch-scope; "Attest" retired). The engine is referenced as "the engine"; the received UCCA capability crossing is cited by the model, not reproduced here — authorship stays home.