Justifying a BCM Platform: A Business Case Finance Accepts

Ask eRMA

Budget requests for business continuity often rest on one argument: a disaster would cost far more than the platform. That is usually true, and finance teams usually discount it, because it can’t be tested and it looks the same every year. A business case that gets approved does something different. It shows what the current way of working already costs, and which of those costs a platform removes, using numbers the organization can check.

Why “it prevents disasters” isn’t enough

Avoided-loss arguments ask finance to price an event that may never happen, at a probability nobody can defend. Reviewers treat them as soft benefits, which is fair. The stronger approach treats the avoided loss as the last line of the case, not the first, and builds the rest from costs the organization is already paying.

The current process is not free. Spreadsheets, survey tools, consultant refreshes and staff hours make up a budget nobody tracks. Making it visible is often the most persuasive part of the case.

Four value lines finance can test

Order the benefits from easiest to prove to hardest. Finance reads from the top, and an early line it trusts makes the later ones more credible.

1. Tools and services retired

List what the platform replaces: survey tools, spreadsheet and SharePoint upkeep, a separate risk register, the consultant engagement behind the annual refresh, and any older continuity software still on contract. These are cash lines with invoices behind them, which makes them the easiest to verify.

2. Effort removed

Count the hours the program spends every year. How many managers complete the BIA, how long each questionnaire takes, and how many follow-ups it needs. Add the hours spent updating plans, preparing and writing up exercises, and collecting evidence for auditors. Multiply by a loaded hourly rate your finance team already uses.

Be precise about the claim: most of this is capacity freed, not cash saved. Say what the team will do with the time, such as more exercises or more coverage, rather than implying headcount reductions nobody has agreed.

3. Audit and regulatory exposure reduced

Don’t put a price on fines. Measure what auditors and regulators actually observe: open findings related to continuity, the time it takes to answer an evidence request, and how many recovery time objectives (RTOs) have been proven in an exercise rather than simply stated. Regulators in the United States, Canada and the Gulf increasingly expect evidence that operational resilience is tested, so a shorter answer time is a credible benefit on its own.

4. Recovery capability improved

This is the avoided-loss line, done properly. Use the impact figures from the organization’s own BIA. Where the platform closes a gap, for example a dependency whose recovery time is longer than its process can tolerate, estimate the hours of disruption it removes, and apply the impact per hour the business has already approved. Show a conservative and an expected value, never just the high one.

Be honest about the cost side

A case that only lists the subscription invites a second review. Include implementation, data migration, integration, training and the internal time needed during rollout. Then compare a three-year total cost of ownership against the three-year cost of the status quo, not against zero. Show a payback period, and say which month the first benefit appears.

Five rules finance respects

  1. Use the organization’s own numbers. Industry averages are easy to dismiss.
  2. Separate cash from capacity. Present them in different rows, and don’t add them together without saying so.
  3. Show a range. Conservative and expected values, with the assumptions written down.
  4. Give each benefit an owner. Someone who will report on it after twelve months.
  5. Measure the baseline now. Without today’s hours and findings, there’s nothing to compare against next year.

Where eRMA fits

eRMA, the resilience platform from eBRP Solutions, maps to each value line. All of the following are available today:

  • Tools retired: BIA, dependencies, plans, exercises, incidents and risk assessment on one data set, with ERM and Compliance (GRC) available as optional add-on modules.
  • Effort removed: group BIA with inheritance, so shared answers are given once; live campaign progress instead of chasing by email; the Employee Kiosk, where staff keep their own details current; and Data Management templates with pre-checks and dry runs for bulk loads.
  • Audit exposure: Exercise results recorded per entity against its RTO, with the evidence kept, plus role-based views that show “Unknown” rather than a false green.
  • Recovery capability: the Impact Map shows where recovery times don’t line up, and the Plan Sequencer shows the full recovery path to check against tolerance.

See it: Business impact analysis →

Three questions finance will ask

  1. What does the current way of working cost today? Have the hours, tools and consultant fees ready.
  2. Which savings are cash and which are capacity? Answer before you’re asked.
  3. How will we know in twelve months? Name the measures and their owners.

The one-page Brief includes a worksheet with each value line and space for your own figures.

Download the worksheet as a one-page Brief: Business case worksheet for a BCM platform (PDF)

Download the eRMA brochure · Join the next live showcase

One resilience program, the right page for every role

A resilience program is run by many people who never look at it the same way. The board wants to know whether the organization can keep delivering. The program manager wants to know what needs attention first. A department head wants to know what they owe the program this week, and an auditor wants proof. eRMA keeps one set of records and gives each of these people their own page into it: their question first, their part of the organization, and only the detail they are allowed to see.

The problem it solves

  • “Every audience gets its own spreadsheet, so every meeting starts by arguing about whose numbers are right.”
  • “Owners only hear from the program once a year, when the BIA form arrives.”
  • “In an incident, nobody is sure who is meant to do what, or what they are allowed to change.”

Six roles, one program

1. Executive sponsor and board: “Can we keep delivering?”

Executives see the program as answers, not appendices. The Executive Resilience Scorecard shows posture, coverage, top risks and overdue reviews on one page. Can We Keep Delivering? compares each important service’s recovery objective with what has actually been proven. When the board meets, the same pages print as a dated, scoped and marked board pack.

Six executive dashboards, one per audience: Executive Resilience Scorecard for the board, Can We Keep Delivering? for the COO, Enterprise Risk for the CRO, BIA Program Progress, Line of Business Scorecard and the Organization Resilience Map

2. Resilience program manager: “What needs me first?”

MyWorkspace opens on a ranked list of what needs attention: BIAs waiting for answers, plans past their review date, services without recovery proof. Each area of the program is a card marked Attention or On track, mapped to the ISO 22301 clause it supports, with the next step one click away. A gap shows as a gap. It never turns green because a document exists.

MyWorkspace Program cards for scope, BIA, risk assessment, strategy, plans and exercise, each marked Attention or On track with its ISO 22301 clause and the next step

3. Regional and business-unit coordinator: “How is my part of the organization doing?”

Coordinators see the same measures as the program manager, scoped to their region, legal entity or line of business. Every dashboard follows the organization tree, so a coordinator can drill from their division into each department, and a restructure changes the scope, not the report.

4. Process, service and application owners: “What do I owe the program?”

Owners see only what is theirs: the BIA to answer, the plan to review, the dependency to confirm, the approval waiting for them. MyWorkspace switches between three modes. Own shows an owner’s records and tasks, Govern shows the program, and Operate takes over when an incident is open.

MyWorkspace mode switch: Own, Govern and Operate, with a time horizon of today, this week or the next 30 days

5. Incident lead: “Who is affected, and who is on it?”

When an incident opens, the response runs from one page: plans activated, tasks for each team, a roll call that knows who is away, decisions recorded as they are made, and messages to the teams involved. Each person sees why they have access, such as incident commander or an invoked team, so nobody has to guess what they are allowed to change.

An open incident with buttons to message teams, record a decision and flag it enterprise-wide, and a line telling the viewer why they have access: incident commander, team invoked

6. Auditor and compliance: “Can I prove it?”

Auditors read everything and change nothing: the audit trail, approvals, access changes, export logs and the evidence behind each figure. Evidence packs collect the register, responses, approvals and gaps in one download, so an audit request does not turn into a two-week project.

Everyone else keeps their own part current too. Through the Employee Kiosk, staff maintain their own profile, contact details and whereabouts, so a roll call reaches the right people.

What holds it together

  • One set of records. Every role reads the same BIA, plans, risks and evidence. Nothing is copied into a second spreadsheet for a different audience.
  • Roles come from teams. Access is granted to teams, not to individuals, and duties that should be kept apart, such as approving your own work, are checked.
  • Same totals for everyone. Totals count every record, so no two people see different numbers. Only the detail depends on what a viewer may open; the rest shows as Restricted, never as zero.
  • Unknown stays unknown. A record with no evidence shows as unproven for every role, from the department to the board.

The six roles at a glance: One program, six questions (PDF, 9 pages)

See it with the roles in your own program: Book a demo

Data Residency vs One Resilience Program: The Federated Answer

A resilience program is judged as a whole. Boards and regulators ask whether critical services can stay within tolerance, wherever they run. But the data behind that answer is increasingly tied to where it was created. A multinational must keep employee and incident data in-country. A group of near-independent businesses wants each to run its own program. A public agency runs many independent operations on the same HR, IT and facilities. Each case pulls the data apart while the program still has to hold together.

Why one central database stops working

The default answer is one platform, one database, with access rules that keep each unit to its own records. That works well inside one jurisdiction. It stops working when:

  • The law decides where data lives. Privacy, residency and sovereign-hosting rules can require personal and operational data to stay in the country. Access rules do not change where data is stored.
  • Some sites cannot be connected. Defence, government and critical-infrastructure sites often run air-gapped. A central platform cannot reach them, and they cannot reach it.
  • Units need real independence. A business being prepared for sale, or a government operation with its own mandate, needs its own platform, not a filtered view of someone else’s.

The opposite answer, a separate tool per country or unit, keeps the data local but loses the program. Each site defines “critical” differently, shared services are recorded several times, and the enterprise view becomes a spreadsheet assembled by hand.

What federation means

Federation sits between the two. Each jurisdiction, line of business or operation runs its own complete platform, hosted where its data must live. One platform acts as the hub. Records fall into three classes:

  • Global: the method and the standards (risk scales, impact categories, BIA time buckets, the control library, plan templates) and the shared entities everyone depends on (enterprise applications, shared services such as HR and payroll, global vendors). These are owned once at the hub and flow down as read-only copies.
  • Local: processes, sites, BIA, plans, risks, exercises and incidents. These stay in the local platform. An agreed summary flows up.
  • Private: people, contacts, evidence files and restricted risks. These never leave the local platform at all.

The enterprise view is built from the summaries: every critical service’s recovery objectives, its dependency on shared services, its last exercise result, across every site, without the hub ever holding another country’s personal data.

Four design choices that decide whether it works

  1. One owner per record. Every shared record has exactly one owning platform; everyone else holds a read-only copy. Nothing is ever merged, so two sites can never disagree about the same record. Change requests go to the owner.
  2. Summaries, filtered at the source. Each summary field carries a data class, and the local platform decides which classes may leave before anything is sent. That is where data-protection officers can sign off the flow.
  3. Standards first. An enterprise heat map only means something if every site uses the same scales. Sharing the standards is the first step of any federation, and the cheapest.
  4. Signed bundles, customer-held keys. Updates move as signed, encrypted bundles in numbered order, so they work across an air gap as well as over a network. The organization, not the vendor, holds the keys.

Incidents need one more thing: a small, fast status channel. When a shared entity such as an enterprise ERP fails, its owner raises the incident once and every dependent site sees its own impact immediately, while the full incident record stays local.

Questions to ask before choosing a platform

  • Where does each kind of record physically live: people, sites, incidents, evidence, restricted records?
  • What exactly leaves a jurisdiction, and who can switch a field off?
  • Who can edit a shared record, and what happens when two sites disagree?
  • Who holds the signing and encryption keys?
  • How do updates and incident status reach a site with no live connection?
  • How does a business unit move to another site or platform after a reorganization?

eRMA and federation

eRMA, the resilience platform from eBRP Solutions, runs on the customer’s own infrastructure, including air-gapped networks, and takes in outside data as signed bundles rather than live connections. Access is granted through teams, sensitive risks can be restricted to the people who should see them, and a complete export pack carries a whole program from one platform to another. These are the foundations the federated model builds on.

The full model is set out in the whitepaper Federated resilience: one program, many jurisdictions (PDF).

Planning a multi-jurisdiction program? Talk to eBRP Solutions.

What Should a Business Continuity Platform Actually Solve?

Ask eRMA

Budgeting season is when many business continuity teams decide whether to renew, replace or buy a platform. The feature lists vendors send are long and look alike. A better starting point is the opposite question: which business problems should the platform make smaller every year? Across banking, insurance, healthcare, energy and the public sector, in North America and the Gulf, the same six come up again and again.

1. The picture is out of date the day it’s approved

The annual business impact analysis (BIA) is the classic example. Questionnaires go out in spring, the results are approved in autumn, and by then teams have reorganized, applications have moved and vendors have changed. The program produces a document, not a current picture.

What good looks like: ISO/TS 22317 treats the BIA as an activity you keep up, not a one-off project. The people who own the data keep it current, a change triggers a review rather than a date on the calendar, and nobody is asked the same question twice. Where processes share a parent, answers are inherited rather than collected again.

Ask a vendor: how does a single change reach the BIA without starting a new cycle?

2. Nobody can see what depends on what

Dependencies usually live in spreadsheets, one per team. Each is right on its own terms, and together they miss the application, site or vendor that quietly supports three critical services at once. That gap tends to show up during an incident, which is the worst time to find it.

What good looks like: one dependency model that connects processes, applications, services, locations, vendors and people. The model should flag a gap on its own, for example an upstream application whose recovery time is longer than the process that needs it can tolerate.

3. Recovery times are stated, not proven

A recovery time objective (RTO) written in a BIA is a target. Until an exercise shows the organization can meet it, it remains an assumption. Many exercise reports are narratives, which makes it hard to say which RTOs were tested and which were met.

What good looks like: ISO 22301 (clause 8.5) asks for an exercise program that validates continuity arrangements. In practice that means recording results per process, application or service against its RTO, and keeping that evidence where an auditor or regulator can follow it.

4. Plans exist, but not in an order anyone can run

Large programs have dozens of plans. Each may be sound on its own, but on the day, someone has to know which runs first, which waits for another, and how long the whole chain takes. That order often lives in one experienced person’s head.

What good looks like: plans sequenced by their dependencies and recovery times, so the total recovery path is visible and can be checked against the business’s tolerance before an incident, not during one.

5. Risk and continuity live in separate worlds

The risk register sits in one tool, the BIA in another and controls in a third. The same vendor can be rated three different ways, and nobody notices until an audit. Regulators increasingly look at operational risk and resilience together, for example OSFI Guideline E-21 in Canada and the US agencies’ sound practices paper on operational resilience.

What good looks like: risk assessments that use the same processes, applications, locations and vendors as the BIA, so a risk rating and an impact rating describe the same thing.

6. Leaders can’t get a straight answer quickly

Executives receive long reports or dashboards that are green because nothing has been measured. Neither helps a leader decide in the minute they have.

What good looks like: each role sees first what needs its attention. Missing data shows as “Unknown”, never as healthy. Data a viewer may not see shows as “Restricted”, never as zero, so a total is never quietly wrong.

Where eRMA fits

eRMA, the resilience platform from eBRP Solutions, was designed around these six problems. All of the following are available today:

  • Business impact analysis with group BIA and inheritance, and live progress for each campaign. The Employee Kiosk lets staff keep their own details current.
  • Impact Map and Dependency Designer: one connected model of processes, applications, services, locations, vendors and people, with RTO gaps shown where they occur.
  • Exercise: rehearse a scenario and record results for each entity against its RTO, with the evidence kept.
  • Plan Sequencer: one bar per plan, chained finish-to-start, so the recovery path can be seen and adjusted.
  • Risk Assessment on the same entities as the BIA, with ERM and Compliance (GRC) available as optional add-on modules.
  • Role-based workspaces that lead with what needs attention, where “Unknown” is never green and “Restricted” is never zero.

See it: Business impact analysis →

See it: Dependency Designer and Impact Map →

See it: Plan Sequencer →

Three questions to ask any vendor

  1. Show one change, live. Add a new application that supports a critical service, and show how it reaches the BIA, the plans and the dashboard, without slides.
  2. Show a proven RTO. Where does the platform show that a recovery time was exercised and met, not only stated?
  3. Show the first ten seconds. What does a senior leader see on opening the platform, and what does it show when data is missing?

A platform earns its budget when these six problems get smaller every year.

Download this as a one-page Brief: What should a business continuity platform solve? (PDF)

Download the eRMA brochure · Join the next live showcase

Business impact analysis: answer once, see every gap

Every recovery decision starts with a business impact analysis (BIA): how long can this stop before the harm becomes unacceptable, and what has to come back first? eRMA runs the BIA as a living register rather than an annual document. A BIA can be done once for a whole group, every value shows where it came from, and the gaps it creates are visible as soon as an answer is saved.

The problem it solves

  • “We send the same sixty questions to forty managers, and most of the answers are the same.”
  • “By the time the BIA is approved, half of it is out of date, and nobody can say which half.”
  • “Our process RTO is four hours, but the application it runs on takes a day to recover, and we found that out in an incident.”

How it works

1. Answer once, at the right level

A BIA can be done on a service, process or application, or on its group. The survey adapts as it is answered: questions appear or disappear depending on earlier answers. The impact-over-time grid rates each kind of harm (financial, customer, legal and regulatory, reputation, operational, health and safety, environmental, contractual) from one hour to one month. Ratings cannot fall as a disruption goes on. While the survey is being answered, the calculated values (RTO, RPO, maximum tolerable period of disruption, minimum business continuity objective, criticality and recovery tier) update beside it. Each value has a “Why?” link and a full calculation trace. Only one person answers a BIA at a time. They can hand it back, so two people never overwrite each other’s work.

When a group’s BIA is approved, its values pass down to every record in the group that has no BIA of its own. Each value is labelled as the record’s own or inherited, and from which group. A record that needs different values gets its own BIA, which takes precedence.

Process BIA survey with an impact-over-time grid rating eight kinds of harm from one hour to one month, and calculated RTO, RPO, MTPD and criticality beside it

2. Watch the campaign as it happens

Coordinators open a BIA cycle, assign who answers each BIA, and follow progress live. Totals for not started, in progress, returned, submitted and approved update as people save, without refreshing the page. The same figures are broken down by family and by team, so a reminder goes to the team that needs it rather than to everyone. Submitted BIAs go through an approval step before their values count as approved.

Live BIA progress board showing percent complete and counts by status, broken down by family and by team

3. See where the objectives don’t fit together

The Gaps view compares objectives across the dependency model. It lists a dependency that recovers later than the record needs it, a process or application with a looser objective than the service it supports, and recovery today that is slower than the objective. It also flags critical records that rely on something with no BIA. A gap that an approved recovery strategy covers is shown as Mitigated, so the list stays focused on what is still open.

BIA Gaps list showing records whose recovery today takes longer than their RTO, each marked Gap

What it proves

The BIA, the dependency model and recovery planning read from one source, so an RTO is never retyped into a second spreadsheet. A record without an approved value shows as Unknown, never as a default that looks healthy. Every count includes only the BIAs the viewer is allowed to read. For an auditor, one download (the evidence pack, an Excel workbook) holds the register, responses, impact grids, answers, approvals, gaps and proposed dependencies. The method follows ISO 22301 clause 8.2 and ISO/TS 22317, with ISO/IEC 27031 used for ICT requirements.

See it on your own data: Book a demo

Dependency Designer and Impact Map: see what depends on what

Most recovery surprises are dependency surprises: the application nobody listed, the server three critical processes share, the vendor behind a service everyone thought was in-house. eRMA gives the dependency model two views. The Dependency Designer is where links are drawn and kept current. The Impact Map is where they are read, so an outage can be traced to everything it reaches before it happens for real.

The problem it solves

  • “Our dependencies are in a dozen spreadsheets, one per team, and none of them agree.”
  • “When a server goes down, it takes an afternoon to work out which processes are affected.”
  • “The process needs to be back in four hours, but nobody checked how long the application behind it takes to recover.”

How it works

1. Draw the links on a canvas

The Dependency Designer opens on one record, such as a process, application or service, and shows what it is linked to: applications, servers, databases, locations, other processes, and customers and suppliers. To add a link, drag a record’s handle onto another record, or place a record from the library and link it there. Keyboard users get the same result through “Link to…”. The designer only offers links that make sense: it refuses a duplicate, a link from a record to itself, or one that would create a loop.

New links and changes are collected first, not saved one by one. “Review and save” lists every change before it is written, and the whole set is saved together or not at all. If someone else changed the same record in the meantime, the designer says so instead of overwriting their work. Any link whose recovery doesn’t fit is marked as a recovery gap on the spot.

Dependency Designer canvas centred on an application, linked to its servers, databases and the processes that use it, with recovery gaps marked in the record panel

2. Trace an outage before it happens

The Impact Map starts from any record and follows the links in either direction. “Impacts” shows everything that relies on the record, “Dependencies” shows what it relies on, and “Both” shows the two together, from one to five levels deep. The business view keeps the picture readable by listing services, processes, applications, and customers and suppliers. Servers and databases appear only where they connect them. One switch shows all records.

The summary beside the map counts what is affected and how many of those records the outage would push past their RTO: here, an application that takes ten hours to recover today, supporting three processes that need it back sooner. Panels on the same page list shared dependencies, data-quality issues to check, and the recovery strategy options for the record in focus. A view can be saved or shared as a link.

Impact Map of an application showing the three processes it supports, each marked Exceeds RTO, with a summary panel counting affected records

3. Let the unknowns show

When a record has no recovery time set, the Impact Map says Unknown instead of assuming it will be fine. Each affected record carries the label, and the summary counts them separately, so missing data is a visible gap rather than a silent pass. Records the viewer is not allowed to read are counted as Restricted, never left out.

Impact Map of a virtual server showing the applications and processes that rely on it, each labelled Unknown RTO, and counted separately in the summary

What it proves

The designer, the Impact Map, the business impact analysis and recovery planning all read the same links, so a dependency is recorded once and used everywhere. A gap is shown where it occurs, at the link that causes it. Unknown is never shown as healthy, and Restricted is never shown as zero. When an incident or exercise starts, the picture of what depends on what is already drawn.

See it on your own data: Book a demo

Plan Sequencer: the order your recovery really runs in

A recovery that needs twenty plans isn’t twenty separate recoveries. Infrastructure comes back before the applications that run on it, and applications come back before the business processes that use them. The Plan Sequencer puts every plan in a scenario on one page, in the order they will actually run, so the team can see how long the whole recovery takes and which recovery objectives it would miss.

The problem it solves

  • “Each plan has its own timings, but nobody can say how long the full data center recovery takes end to end.”
  • “The order plans run in lives in one person’s head, or in a slide from the last exercise.”
  • “We only found out the application team was booked on three plans at once when the exercise started.”

How it works

1. Start from the scenario, not a blank page

Open a scenario’s Sequence tab and the sequencer proposes a first order from what the scenario covers. It brings in the plans for the records in scope, puts infrastructure, applications and processes in their own lanes, and chains a plan after another wherever the dependency model says one record relies on the other. Each plan is one bar. In the Sequence view, each column is a step, so the order reads left to right at a glance. Plans can also be added from the plan catalogue, or the sequence can be built from scratch.

Plan Sequencer Sequence view of a data center recovery scenario: one bar per plan, infrastructure plans first, then applications, then business resumption, chained left to right

2. See the timeline and the critical chain

The Timeline view gives each bar its real duration. It highlights the critical chain, the plans that set the total recovery time, and marks the shortest RTO of what each plan covers, so a plan that finishes too late stands out. Relations are set by dragging. A plan can start with another, when another finishes, or a set time after either one, and each plan shows its slack, the time it could slip without delaying the end. A team load switch flags any recovery team that is needed in two or more plans at the same time. Play runs the recovery against the clock so a walkthrough can follow it step by step, and undo and redo keep editing safe.

Plan Sequencer Timeline view with plans in lanes on a time axis, the critical chain in red and diamond markers for the RTO of what each plan covers

3. Approve it, and keep it for the record

The List view sets out every plan with its lane, duration, start, finish, slack and the plans it runs after. A draft is validated and then approved as a numbered version, and the change history is kept. “New draft from this” starts the next round from the approved one, and two versions can be compared before the next approval. A printable brief gives the same order to anyone who needs it on paper.

Plan Sequencer List view of an approved sequence, giving each plan's lane, duration, start, finish, slack and the plans it runs after

What it proves

The order comes from the same dependency model and plans the rest of eRMA uses, so nothing is retyped into a project tool. When the model changes, a new draft can be derived again, with the differences shown. The total recovery time is calculated, not estimated, and a plan that finishes after the RTO of something it covers is shown as late. Plans that cover nothing in the scenario are listed separately rather than hidden. Going into an exercise, the order is already agreed, approved and printed.

See it on your own data: Book a demo