Work Handover Checklist

The problem it addresses

When an employee resigns, takes leave, or moves teams, handovers usually fail because items are not closed: documents are hard to find, permissions are not transferred, in-flight project status is unclear, and customer contacts are not reassigned. This skill turns ad-hoc verbal handovers into an executable checklist and document template.

How it works

It starts with the handover type, role responsibilities, handover window, and successor, then builds a checklist covering:
- Work items: open tasks, in-flight projects, known issues
- Documents: specs, code notes, runbooks, data definitions
- Access and accounts: systems, repositories, customer portals, approval flows
- Customer and collaborator context: contacts, follow-ups, ownership

The output emphasizes priorities, actionable steps, and mutual confirmation, and flags common omissions such as resetting sensitive passwords through IT or recording complex operations.

Boundaries

It is intended for work-content handover, not HR, payroll, benefits, resignation approvals, or legal matters. It requires role information; if there is no successor or little time, it favors producing documented priorities and follow-up recommendations first.