The East and Gulf Coast dockworker strike that began on October 1, 2024, ended after three days, but it showed why technology leaders need a clear view of how port disruptions could affect shipments, suppliers and operations. The strike is over: the International Longshoremen’s Association (ILA) and United States Maritime Alliance (USMX) signed a six-year master contract on March 11, 2025, running through September 2030. The episode remains useful as a continuity-planning case, not as evidence that particular companies or CIOs took specific actions.
What happened in October 2024
The ILA and USMX did not reach a new master contract before their existing agreement expired on September 30, 2024. The ILA began a strike at East and Gulf Coast ports on October 1. On October 3, the parties announced a tentative wage agreement and extended the contract to continue bargaining; workers returned, ending the three-day stoppage. The Department of Labor’s October 3 announcement documented the agreement and return to work.
The affected ports handled more than 68% of U.S. containerized exports and 56% of imports, with daily trade value exceeding $2.1 billion, according to the U.S. Chamber of Commerce on October 4, 2024. Those figures describe trade handled through the ports; they are not estimates of losses caused by the strike. The Chamber’s explainer provides that exposure context.
What the episode shows about preparedness
Coordination extends beyond the port
The Department of Transportation said its Multimodal Freight Office had engaged shippers, ocean carriers, ports, railroads and other supply-chain partners since early summer about the potential impact. This is evidence of advance coordination across the freight network, not evidence of what any individual corporate CIO did. On October 3, Transportation Secretary Pete Buttigieg said the department would continue coordinating with stakeholders to support an orderly return to service and encourage a good outcome in subsequent negotiations. DOT’s statement records both the coordination and the department’s response.
#1 Best Overall
Continuity includes people, equipment and systems
The Port of Virginia described safety and preparation measures, positioning equipment, and checking that operating systems were working in concert. For technology leaders, the practical lesson is that continuity is not just an IT failover question: it can depend on staff, physical equipment and operational systems functioning together. The port’s account describes its own preparations, not a company CIO’s response. The Port of Virginia’s notice outlines those measures.
Exposure depends on cargo and activity
A disruption does not affect every shipment or port activity in the same way. Port Everglades said the labor discussions centered on some containerized cargo operations and distinguished those from petroleum products, aggregate materials, cement and cruise activity. A useful risk assessment therefore needs to identify the specific port, terminal, cargo and operating activity rather than treat all freight as equally exposed. Port Everglades’ statement describes that distinction.
Temperature-sensitive freight needs specific attention
In its historical customer advisory, Maersk warned that a disruption could delay cargo, add costs and create logistical challenges. It singled out reefer containers because terminal monitoring could be affected. For planning, temperature-sensitive freight merits explicit checks of shipment status, monitoring responsibility, carrier communications and contingency options. This was a warning about potential effects, not confirmation that those losses or failures occurred; it is not current carrier guidance. Maersk’s September 30, 2024 advisory gives the historical details.
A practical exposure review for CIOs
The sources establish network-level and port-level preparation, but do not document named CIOs or companies taking particular actions. The following is a planning framework drawn from the episode, not a record of verified corporate responses.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Map dependencies. Identify critical suppliers, shipment origins and destinations, ports, terminals, carriers, and the systems or service providers that supply shipment-status information. Include indirect dependencies where a supplier relies on the same route.
- Measure concentration. Compare how much critical inbound and outbound freight depends on a particular port, route or carrier. Note whether alternatives are genuinely available or merely listed in a plan.
- Classify cargo by consequence. Flag temperature-sensitive goods, time-critical inputs and shipments whose delay could interrupt operations. For each, record the relevant monitoring, handling and escalation requirements.
- Check buffers and switching options. Establish what inventory coverage exists for critical items and how long it would take—and what added cost it would incur—to switch routes or modes. These are decision variables to assess, not universal targets.
- Set status and escalation paths. Decide who receives carrier and supplier updates, how exceptions reach operations and technology teams, and who can authorize a contingency. Test whether the process works when normal visibility systems or contacts are unavailable.
- Rehearse a disruption scenario. Walk through a delayed shipment from the first alert to the operational decision: verify the data, identify affected dependencies, communicate internally, assess alternatives and record who owns each action.
How to compare supply-chain exposure
Use the same dimensions across routes or business units so a plan can be compared on more than the apparent availability of an alternate port.
| Comparison dimension | Question to answer | Why it matters |
|---|---|---|
| Port and route concentration | How much critical freight relies on one port, route or carrier? | Concentration can make a localized disruption consequential across multiple suppliers or products. |
| Cargo sensitivity and time criticality | Would delay, handling conditions or a monitoring gap put the shipment at risk? | Reefer cargo and time-sensitive inputs may need different escalation and contingency plans. |
| Inventory or buffer coverage | How long can operations continue if replenishment is delayed? | Coverage helps frame the time available to resolve a disruption or switch plans. |
| Carrier, supplier and visibility dependencies | Which parties and information systems are needed to detect and respond to a delay? | A backup route is harder to use if status information or supplier coordination is missing. |
| Time and cost to switch | How quickly can freight move by an alternative route or mode, and at what cost? | An alternative is useful only if it is feasible within the operational window. |
What is established—and what is not
The record supports the duration and resolution of the stoppage, the scale of trade handled by affected ports, and examples of government, port and carrier preparation or advisories. It does not establish quantified realized losses, company-specific shortages, or a sector-by-sector measure of economic impact caused by the three-day stoppage. The Chamber’s trade figures indicate exposure, not strike-caused damage.
Rank #4
The labor agreement was later resolved: FreightWaves reported that ILA members ratified the contract on February 25, 2025, and USMX reported that the ILA and USMX signed the six-year master contract on March 11, 2025, through September 2030. FreightWaves’ ratification report and USMX’s signing announcement document those milestones.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
