Resignation Handover Checklist

Problem

Resignation handoff is often reduced to “send files to the successor,” but the real risk comes from scattered tasks, permissions, client or vendor relationships, and documentation evidence. Different roles require very different checklists; ad hoc verbal handovers easily miss items and later turn into responsibility disputes.

How It Works

The skill activates when the user mentions triggers such as resignation handover, work transfer, or permission transfer, and generates a role-based actionable checklist. Core capabilities include:

• Work handoff: projects, daily duties, and open tasks
• Documentation handoff: file locations, operating notes, and knowledge capture
• Account and permission handoff: systems, tools, groups, and credentials
• Relationship handoff: clients, vendors, and partners
• Traceability: sign-off, email confirmation, or third-party acknowledgment

Typical steps are:

1. Confirm role, core responsibilities, active projects, and handover period
2. Generate a prioritized checklist focused on critical items first
3. Design timeline, confirmation mechanism, and post-handover support
4. Output templates and confirmation methods for handover

Boundaries

It does not handle resignation letters, labor arbitration, non-compete analysis, or exit interview preparation. If the role is unclear, time is short, there is no successor, or legal issues appear, the user should supplement context, confirm company process, or consult a lawyer. The skill emphasizes completeness, confirmation, and traceability, but company policies, system permissions, and contractual obligations still depend on the user’s actual environment.