Skip to content

Systems

Employee offboarding checklist: the laptop and badge that outlive the account

Disabling a leaver's account stops new sign-ins. Sessions already issued, departmental apps and door controllers keep working until each expires or is removed.

Computing America IT. Help desk support, backups and network infrastructure.

Send the checklist
Updated 5 min readComputing America
A clean rectangle in the dust of a desk where a laptop sat, its charger still plugged in.

In short

  • Recovering hardware and removing access are separate jobs with separate owners.
  • Disabling an account does not end sessions already issued. Revoking sessions is a separate administrative action, so name it in the checklist.
  • A collected badge leaves the door record in place. The card carries a number, the access system holds the record, and door controllers keep honoring a cached list until they next sync.
  • Disk encryption protects a powered-off device, not one that left while unlocked. The escrowed recovery key and enrollment record are what prove the encryption was real.
  • NIST SP 800-88 Rev. 1 was superseded by Rev. 2 on September 26, 2025, so a checklist still citing Rev. 1 cites a withdrawn document. A certificate of destruction naming serial numbers is evidence; a vendor's general assurance is not.

Getting the laptop back does not end the leaver's access. Disabling the account stops new sign-ins, and issued sessions, departmental apps and door controllers keep working until each expires or is removed.

Fig. 1
  1. Termination recorded

    Payroll or HR

    • To Account disabled
    • To Revoke sessions
  2. Revoke sessions

    A separate action

    • To Cached device sessions
  3. Cached device sessions

    Live until expiry or revoked

  4. Account disabled

    In the directory; blocks new sign-ins only

    • To Departmental apps
    • To Door access record
  5. Group: Not reached

    Departmental apps

    Separate accounts

  6. Group: Not reached

    Door access record

    Controllers hold a cached list

Disabling the directory account does not reach departmental apps or door controllers; each needs its own removal.

The offboarding checklist

The steps in the order they should run. The sections below say why each one is on the list and what it leaves open.

  1. 1.Record the termination with its date and time, from payroll or HR, for contractors and unplanned departures as well as planned ones.
  2. 2.Disable the directory account. This blocks new sign-ins and nothing else.
  3. 3.Revoke sessions, using the exact action your platform names: "Revoke sessions" in Microsoft Entra, resetting the user's sign-in cookies in Google Workspace.
  4. 4.Remove the leaver from each departmental app whose accounts have no link to the directory.
  5. 5.Remove each door credential at the controller, not only at the head end, and note the controller's last acknowledged sync.
  6. 6.Collect the laptop and the badge. A collected badge does not remove the door record, and a returned laptop does not end the access it held.
  7. 7.Confirm the device's encryption enrollment and escrowed recovery key. If a remote wipe was sent, record it as issued until the platform confirms it completed.
  8. 8.Sanitize or dispose of the device according to the data classification set when it was issued, and keep the certificate of destruction with its serial numbers.
  9. 9.Write the dates and outcomes into the five records at the end of this article.

A returned device can still hold valid access

Microsoft says that after an administrator disables the user and revokes sessions, the user "can't gain new tokens for any application tied to Microsoft Entra ID". Tokens already issued still work. Access tokens last one hour by default (opens in a new tab), and an application that issues its own session token ends it only when it syncs or is told. Exchange, SharePoint and Teams with continuous access evaluation (opens in a new tab) react within minutes. A departmental tool whose accounts have no link to the directory is not reached at all, and a laptop that is offline keeps whatever data it stored locally.

Revoking sessions is a distinct administrative action. In Microsoft Entra it is "Revoke sessions" on the user's page, or Revoke-MgUserSignInSession in PowerShell; in Google Workspace it is resetting the user's sign-in cookies. Put the exact name for your platform in the checklist, because "disable the account" leaves it out. Two other things can survive:

  • Data synchronized to personal storage, usually found after the fact.
  • Credentials in a browser profile on a device that was not returned.

A collected badge leaves the door record untouched

The card carries a number. What opens the door is a record in an access system saying that number is allowed, and the plastic changing hands doesn't touch it. A card copied before it was collected still works until the record goes.

Payroll records the termination. Facilities or a contractor runs the access platform. The join between them is a person remembering to send a message, which survives planned departures and fails on unplanned ones: a Friday-afternoon dismissal gets processed Monday, if the person who does it is in. Contractor badges, temporary credentials and unreturned visitor cards have no termination event to hang a revocation on.

A second gap sits at the door. A controller with no route to the head end opens doors from a list it already holds, which is what it was bought for. So a removal reaches each controller when it next syncs, and one offline since Tuesday still holds Tuesday's answer. The screen says removed, and the door says yes.

Ask the maintainer two questions. What is the longest delay between a head-end change and the furthest door? And does the system flag a controller that hasn't synced in a week? A twelve-person office with one controlled door can settle for a quarterly look at the credential list. The exposure is real when doors protect a plant floor, a pharmacy cupboard or a server room, when contractors hold credentials, or when an auditor will ask for evidence.

Disk encryption answers one question

Encryption protects a powered-off device in someone else's hands. For the laptop left in a taxi it's close to decisive. It does nothing about a device that left while someone knew the passphrase, or about a session already established.

What carries weight afterward is the escrowed recovery key and enrollment record: proof that this serial number was encrypted, from this date, with the key held centrally. Without it, "the lost device was encrypted" is a claim you can't evidence when a regulator asks. Remote wipe works only if the device comes online, so treat the command as issued, not completed, until the platform confirms it, and record which you have.

Disposal guidance changed on September 26, 2025

NIST SP 800-88 Rev. 1 had been the media sanitization reference for a decade, and Rev. 2 superseded it (opens in a new tab) on that date. Anything still naming Rev. 1 cites a withdrawn document.

The substance matters more than the version. Rev. 2 chooses techniques and controls "based on the sensitivity of their information," so the decision follows what the data was. It also gives more attention to validating that sanitization worked, the step usually skipped, because a wipe that reports success and one that succeeded look identical in a ticket. One standard for every device is too expensive for laptops that held nothing and too weak for the few that held everything. Classify each device when it's issued, while someone still knows what it was for.

A disposal vendor is enough when it returns evidence

A dated certificate of destruction listing serial numbers and the method survives someone else's audit. An assurance that devices are securely wiped is a sentence, and it transfers no obligation: you're still answerable for the data. For a handful of machines a year, a reputable vendor with serialized certificates beats building any capability in-house.

Resale adds a next owner, so the sanitization evidence has to exist before the device leaves.

The five records worth keeping

  1. 1.Which serial number was issued to which person, and when, and the data classification of the device.
  2. 2.The encryption enrollment and escrowed recovery key per device.
  3. 3.Two dates: when the account was disabled, which blocks new sign-ins, and when sessions were revoked, which ends the refresh tokens already issued.
  4. 4.The date each door credential was removed at the controller, not only at the head end.
  5. 5.The disposal outcome per serial number, naming the method and the vendor, with the certificate attached.

Sources

  1. 1.SP 800-88 Rev. 2: Guidelines for Media Sanitization (opens in a new tab), NIST,

Next step

Send us your offboarding checklist.

The checklist as it is actually used, not the policy document. We will mark which steps remove access, which only recover hardware or cards, and which gaps would still be open a week after somebody leaves.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing