Frequently Asked Questions


5


6

7

8

9

10

11

12

Does my organization actually need a business continuity program?

1

The question isn't whether, but how mature your program should be. Many organizations either have no plan or have one that was built once and never revisited, which leaves leadership making critical decisions blind in the moment it matters most.

We build programs sized to your actual risk exposure, not a generic template.

What is a Business Impact Assessment (BIA)?

2


A Business Impact Assessment (BIA) gives leadership the data needed to make informed strategic continuity decisions — which functions must be protected first, how much disruption the business can absorb, and where hidden dependencies put revenue or reputation at risk.

A well-run BIA becomes a strategic planning tool, not just a compliance document. Ours are built to directly inform your BC investment priorities, not sit in a binder.

What is a business continuity risk assessment?

3


A business continuity risk assessment tells leadership where the organization is most exposed — and how prepared it actually is to withstand those exposures.

Paired with a BIA, it shifts continuity planning from a reactive exercise into a strategic risk-management input, directly informing where to allocate budget and attention.

Generic risk assessments often use a standard threat checklist; we tailor the assessment to the risks that are actually material to your business and industry.

What does it mean when a vendor or regulator is asking for my BCP?

4


What does a business continuity consultant do?

What's the difference between BC, DR, and Crisis Management?


How much does consulting typically cost?


How do I pick the best business continuity consultant for my needs?


Should I align my program to a standard?


What is end-to-end DR testing? How do I accomplish it?


What is a tabletop exercise, and why do I need one?

How often should a BCP be reviewed, updated, or tested?

It means a stakeholder is testing whether your organization can be trusted to keep operating — and keep serving them — under pressure.

This is now standard in vendor due diligence, RFPs, and regulatory exams, and an inadequate answer can cost contracts or compliance standing, not just hurt your operations posture.

We help leadership walk into that conversation with a plan that reflects how the business actually runs, not a boilerplate document assembled to pass review.

A business continuity consultant helps leadership understand where the organization is exposed and builds the plans, capabilities, and muscle memory needed to protect the business when disruption hits.

That includes BIAs, continuity and crisis plans, tabletop exercises, and alignment to relevant standards — but the real value is a program leadership actually trusts and uses, not a document that looks good in an audit.

That's the difference between a templated engagement and a bespoke one.

For leadership, the distinction matters because each protects something different: Business Continuity (BC) protects the business's operations, Disaster Recovery (DR) protects the technology underneath it, and Crisis Management (CM) protects the organization's ability to lead and communicate while the other two recover. Many programs are strong in one area and weak in the others — which is where real vulnerability hides. We build programs that integrate all three, because a gap in any one undermines the rest.

Investment scales with scope — a single BIA for one business unit is a very different engagement than a multi-year, enterprise-wide program.

Rather than a one-size-fits-all rate card, engagements are typically structured hourly, per-deliverable, or on retainer, based on what the business actually needs.

Look past certifications (MBCP, CBCP, MBCI) alone — ask whether the consultant has actually run engagements like yours, or just trained on the frameworks.

The sharpest signal is whether they tailor their approach to your organization's structure and risk profile, or hand you the same template every client gets. That distinction is often the difference between a program leadership trusts and one that sits unused.

Aligning to a recognized standard like ISO 22301 gives leadership a defensible, board-ready framework — one that's far easier to justify to regulators, auditors, and the executive team than an ad hoc approach.

It's not mandatory for every organization, but it becomes increasingly important as scrutiny, vendor requirements, or company scale grow.

We help you use the standard as a foundation, then build the program around your actual operations — not force your business to fit the standard.

End-to-end DR testing proves — not assumes — that your full recovery process works together under real conditions: failover, data recovery, application function, and user access, not just individual systems in isolation.

This is where leadership often discovers that technically "complete" DR plans fail in practice, because the pieces were never tested together.

We help organizations build toward full end-to-end testing safely, starting with smaller component tests, clear success criteria, and a storytellers perspective

A tabletop exercise is where leadership discovers whether a plan actually works — before a real crisis forces the discovery.

It's a facilitated, scenario-based discussion that exposes gaps, unclear ownership, and communication breakdowns while the stakes are still low.

Generic tabletop exercises run a canned scenario; ours are built around the specific pressures and dependencies your business actually faces, including multi-stakeholder and vendor-involved scenarios many firms don't simulate.


At least annually — reviewed and tested through a tabletop exercise or simulation — with earlier reviews triggered by major organizational change, new regulations, vendor or system shifts, or lessons from a real incident.

A plan that isn't regularly tested quietly goes stale, often without leadership realizing it until it's needed.

Part of a bespoke engagement is building a review cadence that fits your organization's actual pace of change, not an arbitrary annual checkbox.