Last Day, Last Login: The Digital Loose Ends a Departing Employee Leaves Behind
The last day usually goes fine on the human side. There's a card, maybe a lunch, a round of handshakes. Then the laptop goes into a drawer and everyone moves on.
The digital side rarely closes as cleanly. Access gets left on because nobody's sure who owns the account. A shared password stays in a spreadsheet. The departing employee's email keeps forwarding to a manager "temporarily," which is now month seven. None of this is malicious — it's just that offboarding is a task with no natural owner in a small company, so it happens in fragments or not at all.
The checklist below is built for teams without an IT department. It assumes the person leaving is trusted, the exit is amicable, and you'd still rather not find out in eighteen months that their old login is the reason a vendor account got compromised.
Start Two Weeks Out, Not Two Hours Before
Most of this work can't happen on the last afternoon, because you need the person's cooperation to hand things over properly. Book thirty minutes with them about two weeks before the end date and walk through what they own: which tools they administer, which shared logins they know, which clients they hold the relationship with inside an app.
People are usually helpful at this stage. They're still employed, still collegial, and it's a lot easier to get a clean handover now than to email them in three months asking for a password.
Build the Account Inventory
Pull together every tool the person touches. The obvious ones you'll remember; the rest you'll find by asking two questions: "What do you log into every week?" and "What do you log into every quarter but would break something if it went dark?"
That second question is where the surprises live — the state filing portal, the domain registrar, the payroll back end, the shipping account.
Once you have the list, sort each item into one of three buckets:
- Transfer — someone else takes over the same account (admin roles, shared mailboxes, vendor portals).
- Remove — the person shouldn't have access anymore and nobody needs to inherit it.
- Delete — the account exists only for them and has no organizational purpose.
Anything stuck in "we'll figure it out later" is the item that becomes a problem.
Shared Passwords Are the Real Exposure
If your team keeps logins in a spreadsheet, a shared note, or a group text, assume the departing employee has a copy of all of them. That's not an accusation — that's just how shared credentials work.
The fix is straightforward: change the passwords on anything sensitive that they could have seen, and move the whole collection into a password manager with individual logins and a shared vault. This is a good week to do it, because the alternative is remembering to do it after someone's already gone.
While you're in there, check for logins tied to the person's work email address. Those become orphaned the moment the mailbox closes, and password resets go nowhere.
Email: Forward, Don't Keep a Live Mailbox
A common shortcut is leaving the old mailbox active for months so nothing gets missed. It works, but it also means an active login with an active password sitting around.
The cleaner version: set up forwarding from the old address to a named person for a defined window — sixty or ninety days is reasonable — set an auto-reply telling senders the new contact, and then convert the mailbox to a shared one or archive it. Put an end date on the forwarding in your calendar so it actually gets removed.
That way, clients don't bounce, but the account isn't a permanent open door.
Devices: Wipe, Don't Stack
Any company laptop or phone should come back and get wiped before it's reassigned, sold, or donated. If the device is enrolled in a management tool, you can often trigger the wipe remotely — which matters most in the case where a device never comes back at all.
If they're keeping the device as part of the exit, get it in writing that company data will be removed, and follow up. Backups from that device should also stop, or you'll keep ingesting their personal files into your storage indefinitely.
Files Need an Owner, Not a Folder
When someone leaves, their documents tend to sit in a personal drive or a folder only they used. Nobody deletes it because nobody's sure what's in it, and it slowly becomes digital sediment.
Assign a specific person to review their file storage within two weeks. Most of it can be archived; a small portion needs to move into a shared location where the team can find it. The point isn't tidiness — it's making sure the client history, the process notes, and the templates don't disappear into an account that gets deactivated next quarter.
The 48-Hour Check
Two days after the last day, sit down and do the boring verification pass:
- Try logging in as the former employee to one or two key tools. You should be blocked.
- Confirm the email forwarding works and lands in the right inbox.
- Check that any shared calendar or distribution list still routes correctly.
- Verify their name is out of the vendor contact records where it matters.
- Look at the phone bill or SaaS billing for anything that was in their name.
That last one catches a surprising number of subscriptions that were quietly paid on a personal card and will expire without warning.
Keep the Checklist Where It Gets Found
Write the whole thing down — one page, in the shared drive, with the steps in order and a blank line for the date and the person who did each one. A checklist that lives in someone's head is not a checklist; it's a habit, and habits leave when people do.
A departing employee isn't a security incident. But the loose ends they leave behind are exactly the kind of thing nobody notices until a vendor asks why there's a login from a city you don't operate in. Thirty minutes of closing the doors is a cheap trade.