Home › Topics › Employee Offboarding

Employee Offboarding

Seven months after the sales manager left Northgate Retail, his account signed in from a coffee shop and downloaded the customer list. Nobody had disabled it. HR had sent the leaver notice to a mailbox that had itself belonged to a leaver. The manager had assumed IT did these things automatically, and IT had assumed somebody would tell them. The laptop had come back, eventually, in a carrier bag. The account had not, because accounts do not come back in bags. The investigation afterwards found four more live accounts for people who had left that year. One was still receiving the weekly payroll report.

This series is about the exit as a security event handled by a help desk. It covers why offboarding is a security ticket first and what a sloppy one leaves behind. It covers the offboarding checklist in the only order that is safe, which is disable first and delete later. Then come same-day and immediate exits, where the minutes matter and the discretion matters more. It covers getting the equipment back from an office leaver and from one who has never been in the building. It covers the leaver's data and mailbox, and the manager who wants everything. And it covers the leaver audit, which is the quarterly reconciliation that finds the accounts nobody disabled. The starter gets a welcome. The leaver gets a checklist. Both are kindness.

Articles in This Series

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.