IT Process Tracker

IT Offboarding Checklist

The access cutover, in the order it has to run. 39 steps across 4 stages, from discovery at T0 to the residual-access audit at LD+3, each with an SLA, an owner, the system its evidence lands in, and a flag on the 24 that are security-critical.

Free Excel workbook — 47 tasks across 8 phases with owners and status, plus a property recovery log and a contract key-dates worksheet.

The order is the content

Stage C runs C-1 to C-12, in that order, and the sequence is not a convenience. The legal hold goes first because it has to precede any deletion. Sessions and refresh tokens are revoked before the account is disabled, because disabling an account does not end a session already running. Secrets are rotated regardless, because a revoked account does not un-know a password. Reorder those and you have a runbook that looks complete and leaves the door open.

The IT offboarding guide explains why each of these matters. This is the runbook: every step timed off T0 or the last day, with the system its evidence lands in, and the 24 markedSecurity-critical separated from the 15 that are ordinary housekeeping.

It is the same 39 steps as the— not a summary of it — and the workbook adds the access revocation register, which is the artefact that turns "we revoked everything" into something auditable.

1. Intake & Access Discovery · T0 to T0+2

You cannot revoke what nobody has listed. The first two days are discovery: pull the real access report, find the privileged and standing grants, and name the service accounts and secrets only this person owned — those are the ones that break something silently when the account goes.

  • Open the offboarding ticket from the HR notificationSame business day as HR noticeEvidence: ITSM ticketIT Service DeskT0
  • Confirm the risk path with HR and set the cutover timeSame day — accelerated cases proceed immediatelyEvidence: ITSM ticketIT SecurityT0Security-critical
  • Check for a legal hold before touching any mailbox or driveBefore any deletion, wipe or licence releaseEvidence: eDiscovery / hold registerIT Security / LegalT0Security-critical
  • Run the access discovery report for the identityWithin 1 business day; covers SSO and non-SSO appsEvidence: IdP + access review exportIAMT0+1Security-critical
  • Identify privileged and standing access heldWithin 1 business day — escalates the path if foundEvidence: PAM / privilege registerIT SecurityT0+1Security-critical
  • List sole-owned service accounts, secrets and integrationsWithin 1 business day — these break silently at cutoverEvidence: Secrets manager + CMDBPlatform EngineeringT0+1Security-critical
  • Pull the assigned asset list from the registerWithin 2 business days; reconcile against MDM enrolmentEvidence: Asset register + MDMIT Asset ManagementT0+2
  • Publish the cutover runbook with named owners per systemAgreed at least 2 business days before LDEvidence: ITSM ticketIT case ownerT0+2

2. Pre-Cutover Preparation · T0+3 to LD-1

Everything that must happen BEFORE the account dies, because most of it cannot happen afterwards. File ownership does not transfer from a disabled account, and a repository with one departing owner is an outage waiting for a merge.

  • Transfer ownership of files, drives and shared documentsBefore cutover — ownership cannot transfer after disableEvidence: Workspace admin logCollaboration AdminLD-5
  • Reassign sole-owned service accounts and integrationsNew owner named and tested before LDEvidence: CMDB + secrets managerPlatform EngineeringLD-5Security-critical
  • Transfer repository, pipeline and cloud-project ownershipNo repo or project left with a single departing ownerEvidence: SCM + cloud IAM logPlatform EngineeringLD-5Security-critical
  • Remove from on-call rotas, escalation trees and alert routing3 business days before LDEvidence: Paging tool configIT OperationsLD-3
  • Agree mailbox disposition with the managerDecided before LD: delegate, forward, convert or archiveEvidence: Mail admin logCollaboration AdminLD-3
  • Send the asset-return instructions and prepaid labelAt least 2 business days before LD for remote leaversEvidence: Asset registerIT Asset ManagementLD-2
  • Stage the mailbox and drive archive; verify it is readableVerified before any deletion is scheduledEvidence: Archive / backup systemCollaboration AdminLD-2Security-critical
  • Dry-run the cutover checklist; confirm every owner is available1 business day before LDEvidence: ITSM ticketIT case ownerLD-1

3. Cutover (run in order) · On LD at time C

Twelve steps, in order, and the order is the point. The legal hold goes first because it has to precede any deletion; sessions and tokens go before the account is disabled, because disabling an account does not end a live session; secrets are rotated because a revoked account does not un-know a password.

  • Apply the legal hold, if one is requiredFirst action — before any revocation or wipeEvidence: eDiscovery holdIT Security / LegalC-1Security-critical
  • Revoke active sessions, refresh tokens and app passwordsAt C — disabling an account alone does not kill live sessionsEvidence: IdP session logIAMC-2Security-critical
  • Disable the SSO / identity-provider accountAt C; disable rather than delete, to preserve audit trailEvidence: IdP audit logIAMC-3Security-critical
  • Remove MFA factors and registered devicesAt C — prevents self-service re-enrolmentEvidence: IdP audit logIAMC-4Security-critical
  • Revoke non-SSO and privileged accessAt C: production consoles, databases, PAM, break-glassEvidence: PAM + per-app logsIT SecurityC-5Security-critical
  • Rotate every shared secret the leaver could have heldWithin 24 hours of C; immediately for privileged leaversEvidence: Secrets manager logPlatform EngineeringC-6Security-critical
  • Revoke API keys, personal access tokens and SSH keysAt C — these survive account disableEvidence: SCM + cloud IAM logPlatform EngineeringC-7Security-critical
  • Remove VPN, network and remote-access pathsAt C: VPN profile, certificates, jump hosts, allowlistsEvidence: VPN + firewall logNetwork OperationsC-8Security-critical
  • Apply the agreed mailbox and chat dispositionAt C: auto-reply, forwarding, delegation, convert or archiveEvidence: Mail admin logCollaboration AdminC-9
  • Terminate MDM enrolment and mark devices for wipeAt C for company-owned; selective wipe only on BYODEvidence: MDM consoleEndpoint ManagementC-10Security-critical
  • Deactivate badge, door and facility accessAt C, synchronised with the IT cutoverEvidence: Access-control systemFacilities / SecurityC-11Security-critical
  • Confirm cutover complete and log every timestampWithin 1 hour of C; exceptions raised immediatelyEvidence: ITSM ticketIT case ownerC-12Security-critical

4. Post-Departure & Verification · LD+1 to LD+30

Revocation is a claim until somebody verifies it. This stage is the audit — zero active grants across SSO and non-SSO, rotation confirmed, egress alerts reviewed — plus the licences, which are the largest recoverable cost in the whole process.

  • Collect or confirm shipment of all assigned devicesReceived or tracked within 1 business day of LDEvidence: Asset registerIT Asset ManagementLD+1
  • Reclaim paid licences and software seatsWithin 1 business day — largest recoverable cost in offboardingEvidence: Licence managementIT Asset ManagementLD+1
  • Remove from distribution lists, groups and channelsWithin 1 business day of LDEvidence: Directory + workspaceCollaboration AdminLD+1
  • Update the CMDB, directory and org chartWithin 1 business day of LDEvidence: CMDB + directoryIT Service DeskLD+1
  • Run the residual-access audit across SSO and non-SSO systemsWithin 3 business days of LD; zero active entries expectedEvidence: Access review reportIT SecurityLD+3Security-critical
  • Verify secret rotation is complete; no old credential worksWithin 3 business days of LDEvidence: Secrets manager logPlatform EngineeringLD+3Security-critical
  • Review pre-departure data-egress alertsWithin 3 business days; escalate anomalies to Security and LegalEvidence: DLP / audit logIT SecurityLD+3Security-critical
  • Wipe and re-image returned devices, or certify destructionWithin 7 business days of receipt; not before the hold clearsEvidence: MDM + disposal recordEndpoint ManagementLD+7Security-critical
  • Decommission integrations and scheduled jobs left behindWithin 7 business days; confirm no failing sync or data gapEvidence: Monitoring + CMDBPlatform EngineeringLD+7
  • Close the ticket with the full evidence pack attachedWithin 30 days of LD; unresolved items escalatedEvidence: ITSM ticketIT case ownerLD+30
  • Release the mailbox and drive archive at end of retentionPer retention schedule; never while a hold is activeEvidence: Archive systemCollaboration AdminPer policySecurity-critical

Every access path to close

The workbook's revocation register, one row per path, each needing a revoker, a timestamp and a verifier. The target is zero un-revoked rows at LD+3 — and a path is marked N/A rather than deleted, so the register shows what was considered as well as what was closed.

System or appAccess type
Identity provider / SSOPrimary account
MFA factors & registered devicesAuthentication
Email & calendarMailbox
Chat / collaborationWorkspace
File storage & shared drivesData
VPN / remote accessNetwork
Jump hosts & bastionNetwork
Cloud console — productionPrivileged
Cloud console — non-productionStandard
Source controlPrivileged
CI/CD pipelinesPrivileged
DatabasesPrivileged
PAM / break-glass accountsPrivileged
API keys & personal access tokensCredential
SSH keysCredential
Secrets managerCredential
Monitoring & pagingStandard
ITSM / service deskStandard
HRIS / finance systemsSensitive
Non-SSO SaaS appsStandard
Third-party / customer systemsExternal
Badge & facility accessPhysical
MDM enrolmentEndpoint

Next

General IT process guidance, not legal advice. Never wipe a device or release an archive while a legal hold is in place, and take advice before a selective wipe on a personal device — retention duties and what may be done to employee-owned hardware vary by state and by policy.

Free template

IT Offboarding Process Tracker

The working runbook: 39 steps across 4 stages, each with its timing, SLA, responsible team and evidence system, plus Timestamp and Verified-by columns so the cutover is auditable after the fact.

Two more tabs come with it — an access revocation register covering 24 access paths, and a device and licence recovery log that tracks wipe and seat reclaim separately, because a returned laptop is not a closed ticket.

Ready to Let AI Run Your HR?

Join 2,500+ companies that replaced HR busywork with AI agents. Sign up and start in minutes.

Get Started