Someone's last day is Friday. On Monday, a colleague needs to pick up an unfinished quote, find a supplier conversation and get on with work. Meanwhile, the person who left should no longer have company access. A useful employee offboarding IT checklist handles both sides of that handoff. Start with the work and the people involved, then agree on the account changes with IT.
Give the Manager and IT the Same Finish Line
"Please remove access on Friday" leaves several questions open. Friday morning or after the final shift? Who will answer incoming email? Does anyone need files from the laptop before it comes back?
Have the manager agree on a specific cutoff with the person authorized to approve it. Let IT know which work needs to survive the change. Those are separate decisions: ending someone's access doesn't tell the next employee where to find a customer's signed proposal.
For example, a manager could send this request through the company's established support route:
Please end access at [approved time]. [Name] is taking over the open customer work. Before any account is deleted, please confirm the file and mailbox handoff with us. The company laptop is being returned to [person]. Let me know which separate app owners need to take action.
Walk Through a Normal Working Day
Ask what the employee actually used. Begin with their daily work rather than hoping the main email account covers everything. Someone may sign into the scheduling tool separately, use a supplier portal occasionally or have access to a shared inbox through another account.
This is a useful starting list to work through with the manager:
- Email, shared mailboxes and calendars.
- Customer records, shared files and current projects.
- Accounting, scheduling and other separately managed applications.
- Remote access, company devices and physical access credentials.
The list will differ by role. A sales employee and a workshop supervisor won't leave the same systems behind. Put the name of the responsible administrator beside each one so a vague request to "remove everything" becomes work someone can verify.
Keep the Work; Avoid Passing Around the Old Password
Have the replacement employee point to the files and conversations they need. Arrange an approved transfer or delegated access with the administrator. Sharing the departing employee's password makes it harder to keep responsibility clear and can leave the handoff dependent on someone else's recovery details.
Discuss retention and any hold requirements with the appropriate decision-maker before deleting an account or erasing a device. The right order depends on the service and the company's obligations. An account that is blocked from signing in may still need to exist while business records are handled.
Ask for Confirmation, Including the Loose Ends
A support ticket marked "received" tells you the request arrived. Ask for the completed actions and any exceptions. Have IT include active sessions and account-recovery methods in that confirmation, using each service's current process. Separately managed applications need confirmation from their own administrators; they can be missed even when the main sign-in has been handled.
Record returned devices and follow the company's lost-device process for anything missing. If a shared password was known to the departing employee, have its owner change it in the approved vault. Keep credentials out of the handoff email.
The final question for the manager is simple: can the person taking over find the work and continue it? If that answer is still unclear, the handoff has an unfinished task. Write the agreed cutoff and the name of the person taking over at the top of the checklist, where both the manager and IT can find them.
Reference and Next Step
FTC: Cybersecurity for Small Business. Reference checked November 15, 2026. The checklist above is a suggested operating process to adapt to your environment.
Contact NHM Ohio about your checklist.
Drafted with AI assistance.

