Outsourced EmploymentPowered by StealthAgents

Practical guide

Define an offboarding access checklist with dated proof

An offboarding access checklist that records each system, the removal time, the person who confirmed it, and the exceptions that remain open.

Published

Practical guide illustration for Define an offboarding access checklist with dated proof
Table of contents

List the systems before the last day

An offboarding access checklist should start with the systems the employee can reach, not with a generic list of departments. Pull the access inventory from identity management, the finance system, the HR system, and any client portal. Add shared accounts and physical access that may not appear in the directory. A system discovered after the last day is a gap that nobody planned for.

Name the owner of each system and the person who can remove access. Record the expected removal time and the evidence that will prove it. A checklist that says remove email without naming the administrator is not actionable. The owner should confirm the removal, not only receive the request.

Include the employee's role and the systems that role typically uses. A role-based list helps the reviewer notice a missing system even when the inventory export is incomplete. Keep the role list current when a job description changes. The checklist should reflect the work, not only the directory.

Separate the last working day from the access end time

The last working day and the access end time are not always the same. An employee may finish at the end of a shift, while access must end at a specific hour. Record both and the time zone. A mismatch can leave an account active for hours after the employee has left.

For a departure that involves sensitive access, set an earlier removal time with the manager. Record the reason and the person who approved it. For a routine departure, follow the standard time. The checklist should show the decision rather than applying one rule to every case.

Record the manager's confirmation of the last working day and the time. A checklist that starts from the HR termination date may miss a manager's later change. If the date changes, reopen the access plan and check the systems again. The record should show which date was used.

Record the removal, not only the request

A request to remove access is not evidence that access was removed. For each system, record the time the account was disabled, the person who performed the change, and the confirmation from the system. If a system does not provide a confirmation, record the manual check and the person who performed it. A checklist full of sent requests is not a completed offboarding.

Check the shared accounts separately. A shared login may remain active even after the individual account is disabled. Record who else uses the shared account and whether the credential was rotated. If the account cannot be rotated immediately, record the exception and the plan. A shared credential without a rotation plan is a standing risk.

Record the time the manager confirmed the last working day. A late confirmation can push the removal past the intended hour. If the confirmation arrives after the deadline, note the delay and the person responsible. The record should distinguish a process delay from a system failure.

Handle client-owned and third-party systems

Some access belongs to a client or a vendor, and the team cannot remove it directly. Record the request, the client contact, the date, and the confirmation. Follow up until the client confirms the removal or gives a date. Do not mark the item complete because the request was sent.

Keep the client communication with the offboarding record. If the client asks for a different process, record the instruction and the person who approved it. The team should not promise a removal it cannot perform. A clear boundary protects both the client relationship and the former employee.

Check the account's group memberships and delegated access, not only the main login. A disabled account can still leave a shared mailbox or a delegation active. Record the group or delegation and the person who removed it. The main account check is not enough for a complete removal.

Close the checklist with a named reviewer

Before the record is closed, a named reviewer should compare the access inventory with the removal evidence. Record the reviewer, the date, and any exception that remains open. The reviewer should not be the same person who performed every removal. A second check catches a missed system or an unconfirmed request.

If an exception remains, give it an owner and a date. A checklist with an open item is more honest than a closed checklist with an unverified assumption. Review the open items at the next weekly meeting. The record should show what remains and who is responsible for it.

Keep the final checklist with the termination record and the access evidence. Do not store it only in a ticket that closes automatically. The next reviewer should be able to open the record and see what was removed. A ticket without the evidence is a request history, not proof.

Learn from the next departure

After the offboarding, compare the systems on the checklist with the systems that actually had access. Add any system that was missing and remove any that no longer applies. Record the change and the date. The next departure should start from a more accurate inventory.

Ask the manager whether the timing caused a business problem. A removal that was too early can block a handover, while one that was too late creates risk. Record the answer and adjust the standard only when the evidence supports it. The goal is a repeatable process, not a perfect guess.

Ask the client to confirm any client-owned access in writing. A verbal confirmation is easy to forget and hard to audit. Keep the message with the offboarding record. If the client does not confirm, leave the item open rather than closing the checklist.

Sources

References supplied with this guide.

Article source directory
SourcePublisherContext
U.S. Department of Labor, Employment Law Guidedol.govPrimary reference supplied with this article.
Internal Revenue Service, Understanding employment taxesirs.govPrimary reference supplied with this article.
National Institute of Standards and Technology, Cybersecurity Framework 2.0nist.govPrimary reference supplied with this article.