IT Solutions

Business continuity plan for SMBs: how to keep operating when things go wrong

March 24, 2026 · 7 min read

Business continuity plan for SMBs: how to keep operating when things go wrong

A business continuity plan explains how your company keeps serving customers when something goes wrong: a ransomware attack, a long power outage, a flooded office, a key supplier that stops delivering or a key employee who is suddenly away. It covers people, processes, suppliers and communication, not just computers. Your IT recovery steps belong in a separate disaster recovery plan that the continuity plan points to.

This guide shows small and mid-sized businesses how to build a continuity plan that fits on a few pages, gets used and stays current. It ends with a 10-point checklist you can work through with your team.

Business continuity plan vs disaster recovery plan

The two are often confused, but they answer different questions.

  • The business continuity plan asks: how do we keep operating while something is broken? It covers who does what, how orders still get taken, how payroll still runs, and what you tell clients.
  • The disaster recovery plan asks: how do we bring our systems and data back, in what order and how fast? It deals with servers, cloud services, backups and recovery targets.

Think of the continuity plan as the umbrella and the disaster recovery plan as one of the documents under it. If you need the IT side, our disaster recovery plan template for Montreal SMBs walks through recovery time and recovery point objectives step by step. This article stays on the business side.

Start with a business impact analysis

A business impact analysis sounds heavy, but for an SMB it is usually a two-hour meeting with the people who run each part of the company. For every activity, ask three questions:

  1. What happens if this stops? Lost sales, missed deadlines, penalties, unhappy clients, safety or legal issues.
  2. How long can it stop before the damage becomes serious? A few hours, a day, a week?
  3. What does it depend on? People, software, equipment, a supplier, a building, internet access.

Write the answers in a simple table. Rank activities by how quickly an interruption hurts. The top of that list is where your plan, and your budget, should focus first. The time limits you set here also become the input for the IT recovery targets in your disaster recovery plan.

Critical functions and the people behind them

Most SMBs discover that only a handful of functions are truly urgent: taking and fulfilling orders, answering clients, invoicing and collecting payment, paying employees, and meeting regulatory deadlines. For each one, name an owner and a backup.

People are often the weakest link. If only one person knows how to run payroll, approve a supplier payment or reset the main admin account, that knowledge is a single point of failure. A few practical habits help:

  • Document the key steps of each critical task in plain language, stored where the backup person can reach it even if the office is closed.
  • Cross-train at least one other person on every critical task, and have them actually do it once or twice a year.
  • Keep an up-to-date contact list for employees, managers and key partners, with personal phone numbers, available offline.
  • Decide in advance who can make decisions and spend money during a crisis if the owner is unreachable.

Suppliers and outside partners

Your continuity depends on companies you do not control: your internet provider, software vendors, your accountant, your bank, your logistics partners and your raw-material suppliers. For each critical supplier, note:

  • What you would do if they stopped delivering for a day, a week or for good.
  • Whether an alternative supplier exists, and whether you have already opened an account with them.
  • Their own continuity commitments, especially for cloud software and IT services. Ask how they handle outages and what their contract promises.
  • Emergency contacts that go beyond a general support address.

Avoiding total dependence on a single supplier for anything critical is one of the cheapest forms of resilience available to a small business.

A communication plan for employees, clients and partners

During an incident, silence creates more damage than the incident itself. Prepare the communication side before you need it:

  • Channels that do not depend on your own systems. If your email is down, how do you reach staff? A text-message group or a phone tree kept on paper and on personal phones works.
  • Message templates. Short, pre-approved messages for employees, clients and suppliers save precious time and avoid improvised promises.
  • A single spokesperson. One person speaks for the company so clients and partners get consistent information.
  • Legal obligations. If personal information may have been exposed, Québec's Law 25 requires you to assess the incident, keep a register and, when there is a risk of serious injury, notify the Commission d'accès à l'information and the people affected. Have your privacy officer's role written into the plan.

Workarounds: how you keep working while something is down

A workaround is a temporary, slower way to keep a critical function going. It is the heart of a continuity plan and the part most often skipped. Examples:

  • Staff work from home or from another site if the office is unavailable, which assumes laptops, secure remote access and multifactor authentication are already in place.
  • Orders are taken by phone and logged in a shared spreadsheet or on paper forms if the order system is down, then entered once it returns.
  • A printed list of client contacts and open orders, refreshed regularly and stored securely, lets the team keep calling clients.
  • Phones are forwarded to mobile devices if the office lines fail.

Write each workaround down, including who switches to it, how, and how you catch up afterwards. Workarounds are what buy time while the IT team restores systems. That restoration only works if your data is safe; our 3-2-1 backup and restore-test guide covers that part.

Testing and updating the plan

A plan nobody has rehearsed will not hold up under pressure. You do not need a full-scale drill to start:

  • Tabletop exercise, once or twice a year. Gather the key people for an hour, describe a scenario ("our email and files are encrypted on Monday at 8 a.m.") and walk through the plan. Note every gap.
  • Small live tests. Have the backup person run payroll, forward the phones or work a full day remotely.
  • Reviews after every change. New software, a new supplier, a move or a key departure should trigger an update.

Keep the plan short, date every version and store copies where you can reach them without your normal systems.

A 10-point business continuity checklist for SMBs

  1. Run a short business impact analysis and rank your critical functions.
  2. Name an owner and a backup for every critical function, and cross-train them.
  3. Document key procedures in plain language and store them where they stay accessible during an outage.
  4. Keep an offline contact list for employees, clients, suppliers, your insurer and your IT provider.
  5. Identify alternatives for critical suppliers and avoid depending on a single one.
  6. Prepare a communication plan with backup channels, message templates and a single spokesperson.
  7. Define workarounds for each critical function, including remote work.
  8. Review your insurance, including business interruption and cyber coverage, with your broker.
  9. Keep enough financial reserves or credit to cover an interruption, as advised by your accountant.
  10. Link the plan to a tested disaster recovery plan and backups, then exercise and update everything at least once a year.

Frequently asked questions

Does a small business really need a business continuity plan?

Yes, and it can be short. Smaller companies usually have fewer people and less cash to absorb an interruption, so a few pages that name owners, workarounds and contacts can make the difference between a bad day and a lost client.

What is the difference between a business continuity plan and a disaster recovery plan?

The continuity plan keeps the business running during an incident: people, processes, suppliers and communication. The disaster recovery plan restores IT systems and data. The continuity plan includes or refers to the recovery plan.

How often should we test the plan?

Run a tabletop exercise at least once a year, and review the plan whenever you change key software, suppliers, premises or staff.

Who should own the plan?

Someone in management, not only IT. The owner coordinates updates and tests, while each department head keeps their own section current.

Nexxo helps businesses across Greater Montreal connect their continuity plan to the IT that supports it, from secure remote work to tested backups and recovery. Learn more about our managed IT services, or contact us to review your plan with our team.

← Back to Blog