How to use the Employee Resignation & Handover Checklist
Fill in the Exit Dossier Parameters at the top of the page: the employee's name, the position title, the last working day, the notice period in days, the department, and the primary handover owner. Add one line per responsibility, system, or access grant in the Main Handover Items box — use a format such as Duty: Reconcile the monthly close | Owner: Finance lead. If you only type plain sentences, the generator still derives a task label for every line, so an unstructured brain dump produces a usable checklist. Press Generate handover checklist and QuitKit builds five interdependent phases (notice and documentation, knowledge transfer, systems and access, assets and compliance, final sign-off), assigns an accountable owner to each task, and reports the derived resignation date, the days remaining, the completion percentage, and the count of privileged-access items. Tick a task row to advance its phase, then copy the checklist, download the plain-text pack, or print the certificate with its signature blocks.
Derived resignation date, notice period, and days remaining
Enter the last working day and the notice period in days, and the checklist derives the day the resignation notice must be served. Long notice periods are routed through the statutory gate: a 90-day notice is flagged as a director-level gate that needs board acknowledgement, a 60-day notice needs HR review, and anything from 30 days upward is checked against contractual notice terms. The governance strip keeps the derived resignation date, the notice period, the days remaining until the last working day, and the count of still-open tasks visible while you work, so an item cannot quietly slip past the exit date. Because the whole schedule is derived from two inputs, you can re-plan a shortened notice period without rebuilding the checklist.
What a complete resignation handover checklist contains
A defensible handover covers more than a farewell email. QuitKit's five phases walk the full exit: formal resignation letter and acknowledgement, employment-contract and non-compete review, the payslip and leave-encashment calculation, a documented knowledge transfer into a named successor, a live-system inventory, credential rotation for every privileged account, company asset return, and the final release letter that closes the employee file. Each task carries a category (Documentation, Knowledge Transfer, Systems and Access, Assets, Compliance, or Communication), a suggested owner, and a completion state, so the checklist doubles as the audit trail when someone asks months later whether a production credential was actually rotated.
Separating knowledge transfer from access revocation
Two failure modes account for most messy exits. The first is undocumented knowledge: a specialist leaves and the process they carried in their head leaves with them. QuitKit forces an explicit knowledge-transfer phase with per-item owners and deliverable descriptions, so the successor receives a document rather than an afternoon of verbal briefing. The second is leftover access: a privileged account is never disabled and becomes a standing risk. The systems and access phase enumerates each application, database, and shared credential, marks the privileged ones, and keeps them in their own completion bucket until someone confirms rotation or revocation. The privileged-access counter in the metrics strip stays visible the whole time so the security-critical items cannot be scrolled past.
Tri-party sign-off and the printable exit certificate
An exit is complete only when three parties agree. The Exit Certificate section prints the employee, the reporting manager, and the HR approver, each with a signature line, the date field, and the count of completed versus total checklist items at the moment of printing. The certificate names the derived resignation date, the last working day, the notice period, and the primary handover owner, so the printed page is self-contained evidence for the personnel file. Use the print action in your browser to produce a clean PDF — QuitKit prints the certificate and suppresses the interactive controls, so the paper copy carries the record and not the workspace.
Is the Employee Resignation & Handover Checklist private?
Yes. QuitKit is a client-side tool. Names, positions, dates, and handover items stay in the browser tab, and the draft checklist is persisted only to your own browser storage so a reload does not lose your work. There is no sign-up, no email gate, and no upload step. The tool ships an Axle API adapter boundary so a self-hosted deployment can point the same checklist operations at a Go/SQLite backend, and when no backend is configured the adapter serves the identical list, get, create, update, and delete surface from a deterministic local store.
Frequently Asked Questions
What should an employee resignation and handover checklist include?
At minimum: the formal resignation letter and its acknowledgement, contract and non-compete review, the final payslip and leave encashment, a documented knowledge transfer into a named successor, a live inventory of systems and privileged access with confirmation that each credential was rotated or revoked, company asset return, and the release letter that closes the file. QuitKit generates all five phases from a role description and assigns an owner to each task.
How is the resignation date calculated from a notice period?
Give the last working day and the notice period in days, and QuitKit subtracts the notice period to derive the date the resignation must be served. It also derives the days remaining until the last working day and flags long notice periods — 30 days and above as a contractual check, 60 days as an HR review gate, and 90 days as a director-level board acknowledgement.
How do I make sure privileged access is actually revoked?
The systems and access phase keeps privileged credentials in a separate completion bucket with a dedicated privileged-access counter in the metrics strip. Each account is a task row that stays open until a named owner marks the rotation or revocation done, so the security-critical items cannot be marked complete by ticking a single blanket checkbox.
Can I use the checklist without a successor already hired?
Yes. Leave the successor field on the duty line blank and the task is assigned to the primary handover owner, with the deliverable description written so it can be forwarded later. When the successor is named, edit that one line and regenerate; the phases, owners, and completion tracking rebuild around the new name.
Is the generated checklist free to use and private?
It is free, needs no account, and runs entirely in the browser. Your inputs and the saved draft stay in local storage on your own device. Nothing is uploaded, and no email address is required to copy, download, or print the checklist.
Does the checklist work on mobile?
Yes. The dossier parameters collapse to a single column, the phase cards stack vertically, and the tool actions stay reachable without horizontal scrolling, so a manager can complete a sign-off from a phone on the last working day.