It’s a Tuesday afternoon, and the person who’s quietly kept your computers running, your email working, and your printer from catching fire for the last three years just handed you a resignation letter.
Maybe it’s your “IT guy,” the one person who wears six hats and IT happens to be one of them. Maybe it’s the office manager who “just kind of became” the tech person because she was good with computers. Either way, your stomach drops a little, because you realize you have no idea what they actually do all day, let alone how to replace them.
This isn’t a story about one employee being irreplaceable. It’s a story about what happens to a business when all of its IT knowledge lives in one person’s head, and what to do about it before you’re staring down a two-week countdown.
Gaps That Start to Show
When that person walks out the door, a few things tend to surface all at once:
Passwords and admin access nobody else has. Server logins, router credentials, the admin account for your accounting software
Vendor relationships with no paper trail. Your internet provider, your line-of-business software support line, your phone system vendor: this person knew who to call and how to get things done. That relationship doesn’t automatically transfer.
Undocumented systems. Why does that one server reboot every Sunday at 2 a.m.?
Backup and disaster recovery knowledge. What is being backed up? Are they running, how do they work, how often do they run, where do the backups live, is it
A hundred small “how do I…” answers that used to take thirty seconds and now take a frantic afternoon of trial and error.
The Real Cost of “We’ll Figure It Out”
Downtime is an obvious risk: something goes wrong and nobody knows how to fix it quickly. Security can become another problem. If a departing employee’s access isn’t fully accounted for, the business can be left with accounts that should have been disabled, shared credentials that were never rotated, or admin access nobody has reviewed. Those are avoidable gaps, but only if someone owns the offboarding checklist.
There’s also hiring pressure. When nobody else can cover the work, it’s easy to feel rushed into a replacement decision because every week without dependable IT coverage feels risky.
How to Protect Your Business Before It Happens
The fix isn’t complicated, but it does take intention:
Document the environment. Not a novel, just a living reference of what systems and software exist, who the vendors are, where business-controlled admin access lives, and how backups and recovery work. This should exist whether or not anyone is planning to leave.
Use a business-managed password manager, not a sticky note or a personal vault only one person can access. Important credentials should be stored so the business can recover them without depending on the person who created them.
Build in redundancy. Even a small operation benefits from more than one person understanding the basics of how things run, or from a partner who already does.
Treat IT offboarding like any other offboarding. When someone with system access leaves, reviewing and removing that access should be a standard checklist item, not an afterthought.
If It’s Already Happening
If you’re reading this because someone just gave notice, start with a list of every system, login, vendor, and recurring task they touch. Make sure the business controls the admin accounts and password vaults. While they’re still available to help, document backup and recovery steps, vendor contacts, and any unusual workarounds. When their access is no longer needed, disable their individual accounts and rotate any shared credentials they knew as part of offboarding. None of this needs to be adversarial. Most departing employees are glad to leave things in good shape if someone simply asks.
Start by capturing business-controlled admin access, vendor contacts, system details, and recurring IT tasks before the employee leaves. Then review and disable access that is no longer needed so someone else can keep the environment running without relying on one person’s memory.
How do I make sure my business isn’t dependent on one IT person?
Keep an up-to-date record of systems, vendors, admin access, backup and recovery steps, and recurring tasks. Make sure at least one other person or outside partner can get to that information when it’s needed.
What is IT documentation and why does it matter?
IT documentation is a written record of your business’s systems, access, vendors, and processes, including how the network is set up, how backups are recovered, and who to call for support. It gives the next person a usable starting point instead of forcing them to rebuild everything from memory.
Should I hire a backup IT person or use a managed IT provider?
It depends on your environment, workload, budget, and how much day-to-day coverage you need. A second employee adds internal capacity; a managed IT provider can add broader coverage, depth of knowledge and strategy without another full-time hire.
How do I offboard an employee who had IT admin access?
Review every system, application, admin account, password vault, and vendor portal they can access. Disable their individual access when it is no longer needed, transfer ownership of business accounts, and rotate any shared credentials they knew.
How much documentation should my IT setup actually have?
At minimum, keep a current list of systems and software, vendor contacts, business-controlled admin access, backup and recovery steps, and the recurring tasks someone else would need to take over. It doesn’t need to be exhaustive. It needs to be useful enough that someone unfamiliar with the environment can step in without starting from scratch.
