When Someone Leaves: The IT Offboarding Process Most Small Businesses Skip

Someone hands in their notice on a Friday. The following week their laptop comes back, the goodbyes are said, and everyone moves on. Three months later, you are still paying for their software licence. Their email account is still live. And the files they were working on sit in a personal Dropbox that nobody can reach. None of it looked like a problem at the time. That gap is exactly what a proper IT offboarding process is built to close.

This is a practical look at what a good IT offboarding process actually does, why the reactive version keeps costing small businesses the same money and the same risk, and how to build one that runs the same way every time.

The problem with treating every leaver as a one-off

Most small businesses handle leavers by memory, not by method. Someone remembers to cancel the email. Someone else assumes the licence was dealt with. The laptop gets wiped, or it doesn’t. Because each departure is treated as a fresh scramble, the same things get missed every time — and the cost stays invisible until it isn’t.

This is the short-term trap in miniature. React to each leaver, patch over whatever surfaces, and move on. The underlying gap never gets fixed, so it reopens with the next person who walks out the door. The fix is not to try harder next time. It is to stop relying on memory altogether.

What a good IT offboarding process actually covers

A good IT offboarding process is not a favour someone does when they remember. It is written down, owned by someone, and identical every time. At a minimum, it covers five things:

• Access — every account and system the person could log into, closed on the day they leave, not the day someone remembers.
• Licences — their Microsoft 365 or Google Workspace seat reclaimed, so you stop paying for someone who has gone.
• Data — their files, mailboxes and anything held on personal devices identified and moved somewhere the business still controls.
• Equipment — laptop, phone and access cards returned, logged and reset.
• Knowledge — whatever only they knew, captured before the last day rather than reconstructed after it.

Written down like that, none of it is clever. That is rather the point. Good IT is mostly the dull things getting done, every time, without anyone having to remember.

Why the account nobody closed is the expensive one

The licence you keep paying for is annoying. The account you forget to close is worse. A live login for someone who has left is a door left open — not because they are malicious, but because it sits outside anyone’s attention. Closing it promptly is basic hygiene, and it reduces the risk of an old account being used long after it should have gone.

You do not fix that by being more vigilant. Vigilance fades the moment things get busy. You fix it with a process that closes access as a matter of course, on a schedule, so it does not depend on anyone being on the ball that week.

The part everyone forgets: knowledge

There is one strand of offboarding that no licence report will ever flag. It is the person who was the only one who knew how the booking system was set up, or where the backups actually run, or which supplier to call when the tills go down. When they leave, that understanding leaves with them.

A good process captures it before their last day, not after. Reconstructing it later is slow, expensive, and sometimes impossible. Enterprises learned this the hard way and built documentation into how they work. Smaller businesses can do the same, at a fraction of the scale, and it pays for itself the first time someone leaves without warning.

Enterprise discipline, at small-business scale

I spent years running IT in hospitality, across more than fifty restaurant sites, where people join and leave constantly. At that scale you cannot offboard by memory — you need a process that runs itself, or things fall through the cracks every single week. The discipline that keeps a fifty-site operation clean is the same discipline a twenty-person business needs. The stakes are smaller; the principle is identical.

That is what Net Tech IT brings to smaller organisations across Sussex, Surrey and London: enterprise-grade process, sized for a business that does not have an IT department. Build the leaver process once, document it, and every departure after that is handled the same way — quietly, completely, and without a scramble.

If you want to go deeper on the security side of account management, the National Cyber Security Centre’s Small Business Guide is a useful, vendor-neutral place to start.

The short version

Offboarding is not an event you react to. It is a process you build once and run every time — problems engineered out, not patched over. Handle it by memory and you will keep paying for people who left, leaving doors open you meant to close, and losing knowledge you did not know you relied on.

If your business handles leavers by memory and you would like a straight look at where the gaps are, that is exactly the kind of thing good managed IT support sorts out once, so it stays sorted. Get in touch whenever it suits.

— Pat | Net Tech IT, Horsham

Posted On: 28 July 2026