RPL personas

RPL personas

Audience: ux, product, qa
Status: specced
Owns: product + UX
Depends on: CAP personas, Lifecycle, Experience flows

Canonical persona definitions (including centre roles, assessor types, awarding-body invite flow) live in CAP personas. This page is the RPL journey lens.

Candidate (RPL)

• Public signup; OTP for verify / password reset; password + Google auth via Orchestrator.
• May later accept a centre-staff invite on the same OL account (staff onboarding + X-CAP-PERSONA).
• Onboarding then application: sector / trade / units / centre → identity gate → centre review → payment → folder arrangement with facilitator → interview → IV → EV → certificate.
• Chats / feedback on revisions and appeals; on unsuccessful interview: LMS recommendations (GAP_TRAINING).

Assessor (QAA / IQM / IV / EV)

• Onboarding + platform approval; may apply to centre requests (facilitator, panel, IV) or awarding-body EV requests.
• Rule: EV must not be an assessor at the centre whose applications they verify.
• RPL-specific: facilitator on Folder Arrangement; panel member / lead on Interview; IV / EV on verification stages.

Platform admin / staff

• Invite-only patterns where applicable; creates / vets centres and assessors (approve / reject / suspend); owns sectors / trades / units / NOS / revenue config.

Centre admin / staff

• Centre onboarding + approval; assign reviewers, facilitators, IQA/IV, interview panels; wallet for application payments; forward to awarding body; hand out certificates.
• Invite staff (OL ProvisionAccount); multi-centre membership; acting headers in the centre workspace.

Awarding body admin / staff

• Platform-invited; assign EV; issue certificates to centres.

See also

• Full detail → CAP personas
• NSQ differences → NSQ overview