Home / Security / Create an employee or contractor offboarding security checklist

Advanced Operational · Security Ring

Create an employee or contractor offboarding security checklist

1 hr to create, then ongoing use Impact: medium Effort: medium ✓ Manual completion

A documented employee or contractor offboarding security checklist ensures that when someone with access leaves, every account, credential, and API key they had is genuinely and immediately revoked, rather than depending on someone remembering to do it.

Old access that lingers after someone leaves is a real, common security gap, without a checklist this depends entirely on memory, which is exactly how forgotten access persists for months or years.

How to do it

1

List every system and account someone with access might have

CMS, hosting, email, shared documents, any tool with meaningful access.
2

Create a real checklist covering all of it

Something to actually work through item by item when someone leaves, not rely on memory.
3

Assign clear ownership for executing it

Someone specifically responsible for running through the checklist promptly.
4

Use it for real the next time someone actually leaves

The value of this mission comes from genuine use, not just having the document exist.

Common mistakes

This is easy to skip when someone leaves on good terms, the checklist matters precisely because access should be revoked consistently regardless of the circumstances of departure.

How you will know it is done

A documented offboarding checklist exists and has been used for at least one real departure.

Track this in your hive

The Security Ring turns this into a real, permanent mission — mark it complete once you have genuinely done it.

Open this mission in H.I.V.E. →

Create an employee or contractor offboarding security checklist

How to do it

Common mistakes

How you will know it is done

Related missions

Track this in your hive