It usually starts with a two week notice and a friendly conversation. The one person who handles all of the technology is moving on. Better offer, family relocation, tired of being on call. Somebody orders a cake. Then, three weeks after the last day, a vendor calls about a renewal nobody knew existed, an alert fires that nobody can silence, and a system needs a password that lived in exactly one head.
We get called into this more than any other situation, and it is the most preventable one on the list. Nobody did anything wrong. A capable person built a working environment over several years, and the company let that knowledge live in one place because it never caused a problem. The fix is not expensive and does not require replacing anybody. It takes a few weeks of deliberate effort at the right moment, plus one structural change afterward.
Why One Person Becomes a Single Point of Failure
This is not a hiring mistake. It is how small businesses grow. You hire one technical person because you need one. They are good, so they take on more. They set up the phone system, so they own it. They know the vendor rep, so they handle the contract. Every reasonable decision concentrates a little more into one person, and because everything works, nobody notices.
The concentration runs deeper than the org chart shows. Administrative accounts get created in that person’s name. Sign in codes route to their phone. Vendors save their cell number and will only speak to them. The Federal Trade Commission’s Start with Security guide for businesses states the principle plainly: “Administrative access, which lets a user make system-wide changes to your system, should be limited to the employees tasked with that job.” The trap is limiting it down to one, which is where a lot of small businesses land without meaning to.
The Questions You Cannot Answer Once They Are Gone
Read these out loud. How many could you answer today without calling one specific person?
- Where does the backup go, and when was it last restored? Not whether a backup runs. Whether anyone has ever pulled a file back out of it, and how.
- Who actually owns each account? Domain registration, email, hosting, accounting software, the payment processor. Not who uses it. Who can reset it.
- Which vendors are we paying, on what terms, renewing when? Especially the small ones, because those are charged to a card nobody reviews.
- What happens if the internet goes down at the main office? Is there a second path, who calls the provider, what account number will they ask for.
- Why is that thing set up that way? The workaround for the machine stuck on an old version. The task that runs before the reports. These never get documented because they were meant to be temporary.
If you cannot answer four of those five, you are not in trouble. You are where most businesses your size are. But you are one resignation away from a hard month.
What to Gather While They Are Still There
The two weeks after notice is given are worth more than the six months before. Use them for capture, not for rushing a replacement hire.
- Credentials, moved rather than copied. Get every administrative account into a password manager the company controls, then verify each one by signing in yourself while the departing person can still help. A credential you have not tested is a credential you do not have. Avoid the pattern the FTC’s guide flags in one case example, where administrative passwords sat in plain text in a personal email account.
- Multifactor sign in, rerouted. If verification codes go to a personal phone, those accounts leave when the phone does. Move them to a company controlled method before the last day.
- Vendor contacts and account numbers. For every provider: company, what they do, account number, support number, rep, renewal date, notice period. One page.
- The written record of how things work. Backups, network layout, how a new employee gets set up and removed, what to do when the main system is down. A rough document that exists beats a polished one that does not.
- The undocumented workarounds. Ask directly: what do you do that nobody else knows about, and what breaks if you stop. Ask more than once. The answers surface slowly, usually in the last few days.
Do a Handover, Not an Exit Interview
An exit interview asks how someone felt about working there. A handover transfers capability. Different meetings, and the second keeps your business running.
Structure it as short working sessions rather than one long download. Have someone else drive the keyboard while the departing person talks, because whoever is clicking is the one actually learning. Spread them across the notice period so questions surface. Treat the last three days as verification: log into everything on the list, run the restore once, call one vendor and confirm the new contact is on file.
On the security side, sequence matters. The CISA Cyber Essentials Starter Kit, published by the Cybersecurity and Infrastructure Security Agency in 2021, advises organizations to “develop IT policies and procedures addressing changes in user status (transfers, termination, etc.)” and to “identify and deactivate unused accounts.” The NIST Cybersecurity Framework 2.0 Small Business Quick Start Guide, published by the National Institute of Standards and Technology in 2024, asks it more simply: “Are we removing access when they no longer need it?” Removal comes after transfer and verification, on a planned date, with a checklist. Not in a panic, and not six months later.
The Two-Person Rule Going Forward
Then make one structural change: nothing critical has exactly one human attached to it. Not two full time technical staff, which most small businesses cannot justify. Just two paths to every capability.
- Two people can reach every administrative account. Through a shared password manager with a documented emergency access process, not sticky notes.
- Two names are on every vendor account. Add an owner or office manager as an authorized contact. One call per vendor removes a whole category of problem.
- Two people know where the documentation lives. A document nobody can find does not exist.
- Two people have watched the restore work. Backups are where assumptions do the most damage, so make the test a scheduled event.
This is also the honest case for co-managed support, where an outside partner works alongside your internal person rather than replacing them. Your employee keeps the relationships and the context. The partner holds the documentation, carries a second set of credentials, and covers vacations. A resignation becomes a transition, not an emergency, because half the knowledge already lives outside the person leaving. We laid out how to evaluate that in why more businesses are outsourcing IT and what to look for in a partner. The value here is mostly recovered time rather than saved dollars, a distinction we drew in why saving time takes priority over saving money.
The Bottom Line
The departure of a single technical employee should be an inconvenience, not a crisis. The difference is decided long before anyone gives notice, by whether credentials, contracts, and context live in the company or in a person. If someone excellent handles your technology today, the kindest thing you can do is make sure the business could survive their absence. Good people appreciate that. It means their vacation is actually a vacation.
If you are in the middle of this, or you can see it coming, we can help capture what matters before the last day and put a two-person structure in place afterward. We work alongside internal staff all over Denton County, and we are happy to be the second set of hands or the whole department. Contact us today.
Sources:
Comments are closed