A recovery team may be proud that a plant has restarted at reduced throughput, while customers are asking why their contracted priority orders still have no reliable delivery commitment. Reduced capacity creates two simultaneous decisions: how to allocate a scarce operational capability and how to communicate consequences to each customer truthfully. Promising normal performance to preserve confidence is likely to amplify later disputes. Effective continuity governance should combine legal obligations, safety, fairness, validated capacity and controlled change to service promises.
An alternative must be an operational control, not a note saying “use paper”
The relevant question is which customer obligations can be fulfilled at the capacity actually available and who may authorize revised commitments. Every exception must remain bounded by safety, contract terms and an accurate customer update.
01Establish the minimum service capacity that is actually available
Record usable people, equipment, materials, facilities, information and service-provider support under current disruption conditions. A headline percentage of normal production can be misleading if the recovered line can make only certain product grades or if quality release staff are unavailable. Describe capacity by deliverable and constraint, including the maximum load the temporary operating method can control safely.
Compare the actual capability with the BIA minimum service requirements and the recovery strategy. If output is not yet demonstrated, call it an estimate and disclose the underlying assumptions to the decision team. A hypothetical commitment should not be passed to sales as a confirmed shipment date. The operations owner must provide an evidence-backed supply position that can be refreshed as conditions change.
Operational capacity. Record product-specific and service-specific constraints, not an overall recovery percentage. Customers may need one high-consequence product that the restarted equipment still cannot safely manufacture. Mark capacity forecasts by confidence and avoid turning a planning assumption into a binding delivery date.
Technical context: ISO 22301:2019 — Business continuity management systems — Requirements (with Amd 1:2024) is one verified source for the concepts discussed here.
02Identify obligations that cannot be deferred unilaterally
Contract terms may specify service levels, order prioritization, notification duties, penalties, force majeure procedures or remedies for non-performance. Regulatory and product-safety obligations may restrict permissible substitutions regardless of customer urgency. Legal or contract management should interpret the applicable language for the relevant jurisdiction; a BCMS plan cannot automatically alter a contractual commitment.
Create a concise obligations view identifying the affected customer, specific duty, action deadline, change authority and required evidence. Distinguish business goodwill commitments from enforceable terms and distinguish approved flexibility from an assumption of flexibility. If a customer asks for an unsafe workaround, escalate the conflict rather than treating customer consent as a substitute for legal or safety compliance.
Contract boundary. Confirm the notice route, potential remedies and authority to vary the agreement before asking sales to make concessions. Customer urgency can justify faster communication, not a unilateral waiver of safety, data protection or mandatory legal obligations.
03Allocate scarce output using transparent decision criteria
Set allocation principles that reflect life and safety, essential services, legal commitments, consequences of delay and agreed contractual priorities. The criteria should be approved by accountable leadership before individual account managers negotiate conflicting promises. Document how exceptions are assessed, including where a lower-revenue customer has a disproportionate safety or community consequence.
Avoid invisible preferential arrangements that use the same capacity twice. Maintain a single allocation view across sites and sales channels, showing committed quantities, confidence level and the effects of each new request. If an urgent exception is accepted, identify which existing commitment must move and who is authorized to make that decision. This converts a stressed allocation conversation into controlled operational governance.
Allocation transparency. A priority exception uses capacity that cannot simultaneously fulfill another customer’s commitment. Record the displaced work and executive rationale. Keep one controlled allocation view across all sales channels to prevent different account managers from independently promising the same output.
04Communicate early with accurate uncertainty
Customers often tolerate a candid limitation better than repeated promises that fail. Explain what has happened to the service, which orders are affected, what the organization is doing, and when the next reliable update will be available. Do not disclose speculative restoration times as confirmed. Keep messages consistent across account managers, customer support and executive contacts.
Use defined approval routes for statements with legal, safety or reputational consequences. Verify contact paths for critical customers without relying solely on failed CRM or email systems. Retain the content and timing of material notifications, but avoid unnecessary disclosure of incident details that could create security or privacy risk. A communication is effective only if the recipient can understand the choice available.
Uncertainty statement. Separate what is known, what is being tested and the next update point. Customers need useful options, not an optimistic restoration date repeated without evidence. Where an incident is still developing, communicate the service consequence rather than unverified technical speculation.
05Control changes to order and service commitments
Where a customer agrees to reduced scope, phased delivery or temporary substitution, capture the precise revised acceptance criteria, period, quantity, location and authorizing parties. Ensure operations receives the approved change and can execute it without ambiguity. A phone conversation does not provide sufficient control if production, logistics and finance act from conflicting versions of the commitment.
Set an expiry or review trigger for temporary terms. When capacity returns, determine whether an earlier concession continues or the original agreement resumes automatically. Maintain traceability from customer communication to the operational instruction and eventual evidence of delivery. This avoids a second dispute caused by a forgotten emergency amendment.
Variation traceability. An approved temporary delivery change should name the affected order, quantities, acceptance method, expiry or review trigger and the people who authorized it. Update production, logistics and finance from the same record so revised promises can be executed consistently.
| Decision domain | Owner or objective | Observable evidence |
|---|---|---|
| Capacity | Operations owner | Validated output by product |
| Obligation | Legal or contract owner | Notification and amendment terms |
| Allocation | Authorized executive | Priority decision and displaced work |
| Closure | Customer account owner | Agreed delivery and backlog proof |
06Monitor performance against the revised promise
Use transaction-level evidence showing on-time delivery of the revised essential service, backlog age, critical customer exceptions and quality conformity. A claim that “most orders shipped” can conceal failures in small but high-consequence segments. Report both aggregate performance and the status of commitments that cannot be safely averaged.
When a revised promise looks likely to fail, notify the customer through the agreed channel before the deadline where practicable. Update the common commitment register and the capacity forecast. Do not allow local teams to remove failed orders from the performance denominator merely because they were affected by an emergency; distinguish original and authorized revised commitments transparently.
Performance distinction. Compare service against the original and the approved revised commitment. Removing disrupted orders from a report can conceal customer harm; counting them as normal failures without context can also mislead. Explain the scope transparently and focus on unresolved priority obligations.
07Restore the relationship after operational recovery
Once normal operations resume, reconcile open orders, credits, replacements, evidence of service and contractual remedies. Customers may have reorganized their own operations around the temporary arrangements. Agree the transition back to standard service explicitly, including which concessions close and which recovery work remains outstanding.
Use customer feedback and contract review to identify where continuity planning underestimated downstream consequences. Investigate whether the same limitations could recur in a different disruption. Leadership should compare the cost of capacity options with the trust, safety and legal exposure created by the reduced service. Continuity is not simply production restart; it is controlled delivery of an acceptable service relationship.
Relationship restoration. On return to normal, reconcile backlog, credits, partial shipments and temporary arrangements. Ask customers about secondary operational impacts they experienced. Their information may show where continuity planning underestimated downstream effects and which service commitments need more robust strategies.
Practical Review Questions
- Do customer statements reflect verified production capability rather than estimates?
- Which contractual or safety duties cannot be changed by a sales conversation?
- Are allocation exceptions transparent about displaced commitments?
- Is each temporary promise reflected in current operational instructions?
Operate a Single Controlled Reduced-Service Commitment Log
Create one view shared by operations, sales, quality and contract owners. Include confirmed available output, customer or product importance, original commitment, required notification, approved revised commitment, accepting parties and next status update. Clearly identify where capacity is forecast rather than demonstrated and where a safety or legal limitation prevents the requested substitution. Require allocation decisions to show the work displaced by an exceptional priority request, so one scarce resource cannot be promised to several customers.
At each capacity review, confirm what can actually be delivered, communicate changes before they become avoidable disputes and reconcile transactions against the approved temporary agreement. Once service stabilizes, agree which concessions expire, which orders remain open and whether customer complaints reveal a neglected dependency. Keep evidence concise but traceable from the decision to the output received.
Closing Perspective
Customer confidence during disruption is earned through verified capability, principled allocation and accurate promises that operational teams can actually fulfill.
References & Further Reading
Official ISO publications informing the continuity method discussed above. Guidance publications provide recommendations; ISO 22301 contains BCMS requirements. The organization must validate any sector-specific legal duties separately.