diff --git a/Crewing-Implementation-Spec.md b/Crewing-Implementation-Spec.md
index e3f4395..42e7b64 100644
--- a/Crewing-Implementation-Spec.md
+++ b/Crewing-Implementation-Spec.md
@@ -407,11 +407,13 @@ with these reconciliations:
 > requisition it relies on is already built in Phase 2, so Epic K is purely
 > additive when it arrives.
 >
-> **Phase 3** is delivered as three stacked sub-PRs: **3a Candidates (Epic B) ✅**,
-> **3b Recruitment pipeline (Epic C) ✅**, **3c Onboarding (Epic D) — pending**.
+> **Phase 3 ✅ complete** — delivered as three stacked sub-PRs: **3a Candidates
+> (Epic B) ✅**, **3b Recruitment pipeline (Epic C) ✅**, **3c Onboarding (Epic D) ✅**.
 > 3b's central-Approvals integration follows §8.13 R8 (Salary/Selection/Waiver
 > gates surface in the unified Manager queue). `SalaryStructure` is attached to the
 > `Application` during the pipeline and bound to the `CrewAssignment` at onboarding (3c).
+> Onboarding promotes the candidate to `EMPLOYEE` with a `CRW-` number; **SITE_STAFF
+> login creation for management ranks (`grantsLogin`) is a deferred follow-up**.
 
 1. **Foundations** — `SITE_STAFF` role; crewing schema + enums; permissions; `CREWING_ENABLED` flag; nav scaffold; reference data (Ranks, RankDocRequirements).
 2. **Requisitions + relief** (Epic A) — requisition lifecycle, relief requests, and the shared `autoRaiseRequisition` backfill helper. *(Epic K sign-off/experience originally sat here; moved to Phase 4 — see status note above, as it depends on the onboarding/assignment schema.)*