What MBCO means in practice
The Minimum Business Continuity Objective (MBCO) is the minimum acceptable level of products or services that an organization intends to sustain during a disruption. It turns a general statement such as “keep the service running” into an operating requirement that can be designed, staffed, exercised and measured. MBCO answers how much service must remain available while normal capability is impaired?
MBCO is different from RTO, RPO and MTPD
| Measure | Decision question | Typical expression |
|---|---|---|
| MBCO | What minimum service level must be sustained? | Volume, percentage, priority segment, transaction floor or operating capacity |
| RTO | By when must an activity or resource be recovered? | Elapsed time |
| RPO | How much data loss can be tolerated? | Time or recoverable data point |
| MTPD | How long can disruption continue before impacts become unacceptable? | Maximum elapsed disruption period |
A four-hour RTO does not tell a response team whether 10%, 50% or 100% of customer demand must be served during those four hours. Conversely, an MBCO of 30% does not say when the primary platform must be restored. The measures work together rather than replacing one another.
Derive the service floor from impact evidence
Start with the BIA and identify the product, service or activity outcomes that cannot simply wait for full recovery. Consider safety obligations, statutory deadlines, vulnerable customers, contractual commitments, cash or liquidity needs, operational backlogs and downstream dependencies. The objective should represent the lowest defensible operating level, not an arbitrary percentage selected because it is easy to communicate.
Where demand changes by time of day, season or incident type, a single percentage may be misleading. A better objective may state a minimum transaction volume, priority-customer population, geographic coverage, number of concurrent cases or essential product subset. Record the assumptions behind the figure so it can be challenged when demand or operating conditions change.
Translate MBCO into resources
An MBCO becomes useful only when it can be translated into required capacity. Determine the minimum competent staffing, application access, data, telecommunications, workspace, equipment, supplier support and decision authority needed to sustain the service floor. Identify the bottleneck resource: providing 50% of normal staffing is meaningless if the alternate system can process only 10% of transactions.
- Define the minimum service outcome and measurement unit.
- Identify the customer, product or transaction priorities included in the floor.
- Estimate minimum people and shift coverage, including deputies.
- Confirm technology throughput and alternate-channel capacity.
- Validate supplier, facility, data and identity dependencies.
- Define how queued or deferred demand will be controlled.
Worked example
A customer-support operation normally receives 2,000 cases per day. Its BIA shows that safety-related outage cases and vulnerable-customer requests cannot wait for full platform recovery. Analysis shows approximately 350 such cases on a severe day, with an additional buffer required for incident-driven demand. Management therefore approves an MBCO of 450 priority cases per day. The continuity design assigns 12 trained agents across two shifts, an alternate telephony route, read-only customer data and a controlled manual case register. Lower-priority requests receive an acknowledgement and are queued.
The primary platform has a four-hour RTO. During an exercise the alternate process sustains only 280 cases per day because identity provisioning limits concurrent users. The RTO may still be achieved, but the MBCO is not demonstrably achievable. The organization therefore has a continuity capability gap that requires treatment.
Define activation and exit conditions
Specify when the minimum-service mode is invoked, who can authorize it and how operators know which demand receives priority. Also define the exit criteria. Returning to the primary system does not automatically mean normal service has been restored: backlog, reconciliations, missed commitments and customer communications may continue after technical recovery.
Common mistakes
- Using MBCO as another name for RTO.
- Setting the same percentage for every activity without impact evidence.
- Defining a target that cannot be measured during an incident.
- Ignoring demand spikes caused by the disruption itself.
- Counting staff without checking competence, access and shift endurance.
- Assuming an alternate application has enough throughput without testing it.
- Failing to define what happens to demand outside the minimum service scope.
Evidence and governance
Retain the approved objective, rationale, assumptions, dependency mapping, capacity calculations and exercise evidence. Review MBCO after material changes to demand, regulation, technology, outsourcing or service design. If an exercise shows the objective cannot be sustained, record the shortfall as a capability issue with an owner, due date and re-test requirement rather than silently lowering the target.
Acceptance checks
A decision-grade MBCO should let an independent reviewer answer five questions: what minimum outcome is required, why that level is justified, which customers or transactions receive priority, which resources provide the capacity, and what evidence proves the objective can be achieved for the required duration. If any answer is missing, the objective is not yet operational.
Duration matters
Validate not only the instantaneous service floor but how long it can be sustained. A workaround that processes the required volume for one hour may fail over a twelve-hour shift because of fatigue, consumables, manual reconciliation or supplier limits. State the assumed disruption duration and test endurance at a level proportionate to the risk.
Also confirm how the service floor will be measured during a real incident. Define the source of actual volume, the reporting interval and the person responsible for declaring a shortfall. This turns MBCO from a planning assumption into a live operational control.
Related guidance
Use MBCO operating-level design for detailed capacity construction and the MBCO governance and testing guide for approval and assurance. Connect the result to the BIA and the applicable continuity strategy rather than managing MBCO as an isolated metric.