Skip to content

Plan for the bad day

Business Continuity
& Disaster Recovery

We work out which processes the business cannot run without, how long each can be down, and how much data it can afford to lose. Then we build recovery plans around those answers and exercise them with your team, so the plan reflects what your people and systems can actually do.

From impact to tested plan

A plan your team
can run cold.

The work follows ISO 22301 and NIST SP 800-34 Rev. 1, with exercises built to NIST SP 800-84. Recovery objectives come from the business instead of IT guessing. Every plan is walked through with the people named in it before we call it finished.

Phase 01 · Impact analysis

Find out what the business cannot live without.

A business impact analysis that ranks processes by the damage downtime causes.

  • Interviews with process owners in operations, finance and customer service.
  • Financial, legal and customer impact of an outage assessed as it grows.
  • Dependencies traced to systems, suppliers, sites and people.

Phase 02 · Recovery objectives

Set how fast and how far back each process must recover.

Recovery time and recovery point objectives, approved by the business.

  • RTO and RPO set per process, then per supporting system.
  • Maximum tolerable downtime agreed with leadership.
  • Gaps between objectives and current capability shown plainly.

Phase 03 · Recovery strategy

Choose how you will come back.

A recovery strategy per process, with the cost and tradeoff of each option laid out.

  • Backup, replication and alternate site options compared.
  • Manual workarounds designed for processes that can run on paper.
  • Ransomware planned for: isolated backups and clean rebuild paths.

Phase 04 · Plans & runbooks

Write plans people can follow under pressure.

Continuity and recovery plans with named roles, contact trees and step by step runbooks.

  • Authority to invoke the plan, and the decision points after it, made explicit.
  • Communication templates for staff, customers and regulators.
  • Plans written for the people who will use them.

Phase 05 · Exercise & handover

Test the plan, fix what breaks, hand it over.

An exercise report showing what worked, what failed and the plan updates that followed.

  • Tabletop or technical recovery exercise designed to NIST SP 800-84.
  • Lessons learned folded back into the plans.
  • Plan owners and review triggers handed to your team.

Find out what the business cannot live without.

A business impact analysis that ranks processes by the damage downtime causes.

  • Interviews with process owners in operations, finance and customer service.
  • Financial, legal and customer impact of an outage assessed as it grows.
  • Dependencies traced to systems, suppliers, sites and people.

Key benefits

Recover on purpose, not by improvisation.

Objectives the business agreed

Recovery targets come from the people who feel the outage, then get checked against what IT can deliver. The gap becomes a funded decision instead of a surprise during an incident.

Plans tested before they are needed

Each plan is exercised with the people named in it. Missing phone numbers, unclear authority and backups nobody can restore show up in a session rather than during an outage.

Built to ISO 22301 and NIST

The method follows ISO 22301 and NIST SP 800-34, so the analysis and plans hold up when a customer, regulator, insurer or auditor asks how you would recover.

What you get

What lands on
your desk.

Three handoffs your team keeps and maintains after the engagement ends.

The document

The BIA and continuity plans

Business impact analysis, agreed recovery objectives, recovery strategies and the plans themselves, with named roles, contact trees and the authority to invoke each one, written for the people who will carry them out.

The working file

The recovery gap tracker

Every gap between agreed objectives and current capability, with an owner, rough effort and status. It turns the plan into a funded list of improvements.

The conversation

The exercise and debrief

An exercise we run with the people in the plan, followed by a debrief on what held and what failed. Plan updates are agreed in the room.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

In their words

"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

Trusted by industry leaders.

Before we start

Continuity
questions.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

Mostly we need people. Process owners, IT and leadership give us the impact and dependency picture. For technical recovery tests we work beside your IT team, who run the restores while we observe and record.

A tabletop exercise costs nothing beyond the time of the people in the room. A technical recovery test is planned with IT around isolated systems or quiet periods, and nothing is failed over without your approval.

Probably, if IT wrote it alone. A DR plan covers systems. Business continuity covers the processes those systems support, including what people do while systems are down. We review your plan and build on it.

Ransomware is one of the scenarios we plan and exercise for. We look at backup isolation, clean rebuild paths and the decisions leadership would face. Our Ransomware Readiness service goes further if you need a dedicated review.

Ready?

Bring us
the problem.

One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.