NSQ lifecycle

NSQ application lifecycle

Audience: all
Status: specced
Owns: product + backend
Depends on: NSQ overview, RPL lifecycle, Workflow abstraction, Policies

Working vocabulary

Stage codes below are a working model aligned with RPL where stages are shared. Confirm final enums with business.

NSQ shares early and late stages with RPL; diverges after payment.

Stages (ordered)

Code	Label	Notes
DRAFT	Application drafting	Sector, trade, unit(s), centre
CENTRE_REVIEW	Centre review	Version history on feedback
PAYMENT	Payment to centre	Gate before induction
INDUCTION	Induction form	NSQ-specific; candidate completes form
ASSESSMENT	Regular assessment / evidence	NOS-aligned evidence; DO + PRF
INTERNAL_VERIFICATION	Internal verification (IV)	Same pattern as RPL
EXTERNAL_VERIFICATION	External verification (EV)	Awarding body; centre forwards
CERTIFICATION	Certificate issue / collection	Awarding body → centre → candidate
CLOSED	Terminal	Including gap-training style closes if applicable

Reusable statuses match RPL lifecycle (IN_PROGRESS, AWAITING_ACTION, ATTENTION_REQUIRED, APPROVED, …).

Happy path (summary)

1. DRAFT — Create application; NIN verified before submit.
2. CENTRE_REVIEW — Reviewer approve or feedback → candidate revises (application_versions) → resubmit.
3. PAYMENT — Required before induction progresses.
4. INDUCTION — Candidate fills induction form (GET/POST /applications/{id}/induction-form). Trade is locked to the application. Qualification level and units on the form are a recorded wish (what the candidate asked to be assessed on), not the assessment allow-list — they are not copied to ApplicationUnit.
5. ASSESSMENT — Upload/gather evidence per NOS; assessor (QAA) reviews with feedback loops. Direct Observation: learner coordinates with assessor; meetings scheduled; PRF captures the session (usually physical). Assessment is holistic on the application’s trade; induction units remain an audit of intent.
6. INTERNAL_VERIFICATION — Centre assigns IV; approve all work or reject with comments (may return toward assessment / prior stage). After IV APPROVED the app sits at external_verification. Same centre share-token and list filter as RPL (GET /applications?ivApproved=true&status=in_progress; POST /applications/{id}/share-token). Flag-off path: centre forwards (POST …/forward-to-awarding-body). When CAP_CENTRE_CERTIFY_BYPASS is on, PATCH /centre/applications/bulk { action: "certify" } applies to NSQ as well (synthetic EV/certification close; no Certificate row).
7. EXTERNAL_VERIFICATION — Centre forwards IV-passed apps; awarding body assigns EV (not an assessor at that centre).
8. CERTIFICATION — Awarding body prepares certificate; centre issues / candidate collects. Centre-bypass certify (flag on) is the off-platform equivalent of this close-out.

Version history

Centre review and assessment evidence loops keep application_versions (and stage-scoped feedback) the same way RPL does for review and folder arrangement.

Relation to RPL

Concern	RPL	NSQ
After payment	Folder arrangement + facilitator	Induction form
Competency evaluation	Interview panel (3 + lead)	Regular assessment + DO/PRF
Tail	IV → EV → certification	Same

Both are two seeded workflow_templates — see Workflow abstraction.