Defining Minimum Acceptable Service Levels During a Crisis

01Define the service from the customer or beneficiary perspective

Start with the essential outcome rather than a technology component or departmental activity. A payment service may need to settle a defined class of urgent transactions; a clinic may prioritize critical medication access; an industrial supplier may maintain emergency spares. Describe the service boundary, qualifying recipients and the performance characteristic that determines success. This limits the temptation to promise full normal operations when resources are constrained.

Get agreement from accountable process owners and the functions responsible for affected safety, regulatory and contractual obligations. Not all commitments can be reduced unilaterally during a crisis. Record what requires advance customer consent, formal notice or a regulatory determination. Any proposed reduction must be evaluated against the exact applicable terms.

For a logistics service, “maintain deliveries” can mean everything from full national distribution to releasing a few urgent healthcare consignments. Specify the defined customer class, order status, release criteria and communication promise. Frontline operators should know which requests qualify without needing to interpret broad executive statements. The contract team should confirm whether a reduced offer is permitted or requires consent.

Technical context: ISO 22301:2019 — Business continuity management systems — Requirements (with Amd 1:2024) is one verified source for the concepts discussed here.

02Choose an achievable minimum output and duration

Define a measurable capacity or service envelope: transactions accepted, priority requests fulfilled, permitted operating hours, response channels or maximum safe load. Couple this to an assumed duration and expected demand. A workaround that supports the first shift may fail after several days because stocks, employees or controls are exhausted. It is not enough to show that the first transaction was completed.

Use the business impact analysis to understand the consequence of reducing service and the strategy assessment to determine feasible capacity. Document uncertainty rather than publishing arbitrary percentages. If a target depends on a third-party supplier or substitute location, test the capacity with that party.

Build capacity estimates from the limiting resource rather than average production output. A manual team may prepare many dispatch forms but only one qualified person can approve refrigerated goods. This creates a hard throughput ceiling. Test the system at that constraint and consider how fatigue or delayed replenishment changes the sustainable rate over several shifts.

03Protect mandatory integrity and safety controls

Minimum service does not mean minimum diligence. Identify approvals, traceability, medical, environmental, security and quality checks that must remain in place. A manual workaround may need additional segregation of duties or post-event reconciliation to compensate for automated controls. If a control cannot be maintained, the organization may have to suspend the affected service rather than continue unsafely.

Process owners should define stop conditions. Examples include missing essential customer identification, inability to protect temperature-sensitive material or absence of a qualified operator. State who can halt activity, who must be notified and how the decision is preserved. A service-level plan should make it easier to say no to an unsafe request under pressure.

Write the safeguards as stop rules. For example, if serialization or temperature history cannot be verified, a regulated product may need to remain on hold. Make it clear that the continuity coordinator cannot waive a legal qualification requirement merely to reach a capacity target. Build alternatives for verification, but never replace a required technical judgment with an undocumented emergency exemption.

04Design priority and fairness rules before demand spikes

If the reduced service cannot cover everyone, decide how requests are prioritized. Consider objective urgency, vulnerability, contractual obligations and legal duties. Avoid relying solely on a salesperson’s influence or the order in which demands reach an overloaded inbox. Describe how frontline employees apply the rule and how disputed cases are escalated.

The policy should be understandable to customers and staff. Where emergency rationing or access rules are governed by public authorities, those requirements prevail. Maintain an exception route for unforeseen critical cases without making it so open-ended that priority criteria lose meaning.

Fairness rules need an appeal mechanism as well as a ranking. A routine customer might present a genuinely urgent medical or safety need that the initial eligibility list omitted. A small accountable panel can review the exception against consistent criteria. Record why the request was accepted or deferred so that pressure from powerful accounts does not silently displace more urgent needs.

05Define communications as part of the service

Degraded service includes how customers learn what is available, what has changed and when the next update will arrive. Prepare approved message components for interruption, alternative access, expected limitation and unresolved uncertainty. Do not give invented restoration times to make a message sound reassuring. Acknowledge commitments that remain binding and explain the route for urgent escalation.

Assign authorized spokespersons and establish communication channels independent of the disrupted platform where possible. Align the public message with the real operating capacity. A service statement promising normal fulfillment while the continuity team has stopped receiving orders creates further exposure and erodes trust.

The reduced service statement should include a channel for verifying requests and updating expectations. Avoid promising a normal response time when staff are using paper forms and alternative phones. Use planned update times instead of unsupported restoration predictions. The communications team should have the same capacity information as the employees performing the service.

06Exercise the degraded mode through an end-to-end transaction

Choose a realistic interruption such as loss of the order system, an unavailable site or a sudden surge in requests. Ask staff to process a qualifying case from initial contact to final accepted result, including approvals, records and customer notices. Measure whether the intended minimum is achievable without compromising mandatory controls. Exercises should reveal awkward handoffs rather than simply confirm that people know the plan exists.

Assess how long the workaround can continue and what triggers a change or termination of that mode. Include recovery of normal systems and reconciliation of temporary records. ISO 22301 supports planning for predefined acceptable capacity during disruption, but the organization must choose and validate its specific operating parameters.

An exercise should include a transaction that must be refused. Successful refusal with clear reason and escalation is evidence of control maturity. Also test how the temporary service is communicated and whether the customer can access it in practice. A technically functioning fallback that no customer knows how to reach does not satisfy the minimum service objective.

07Govern exit and return to normal

Restoring technology does not by itself justify declaring normal service. Require the process owner to verify data integrity, backlog handling, staffing and customer communication before changing operating status. Keep a decision log recording why the organization entered degraded mode, the conditions under which it operated and the acceptance evidence for ending it.

Review whether the minimum service was actually valuable: Did it protect priority beneficiaries, prevent safety harm, preserve legal duties and avoid unacceptable consequences? Where it failed, adjust recovery resources or the service promise. An honest minimum is preferable to an optimistic but unexecutable continuity statement.

The return-to-normal gate should distinguish system restoration, transaction reconciliation and customer service recovery. The process owner may accept the system while still having a backlog of unresolved priority requests. State what residual backlog is tolerable and who approves the transition. Preserve the degraded-service decisions to explain later customer inquiries or corrective actions.

Closing Perspective

Minimum acceptable service is a governed compromise between urgency and capability. It becomes credible when the service boundary, controls, priorities and exit conditions are explicit and repeatedly demonstrated.