Business Continuity Plan for Small Business After the July Outage
A business continuity plan for small business is one page. That’s it. It names your critical tools, a manual fallback for serving clients, who calls whom, and where the offline copy of essentials lives. Below we build that page step by step, so your team knows how to get through a day without laptops or without one key application.
Table of Contents
What the 19 July outage showed small companies
That a company can lose its computers through no fault of its own. According to the CISA alert on the outage, a faulty CrowdStrike content update crashed machines running Windows 10 and later, while Mac and Linux hosts were unaffected. And no, the cause was not malicious activity. The same alert reports Microsoft’s estimate that 8.5 million Windows devices were hit.
Nobody’s to blame here. A small firm can’t prevent a vendor’s failure. But it can decide in advance how it operates when screens stay blue or a single service stops responding.
Which tools can your team not work without?
The critical ones are those whose loss stops you from answering clients, taking orders or getting paid. Everything else? An inconvenience that can wait. Start with an inventory of the usual dependencies:
- CRM
- phone system
- invoicing
- file storage
- password manager
- team chat
For each one, note the owner, what stops when it fails, and whether the failure is a device problem or a cloud service outage. The workaround is not the same: a dead laptop is solved by grabbing another device, an unavailable provider is not. Look for shared single points of failure too - one login provider, one office connection, or (a classic) one person who knows the admin passwords.
The minimum way to keep serving clients when systems are down
The bare minimum: you can reach every active client and you know what was promised to each, without the usual software. An offline fallback for sales and support doesn’t need much. A recent export of key contacts and open deals, a list of open tickets with their owners, and a call list printed or stored on a phone.
Then there are roles. Decide who declares the plan active, who calls which clients, and who logs requests on paper or in a shared note for later entry. EpicCRM is browser-based, so a crashed laptop does not block access from another device, and its data export gives you the contact and deal list for your offline copy.
Agree beforehand which work can wait a day and which can’t. Otherwise people make up priorities on the fly, under pressure. And the loudest request wins over the most urgent one.
Where to keep the offline copy of essentials
In two places that don’t depend on the system that failed - say, a printout and a personal phone, or an encrypted USB drive. The copy should hold:
- client and supplier phone numbers
- private numbers of team members
- open deals and deadlines
- vendor support contacts
- account recovery details, stored safely
Tie the refresh to a routine that already exists, like the weekly sales meeting or month-end invoicing, and name one person responsible. One person, not “the team”. Keep in mind that an export of contacts is personal data, so limit who holds it and protect it with the same care you expect from the security of cloud CRMs. Restoring lost records is a separate subject, and we cover it in our guide to CRM backup and restore.
What to tell clients during an outage
Tell them early. What is affected, how to reach you in the meantime, and when you’ll update them next. Have a short message template ready in advance and pick a channel that will still work: phone, SMS, a personal mailbox agreed beforehand, or a social profile. Promise the time of the next update. Never a fix time you don’t control.
Warn the team about phishing as well, because criminals jump on incidents like this; CISA advised following instructions only from legitimate sources. And don’t ignore the quiet failures. A calendar that stops updating hurts clients just as a crash does, so noticing sync failures early belongs to the same discipline.
A one-page business continuity plan for small business: the checklist
The whole IT outage plan fits on one page. Five entries. Use this continuity checklist as the template:
- Critical tools and their owners.
- The fallback for each of them.
- The call tree - who calls whom.
- Location and refresh date of the offline copy.
- The client message template and the channel for sending it.
Store the page where it survives the failure: printed in the office and saved on each person’s phone. And keep it short enough that a new employee gets it in one reading.
How to test the plan once without disrupting work
One short drill is enough to expose most gaps: the team pretends one tool is unavailable and follows the page. Pick a quiet hour, declare the CRM or email off limits, and ask everyone to find a client’s number and the status of one open deal using only the offline copy.
Write down what was missing or outdated. Fix the page the same day. Then re-run the export so the copy matches current data.
In the end, a business continuity plan for small business is about a prepared day of manual work, not expensive infrastructure. The first step costs nothing: list your critical tools this week.
FAQ
Does a company with five people really need a continuity plan?
Yes. In a small team each person and each tool is a larger share of the operation, so when one application or one colleague is unavailable, there’s nobody to absorb the gap. A single page is enough.
What is the difference between a continuity plan and a backup?
A backup restores data after something has gone wrong. The plan describes how to keep working in the meantime, while systems are still unavailable. You need both - they complement each other, and neither replaces the other.
What should we do first when a cloud service outage hits?
First, confirm that the problem really lies with the provider and not with your own device or connection. Then activate the fallback and send the prepared client message. For news about the fix, rely only on the vendor’s official channels.
