Support Login 0800 046 9957

What Should You Do If Your IT Manager Leaves Suddenly

Josh Kirk
  • 23 Mar 2026
  • 6 min read

Introduction

Most SMEs rely heavily on one capable IT person who “looks after everything”. When they leave suddenly, the business often realises how much knowledge, access and day to day continuity was held by a single pair of hands. The good news is that you can stabilise the situation quickly with the right sequence, and you can also use this moment to rethink whether replacing like for like is the best long term path.

The quick answer

Focus first on regaining control of admin access, securing email and identity, and confirming that backups are working. Once the immediate risk is contained, document the essentials, stabilise support and decide whether the organisation should replace the individual or move to a more sustainable hybrid or outsourced model.

Why this moment becomes risky faster than most people realise

Most SMEs don’t operate with a fully documented IT estate. The person who leaves usually carries a huge amount of unwritten knowledge: historic decisions, vendor contacts, “workarounds” that keep old systems running, and where all the admin accounts live.

Even when the departure is friendly, the risk isn’t the individual, the risk is the concentration of access. A business depending on a single point of failure is fragile, and that fragility is invisible until something breaks, we know sometimes this is unavoidable though.

This is why the priority is not hiring someone new on day one, the priority is regaining technical control so the business stays stable while you work out the right long‑term plan.

Your first day: regain control without breaking anything

Most instability after an IT manager leaves comes from two places: missing access and over‑hasty changes. The aim is to move carefully, confirm what you control, and avoid accidentally locking out systems.

Start with the core identity and infrastructure pieces that underpin everything else.
Focus on:

  • Access to Microsoft 365 or Google Workspace admin
  • Control of the domain registrar and DNS
  • Backup system admin logins
  • Firewall and network equipment admin credentials
  • Remote access tools or support portals

Keep the tone calm internally. People will naturally get nervous, especially if they were used to going to a single go‑to person. You don’t need to solve every support issue today. You just need to ensure nothing is exposed.

Once you know you hold the keys to your identity, email and backups, you’ve removed the biggest sources of risk.

The first week: stabilise support and make the environment manageable

With access secured, the next step is to prevent operational disruption. Teams need somewhere to report issues, and there needs to be a way to prioritise what matters.

A simple triage pattern is enough at this stage. Staff need a single place to raise problems and know that urgent issues will be prioritised. Someone should own this queue, even if temporarily.

You’ll also want a quick “minimum viable documentation pack” covering the essentials. This isn’t a full network diagram. It’s simply a brief inventory of:

  • Key systems
  • Where they are hosted
  • Who the vendors are
  • How backups work
  • What the main admin accounts are

This gives you a baseline to work from and stops the knowledge drain from getting worse.

The first month: decide what the long‑term operating model should look like

Once the business is stable, you can decide how IT should be run in the future. You have three realistic paths: hire internally, outsource to an MSP, or use a hybrid model.

Hiring in-house gives you a dedicated person who knows the environment day to day. The challenge is that SMEs often need a mix of skills: cybersecurity, Microsoft 365 configuration, networking, documentation, onboarding, vendor management and general support. Expecting any one individual to excel at all of these permanently is a big ask.

This is where the MSP model can help. It’s similar to how many marketing teams use an agency to supplement skill gaps. A marketing agency has specialists in design, PPC, SEO, branding and web. You wouldn’t hire one person and assume they can do all of that to the same depth. IT is similar, a good MSP brings depth across multiple disciplines and removes the single point of failure.

A hybrid approach can also work well if you already have someone internal who knows the business intimately but doesn’t have the specialist depth or the capacity to cover everything.

The important question isn’t “should we hire or outsource?”. It’s “what gives the business the most resilience and the widest range of expertise, without becoming dependent on one person again?”.

An example scenario that shows how this plays out

A 60‑person professional services firm had a long‑serving IT manager who handled everything from onboarding to firewall updates. When he resigned with short notice, the business discovered that admin credentials were saved in browser profiles rather than documented, backups hadn’t been tested in over a year, and no one else knew who the telecoms provider was.

They stabilised the environment by securing identity, confirming backup access and creating a rapid “IT truth pack”. Once the dust settled, they evaluated whether to replace the individual or switch to an MSP. They realised that the business had outgrown the generalist model. The MSP option gave them cybersecurity expertise, Microsoft 365 governance, network specialists and a helpdesk team, all covered by predictable monthly costs. They still hired internally, but the internal role shifted to coordination and vendor oversight rather than firefighting.

The result was an IT model that could scale with the business instead of being built around a single person.

FAQs

What’s the biggest risk when an IT manager leaves?

The biggest risk is not malicious behaviour. It’s loss of access and loss of continuity. Without admin control of identity, DNS or backups, small issues can quickly turn into outages.

Should we reset every password immediately?

Reset privileged accounts early, but be cautious about mass resets without a plan. Some systems are interconnected and a rushed change can cause disruption.

How urgently do we need to hire someone?

Focus on stabilisation first. Once you understand your environment and risks, you can make a more informed decision about hiring, outsourcing or using a hybrid model.

Is outsourcing more expensive than hiring?

It depends on what you compare it against. A single in‑house person can be cost‑effective for general support, but an MSP brings specialists across multiple areas, which often leads to better resilience and predictable costs. It’s difficult to compare apples to apples here with two very different scenarios so be ensure to look at the complete costs involved with either choice.

What if we’re halfway through projects?

Document the status quickly and then decide whether to pause, finish internally or hand over to an external partner. The priority is understanding the impact before making changes.

Next steps and closing thought

A sudden departure feels unsettling because it exposes how dependent the business had become on a single person. Once you regain access and stabilise the day‑to‑day, treat this as an inflection point. Decide whether repeating the same model is right for the next stage of your growth, or whether a pooled team of specialists would give you more resilience.

The goal isn’t simply to replace what you lost, it’s to put IT on a footing that’s stronger, more predictable and less dependent on any one individual. Taking it a step further, IT shouldn’t be a break-fix reactionary environment, it should be driving your business forward and giving you the resilience you need.

We use third-party cookies to personalise content and analyse site traffic.

Learn more