Employee Offboarding: 24-Hour Access Revocation Checklist
Use this 24-hour checklist to transfer work data, revoke sessions and account permissions, recover devices, and document each offboarding step without disrupting approvals or losing business records.
When an employee leaves, changing the email password is not enough, because access may still exist in active sessions, management software, shared links, and devices in use. If the account is locked without handing over the data first, the business can easily lose track of the work or interrupt approval steps that are still running. The checklist below helps HR, the direct manager, and the IT owner coordinate access revocation within 24 hours, while recording each action taken and the person who carried it out.
Before the last working day: hand over the data first
As soon as the departure date is confirmed, the direct manager should work with the employee to list the tasks, data, and access they hold. This should be completed before the account is locked so that the receiving colleague can still review the content, ask questions, and deal with files stored in the wrong place.
- Work in progress: state the status, the person taking over, the deadline for handling it, and where the related documents are kept.
- Files and folders: transfer ownership to the individual or unit taking over, not just send a sharing link. Check files stored on personal machines that the company manages as well.
- Mailbox: identify work email that must be kept, who is authorized to handle it, and how new mail will be received. Do not forward the entire mailbox to a personal account.
- Approval flows: transfer pending requests, delegation rights, and administrative roles to the new owner.
- Shared login details: move recovery keys, configuration codes, or administrative information belonging to the business into controlled storage. Do not write passwords directly into the minutes.
Checklist of items to lock or revoke
Work through each system separately rather than marking a single “account locked” box and moving on. For each item, record the account identifier, the action taken, and the person responsible for checking it.
- Email and identity accounts: disable sign-in, revoke active sessions, block applications, app passwords, and access codes. Check mail forwarding, delegation rights, recovery phone numbers, backup emails, and multi-factor authentication devices. Do not delete the mailbox yet if internal rules require the data to be retained.
- Management software and other applications: disable the user, remove roles and permission groups, revoke API keys or integration codes tied to the individual. Transfer administrative rights and pending approvals before closing the account.
- Chat groups: remove the person from internal groups and from groups with customers or partners; transfer group administration where applicable. Keep the history of work discussions according to the retention policy, and do not delete conversations just to close out the paperwork.
- Shared drives: revoke direct permissions, group-based permissions, and sharing links the employee created. Check third-party applications, synchronization utilities, and devices already signed in so that data is not still being downloaded.
- Devices and infrastructure: collect laptops, phones, security keys, and accompanying assets; lock them through the device management system if needed. Disable VPN access, access certificates, local accounts, and machine administrator rights. Only wipe devices remotely when a process permits it and the plan for preserving work data has been settled.
The order of work within 24 hours
One coordinator should track the entire checklist, so that no department assumes another has already handled the item. The sequence below prioritizes shared entry points first, then reviews individual systems.
- When the departure date is confirmed: finalize the list of accounts, devices, data to hand over, and who receives each part.
- At the effective time: lock the central identity account first, revoke sign-in sessions, and remove recovery methods the employee controls.
- Immediately after: handle applications that do not use central sign-in, chat groups, shared drives, VPN, and devices. Change shared secrets the employee knew, but do not write the new values into the checklist.
- Before the 24 hours end: compare the staff list with accounts still active, review administrative logs, and confirm that the receiving colleagues can open the data they need.
Handover minutes must show who did which step
The minutes should be a shared record, held in an internal request ticket or an access-controlled document. Each row needs the system, the account identifier, the action, the person who performed it, the time, and the person who checked it. Where possible, attach the ticket number or a log reference instead of screenshots that contain sensitive data.
- The data section records the final storage location, the new owner, and unfinished work.
- The device section records asset tags, handover condition, and administrative actions already performed.
- The exceptions section records why something could not be locked yet, which temporary access remains, who approved it, and when it must be reviewed again.
HR confirms the departure date, the direct manager confirms the handover content, and the IT owner confirms the technical actions. Do not put passwords, OTP codes, or private keys into the minutes.
What to do now
If the current process still depends on chat messages, standardize it with the three steps below.
- Create one shared checklist template for HR, the direct manager, and IT.
- Review all administrative accounts, sharing links, and current data ownership.
- Pick the most recent departure to run the process as a test and add the missing points.
Revoking access is only complete when the data has a new owner, every entry point has been checked, and every action can be traced. VASCOM can help businesses standardize the checklist, review permissions, and build a confirmation flow that fits current working practices.