ISO 22301 business continuity, with recovery targets your systems can actually hit

Trusted by

  • Broadcom
  • SSENSE
  • Mondou
  • Western University
  • Votatec
  • Ren's Pets
  • City of Mississauga
The work

ISO 22301 business continuity, three pillars, one operator.

One Canadian team runs the business impact analysis, builds the business continuity management system (BCMS), and proves the plan against the infrastructure you actually run.

  1. Business impact analysis

    Critical activities ranked and tolerable disruption periods agreed with the people who own them, then mapped through to the systems, suppliers and people each activity depends on.

  2. The management system

    Clauses 4 to 10 built: scope, policy, continuity strategy, plans, exercise programme, management review, and the records an ISO 22301 certification audit asks to see.

  3. Plans that hold

    Continuity plans exercised against the estate you actually run, not against a boardroom table. Where the agreed target and the infrastructure disagree, our engineers fix the infrastructure.

By industry

Does ISO 22301 Business Continuity work the same way in every industry?

No. The ISO 22301 Business Continuity work is the same craft in every sector, but the conditions around it are not. In manufacturing that means production lines that can't stop for a patch window; in energy and mining, SCADA networks and remote sites that can't go offline. We keep the service and change the part that bends.

  • The continuity certification your larger customers ask for.

    OT and IT convergence. A flat network between plant and office is the common failure, and segmentation is the fix. It's a design problem, not a purchase.

    • Patch windows
    • Legacy equipment
    • ISO 22301
    Manufacturing IT
  • Continuity planning that accounts for physical isolation.

    SCADA and ICS. Availability outranks confidentiality here, and you often can't take a system offline to investigate what happened on it.

    • Bill C-8 and the CCSPA
    • Remote-site connectivity
    • ISO 22301
    Energy and mining IT
Request a consult

What do you need from ISO 22301 Business Continuity?

Tell us who you are and what you're working on. A senior engineer reads your message before replying, so the first answer is a real read on scope, risk and timing, within an hour, 24/7. Nothing here is a commitment, and we'll tell you plainly if we're not the right fit.

I agree to receive emails from SMEnode.

We use your details to reply to this message. You can unsubscribe from our emails at any time. Privacy

Your request

Service
ISO 22301 Business Continuity

What happens next

  1. A senior engineer replies within an hour, 24/7, never an SDR.
  2. We book a 30-minute call to listen, sketch options, and flag risks.
  3. You get a scoped statement of work within 3 business days.

Call the 24/7 line

+1 514-465-1584
The deep dive

ISO 22301 business continuity in Canada, made real.

I run this practice, so this is written by the engineer who'll own the gap between your plan and your platform, not a product page.

Most continuity plans promise what the estate can't deliver.

Most continuity plans get written by people who have no authority to change the systems the plan depends on. That's the problem in one sentence. A business impact analysis sets a tolerable period of disruption for each critical activity, and the plan then promises it. Almost nobody checks whether the estate can deliver it, and the certificate won't tell you, because ISO 22301 certifies that a business continuity management system exists and runs, not that your platform can come back inside the window you wrote down. Both things matter. Only one of them is what a customer experiences during an outage.

Where the risk actually sits.

Risk sits in three predictable places. A business impact analysis done with a consultant and a spreadsheet rather than with the people who own the critical activities, which produces numbers nobody will defend under pressure. Plans exercised only as tabletop discussions, so the first real test is a real incident. And suppliers whose own continuity arrangements nobody has ever asked about, which is where a surprising share of Canadian outages start.

The Canadian calendar, and what OSFI E-21 already expects.

The Canadian calendar makes this urgent for one sector in particular. OSFI published Guideline E-21, Operational Risk Management and Resilience, on 2024-08-22, began compliance checks on 2025-09-01, and expected full adherence by 2026-09-01 (source: OSFI, 2024). It calls for business continuity, disaster recovery and crisis management to sit inside one resilience framework, with scenario testing across all critical operations by 2027-09-01. E-21 names no standard, so ISO 22301 is one credible way to evidence it rather than a requirement. ISO 22301:2019 is still the current version of this continuity planning standard, and it now carries the 2024 climate amendment (source: ISO).

Want a Senior IT Consultant's Read on Your Setup?

Tell us what you run today and what keeps breaking. A senior SMEnode engineer replies within an hour with a first read on scope, risk and timing. No sales handoff.

Request a consult
The method

How our BCMS and continuity planning work runs.

Four steps, and step 01 is the one that gets skipped. A business impact analysis is a series of uncomfortable conversations with the people who own each critical activity, and it produces numbers they'll stand behind. Done as a questionnaire it produces numbers nobody owns. We run it as workshops, we write down who agreed to what, and the output is short enough that an executive will read it.

Engagement phases

Phases 01 to 04

  1. Run the impact analysis

    Critical activities identified with their owners, tolerable disruption periods agreed and recorded, and dependencies mapped through to the systems, suppliers and people each activity actually needs.

  2. Build the management system

    Scope, policy, continuity strategy, plans, exercise programme, management review, and the records a certification body will ask to see, sized so your team can keep it running.

  3. Close the capability gap

    Where the agreed target and the infrastructure disagree, our engineers fix the infrastructure. This is the step no continuity consultancy can offer, and it's why the plan stops being fiction.

  4. Exercise, then certify

    Real exercises against real systems, findings fed back into the plans, an internal audit, and stage 1 and stage 2 support with the accredited body that issues the certificate.

Questions

ISO 22301 questions, answered straight.

Answers first, including what the certificate does not prove. An architect takes the call, not a salesperson.

What they protect. ISO 27001 governs information security: who can reach data, how it's defended, how incidents get handled. ISO 22301 governs continuity of delivery: which activities matter, how long they can stop, and how you restart them. The clause structure is nearly identical, so holding one makes the second much cheaper. Most Canadian organisations we meet should do information security first, and we'll say if you're the exception.

No, and the difference decides who writes it. A disaster recovery plan covers technology: bringing systems back. A business continuity plan covers the business: how payroll runs, how orders get taken, where people work, what customers get told. Continuity is the wider document and recovery is one chapter of it. A plan that only covers technology leaves out the questions your operations team will actually be asked.

No. Certification comes from an accredited body, and the firm that builds your management system can't be the one that audits it. We build it, we prepare you, and we sit in the audit. Anyone offering to do both is selling you a certificate your customers will discount the moment they look at who signed it.

No, and this is the most useful thing on this page. The certificate proves you run a business continuity management system that identifies critical activities, sets targets and exercises plans. It doesn't prove your platform meets those targets, because that isn't what an auditor measures. We test both, and when the two disagree we'd rather rebuild the capability than lower the target on paper.

When no executive will own it, because continuity decisions are business decisions about what gets sacrificed first. When a major platform migration is already funded, since your dependencies and targets will both change. And when what you need is technology recovery rather than a management system, which is a smaller and cheaper piece of work, and we'll tell you if that's the honest answer.

We won't quote a range that means nothing without your scope. The bill has four parts: the accredited body's stage 1 and stage 2 audit, priced on headcount and number of sites; surveillance audits between recertifications; a copy of the standard from ISO; and your own team's time, which is usually the largest line. We size the first and the last with you before you commit.

Let's connect

A senior SMEnode engineer replies within an hour, 24/7.