Metrics

BCM Program Health Dashboard: Executive Decision View

Build an executive BCM health view that combines validated capability, material exposure, exceptions, trends and decisions without hiding critical failures in averages.

A BCM program health dashboard is the executive decision view of continuity capability. It should reveal where exposure is increasing, which commitments are not being met and what management decision is required now. It is not the place to invent KPI formulas; define those first in the BCM KPI Framework.

Use a small set of decision panels

PanelExecutive questionEvidence
Recovery confidenceWhich critical services have demonstrated recovery within approved tolerances?End-to-end tests and achieved RTO/RPO.
Material exposureWhere are single points of failure, unsupported dependencies or accepted gaps?Risk, dependency and exception records.
Exercise assuranceWhich capabilities failed acceptance criteria?Objectives, observations and after-action evidence.
Corrective actionsWhich high-risk actions are overdue or repeatedly deferred?Action register and ageing.
Change pressureWhich new services, suppliers, systems or sites have changed the risk picture?Scope/change records.

Do not average away critical failures

Segment results by criticality. Ninety-eight low-impact plans should not turn a dashboard green when two tier-one services cannot meet recovery objectives. Show the exception explicitly and retain the denominator so leadership can see whether a percentage changed because capability improved or because scope changed.

Worked executive scenario

The dashboard shows 96% plan currency but only 61% of tier-one services have executed end-to-end recovery during the required period. Three shared applications support 18 critical processes and have never been failed over. The executive conclusion is not “96% healthy.” The dashboard should surface recovery assurance as amber/red, identify the shared dependencies, show the accountable owners and record the decision to test, remediate or accept the exposure.

Trend and commentary

Every material movement needs commentary. If recovery confidence falls, identify whether the cause is failed testing, new scope or overdue remediation. If it improves, link the improvement to evidence. Preserve prior periods so leadership can distinguish sustained improvement from a one-off reporting change.

Dashboard acceptance criteria

  • Critical exceptions remain visible even when portfolio averages are high.
  • Every red/amber condition has an owner, action and decision date.
  • Reported capability can be drilled back to evidence.
  • Missing data is visible rather than excluded.
  • Trends retain consistent definitions or disclose definition changes.
  • The view is concise enough for management review while operational detail remains available by drill-down.

For formal narrative packs, decisions and committee reporting, use the Business Continuity Reporting Guide. For detailed indicator design, use the KPI framework rather than duplicating formulas in the dashboard.

Build an executive view that cannot hide critical weakness

A BCM program-health dashboard should support decisions, not merely aggregate activity. Separate coverage, capability, exposure and remediation. A high completion percentage can coexist with unacceptable risk: for example, 96 percent of plans may be current while the four expired plans support the organization’s most critical services. Preserve criticality in every roll-up so averages do not create a false green status.

Use decision-oriented measures

Group measures by the question leadership must answer. Coverage asks whether required BIAs, strategies, plans and exercises exist. Capability asks whether tested recovery met approved RTO, RPO, MBCO and dependency criteria. Exposure shows overdue critical gaps, concentration risk and unsupported dependencies. Remediation shows whether corrective actions close on time and whether closure has been re-tested. Avoid mixing these dimensions into a single opaque score.

Define denominators and cut-off rules

Every percentage should disclose its denominator. If 18 of 20 critical services have current plans, report 90 percent and identify the two missing services; do not calculate against only the 18 records already entered in the system. Establish a reporting cut-off time and snapshot rule so late edits do not silently change a previously issued executive view. Mark missing data as missing rather than assuming compliant or zero risk.

Weight criticality transparently

Where weighting is used, publish the rule and retain drill-down. A simple example is to assign critical services a weight of five, high services three and standard services one, then calculate coverage against weighted required items. Weighting can focus attention but must never erase an absolute red condition such as an untested recovery strategy for a life-safety or regulatory service. Define override rules for such conditions.

Show trend and evidence age

A current green measure based on evidence from two years ago may be misleading. Display the evidence date, next review date and trend alongside status. For exercise capability, distinguish “discussed,” “partially demonstrated” and “demonstrated under representative conditions.” For corrective actions, show opened, overdue, closed-awaiting-retest and verified-closed states rather than counting administrative closure as risk reduction.

Design drill-down for challenge

Executives should be able to move from an enterprise indicator to business unit, service and underlying evidence. Each red or amber condition should identify the accountable owner, reason, decision required and target date. Keep metric lineage: source system, extraction time, transformation rule and owner. This allows assurance teams to reproduce a reported value and reduces debate over whose spreadsheet is correct.

Example executive interpretation

Suppose plan currency is 94 percent, exercise completion 91 percent and corrective-action closure 88 percent. Those figures appear healthy until drill-down shows that two tier-one services missed RTO in their latest tests and one shared identity dependency has no proven alternate. The dashboard should elevate those conditions as explicit executive decisions rather than averaging them into an overall green score.

Dashboard acceptance checks

  • Every KPI has a defined purpose, formula, denominator, owner and data source.
  • Critical failures can override aggregate green status.
  • Missing and stale evidence is visible.
  • Users can drill from summary to accountable service and evidence.
  • Corrective-action closure distinguishes administrative closure from verified risk reduction.
  • Issued reporting periods remain reproducible through controlled cut-off and lineage.