diff --git a/Crewing-Implementation-Spec.md b/Crewing-Implementation-Spec.md
index 42e7b64..d2b75cb 100644
--- a/Crewing-Implementation-Spec.md
+++ b/Crewing-Implementation-Spec.md
@@ -414,6 +414,15 @@ with these reconciliations:
 > `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**.
+>
+> **Phase 4** is in progress as stacked sub-PRs: **4a Crew records & profile + PPE
+> (Epics E, F) ✅**, **4b Leave & attendance (Epic G) — pending**, **4c Sign-off &
+> experience (Epic K) — pending**. 4a applies role-based PII masking server-side
+> (bank/Aadhaar full only for Accounts; salary hidden from site staff, §6/§8.8).
+> Deferrals carried in 4a: site-staff own-site scoping (needs a User↔Site link),
+> the records **verify queue** (§8.11 → Phase 5), and the Pay-status tab beyond the
+> salary structure (→ payroll, Phase 6). The leave-clash auto-backfill in 4b will
+> reuse the Phase-2 `autoRaiseRequisition` helper.
 
 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.)*