Every seeded stage in order with its code, owning role and entry requirements, the six terminal stages, and all nineteen checklist codes.
5 min read·Last updated September 3, 2026
Twenty-two stages are seeded: sixteen active stages in process order, and six terminal stages reachable from anywhere. Everything here is per-organization data — codes, names, order, owning roles and requirements are all editable, so read this as the shipped default rather than a fixed pipeline.
Requirements listed are entry conditions.Each row lists what must be true to enter that stage, not to leave it. Unless noted, every seeded requirement is blocking. See Stage gates.
CHECKLIST_ITEMEMPLOYER_INTERVIEW_SCHEDULED — completed automatically when the application is added to an interview plan. Entering this stage stamps endorsedAt.
SELECTED
Selected by Employer
Recruitment Officer
CHECKLIST_ITEMEMPLOYER_INTERVIEW_PASSED — completed automatically when the interviewer finishes with a PASSED result.
Entering Deployed does three extra things.It stamps deployedAt, flips the applicant’s own status to DEPLOYED so lists agree with the board, and creates a Deployment record with status DEPARTED for post-arrival welfare monitoring.
Contract Completed is an active stage, not a terminal one.By default it is the last stage in the sequence rather than a terminal state, so an application that reaches it keeps status IN_PROGRESS. If you mark it terminal in your own configuration it closes as CLOSED_SUCCESS — it is the only stage that closes successfully; every other terminal stage closes as CLOSED_FAILED.
Reachable from any stage, never gated, and open to any staff member who can write applications. Entering one sets the application status to CLOSED_FAILED and records the matching TerminalReason.
Code
Name
Owner
Reason recorded
WITHDRAWN
Withdrawn
Any staff
WITHDRAWN
REJECTED
Rejected
Any staff
REJECTED
FAILED_MEDICAL
Failed Medical
Liaison Officer
FAILED_MEDICAL
VISA_DENIED
Visa Denied
Liaison Officer
VISA_DENIED
DISQUALIFIED
Disqualified
Any staff
DISQUALIFIED
CONTRACT_TERMINATED
Contract Terminated
Welfare Officer
CONTRACT_TERMINATED
The remaining TerminalReason values — DOCUMENT_INCOMPLETE and OTHER — are available to set explicitly on a close rather than being inferred from a stage.
Nineteen items are seeded. Each has an owning role, which is who is expected to complete it.
Operational checklist items.
Code
Label
Owner
Notes
BIODATA_COMPLETE
Applicant bio-data complete
Recruitment Officer
SCREENING_INTERVIEW_DONE
Agency screening interview conducted
Recruitment Officer
EMPLOYER_INTERVIEW_SCHEDULED
Employer interview scheduled
Recruitment Officer
Completed automatically when the applicant is added to an interview plan.
EMPLOYER_INTERVIEW_PASSED
Employer interview completed with a Passed result
Recruitment Officer
Completed automatically when the interviewer finishes with PASSED.
REQUIREMENTS_BRIEFED
Applicant briefed on requirements and collectible costs
Recruitment Officer
Records that the applicant was told exactly which costs are collectible. This is what protects the agency in a DMW complaint.
CONTRACT_SIGNED
Employment contract signed by worker
Recruitment Officer
MEDICAL_SCHEDULED
Medical examination scheduled
Liaison Officer
MEDICAL_RESULT_RECEIVED
Medical result received and recorded
Liaison Officer
VISA_FILED
Visa application filed
Liaison Officer
CONTRACT_VERIFIED
Contract verified at MWO/POLO
Document Officer
OEC_ISSUED
OEC issued
Document Officer
PDOS_COMPLETED
PDOS completed
Welfare Officer
Read by the 7-day pre-departure automation rule.
FLIGHT_BOOKED
Flight booked and ticket issued
Liaison Officer
PRE_DEPARTURE_BRIEFING
Pre-departure briefing conducted
Welfare Officer
ARRIVAL_CONFIRMED
Arrival at jobsite confirmed
Welfare Officer
ONBOARD_CONFIRMED
Employer confirmed onboarding
Welfare Officer
Role sign-offs. A `ROLE_SIGNOFF` requirement resolves to `SIGNOFF_` plus the role name.
Code
Label
Owner
SIGNOFF_RECRUITMENT_OFFICER
Recruitment Officer sign-off
Recruitment Officer
SIGNOFF_DOCUMENT_OFFICER
Document Officer compliance sign-off
Document Officer
SIGNOFF_WELFARE_OFFICER
Welfare Officer deployment-readiness sign-off
Welfare Officer
Five seeded items are not referenced by any default requirement.REQUIREMENTS_BRIEFED, VISA_FILED, CONTRACT_VERIFIED, OEC_ISSUED and PDOS_COMPLETED are tracked but do not gate anything in the shipped tree. They are there for you to attach to a stage if your process needs them — REQUIREMENTS_BRIEFED in particular is worth making a blocking requirement somewhere before money is collected.
Stages are ordered by sortOrder, seeded in tens from 10 to 160 for active stages and from 900 to 950 for terminal ones. The gaps are intentional: inserting a stage between two existing ones means picking a number in between rather than renumbering the tree. Terminal stages sit far above everything so they always sort last.