Why your IT person leaving should not panic your business
When your IT person hands in their notice, it's natural to worry. They know your systems, your passwords, your workarounds. But losing IT staff doesn't have to mean your business grinds to a halt. The difference between a manageable transition and a real crisis comes down to preparation and documentation.
The real risk isn't knowledge, it's access
Here's what actually matters: your IT person holds keys. Literally and figuratively. They have passwords to your email, your cloud services, your servers, your financial software, and probably a dozen systems you don't even remember exist. They know which vendor to call when the printer breaks, which settings keep your backups running, and what that weird script does at midnight every night.
The panic comes from thinking that knowledge walks out the door with them. But knowledge can be written down. Access can be transferred. Systems can be documented. These things are friction to do, which is why most businesses skip them until they have to scramble, but they're all fixable before someone leaves.
What's actually dangerous is not knowing what you have. If you don't have a list of your systems, your vendors, and who has access to what, you can't hand it over to anyone. That's the real problem.
The checklist you should have finished already
Before your IT person leaves, you need three things documented:
First, an inventory of everything that runs your business. Your email system. Your file storage. Your accounting software. Your customer database. Your backup system. Your phone system. The WiFi. The servers. The workstations. Just a list. It doesn't need to be fancy. A spreadsheet with the name of the system, what it does, and who the vendor is will do.
Second, passwords and access stored securely. Not on a sticky note under the keyboard. A password manager is not optional at this point. Something like Bitwarden or your cloud provider's native option keeps credentials safe and shareable. Your IT person puts everything in there before they leave, and you (or whoever is taking over) can access it without them staying around to tell you passwords over the phone.
Third, documentation of the setup. This sounds scary, but it's not as big as it sounds. You need answers to things like: How often do backups run? What's the backup tested? Where are your servers? Are they physical machines in a closet or in the cloud? What does the network look like? Who has admin access to what? You don't need a dissertation. Bullet points are fine. A one-page overview per system is plenty.
Your departing IT person should spend a few hours documenting this before they go. If you're asking them to do it as they're leaving, you've already lost. Ask now.
Who takes over matters less than you think
If you have all three things above, the person who takes over doesn't need to be an expert in every system. They need to be able to read the documentation, access the passwords, and know who to call. That could be your new hire. It could be a managed IT provider. It could be the smart person in your office who isn't quite IT but is good at solving problems. With documentation and access, they can handle the day-to-day until something breaks, and then they can work through the ticket with the vendor.
If you don't have those three things, your business is vulnerable whether or not you lose this person. You're gambling that nothing breaks while you figure it out.
Do this before the notice is handed in
The time to prepare is not when someone leaves. It's now. Don't wait. Sit down with your IT person and spend a couple of hours getting the documentation and passwords into one place. It's not glamorous work. It's exactly the kind of thing people skip because the business is running fine. But it's insurance.
If you don't have an IT person yet, start the documentation anyway. If you do, ask them to do it this week. It's cheaper and faster than learning it under pressure.
Losing staff is part of running a business. But losing that person's knowledge doesn't have to be part of it. Write it down, secure it, and you can sleep better knowing the transition will be a headache, not a disaster.