What Happens When Your IT Person Is on Holiday?
Most small businesses have one person who quietly holds the whole IT setup together. Sometimes it is a dedicated IT hire. More often it is whoever turned out to be good with computers, and ended up owning everything from password resets to the server in the cupboard. It works, right up until that person is unreachable.
The Risk Nobody Budgets For
This is sometimes called key person risk, and IT is one of the places it shows up hardest, because so much of it lives in one person’s head rather than anywhere written down. Admin passwords. Which supplier to call for which system. Why a particular workaround exists and what happens if you undo it.
None of that is a problem on a normal Tuesday. It becomes a very expensive problem on the day something breaks while that person is on a plane, in hospital, or has simply moved on to a different job with two weeks notice.
Why This Happens Even in Well-Run Businesses
It is not usually a mistake, exactly. It happens gradually. One person picks up the first IT task because they were available and capable. They pick up the next one for the same reason. Eighteen months later, they are the only person who fully understands how anything fits together, and nobody made that decision on purpose.
Documentation always feels like the thing to do later, once things calm down. Things rarely calm down. The knowledge stays in one head because writing it down never quite made it to the top of anyone’s list.
What It Actually Costs When It Goes Wrong
When the one person who understands the setup is unreachable and something breaks, the cost is not just the technical problem. It is the time spent trying to reconstruct what that person would have known instantly. Password resets that need identity verification nobody else can provide. A supplier call that starts with "sorry, who are you and what account is this?" A fix that gets delayed for days simply because nobody else knew where to start.
For a business that depends on its systems working every day, that delay is not a minor inconvenience. It is lost billable time, missed deadlines, and in some cases, a security gap that nobody was watching while the one person who usually watches it was unavailable.
What Actually Reduces This Risk
None of the fixes here are complicated. They are just easy to keep putting off.
A password manager with shared, controlled access. Nobody should need to know an individual’s personal memory to get into a business-critical system.
A simple, current written record of what exists. What systems the business runs, who supplies them, and roughly how they fit together. It does not need to be sophisticated. It needs to exist and be kept up to date.
More than one person with visibility. Not necessarily equal expertise, but enough access and context that a single absence does not mean a total blackout.
A managed IT partner as the backstop. Even businesses with a strong in-house person benefit from a second line that already knows the environment, rather than starting from zero if that person is ever unavailable.
The Question Worth Asking This Week
If the person who understands your IT best did not answer their phone tomorrow, how long before that actually became a visible problem?
For most small businesses, the honest answer is sooner than they would like. The fix is not complicated. It just needs to happen before the holiday is booked, not during it.
Find Out Where Your Practice Stands
Answer a few quick questions in our free Business IT Health Check and find out exactly where your business stands, along with practical tips on what to tackle first. It takes less than 5 minutes, it is written in plain English, and there is no hard sell at the end.
