The prompt
Score 10 of 10, Excellent
Use it when Someone is leaving, and you need a dated checklist with owners so that their work is handed over and their access and final pay are handled correctly.
- {{employee_role}}
- {{last_day}}
- {{owner}}
- {{departure_type}}
- {{responsibilities}}
- {{access_and_equipment}}
- {{policy}}
- {{location}}
- {{successors}}
Full prompt and why it works
Prompt
Plan the offboarding of {{employee_role}}, whose last day is {{last_day}}, for {{owner}} to run, so that their work is handed over before they go, their access ends at the right moment, equipment comes back, and final pay is correct and on time. The departure is {{departure_type}}. What they own now (projects, clients, systems, recurring tasks, documents): """ {{responsibilities}} """ Systems and equipment they have: {{access_and_equipment}} Our offboarding policy and final pay rules, as written: """ {{policy}} """ Where they work: {{location}} Who takes over their work: {{successors}} Produce, each with a heading: 1. Checklist: a table with the columns When (a date, or "last day" with a time), Task, Owner, Done, sorted by date, covering handover, access removal, equipment return, final pay and benefits, the exit interview, and telling the team and any clients. 2. Handover plan: for each responsibility, who takes it over, what they need (documents, introductions, shared passwords changed after the person leaves) and a handover meeting date. 3. Final pay and benefits: what our policy says about the final paycheck, unused vacation, expenses, equity and when benefits end. Rules on final pay timing and vacation payout differ by place, so beside each item write [CHECK RULES FOR {{location}}] for HR or payroll to confirm, and do not state the law yourself. 4. Exit interview: 6 to 8 open questions about their work and the team, for example "What would you change about how work reaches you?" That example shows the form only. 5. Messages to the team and to any clients, under 100 words each, saying when they leave and who to contact from now on. A good plan leaves nothing that only the leaver knows how to do. Keep it practical and respectful. Do not say or hint why they are leaving in any message, and leave out personal details. If the departure is involuntary, time access removal for the meeting where they are told, and send the team message only after that meeting. If a responsibility has no successor, mark it [OWNER NEEDED] and list it at the top.
Variables
- {{employee_role}}
- The leaver's role, for example "our accounts payable specialist".
- {{last_day}}
- Their last working day, for example "Friday, May 15".
- {{owner}}
- Who runs the offboarding, for example "their manager with HR".
- {{departure_type}}
- For example "a resignation with four weeks' notice" or "involuntary, effective immediately".
- {{responsibilities}}
- What they own: projects, clients, systems, recurring tasks and where their documents live.
- {{access_and_equipment}}
- The systems they can sign in to and the equipment they hold.
- {{policy}}
- Your offboarding and final pay policy, including vacation payout and benefits end dates.
- {{location}}
- The country or state where they work.
- {{successors}}
- Who takes over each area, or "not decided".
Why it works
- Format. One dated checklist with an owner for every task, so nothing depends on someone remembering it in the last week.
- If unsure. Final pay and vacation payout carry a [CHECK RULES] marker for payroll, and work with no successor is listed at the top.
- What to avoid. No message says or hints why the person is leaving, and access is timed with care when the departure is involuntary.