Build an offboarding checklist that removes every access
Creates a role-specific checklist to revoke accounts, devices, and data access when someone leaves, with timing.
The prompt
Create an IT offboarding checklist for a departing employee.
Role and department: [e.g. "sales manager", "DevOps engineer"]
Type of exit: [planned resignation / involuntary termination / contractor end]
Last working day and time: [DATE, TIME, TIME ZONE]
Systems they use: [e.g. "Entra ID, Google Workspace, Salesforce, AWS, GitHub, VPN, building badge"]
Devices they hold: [laptop, phone, tokens, keys]
Shared or privileged access: [admin accounts, shared mailboxes, service accounts, password vault entries, API keys they created]
Build the checklist in phases:
1. Before the exit: inventory their access, identify data and files to transfer, find accounts and automations owned by this person.
2. At the exit time: disable sign-in, revoke sessions and tokens, remove MFA devices, disable VPN and remote access, block mobile email.
3. Same day: rotate any shared passwords, secrets, or keys they knew; remove from privileged groups; collect devices.
4. Within 30 days: transfer file and mailbox ownership, set auto-reply or forwarding per policy, reassign licenses, wipe and reimage devices, then delete or archive accounts per retention policy.
For an involuntary exit, make disabling access happen at the same moment as the conversation, coordinated with HR.
Return a table: Step | System | Action | Owner | When | Done (checkbox). Add a short list of the access items most often missed. Follow our data retention and legal hold rules; mark anything that needs HR or legal sign-off as [CONFIRM WITH HR/LEGAL].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- e.g. "sales manager", "DevOps engineer"
- DATE, TIME, TIME ZONE
- laptop, phone, tokens, keys
- CONFIRM WITH HR/LEGAL
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Create a new supplier onboarding checklist and questionnaireA risk-based onboarding pack with the documents, checks, and approvals to collect before a new supplier gets a first PO.
- Find unnecessary approvals in a workflow and simplify sign-offsReviews every approval in a workflow, flags the ones that add delay without reducing risk, and proposes a leaner sign-off design with thresholds.
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Build a punch list and closeout plan to finish the jobAn organized punch list by area and trade plus a closeout checklist for documents, inspections, and final payment.