A useful logistics contingency plan names the essential flow, activation trigger, decision authority, feasible alternatives, operating constraints, communications, and recovery test.

A carrier contact list is not a logistics contingency plan.

Neither is a slide that says “use alternate routes,” “add inventory,” or “expedite.” During a disruption, the alternate carrier may not be approved, the route may carry the same physical dependency, the backup warehouse may not have system access, and the expedited option may miss the customer's last usable recovery point.

Use a stricter definition:

A contingency is real only when a defined trigger gives a named person authority to move an essential flow through a feasible alternative under known operating, legal, commercial, and data constraints.

The objective is not to predict every disruption. It is to prepare reusable decisions before information becomes scarce, capacity tightens, and every team competes for the same recovery resource.

Define the essential flow

Start with what must continue or recover—not with a list of hazards.

An essential logistics flow might be:

  • raw material feeding a constrained production line;
  • medicine, food, or another time- or condition-sensitive product;
  • service parts supporting critical equipment;
  • high-volume customer replenishment;
  • export cargo approaching a cut-off;
  • an import needed before inventory exhaustion;
  • parcel or final-mile volume tied to a stated customer promise;
  • return flow required for repair, reuse, compliance, or customer credit.

Describe each flow as an operating chain:

origin → release condition → facility → transport leg → transfer node → final facility or customer → evidence and settlement

Then document:

  • product or commodity;
  • volume and demand pattern;
  • origin, destination, and transfer nodes;
  • mode, equipment, capacity, and handling;
  • normal lead time and variability;
  • inventory position and time to consequence;
  • customer or production commitment;
  • temperature, hazardous-material, security, customs, or other control;
  • primary providers and legal roles;
  • systems and data required;
  • payment, credit, or financial dependency;
  • maximum tolerable interruption;
  • minimum acceptable degraded service;
  • recovery point and recovery-time objective for the operating process.

FEMA's 2024 update to the Continuity Guidance Circular frames continuity around essential functions, delegations of authority, vital records, alternate strategies, communications, training, and exercises. A commercial logistics plan does not need to copy a government continuity program, but those elements expose the weaknesses of a plan built only around vendor phone numbers.

Map dependency, not just geography

Two routes are not redundant if they depend on the same bridge, terminal, carrier dispatch system, fuel source, customs release, warehouse labor pool, or upstream supplier.

For each essential flow, map dependencies in six layers:

  1. Physical: facilities, roads, rail ramps, ports, airports, crossings, yards, power, fuel, and equipment.
  2. Provider: carrier, broker, forwarder, warehouse, terminal, subcontractor, and critical local vendor.
  3. Inventory and capacity: safety stock, production timing, trailer or container pool, labor, dock, staging, and storage.
  4. Information: order release, tender, tracking, appointment, customs, warehouse, billing, identity, and communication systems.
  5. Authority and compliance: contracts, permits, operating authority, insurance, licenses, product rules, hazardous-material duties, and customs status.
  6. Financial: credit limits, prepayment, emergency buying authority, claims, fuel, accessorials, and cash required to operate.

CISA's infrastructure dependency guidance emphasizes dependencies, secondary providers, continuity, and critical supplies. Apply the same skepticism to logistics alternatives. “Second carrier” is not resilience when both rely on the same small pool of owner-operators or the same closed facility.

Record single points of failure and concentration:

  • one site performing a unique compliance or packaging step;
  • one person able to approve emergency spend;
  • one interface that releases all tenders;
  • one transload or cross-dock with the required equipment;
  • one customer appointment channel;
  • one broker or carrier controlling most recovery capacity;
  • one source for refrigerated, hazmat, bonded, or oversize capability;
  • one identity or payment process that cannot operate offline.

The current U.S. Department of Transportation National Freight Strategic Plan explicitly includes identifying single points of failure, increasing redundancy and rerouting capability, and strengthening preparedness, response, and recovery. A company plan should bring that logic down to actual loads, facilities, providers, and decision rights.

Set trigger levels before the disruption

“Activate when needed” delays action until every option is worse.

Use observable trigger levels:

Level Example condition Operating posture
Monitor Credible threat or performance deterioration; no committed shipment affected Confirm data, inventory, contacts, and alternatives
Prepare Essential flow likely to be affected inside the planning horizon Hold capacity, stage inventory, adjust appointments, notify decision owners
Activate Commitment or control threshold crossed Execute approved alternative and customer or facility communication
Stabilize Degraded flow operating under contingency Monitor constraints, cost, safety, service, and depletion
Recover Primary or redesigned flow meets return criteria Reconstitute deliberately; release temporary capacity and reconcile records

Triggers should connect to consequence:

  • hours of production inventory remaining;
  • number of customer orders at risk;
  • facility downtime estimate;
  • missed terminal, sailing, flight, or appointment cutoff;
  • road, bridge, port, rail, or air closure affecting the active path;
  • carrier failure, cyber outage, or identity concern;
  • temperature, seal, security, or custody anomaly;
  • loss of required data or release authority;
  • forecast demand exceeding committed capacity;
  • dwell or storage clock approaching a commercial threshold.

Use both leading and confirmed triggers. A forecast can justify preparation; a verified closure may justify activation. Preserve who declared the trigger, source, time, affected scope, and next review.

The freight-visibility workflow should deliver these signals with provenance and latency. Do not allow an unverified social post or ambiguous map alert to redirect controlled freight.

Give someone authority to act

Contingency plans often name responsible departments but not a decision maker.

For every playbook, identify:

  • incident owner;
  • transportation decision authority;
  • product, quality, safety, customs, or security authority where relevant;
  • emergency procurement and spend limit;
  • customer-commitment authority;
  • communications owner;
  • legal, insurance, or executive escalation;
  • primary and backup for each role;
  • succession if systems or normal leadership are unavailable.

Define which actions are preapproved:

  • tender an alternate carrier;
  • use spot or expedited capacity up to a limit;
  • change mode or route;
  • move inventory between facilities;
  • authorize overtime, weekend work, or temporary storage;
  • reschedule customers;
  • prioritize or allocate constrained inventory;
  • stop a shipment for safety, security, or product review.

A plan that requires an unavailable executive to approve every premium truck is a waiting procedure, not a contingency.

Write playbooks around decisions

Each playbook should fit on a page before its detailed references.

Include:

  1. Purpose and scope: which essential flow and consequence it protects.
  2. Activation trigger: observable condition and source.
  3. Authority: who activates, spends, changes commitments, and stops work.
  4. Current-state data: shipments, orders, inventory, capacity, people, systems, and constraints.
  5. Immediate containment: what prevents the problem from growing.
  6. Alternatives in priority order: provider, mode, route, facility, inventory, or service choices.
  7. Eligibility and controls: what must be verified before each alternative is used.
  8. Commercial logic: rates, premiums, credit, accessorials, and approval.
  9. Communications: who needs which message and update cadence.
  10. Evidence: events, decisions, documents, and costs to retain.
  11. Exit criteria: conditions for stabilizing, returning, or redesigning the flow.

Use checklists for execution, not vague advice. “Find another carrier” should become:

  • identify approved carrier or broker for the lane and service;
  • authenticate the legal entity and contact through known channels;
  • verify current authority, insurance, equipment, driver and facility fit;
  • transmit the complete tender and special controls;
  • receive explicit acceptance;
  • validate pickup identity;
  • set milestones and escalation;
  • record premium and approval.

The existing carrier-vetting gate, routing-guide fallback logic, and freight-fraud controls should remain in force under pressure. An emergency is when identity shortcuts are most expensive.

Build scenario families

Do not write one playbook for every imaginable event. Build reusable families around the operating failure.

Facility loss or constraint

Examples include power loss, fire, labor shortage, equipment failure, cyber outage, contamination, structural damage, or access restriction.

Decisions:

  • hold, divert, or stop inbound freight;
  • shift work to another qualified facility;
  • stage trailers or inventory safely;
  • change appointments and customer commitments;
  • restore system, labeling, temperature, security, or regulatory controls;
  • manage labor and yard capacity at the alternate site.

Verify that the alternate facility can perform the actual work. A warehouse with open square footage may lack racking, dock geometry, food registration, hazmat capability, bonded status, labor, packaging, WMS data, or customer authorization.

Provider or capacity failure

Examples include carrier shutdown, tender collapse, driver shortage, broker fraud, insurance cancellation, strike, financial distress, or widespread peak demand.

Decisions:

  • activate secondary and recovery providers;
  • prioritize lanes or products;
  • consolidate or defer eligible shipments;
  • use alternate mode or equipment;
  • change service promise;
  • source short-term capacity within an approved premium.

A recent freight RFP and carrier scorecard can expose feasible alternatives. A provider that never passed onboarding, integration, or trial loads is a prospect, not standby capacity.

Infrastructure and weather disruption

Examples include bridge or highway closure, severe weather, wildfire, flood, port closure, rail service interruption, airspace constraint, or border congestion.

Decisions:

  • reroute around the affected dependency;
  • change mode or transfer point;
  • hold freight at the safest qualified node;
  • change operating window;
  • protect equipment, driver time, product, and customer appointments;
  • account for permits, route restrictions, and fuel.

Do not tell a driver or carrier to improvise an oversize, hazmat, high-value, or temperature-controlled route. Use the applicable controls in the oversize and overweight guide, hazmat responsibility map, and cold-chain operating plan.

Technology or cyber disruption

Examples include TMS, WMS, ERP, EDI, telematics, identity, payment, email, or vendor outage; ransomware; account takeover; and corrupted shipment data.

Decisions:

  • isolate affected systems;
  • move essential work to a tested manual or alternate channel;
  • authenticate instructions outside compromised communications;
  • protect tender, pickup, delivery, product, and payment evidence;
  • reconcile transactions after restoration;
  • communicate without spreading unverified information.

CISA recommends that leadership identify systems supporting critical business functions and test continuity after a cyber intrusion. NIST's Cybersecurity Supply Chain Risk Management practices also address supplier and service resilience. Include logistics technology providers and integrations in the dependency map, not only internal infrastructure.

Border, terminal, or regulatory hold

Examples include customs hold, missing release, inspection, terminal closure, documentation defect, rejected filing, embargo, or sudden operating restriction.

Decisions:

  • identify the controlling agency, carrier, terminal, broker, or document;
  • correct the record through the authorized party;
  • protect free time and storage;
  • hold or redirect connected transport;
  • communicate realistic release uncertainty;
  • avoid unauthorized movement.

The customs-broker and forwarder handoff and drayage control model identify owners that a generic emergency team may otherwise confuse.

Demand or supply shock

Examples include promotion overrun, supplier loss, customer surge, product recall, allocation, or sudden inventory imbalance.

Decisions:

  • prioritize customers, products, and orders;
  • change replenishment cadence;
  • pool, consolidate, expedite, or defer;
  • move inventory;
  • change sourcing or production;
  • align the commercial promise with constrained capacity.

Premium freight is not the first answer to every shortage. Use the expedited-freight decision framework to compare recovery cost with shutdown, inventory, service, and handoff consequences.

Prequalify alternatives

An alternative should have a current readiness record:

  • legal entity and role;
  • authority, insurance, license, permit, or qualification;
  • contract or emergency commercial terms;
  • lane, equipment, commodity, and operating capability;
  • contact authenticated through known channels;
  • data and tender method;
  • facility, customer, and product approval;
  • test or prior operating evidence;
  • weekly and surge capacity;
  • lead time to activate;
  • known shared dependencies.

For facilities, include system configuration, master data, labels, inventory method, labor, utilities, security, regulatory status, and physical flow. For alternate modes, include the new handling, packaging, transit, cutoff, claims, and custody model.

Pay for options consciously. Trailer pools, reserved capacity, extra inventory, alternate suppliers, dual systems, and secondary facilities all have carrying cost. Compare that cost with the consequence and recovery-time objective they protect. “Free redundancy” often means uncommitted capacity that will not be available during a market-wide event.

Preserve commercial and operational evidence

Disruptions generate premium charges, disputed appointments, cargo exceptions, emergency purchase orders, customer credits, and claims.

Record:

  • trigger and activation decision;
  • provider offers and acceptance;
  • rate, fuel, premium, and accessorial terms;
  • shipment and product instructions;
  • route, mode, facility, and appointment changes;
  • custody and condition events;
  • customer communications;
  • mitigation decisions;
  • invoices and approvals;
  • recovery and return-to-normal decision.

The controls in freight audit and payment, accessorial management, and freight claims still apply. A contingency approval should accelerate a bounded decision, not eliminate the record.

Exercise the plan

Ready.gov recommends developing business continuity, communications, emergency response, and IT recovery plans together rather than treating them as isolated documents. Its business emergency-planning guidance is a useful baseline for cross-functional exercises.

Run at least three kinds of test:

  1. Tabletop: decision owners work through a credible scenario and reveal missing authority, data, contacts, or choices.
  2. Functional test: tender an alternate provider, restore a data export, contact an alternate facility, or execute the communication path without moving live freight.
  3. Controlled operating test: move a bounded shipment or order through the alternate route, facility, provider, or system.

Inject complications:

  • primary decision maker unavailable;
  • email compromised;
  • alternate carrier already full;
  • customer refuses the new appointment;
  • product cannot use the assumed facility;
  • disruption lasts longer than forecast;
  • two essential flows compete for the same capacity;
  • fuel, detention, or storage cost exceeds the approval;
  • recovery creates a second backlog.

Measure detection, activation, time to decision, time to stable flow, service protected, inventory consumed, premium spend, safety or compliance deviations, data completeness, and recovery time.

Define recovery before activation

Returning too early can create a second disruption. Remaining on a contingency too long can create avoidable cost and control drift.

Set recovery criteria:

  • primary capacity and facility are stable for a defined period;
  • systems and integrations are restored and reconciled;
  • backlog and inventory position are understood;
  • product, safety, security, customs, and customer controls are confirmed;
  • temporary providers and sites can be released without stranding freight;
  • appointments and commitments are reset;
  • invoices, claims, and records are captured;
  • leadership accepts residual risk.

Reconstitution needs an owner and sequence. Decide which flows return first, how duplicate orders or tenders are prevented, how inventory in alternate nodes is reconciled, and when emergency authority ends.

Within days, hold an after-action review. Separate:

  • what happened;
  • what the plan predicted;
  • which trigger fired;
  • which action worked;
  • which dependency or assumption failed;
  • what decision took too long;
  • what permanent network change is justified;
  • who owns the correction and test date.

Update the playbook while evidence is available.

What preparedness looks like

Logistics resilience is not the number of alternatives on a slide. It is the number of essential flows that can move through a tested alternative before the business consequence becomes irreversible.

Define those flows. Map shared dependencies. Establish leading and confirmed triggers. Delegate authority. Write decision playbooks. Prequalify providers, facilities, modes, systems, and commercial terms. Preserve evidence. Exercise the ugly cases. Set return criteria before the emergency.

When disruption arrives, the team should not be debating who can act or discovering whether the backup is real. It should be selecting among prepared tradeoffs with enough time left to change the outcome.

Use the UniteCargo logistics directory to identify potential carriers, brokers, forwarders, warehouses, customs brokers, 3PLs, and last-mile providers—then qualify and test them before treating them as contingency capacity.

Sources and further reading

Supply Chain