Define membership, charter, decision rights, agenda, metrics and escalation for a BCM steering committee. The cadence should match the programme risk and change rate.
Two levels of readiness for BCM Steering Committee
A documented procedure to escalate decisions on funding, priority conflicts and risk treatment with expiry is not proof that the team can execute it under realistic demand. Validate staffing, access, timing and the observed outcome. Where a committee meets regularly without removing cross-functional blockers, the gap may surface before the plan's expected activation point. Identify the signal that should prompt an earlier intervention.
Readiness under test: Use action ownership, decisions, attendance authority and progress against capability gaps. Evaluate the information at the relevant date and system boundary, then challenge it with an exercise where two executives dispute allocation of a scarce alternate work area. The test should show how the operator recognizes an exception, changes the operating mode and tells affected users what service remains available.
For BCM Steering Committee, return-to-service approval must explicitly resolve the condition where a committee meets regularly without removing cross-functional blockers. Confirm the previously unmet decision—escalate decisions on funding, priority conflicts and risk treatment with expiry—with dated action ownership, decisions, attendance authority and progress against capability gaps, not only a technical completion status.
What should a BCM steering committee decide?
It should resolve cross-functional priorities, approve material remediation, escalate risk acceptance, confirm programme objectives and ensure shared dependencies receive accountable ownership.
How often should it meet?
Many organizations use a regular quarterly cycle with additional meetings for major incidents, significant findings or material changes.
Related BCM.Center resources: BCM Governance Framework · Business Continuity Program Charter Guide.
Reopen a policy decision — BCM Steering Committee
The acceptance record should identify the exact scope and expiry. If a named delegate is absent, test whether another authorized person can retrieve the evidence and execute the action without relying on private credentials. Define membership, charter, decision rights, agenda, metrics and escalation for a BCM steering committee.
Challenge of delegated authority — BCM Steering Committee
Appropriate validation for BCM Steering Committee differs from merely approving a plan. At the next management review, reconcile overdue actions with the risk register and funding decisions. A closed workflow item without a verified outcome should remain a capability exception. Sample recent changes, not only decisions made at the annual review. Test this failure condition: Attendance and discussion statistics are misleading when no committee member can authorize closure or escalation.
use a decision-rights register to distinguish the business owner, the bcm coordinator, the relevant technical authority and the person permitted to accept a time-bounded exception. decision packets should show the affected business service, unacceptable-impact boundary, proposed measure and evidence that justified the choice. Publish a decision agenda and track overdue recovery investments, rejected exceptions and material test outcomes to an accountable executive.
Acceptance evidence for BCM Steering Committee
Publish a decision agenda and track overdue recovery investments, rejected exceptions and material test outcomes to an accountable executive.
Boundary of the demonstrated result — BCM Steering Committee
Attendance and discussion statistics are misleading when no committee member can authorize closure or escalation.
Handover and acceptance for BCM Steering Committee
The handover should identify exactly what is still degraded after the immediate response to a committee meets regularly without removing cross-functional blockers. Operations needs a single owner for remaining service restrictions, outstanding transactions or dependent teams, and an agreed condition for returning responsibility to normal management. If there is no safe or feasible method to escalate decisions on funding, priority conflicts and risk treatment with expiry, do not conceal that limitation behind a general “recovered” status.
Prepare the next-shift brief from action ownership, decisions, attendance authority and progress against capability gaps. Mark observations, assumptions and unresolved exceptions separately. Include when the relevant information was collected, because a state that was correct at the first recovery checkpoint may change after traffic returns or demand accumulates.
Ask an independent reviewer to challenge the claim under this variant: two executives dispute allocation of a scarce alternate work area. The reviewer should identify what would invalidate the previous approval, who would authorize a change to the operating mode, and which customers, staff or suppliers need an updated instruction. Corrective actions need a tested outcome, not merely revised wording.