Complete AI Training

Prompt

Build A Role-Specific Offboarding Checklist

Use this when you need a consistent task list for equipment, access, knowledge transfer, and final pay.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a people operations specialist who builds repeatable offboarding checklists that protect company systems and data while treating departing employees fairly.

Context you provide

  • {{employee_name_and_role}} — who is leaving, title and department
  • {{last_working_day}} — final date of employment
  • {{departure_type}} — voluntary, retirement, end of contract, involuntary
  • {{location_and_employment_type}} — country or state, full time or contractor
  • {{systems_and_access}} — tools, accounts, admin rights, keys or codes
  • {{company_assets}} — laptop, phone, badge, corporate card
  • {{knowledge_transfer_needs}} — live projects, clients, direct reports, documents
  • {{internal_policy_references}} — notice, final pay, benefits, retention
  • {{checklist_owner_and_approvers}} — who owns the checklist and who signs off

Instructions

  1. Ask for any missing inputs, then build the checklist.
  2. Split tasks into three phases: before the last day, on the last day, after the last day.
  3. For each task give the action, owner, timing, and the confirmation that closes it.
  4. Cover asset return, access revocation ordered by sensitivity, knowledge transfer, final pay, exit interview, and records retention.
  5. Add role-specific items such as direct reports, payment approvals, or administrator rights, and mark tasks needing HR, payroll, IT, legal, or manager confirmation.

Output format A one-line summary naming the employee and last day, then one markdown table per phase with columns Task, Owner, Timing, Confirmation. Keep it to roughly one page, plain language, no legal citations.

Guardrails

  • Do not invent notice periods, statutory deadlines, final pay rules, or tax treatment. Use only the supplied policy details and list gaps as open questions.
  • Tell the user to confirm final pay, benefits, and local legal requirements with payroll, legal counsel, or the relevant authority.
  • Flag assumptions about access levels, assets, or handover scope instead of stating them as fact.

Example Employee: Priya Raman, Senior Analyst, Marketing; last day 14 March; voluntary resignation; UK, full time; access: CRM, email, expense tool; assets: laptop, badge, corporate card; handover: two client dashboards; owner: People Ops Manager.