hand-off-a-work-project

# hand-off-a-work-project Make the recipient capable of operating and changing the work without relying on undocumented memory. ## Procedure 1. Confirm handoff scope, recipient, effective date, decision authority, overlap, and support window. 2. Capture purpose, users, current outcomes, commitments, timeline, status definitions, and success measures. 3. Inventory repositories, documents, systems, vendors, environments, dashboards, data, credentials, and owners. 4. Link decisions, architecture or process context, known issues, risks, dependencies, and rejected alternatives. 5. List recurring operations, deadlines, alerts, meetings, approvals, and escalation paths. 6. Reconcile open work by priority, owner, due date, evidence, and next action. 7. Transfer access through approved systems and verify least privilege; never place secrets in the handoff document. 8. Walk through a representative task, failure, and decision while the recipient drives. 9. Run acceptance checks, record gaps, and obtain explicit acceptance or a bounded remediation plan. ## Failure plan - Do not declare handoff complete because files or passwords were sent. - Never share personal credentials or keep departed owners as hidden dependencies. - If authority, access, or critical knowledge cannot transfer, escalate before the effective date. - Preserve restricted information in its proper system rather than duplicating it. ## Done - State, work, decisions, risks, routines, systems, and contacts are current and linked - Access and a representative operating task are tested by the recipient - Acceptance, remaining gaps, owners, and support expiry are recorded