IT Offboarding: When the Checklist Lives in One Head
Someone leaves the company on Friday. On Monday, a person who has never done it before is asked to offboard them: disable the directory account, shut off email, remove chat access, and forward their phone line to a colleague. They get it done, with some trial and error and a few searches for vendor instructions. Everyone moves on. Nobody asks whether that was the full list, and nobody wrote down what they learned along the way. The next time someone leaves, the process starts from scratch.
This is how offboarding works in a lot of growing companies. The task is routine, but the knowledge behind it is not written down in one place. It lives in old tickets, in a few email threads, in a vendor help article someone bookmarked, and above all in the head of whoever did it last. When that person is busy, on vacation, or gone, the work falls to whoever is available, and they rebuild the checklist from memory and guesswork.
Why is offboarding so easy to get wrong?
Because the number of systems keeps growing and nobody keeps the list current. BetterCloud's 2026 State of SaaS report put the average company at 118 SaaS applications, up 11 percent after two years of consolidation. Not every employee uses all of them, but a typical person touches email, chat, file storage, a phone system, an HR platform, and several department tools. Some sit behind single sign-on. Many do not, and those exceptions are exactly what gets missed.
The steps also vary by role. Removing a salesperson means reassigning CRM records and transferring a phone number. Removing a developer means rotating keys and revoking repository access. Removing a manager means handing off shared inboxes, approval workflows, and calendar ownership. A generic checklist covers the first five minutes. The rest is in prior tickets and the memory of whoever handled the last similar departure.
What happens when an offboarding step gets missed?
The visible cost is security. Surveys from identity vendors have repeatedly found that a large share of former employees could still log in to at least one account from a previous job. One Beyond Identity survey put that figure at 83 percent. The numbers vary by study, but the pattern is consistent: access tends to linger in the tools nobody remembered to check.
The less visible cost is operational. A forwarded phone line that was never set up means calls go to voicemail for weeks. A mailbox that was disabled instead of transferred means a customer thread disappears. A shared document owned by the departed user stops being editable. Each problem is small, but each one becomes a help desk ticket, and each ticket starts with someone asking how the offboarding was done in the first place.
Who should own employee offboarding, HR or IT?
In most organizations the honest answer is both. HR owns the trigger, the last day, and the paperwork. IT owns access removal, data handoff, and device recovery. The gaps appear between the two, when HR assumes IT knows about every tool the person used, and IT assumes the request lists everything that needs to happen. Clear ownership helps, but it does not solve the underlying problem: the knowledge of which steps apply to which role is spread across both teams' systems.
How do you build an offboarding process that survives turnover?
Start with a written checklist that is organized by role and kept with your other runbooks, not in someone's personal notes. Every time an offboarding turns up a new step, add it. That alone is a big improvement. But checklists still drift, and the context behind each step, such as why a certain tool needs a manual export or which vendor needs a support ticket to remove a license, usually lives somewhere else.
This is where retrieval-augmented generation, or RAG, helps. Instead of relying on one perfect document, it indexes the places offboarding knowledge already lives, including tickets, runbooks, email threads, and vendor documentation, and lets people ask questions in plain language. A new team member can ask "how did we offboard the last sales manager" and get the relevant steps from past tickets and emails, each with a citation back to the source. The same approach that helps employee onboarding go faster works in reverse when someone leaves.
How does RetrieveIT help IT teams with offboarding?
RetrieveIT connects to SharePoint, Google Drive, OneDrive, Confluence, Jira, Gmail, Outlook, and Microsoft Teams, so the runbooks, past tickets, and email threads behind your offboarding process become searchable from one place. You do not have to migrate anything or write the perfect checklist first. Every answer cites the source document, the author, and the date, with a link to the original, so whoever is doing the work can check that a step is still current before they act on it.
For IT and help desk teams, that means the person handling an offboarding for the first time can find what the last person did without tracking them down. Permissions from each source system are enforced at query time, so people only see what they already have access to. And because it is one enterprise search layer across all of your tools, it also answers the questions that come after: who owns that shared drive now, and where did that customer thread go.
RetrieveIT does not disable accounts or replace your identity provider. It makes sure the knowledge behind every step is findable, so offboarding stops depending on one person's memory.
Make every offboarding step findable
Connect your runbooks, tickets, and inboxes and let anyone on the team find how it was done last time, free for 14 days. No credit card required.
Get Started Free