Offboarding employees remotely is the usual offboarding with three things made harder: the laptop is in their home, not your office; their last working hour may fall in your night; and you cannot walk over and see what is still signed in. Treat the equipment return and the access removal as two separate jobs, each with a date and time agreed in writing, in the employee's time zone.
The general steps are in the employee offboarding checklist. This post covers only what changes when the person is remote, and ends with a checklist for that case, written out step by step.
What changes when they are remote
In an office, a lot of offboarding happens by accident. The laptop goes back on the desk. Someone notices the badge. The last-day conversation happens face to face, at a time everyone is awake.
Remotely, every one of those needs a plan. Hardware is somewhere else, often in another city or country, and has to be shipped back by the person who is leaving. You depend more on remote controls: if the laptop is not in device management, you cannot lock or wipe it from where you are. Time zones split the day, so "end of their last day" might be early morning for whoever removes access.
The work itself also looks different. Remote workers rarely touch an on-site server; their whole job is in browser tools, so the tool list is the job. And home setups blur lines: company accounts on personal phones, a VPN profile on a home computer, a password saved in a personal browser.
None of this makes remote offboarding harder in principle. It makes it less forgiving of the things an office used to catch for you.
The last conversation, over video
The leaving conversation sets up everything after it, so plan it like a meeting with an agenda. Confirm the last day and the exact time access ends. Confirm the return of equipment, with the shipping arrangements. Agree what gets handed over, to whom, and by when. And give them a single person to contact with questions after they leave, so they are not messaging former colleagues on accounts you are about to close.
Write it all down and send it to them the same day. A remote leaver who has the plan in writing can follow it. One who only heard it on a call will remember half.
Equipment return
Start the return conversation as soon as the leaving date is known, not on the last day.
Make returning easy. Send a prepaid shipping label or arrange a courier pickup, with packing material if they do not have the original box. Give a clear list of what comes back (laptop, charger, any monitor, phone, security keys) and a date. Ask for a tracking number.
Back up before anything ships. Make sure their work is in shared storage before the laptop leaves their hands. A laptop lost in transit should cost you a laptop, not a quarter's work.
Ask them to sign out of personal accounts. Especially on Macs. Apple says Activation Lock is turned on whenever Find My is on, on Macs with Apple silicon or the T2 security chip, and that the Apple Account password or device passcode is then needed to erase or reactivate the Mac (Apple's Activation Lock help). If they ship it with their personal Apple Account signed in, you may receive a laptop you cannot reuse. Ask them to turn off Find My and sign out before packing it.
Decide what is not worth chasing. A keyboard or a cheap headset may cost more to ship than to replace. Say so up front, so the conversation is about the laptop.
If you want to hold back pay or charge for unreturned equipment, check local law and your contract first. That varies by country and state, and is a question for a lawyer, not a blog.
Remote wipe, with the MDM you already have
Mobile device management (MDM) is software that lets you lock, configure and wipe company devices remotely. Use the one you have; this is not the week to buy one. What it can do depends on how each device was enrolled.
If you use Google Workspace's built-in device management, Google's help page on wiping devices draws clear lines (Google's wipe help). "Wipe account", meant for a personal device when the user is leaving, removes the work account; it needs basic or advanced mobile management on phones, or Drive for desktop on computers. "Wipe device" needs advanced mobile management on phones, and Windows device management enrollment on Windows 10 or 11. Macs are covered only by a Drive for desktop account wipe, and Google warns that files with unsynced edits may remain. In every case, the wipe runs at the next sync, so a device that stays offline will not be wiped until it reconnects.
If a laptop was never enrolled, you cannot wipe it remotely. The practical fallback is to make sure every account on it is closed, so the data it holds stops updating, and to wipe it yourself when it arrives.
Timing across time zones
Agree the exact time access ends, in their time zone, and write it down. For a resignation, that is usually the end of their last working day. Then work backwards: who removes access at that moment, and are they awake?
If their end of day falls in your working hours, do it at that moment, and put it in your calendar. If it falls in your night, do the removal first thing in your morning, and tell the leaver in advance. A short gap you planned is fine; one you forgot is not. Have them finish their handover before they sign off, not after.
For a dismissal, hold the call at the start of their working day and remove access while it is happening. The employee termination checklist covers the order.
Also hand over anything time-zone bound: on-call rotations, customer meetings in their region, and scheduled posts or reports that run under their account. These are easy to miss because they work fine until the account is closed, and then fail quietly at 4 a.m. your time.
Access removal
The removal itself is the same list as for anyone else; the IT offboarding checklist has it in order. Remote work adds a few things.
Company accounts on personal phones. Remove the work account from their phone using your device management, rather than asking them to do it.
VPN and Wi-Fi certificates. If you issued a VPN profile or certificate, revoke it on your side; you cannot rely on them deleting it.
Their home network. Unless you supplied the router, it is theirs. Your job is to make sure nothing on it can reach your systems, and revoked VPN access plus closed accounts do that.
Shared passwords used remotely. Remote teams tend to share more logins over chat. Rotate every one they knew, including the two-factor setup if it lived on their phone. Revoking access covers sessions and tokens in more detail, and shared accounts covers how to stop depending on them.
Google Workspace itself. Suspend, transfer and forward as usual; Google Workspace offboarding has the steps.
Remote contractors and people who never had a laptop
Some remote leavers have no company hardware at all: contractors, part-timers, people who worked on their own machine by agreement. For them, the equipment half disappears and the access half gets more important, because every account lives on a device you will never see. Close the accounts, revoke the keys, and wipe the work account from their devices through your device management if they were enrolled. Contractor access management covers the contractor case, including people who used their own email in your tools.
At 5 people and at 50
At five people, the founder usually does the whole thing, and the main risk is the laptop: there is often no device management at all, so getting the machine back and wiping it is the only control you have. Start the shipping conversation early.
At fifty, with people spread across several time zones, the main risk is coordination. HR, the manager, whoever owns IT and whoever ships equipment are often four different people in two time zones. Write down who does which step, and when, in the leaver's time. The offboarding process post covers how to split those jobs.
The checklist
As soon as the leaving date is known, agree the leaving date and the exact time access ends, in their time zone. Name who removes access at that moment, and check they will be awake. Send a shipping label or book a pickup, with a list of items and a return date. And make sure their work is in shared storage.
Before the last day, hand over on-call, regional meetings and anything scheduled under their account. Ask them to turn off Find My and sign out of personal accounts on company devices.
At the agreed time, suspend their main account and end their sessions, then remove them from every other tool. Wipe the work account from personal devices and revoke VPN profiles and certificates. Rotate the shared passwords and two-factor setups they had.
Afterwards, track the shipment, and wipe and check the laptop when it arrives. Wipe remotely any company device that is not coming back. A week later, check each tool's member list for their name and email.
Where SmashSSO fits
SmashSSO is useful here because nothing about it needs the leaver or the hardware. It reads your people from Google Workspace, and when someone is suspended there it alerts you and shows every tool where they still have an account. You remove them from one place: through a tool's member API where you have added a token, otherwise through an agent working in your own Chrome, in tabs where you are signed in as an admin.
Two limits matter more across time zones. The agent works in your browser, so Chrome has to be open on your machine when the removals run: if access ends at 6 p.m. their time and that is 3 a.m. yours, plan to run it when you are up. And agent runs can fail when a tool redesigns its screens; a failed run says so and shows its last screenshot, so check the results rather than assuming. Some tools' terms restrict automated use. It does nothing for laptops, shipping or device wipes; that stays with your device management. It costs a flat fee from $199 a month, billed annually (pricing), and how it works shows the flow.