RPL lifecycle
RPL application lifecycle
Section titled “RPL application lifecycle”Audience: all
Status: specced
Owns: product + backend
Depends on: Domain entities, Policies, Workflow abstraction, NSQ lifecycle
An RPL application moves through stages. Within a stage it has a status. Composite examples appear after the tables. Sequencing is also expressed as a seeded RPL workflow_template — see Workflow abstraction.
Stages (ordered)
Section titled “Stages (ordered)”| Code | Label |
|---|---|
DRAFT |
Application drafting |
CENTRE_REVIEW |
Centre review |
PAYMENT |
Payment to centre |
EVIDENCE |
Folder arrangement / evidence collection |
INTERVIEW |
Panel interview |
INTERNAL_VERIFICATION |
Internal verification (IV) |
EXTERNAL_VERIFICATION |
External verification (EV) |
CERTIFICATION |
Certificate issue / collection |
CLOSED |
Terminal |
Statuses (reusable)
Section titled “Statuses (reusable)”| Code | Meaning |
|---|---|
IN_PROGRESS |
Actor is working |
AWAITING_ACTION |
Waiting on a specific actor |
ATTENTION_REQUIRED |
Feedback; candidate or prior stage must fix |
APPROVED |
Gate passed; advance stage |
REJECTED |
Gate failed |
APPEAL_OPEN |
Appeal / discussion open |
SCHEDULED |
Interview booked |
COMPLETED |
Stage work finished |
Close reasons (when stage = CLOSED)
Section titled “Close reasons (when stage = CLOSED)”| Code | Meaning |
|---|---|
CERTIFIED |
Certificate issued / collected path finished |
WITHDRAWN |
Candidate or centre withdrew |
GAP_TRAINING |
Interview unsuccessful; LMS recommendations |
REJECTED_FINAL |
Failed a terminal reject path |
Happy path (summary)
Section titled “Happy path (summary)”- DRAFT — Candidate creates an application with sector, trade, centre and qualification level (
qualificationLevelIdis required for RPL, forbidden for NSQ; the level must be on the trade’s active NOS); fills the wizard (personal SoT via onboarding, experience/trade preferences, identity verify, declarations) viaPATCH; NIN verified + complete draft required before submit; otherwise stuck in draft. Candidate may attach a CV viaPOST /applications/{id}/cv(cvonGET /applications/{id}). Self-pay candidates mayPOST /applications/{id}/withdrawwhileDRAFTor pending Application Form (IN_PROGRESS+application_form) — status becomesWITHDRAWN; the candidate then creates a new application to change centre or trade. CandidatePATCH /applications/{id}/centreis deprecated. Platform staff may still move a self-pay draft (PATCH /admin/applications/{id}/centreand bulkPATCH /admin/applications/bulk) and that notifies the candidate and both centres; org-sponsored drafts (organizationIdset) stay locked (409 application.sponsored_centre_locked); trade/sector/wizard/CV stay put on an admin move. Payment later quotes the newcentreId. Centre staff cannot change centre. Unit ids are preferences only (not assessment scope) and must belong to the selected level; changingexperienceAndTrade.qualificationLevelIdclears them. At most oneDRAFT/IN_PROGRESSapp per trade (retry allowed after rejected/withdrawn/certified). Application payload may live in JSONB withschema_versionwhile requirements settle. (Application Form is intended as a real tracked stage onceself_serviceis seeded — see Workflow abstraction.) - CENTRE_REVIEW — Submit → centre reviewer accepts or returns feedback via unified
POST /applications/{id}/reviewwithstageKey: application_form(single_approval, engine-backed). Candidate revises and resubmits —application_versionskeeps history (v1 on apply, v2 after feedback, …). While still pending here, a self-pay candidate may withdraw instead of waiting (POST /applications/{id}/withdraw); the centre is notified. Reject from the centre still returns the row toDRAFTfor amend/resubmit (notWITHDRAWN). - PAYMENT — After centre approval, the candidate (or centre staff, for display) may preview the fee with
GET /applications/{id}/payment-quote. Only the candidate pays viaPOST /applications/{id}/pay. CAP computes the fee and initiates processing on Orchestrator; required before Folder Arrangement / facilitator assignment. Only paid applications get a facilitator. Onpayment.completed, CAP stores a receipt snapshot (paidAt, provider, amounts, candidate) plusreceiptAssetId(GET …/receiptreturns details even if the PDF URL is still null). The payment row ofGET …/stagesmay include amount + receipt so the centre UI does not need a second quote call. Centre owners list checkouts onGET /centre/payments. See Payment architecture. - EVIDENCE (Folder Arrangement) — Centre assigns a facilitator; candidate fills the Evidence Vault (RPL-only): general uploads whose
evidenceTypeis the union of NOSassessmentMethodson the application’s qualification level and wizard document kinds declared onevidenceCandidateCanProvide(GET /applications/{id}/evidence-types; resume staysPOST …/cv, third-party report stays its dedicated kind), one self-assessment, one third-party report — not NSQ per-unit evidence. General items may optionally tagunitIds[](qualification-level units; many allowed; omit/[]for none) soGET …/assessment-mappingcan join those claims onto unit rows (wizard preferences ∪ tagged units). Folder approve is still ≥1 general item all approved (declared types and unit tags are not a coverage gate). The assigned facilitator reviews each general evidence item (PATCH …/evidence/{evidenceId}/review{ decision, comment? }; reject needs a comment); candidate general-evidence writes are only allowed during this stage and a content or unit-tag edit resets that item topending. Folder review (POST /applications/{id}/review,stageKey: folder_arrangement) is facilitator-only and approve requires at least one general upload with all general evidence approved (409 otherwise). Revision viaapplication_versionsuntil approve → interview. Centre may add paid, in-progress RPL applications to a shared induction sitting (/centre/inductions*); this writes aninductioncalendar event for the candidate. Read-onlyGET …/assessment-mappingandGET …/portfoliocompose the folder for review. Centre may already book an interview sitting here (GET /applications?interviewSchedulable=true;POST /centre/interviews/{id}/scheduleor ad-hoc panel/schedule) without entering or completing the interview stage. Evaluate, forms, candidate sign-off, and observer comments stay interview-only. - INTERVIEW — Centre may reuse panel and interview sitting templates (
/centre/panels,/centre/interviews; list sittings withfrom/to/scheduledAt) and copy one onto an application viaPOST /centre/interviews/{id}/schedule{ applicationId }or bulk{ items }(frozen per-app snapshot +centreInterviewId; sitting on or after the template clock; not a cohort). Copy/curate/schedule also allowed while still on folder arrangement. Centre diary:GET/PATCH /centre/interview-bookings(application + candidate; PATCH reschedules that application only). Ad-hoc: centre curates a panel of 3 and selects a lead, plus an IV observer who may be one of the three or a fourth person; schedules viaPOST /applications/{id}/interview/schedule(scheduledAt,modephysical|online,locationoruseCentreAddress,linkwhen online).GET …/interview/schedulereturns the current booking (do not scrape events).useCentreAddresscopiesGET /centre/profileformatted address (422 if missing). Editing panel members wipes the schedule — POST schedule again.PUT …/interview/forms/{formType}{ data }: the lead fills the four canonical forms (records,assessment_grid,practical_observation,skill_demonstration) — blocked after candidate signoff; those are what matter for the candidate path. Other seated members (voting panelists and the IV observer) may upsert their own optionalInterviewFormRecordfor the same form types (isolated, not candidate-signed, never required to leave interview).GET …/interview/formsreturns{ forms, panelistRecords }. Candidate signs each canonical form withPOST …/forms/{formType}/signoff(signatureModeupload|default|typed). Voting panelistsPOST …/interview/evaluate(feedback,signatureAssetId); the lead may also senddecisionapprove|rejectand, on reject,outcomeunsuccessful|inconclusive. Appeal: candidate comment to lead → lead reopens/reschedules or dismisses with reason. Unsuccessful/inconclusive → recommendation service consults LMS (GAP_TRAINING). Success → IV. - INTERNAL_VERIFICATION — Centre assigns an IV (
POST /applications/{id}/iv, or with QAA viaPOST /applications/{id}/assignments; bulkPOST /centre/applications/assignments/bulk). IV may be pre-assigned before this stage; the same assessor cannot be both QAA and IV. PickerGET /centre/assessors?qualification=IV.GET /applications/{id}includesinternalVerifierwhen assigned. IV reviews all work to date; rejects with comments may return to prior stage (head panelist notified). Success → engine advances toexternal_verification. Ready-to-share / ready-to-certify queue isGET /applications?ivApproved=true&status=in_progress(IV StageHistory APPROVED — notstage=internal_verification). Centre mayPOST /applications/{id}/share-token(one live token; POST replaces;DELETErevokes) so a viewer canGET /shared/applications/{token}without Bearer (files via…/assets/{assetId}). Flag-off path: centre forwards to awarding body (POST …/forward-to-awarding-body; IV must be approved). WhenCAP_CENTRE_CERTIFY_BYPASSis on,PATCH /centre/applications/bulk{ ids, action: "certify" }setsCERTIFIEDand synthetically closes leftover EV/certification history (no Certificate row /cap.certificate_issuednotification). Flag off → 404. - EXTERNAL_VERIFICATION — Awarding body assigns EV per centre (EV must not hold a role at that centre). Issues return to prior stage; clean apps → notify awarding body for certificates.
- CERTIFICATION — Awarding body prepares certificate; sends to centre for candidate pickup / digital delivery. Centre-bypass certify (flag on) is the off-platform equivalent of this close-out.
GET /applications/{id}/stages exposes the uniform seven-stage breakdown (Application Form → Payment → Folder Arrangement → Interview → IV → EV → Certification). Calendar: GET /applications/{id}/events (one app), GET /candidate/events (candidate’s apps), and GET /assessor/events (assessor’s actively assigned apps only).
Version history & abstractions
Section titled “Version history & abstractions”- Review and Evidence Vault loops:
application_versions+ stage-scoped feedback. - Appeals / resolutions: generic across stages — Workflow abstraction.
- Actors: evaluators vs evaluatees; handlers
single_approval(review, facilitator approve, IV, EV) andpanel_evaluation(interview). Planned TODOs:self_service(Application Form),external_gate(Payment).
Example composites
Section titled “Example composites”| Stage | Status | Meaning |
|---|---|---|
DRAFT |
IN_PROGRESS |
Filling form; NIN not verified |
DRAFT |
AWAITING_ACTION |
NIN verified; can submit |
CENTRE_REVIEW |
ATTENTION_REQUIRED |
Candidate must amend |
EVIDENCE |
AWAITING_ACTION |
Awaiting facilitator assignment (payment done) |
INTERVIEW |
SCHEDULED |
Interview booked |
INTERVIEW |
APPEAL_OPEN |
Candidate appealed evaluation |
CLOSED |
COMPLETED + reason GAP_TRAINING |
Unsuccessful interview |
Concurrent application rule (summary)
Section titled “Concurrent application rule (summary)”A candidate may only have one active (non-draft) application path per policy: after submit, starting another is blocked until feedback/ATTENTION_REQUIRED handling or {x} days without centre response (exact {x} TBD — see Policies).
Same early/late stages; after payment see NSQ lifecycle (induction + assessment instead of folder arrangement + interview).