An IT checklist for staff departures
Coordinate a staff departure with a timed access checklist, records handover, device return and verified completion across business applications.

A staff departure needs a coordinated handover of accounts, devices and business records. Returning a laptop completes only one part of it. Use a checklist with an owner and a completion record for each system.
The staff-lifecycle guide covers building that inventory during employment. This checklist focuses on using it when someone leaves.
Agree the timing and responsibilities
HR or the person’s manager should confirm the departure time, the access-removal time and who signs off on the records handover. Give IT the information it needs through a restricted channel.
Identify someone who can handle a change in timing and contact the application owners. For a contractor, also check the engagement’s end date and any access managed by the contractor’s own organization.
Prepare a checklist that includes central identity, email, local and cloud applications, remote access, administrator accounts and physical access. Add shared credentials, API keys and automations the person created or controlled.
Close access in every application
At the agreed time, block new sign-ins and revoke sessions using the platform’s supported process. In a hybrid directory, follow the process for both the local and cloud accounts.
Microsoft explains that application-owned sessions need their own revocation. Disabling a central account doesn’t guarantee that every application immediately closes its existing sessions. Check local application logins, recovery methods and direct access separately.
Rotate shared secrets the person knew and update the integrations that need them. Move each automation to a service account where the platform supports one; don’t leave it dependent on a former employee’s login. Record exceptions with an owner and a deadline.
Hand over records before deleting accounts
Identify client work, shared documents, application ownership and business contacts that need a new owner. Check legal holds and retention requirements before deletion or licence removal.
Microsoft’s former-employee guidance covers preserving and transferring Microsoft 365 data alongside removing access. Confirm the relevant storage, mailbox and licence requirements for your tenant before acting.
Choose a contact route for new enquiries. An automatic reply may be enough. Mailbox access or forwarding needs a defined business purpose, a named list of who can read it and a review date; don’t apply one fixed forwarding period to every departure.
Recover devices and respect privacy
Record the return of company computers, phones, keys and other equipment. Keep a record of receipt, and have IT reset each device before it’s reissued. Preserve required records first.
For a personal device, remove only company data, using the process its management arrangement supports. An offline device may not receive a remote action, and removal can’t retrieve every downloaded copy. Confirm what completed and what still needs follow-up.
The OPC’s workplace-privacy guidance emphasizes proportionate monitoring and explains that applicable laws vary. Review mailbox access, log searches and device actions against your province, sector and employment policies. Leaving a job isn’t misconduct, and it doesn’t give you grounds for an unrestricted search.
Verify and close the checklist
Ask each application owner to confirm removal and the handover. Record when it happened, who checked it and any remaining work. Reconcile paid licences only after the data and retention decisions are complete.
If earlier departures lack records, use the SaaS access audit to investigate those gaps. Talk to us if you need help turning your account inventory into a repeatable departure checklist.


