Business Continuity: Keep Trading When Your IT Fails
Everything works until it doesn't. The mail queue stops moving, the website returns an error, or the machine everything depends on refuses to boot — and the question stops being technical and becomes commercial: how do we keep serving customers today? A written disaster recovery plan is the framework; this is its practical companion, built around the three failures that stop a small business trading, from Wishaw and Lanarkshire to Edinburgh and the Lothians.
The first ten minutes of any outage
Before you change a single setting, establish the shape of the problem. Most wasted hours come from one person fixing the wrong layer while nobody tells the customers.
- How wide is it? One person, one device, one office, or everyone? That single answer usually separates a local fault from a provider outage.
- Test from outside. Check the same service on a phone using mobile data rather than the office Wi-Fi. If it works there, the fault is likely to be your network or that one machine.
- What changed? An update, a renewal, a password change, a new router. A recent change is the first thing to rule out.
- Note the start time and keep a rough log. Providers will ask.
Scenario one: email goes down
Decide quickly whether mail is genuinely down or your access to it is. Try webmail from a phone on mobile data. If webmail works, the problem is your connection, your device or your mail client — annoying, but contained. If webmail is also failing, check your provider's service status page before you ring anybody.
Contact whoever administers your mail platform — for most small businesses that's your IT support rather than the vendor. Treat a flood of bounces, missing messages or unexpected forwarding rules as suspicious rather than routine, and follow the steps for a compromised mailbox. To keep trading, publish another route the same day: divert the phones, post a temporary number, and have staff reply from one agreed mailbox, not personal accounts where replies later vanish.
Scenario two: the website is unreachable
Websites fail in a handful of recognisable ways, and knowing which you're looking at tells you who to ring. A server error points at the hosting or the site's code; a browser security warning at an expired certificate; and "site can't be reached" for everyone at DNS or a domain or hosting renewal that failed quietly, billed to an old card or an ex-employee's inbox.
You'll need two contacts: your hosting provider, and whoever built or maintains the site. Keep both, plus your registrar login, somewhere that doesn't depend on the systems that are down. We build and host business websites, so both roles can sit with one contact. Meanwhile, keep selling — a pinned social post with a phone number stops enquiries evaporating while the site is fixed.
Scenario three: the server or main system fails
This is the one that stops work altogether, and where rushing costs most. Establish first whether you're facing hardware failure, a corrupted system or a security incident, because the right opening move differs sharply. At any sign of ransomware — renamed files, ransom notes, mass encryption — disconnect the affected machines from the network and get help before touching the backups.
For a straightforward failure, only two questions matter: how recent your backups are, and how recently one was tested. A restore is only as good as the last verified copy, which is why a 3-2-1 backup strategy counts for more than the brand of hardware. Know in advance where the business would work from if the premises were unavailable for days.
Keeping the business trading
Continuity is not only recovery. Agree a manual fallback for taking orders and payments, even if it's paper and a phone, and decide who speaks to customers. A short, honest message beats silence, and it keeps enquiries alive while you fix the fault.
What to prepare while everything is working
- An off-system contact sheet. IT support, broadband and phone provider, hosting, domain registrar, bank, insurer — printed or on a phone, not only on the server.
- A register of who owns what. Which account holds the domain, which card pays for hosting, who has administrator rights. Renewals fail quietly.
- Tested restores, not just backups that report success.
- A spare route to work — a mobile hotspot or a loan laptop. For many firms in Livingston and Musselburgh, one broadband line is the real weak point.
Let's pressure-test your plan
We're based in Wishaw and work with businesses across Edinburgh, Linlithgow and the Lothians. Talk to us about business IT support or managed IT services and we'll help you find where you'd actually struggle, with a clear quote before any work.