Caracal Intelligence

Practical guide

Supply chain resilience: a disruption response checklist.

Supply chain resilience is the ability to prepare for disruption, maintain critical supply, and recover when conditions change. Start with the parts, sites, and routes that your customer commitments depend on.

By Caracal Intelligence · Published · Updated

How risk intelligence supports disruption prevention

Risk intelligence connects an external event with a possible business effect. Supply chain visibility shows known suppliers, stock, and shipment status. Resilience also needs a tested response, an action owner, and available resources.

A warning cannot stop every strike, storm, or system outage. Use it to reduce avoidable delays and losses. Confirm the evidence before you change a shipment, approve extra cost, or use an alternate part.

The UK resilience framework puts supply chain data at the start of this work. The OECD review also stresses the ability to respond and adapt. The checklist below is Caracal's practical application of these principles.

What is a supply chain disruption?

A supply chain disruption is an event that interrupts the planned flow of goods, materials, information, or services. It can affect supply, production, transport, or delivery. A disruption becomes relevant to your business when it affects a dependency or commitment.

Common causes and the first check

Use these examples to start a review. They are possible scenarios, not reports of current incidents.

Supplier or factory failure

Check the affected part, confirmed output, available stock, and approved alternate source. Ask whether another supplier uses the same upstream site.

Port, border, or route delay

Confirm the affected shipment and route with the carrier. Check alternate capacity, transit time, and the final delivery connection.

Severe weather or power loss

Check site status, access routes, and local notices. Confirm when usable production or transport service can resume.

Cyber incident or service outage

Identify the order, booking, warehouse, or payment process that depends on the service. Use the approved continuity procedure and verify recovery.

NIST's manufacturing guidance identifies delivery delays, transport constraints, shortages, single-supplier dependence, and limited visibility as supply chain challenges. The checks above are Caracal's suggested starting points.

From prevention to recovery

Before an incident, qualify alternatives and test the plan. When a warning appears, verify the event and your exposure. During disruption, use approved actions and check the remaining stock and delivery time. After service returns, clear the backlog and review what failed.

Six checks for a supply chain disruption

Use one record for each affected part, product, or service. Record the source, check time, responsible person, decision deadline, and next action.

  1. 1. Identify the critical dependency

    Link the supplier site to its part, receiving site, transport route, and customer order. Identify a single source or shared transport link. Mark unknown upstream suppliers as unknown.

    Record: part or service, site, route, order, and the person who can confirm each link.

  2. 2. Check the event and its timing

    Read the original operator notice, official update, or supplier statement. Separate the event time from the report time. Check whether the event affects the named site or route. Record what is still unconfirmed.

    Record: source link, event time, check time, confirmed effect, and evidence limits.

  3. 3. Calculate the time available

    Check usable stock and demand. Exclude stock that is reserved, damaged, or awaiting release. Compare stock cover with the earliest confirmed replenishment date. Include transport, customs, and quality checks in that date.

    Record: usable units, units required per day, expected receipt, and the next customer deadline.

  4. 4. Test the response options

    Compare an alternate supplier, route, transport mode, or production plan. Confirm capacity, arrival time, quality approval, and total cost. Check whether the alternate option depends on the same port, site, or upstream supplier.

    Record: confirmed capacity, approval owner, cost, constraints, and the last useful decision time.

  5. 5. Assign and approve the action

    Give each action to a named person. Use the agreed approval limit. Tell affected operations and customer teams what is confirmed, what can change, and when the next update is due.

    Record: decision, owner, approval, due time, and communication status.

  6. 6. Confirm recovery

    Check actual receipt, usable output, and overdue orders. A reopened route does not prove that your backlog is clear. Close the incident when agreed service conditions are met. Update the plan with the limits found during the response.

    Record: receipt evidence, remaining backlog, extra cost, and the plan changes required.

Illustrative example

Will stock last until the next delivery?

This is a planning example with invented inputs. It is not a customer result or a forecast.

Usable stock
1,200 units. Reserved and blocked stock is already excluded.
Demand
200 units each day, including weekends.
Stock cover
1,200 ÷ 200 = 6 days at this demand rate.
Next usable receipt
8 days from the same start time. No other receipts are expected.

The possible gap is 8 − 6 = 2 days. At 200 units per day, 400 units are at risk. This calculation assumes constant demand and no loss of usable stock. Recalculate it if either input changes.

The planner must confirm the receipt date. The buyer must check an approved alternate source or partial delivery. Operations must check whether the production plan can change. Set the action deadline from the lead time for the chosen response.

Measure response and recovery

Agree the definitions before a test or incident. Compare similar products, routes, demand levels, and time periods.

Time to verify
Elapsed time from the first recorded signal to a documented exposure check. A rejected signal still needs a reason.
Time to decide
Elapsed time from confirmed exposure to an approved response. Record waiting time for cost, quality, or customer approval.
Recovery time
Elapsed time from service loss to the agreed service level. State the start condition and the recovery condition.
Delivery and cost effects
Count affected orders, late units, and recorded extra cost. Keep estimated losses separate from actual costs. Do not call every warning a prevented disruption.

Use the right evidence for the decision

Manufacturing teams need part and quality data. Logistics teams need confirmed route and capacity data. Procurement teams need approved supplier options. A public briefing provides event context. It cannot confirm a private order, supplier relationship, or delivery promise.

Recent security briefings

Read dated events, possible effects on trade, and practical checks. Each briefing states its review period and source limits.

Read all security briefings

Sources and limits

Sources and claims checked on (UTC). These sources support the general principles. The checklist, example, and measurement definitions are Caracal's practical guidance.

  • DBT supply chains resilience framework

    UK Department for Business and Trade · Published

    The framework identifies five options: supply diversity, international cooperation, stock and reserve capacity, domestic production, and demand management. It places data and visibility under all five options.

  • OECD Supply Chain Resilience Review

    OECD · Published

    The review supports fast responses, the ability to adapt, and cooperation across supply chains. It also finds that a move to domestic supply does not always improve resilience.

  • Building Resilient Supply Chains: Strategies and Successes for Manufacturers

    National Institute of Standards and Technology · Published

    Manufacturing guidance on delivery delays, transport constraints, shortages, supplier dependence, and visibility.

Use current supplier and operator information for a live decision. Confirm regulated changes with the responsible specialist. This guide does not establish compliance or guarantee that a disruption can be prevented.