Industry
Port strike contingency planning: run a control drill
Port strike contingency planning starts with a testable drill for importers: set triggers, owners and evidence, then rehearse a five-day disruption.
What to take away
- A port strike contingency planning drill turns a live disruption into a documented test with named triggers, owners, and evidence.
- Control logic borrowed from process safety fits freighthazard, safeguard, verification, corrective action.
- A corridor plan records candidate gateways and requires carrier, terminal, drayage, and storage checks before any diversion.
- Each drill produces an evidence pack that internal control teams can test on a schedule.
- Capture current quotes for rerouting, drayage, storage, demurrage, and detention; record who obtained each quote and who approves the decision.
Why a port strike drill beats a post-mortem
A post-mortem explains what happened. A drill changes what happens next. The difference is timing and documentation.
A labor action at an East Coast or Gulf port can halt discharge within a day. The International Longshoremen's Association (ILA) and the United States Maritime Alliance (USMX) were central to the 2024 strike, which showed how fast berth windows close. Track actual notices under the current ILA-USMX agreement rather than assuming a generic notice period. The National Labor Relations Act and Labor Management Relations Act (Taft-Hartley Act) provide federal labor-law context, but do not replace checking the agreement's current deadlines with counsel.
A drill runs the disruption on paper, on a schedule, with a stopwatch. It tests the control points a live event would test, without paying demurrage or detention.
OSHA's Process Safety Management standard has 14 elements, but it is not the authority for port labor or customs disruption. Borrow process-control habits such as written procedures, training, and management of change as design analogies; do not treat PSM as a port-strike compliance checklist.
Building the corridor-planning control
The plan needs four columns: trigger, action, owner, evidence. Keep it on one page. If it needs two, cut scope.
Four-column contingency plan
- Triggerstrike vote, 48-hour notice, backlog threshold
- Actionreroute, book drayage, move priority SKUs
- Ownernamed role, not a department
- Evidencebooking confirmation, gate receipt, revised schedule
Triggers are observable: a strike authorization vote, a verified notice under the current ILA-USMX agreement, or a terminal appointment backlog above a defined threshold. Write the source and threshold, not an adjective, and do not substitute a generic notice period for the contract's actual deadlines.
For a tabletop, treat Savannah, Houston, and NY/NJ as candidate gateways, not prescribed alternates. Pair a candidate with the primary port only after the ocean carrier confirms a sailing and the receiving terminal confirms appointments and cutoffs. Check port-level status with the Georgia Ports Authority, Port Houston, or the Port Authority of New York and New Jersey, then verify terminal-specific conditions. Book drayage inside a defined radius, obtain written quotes, and name the carrier and cutoff time. Move priority SKUs to a bonded warehouse only after confirming the customs and storage requirements.
Owners are named roles, not departments. Evidence is the artifact the action produces: a booking confirmation, a gate receipt, a revised delivery schedule.
Before a diversion, have the customs broker confirm how U.S. Customs and Border Protection (CBP) entry filings and port-of-entry details must be handled; retain the broker's confirmation and relevant filing records. Under 19 CFR 144.21, the right to withdraw merchandise entered for warehouse may be transferred by endorsement on the withdrawal form only if the transferee files a bond on Customs Form 301 (warehouse transfer condition). A foreign-trade zone is a separate customs pathway: verify the zone admission and duty treatment under 19 CFR Part 146 with the broker and zone operator before counting it as ready.
Score operational risk with a likelihood-and-impact grid, and record the evidence behind each score. The NIST Cybersecurity Framework can inform general risk prioritization, but it is not the authority for port labor notices, customs entries, terminal appointments, or carrier billing. Assign those checks to the current ILA-USMX agreement, CBP, and the selected terminal.
Example: a five-day drill framework for a Gulf port
Run this sequence in one week, before any labor action is announced.
Five-day Gulf port drill
- Day 1Confirm triggers, name drill controller
- Day 2Simulate berth closure, reroute three containers
- Day 3Test drayage and bonded storage bookings
- Day 4Walk escalation path, note delays over 30 minutes
- Day 5Assemble evidence pack, log corrective actions
- Day 1Confirm the trigger list and name a drill controller who is not the freight manager.
- Day 2Simulate a berth closure at a hypothetical primary port and select a candidate alternate gateway for three inbound containers; record what the carrier and terminal must confirm before the reroute is feasible.
- Day 3Test drayage and bonded storage bookings, capturing confirmation timestamps.
- Day 4Walk the escalation path from dispatcher to director, noting every delay over 30 minutes.
- Day 5Assemble the evidence pack and log corrective actions with due dates.
A drill that produces no artifact did not happen. The artifact is the control.
The output is a folder, not a memo. Include the trigger log, booking confirmations, escalation notes, and the corrective action list.
Control points, triggers, and evidence packs
| Control point | Test | Evidence |
|---|---|---|
| Trigger detection | Does the alert fire within 4 hours of a public notice? | Alert log with timestamps |
| Reroute decision | Is the alternate port named in writing? | Decision record with owner |
| Capacity booking | Is drayage confirmed before cargo arrives? | Booking confirmation |
| Inventory cover | Does safety stock cover the reroute lead time? | Inventory report |
| Cost tracking | Are demurrage and detention accruals recorded? | Accrual journal |
Each row is testable. Each row produces an artifact. Auditors ask for artifacts, not intentions.
For general control documentation, New York audit readiness is a reference, not a substitute for port-specific checks. For a NY/NJ diversion, confirm current port-level status with the Port Authority of New York and New Jersey and appointments and cutoffs with the selected terminal.
A labor disruption also stresses the control limits used to absorb volume surges. Supply chain disruptions test process control explains how Census Bureau trade data feeds control limits and escalation rules.
For broader capacity planning, strategic planning questions can help identify binding constraints. The strike drill itself should rely on verified carrier and terminal confirmations.
