An offboarding process is the agreed sequence of steps a company follows when someone leaves, with a named owner for each step and a date it happens. In a small business that usually means three people: the leaver's manager, whoever handles HR or operations, and whoever runs the company's tools. The process is what stops each of them assuming one of the others did it.
The steps themselves are not complicated. What goes wrong is ownership and timing: the manager thinks IT knows, IT finds out on the last day, and HR finds out the laptop never came back. This post is about who does what, and when. For the step-by-step list itself, see the employee offboarding checklist.
What offboarding covers
Offboarding is everything between "I'm leaving" (or "we're letting you go") and the point where the person has no access, no company property and no loose ends. It falls into five areas, and each has a natural owner.
Paperwork and pay comes first in most people's minds: the resignation or termination letter, final pay, holiday owed, benefits and references. This is HR's territory, often called HR offboarding, and it depends on your country and your contracts.
Work is the second area: open projects, customers, recurring meetings, and anything only the leaver knows how to do.
Access is the third, and the one this blog is mostly about: every account in every tool, admin roles, keys and shared passwords.
Property is the fourth: laptop, phone, security keys, badges, and anything else you bought.
Goodbye is the last: telling the team and, where relevant, customers, plus an exit conversation if you do them.
Offboarding is not the same as termination. Termination is one way a job ends: the employer ends it. Offboarding happens however the job ends, whether that is a resignation, a contract finishing, a retirement or a dismissal. The process is mostly the same; the timing is not, which is why dismissals get their own checklist.
Offboarding is also the last third of a longer cycle. People join, change roles and leave, and the same accounts are touched each time. Our post on the joiners, movers and leavers process shows how one access list serves all three.
Roles: manager, HR or ops, whoever runs IT
In a company of 15 people, these might be three people, two, or one person wearing three hats. Write the names down anyway. The point is that every task has exactly one owner.
| Area | Owner | What they are on the hook for |
|---|---|---|
| Starting the process | HR or ops | Telling the other two the moment a departure is confirmed, with the date |
| Handover plan | Manager | Deciding who takes over each piece of work, file and customer |
| Paperwork and pay | HR or ops | Letters, final pay, benefits, any legal steps |
| Access inventory | IT | Listing every tool, role, token and shared password the person has |
| Ownership transfers | IT, with the manager | Moving admin roles, files and billing contacts to someone staying |
| Access removal on the day | IT | Doing it, at the agreed time |
| Property return | HR or ops | Getting devices back, or arranging the courier for remote staff |
| Announcement | Manager | Telling the team and customers what changes |
| Final check and record | IT | Confirming access is gone everywhere and writing down what was done |
Two rules make this work.
HR or ops starts it, every time. Managers forget to tell IT. HR does not, if starting the offboarding is part of processing a resignation. Make "send the departure notice to IT" a step HR cannot skip.
IT does not decide the handover. The person running your tools can move a Drive folder, but they do not know who should get it. The manager decides, and IT executes. Without that split, files end up with whoever happened to be the admin.
"IT" here means whoever has admin access to your tools. In many small companies that is a founder or the operations lead, not an IT department. That is fine; it still needs to be one named person, with a named backup for when they're on holiday.
The timeline
A resignation usually gives you a notice period. How long depends on the contract and the country, so the timeline below is relative to two dates you will know: the day notice is given and the last working day.
The day notice is given
HR or ops confirms the last day and tells the manager and IT, in writing. That message is the trigger for everything else, so it should go to the same place every time: a shared channel, a ticket, or a calendar invite to the person who runs the tools. On the same day, IT starts the access inventory. Most of the time the whole process takes is spent here.
During the notice period
The manager writes the handover plan. Each project, document set, customer and recurring meeting, and who gets it.
The leaver documents what only they know. More on that below.
IT moves admin roles and ownership of anything critical to someone who is staying. Doing it now, while the leaver can answer questions, is easier than doing it after. Some tools insist on it: Slack won't deactivate a Primary Owner until the role has been transferred.
HR or ops arranges property return, especially for remote staff. A courier booked a week ahead arrives on time; one booked on the last day doesn't. Offboarding employees remotely covers shipping, remote wipes and time zones.
The last working day
IT removes access at an agreed time, usually the end of the day, and it's in the calendar. Devices come back, or a return is booked. The manager announces the change to the team and to customers who need to know.
The day after
IT transfers remaining data (drive, calendar, email routing) and lowers paid seat counts where removal didn't do it automatically.
A week later
IT checks every tool again for the person's name and email, including accounts under personal addresses, and writes down what was removed and when.
About a month later
Decide whether to delete the main account or keep it archived, once you are sure nothing else needs moving. In Google Workspace that choice has billing consequences; Google Workspace offboarding explains suspend, archive and delete.
For a dismissal, compress all of this. The inventory and transfers happen before the conversation, and access goes during it.
Access removal
Access removal is the step with the most risk and the least visibility. A forgotten tool does not complain. The leaver's account just sits there, sometimes holding a paid seat, sometimes holding admin rights.
The process view of it is simple: one owner (IT), one input (the access inventory), one deadline (the agreed time on the last day), one output (a record). The detail of what to remove, in what order, is in the employee offboarding checklist, and the technical side, including API keys and shared credentials, is in the IT offboarding checklist. If you want the vocabulary, removing access across systems is called deprovisioning.
The one thing the process has to guarantee is that IT hears about the departure in time to do the inventory. Everything else follows from that.
Knowledge handover
Access can be removed in an afternoon. Knowledge cannot be recovered once the person is gone. Use the notice period for it.
Ask the leaver to write, in a shared document rather than their own drive, five things. First, the recurring tasks they do, how often, and where the instructions live. Second, the accounts or integrations they set up, and anything connected with their personal credentials, because those break or linger when the account goes. Third, the customers, suppliers and partners they deal with, and the state of each relationship. Fourth, the work in progress: where it is, what is left, and who should finish it. And last, anything they know that is not written down anywhere else.
The manager reads it with them before the last day and asks the obvious questions. A handover document no one has read is a handover document with gaps.
Contractors and people who just stop
The process above assumes someone resigns and a date is known. Contractors break that assumption. Their contract ends, or simply isn't renewed, and nobody sends a departure notice because nobody thinks of it as a departure.
The fix is to give the trigger to a date instead of a person. When you bring a contractor in, record an end date and an internal owner, and put a reminder on the owner's calendar a week before. If the work continues, extend the date. If it doesn't, the offboarding starts on its own. Contractor access management goes further, including what to do about contractors who use their own email addresses in your tools.
At 5 people and at 50
At five people, one person usually holds all three roles. The process still matters, but it shrinks: a calendar reminder on the last day, a list of tools to go through, and a note afterwards saying what was done. The risk is that the one person who knows is also the one leaving.
At 50, the roles are real and separate, and the handoffs between them are where things fall through. You'll have several managers, at least two people with admin rights, and more tools than anyone can name from memory. The written trigger, the owner table and the week-later check stop being nice to have.
Writing it down
The process itself should fit on one page, in a shared document. Put the three owners at the top, by name, with a backup for each. Then write the trigger: who tells whom, and how. Add the timeline above, adapted to your company and notice periods. Link your checklist, and the list of tools with who has access to each. Finish with where the record of each offboarding is kept.
Review it after every departure. If something was missed, add it. The second offboarding should be faster than the first, and the fifth should be routine.
Where SmashSSO fits
SmashSSO covers IT's part of the process: the access inventory, the removal on the day, the check afterwards and the record. It is not SSO and does nothing for paperwork, devices or handovers.
It reads your people from Google Workspace and shows who has an account in each of your tools, with their role, so the inventory exists before anyone resigns. When someone is suspended in Google Workspace, it alerts you and shows where they still have access, which gives IT the trigger even if nobody sent the email. Removals run through each tool's member API where you have added a token, or through an agent in your own Chrome where you are signed in as an admin; that browser has to be open for agent runs, and an agent can fail when a tool changes its screens. Every change is recorded in an audit log. It costs a flat fee from $199 a month, billed annually (pricing).