Prove that the MBCO can be achieved
This guide is for continuity owners who already have an MBCO and need to govern and validate it. For the basic definition and relationship to RTO, read MBCO explained. For designing measurable service capacity, use MBCO operating-level design.
Assign accountable ownership
Each objective should identify the business owner who accepts the minimum service level, the continuity owner who maintains the strategy, and the operational/technology/supplier owners whose capabilities are necessary to achieve it. Approval should record assumptions rather than treating the target as a standalone number.
Build an evidence pack
- BIA evidence supporting the minimum level and priority population.
- Capacity calculations for people, systems, workspace and suppliers.
- Documented workaround duration and control limits.
- Exercise or live-event evidence showing achieved throughput.
- Known gaps, corrective actions, owners and due dates.
Use measurable exercise acceptance criteria
| Test area | Example acceptance criterion | Evidence |
|---|---|---|
| Activation | Degraded mode active within 30 minutes | Timestamped exercise log |
| Capacity | Priority service remains above approved floor | Transaction/queue metrics |
| Staffing | Required qualified roles filled for the test period | Roster and role log |
| Controls | Deferred transactions captured for reconciliation | Exception register |
| Dependencies | Critical supplier and technology paths demonstrated | Test records and screenshots |
Do not pass on activation alone
An exercise is not successful merely because the workaround started. Compare actual throughput, backlog growth, error rates and staffing sustainability with the approved minimum level. Record partial achievement as a gap rather than converting it into a pass through narrative judgment.
Revalidate after material change
Review the MBCO after material demand growth, process redesign, new regulatory obligations, supplier changes, technology migration, organizational restructuring or an exercise/live event that exposes an assumption failure.
Assurance questions
- Who accepted the minimum service level and on what evidence?
- When was it last demonstrated under realistic conditions?
- Were all critical dependencies included in the test?
- Can the service floor be sustained for the required duration?
- Are failed criteria tracked to closure and retested?
The assurance objective is straightforward: management should be able to distinguish an approved aspiration from a minimum service level that has actually been demonstrated.
Build an MBCO assurance case
An MBCO is useful only when management can see why the stated minimum service is sufficient, achievable and sustainable during the disruption window. Treat approval as an assurance case rather than a single percentage. Record the customer or regulatory outcome that must continue, the minimum transaction or case volume, operating hours, maximum queue or backlog, locations or channels that must remain available, minimum competent roles, required information and technology, and the duration for which the reduced mode must operate. Link each element to BIA evidence and the selected continuity strategy.
Challenge capacity, not just availability
A workaround that is technically available can still fail its MBCO when capacity is too low. For each critical activity, convert the MBCO into measurable throughput. If normal demand is 1,000 cases per day and the approved minimum is 40 percent, the plan must demonstrate capacity for at least 400 cases per day under disruption conditions. Include arrival patterns, manual handling time, shift length, staff productivity, dependency constraints and backlog growth. State which demand can be deferred and the point at which deferral becomes unacceptable.
Test the complete operating chain
Evidence should cover the end-to-end service, not isolated component recovery. Exercise the trigger, staff notification, delegated authority, alternate access, data availability, supplier response, manual controls, transaction processing, customer communication, exception handling and handback. Measure time to reach minimum service, sustained throughput, error rate and unresolved backlog. A desktop discussion can validate assumptions, but it should not be recorded as proof of operational capacity when no representative processing occurred.
Define failure and escalation criteria
Before an exercise or incident, define what constitutes failure. Examples include minimum service reached later than the required time, throughput below the approved floor for two consecutive measurement periods, critical role coverage below minimum staffing, unreconciled manual transactions exceeding a threshold, or a dependency with no usable fallback. Each failure should have an owner, corrective action, target date and re-test requirement. Temporary acceptance of a gap should identify the approving authority, expiry date and compensating control.
Govern changes to the minimum
Review the MBCO when demand, products, regulation, technology, suppliers, locations or staffing models materially change. Do not lower the minimum merely because the current recovery solution cannot achieve it; that reverses the purpose of the requirement. Where feasibility and business need conflict, document the gap and take an explicit risk, investment or service-design decision. Keep the approved requirement, current demonstrated capability and residual gap visible as separate values.
Evidence checklist for approval
- Traceable BIA rationale and named business owner.
- Measurable service, capacity, quality and duration criteria.
- Minimum people, technology, information, facility and supplier dependencies.
- Exercise evidence showing when minimum service was achieved and sustained.
- Known gaps, accepted exceptions, corrective actions and re-test dates.
- Review trigger and approval history so the requirement remains current.
Use the MBCO during a real incident
During response, compare actual delivered service with the approved minimum at agreed intervals. Record capacity, demand, backlog, staffing and dependency constraints rather than a simple available/unavailable status. If demand changes materially, incident command can prioritize customer groups or transactions using pre-approved rules while preserving safety and legal obligations. Any temporary departure from the MBCO should identify the decision maker, rationale, affected services and next review time. After stabilization, reconcile deferred work and compare actual performance with the assurance evidence used before the incident. This creates a feedback loop: incidents validate or challenge assumptions, and the next BIA, strategy review and exercise program can focus on the weaknesses actually observed.