Approximately 250 watchmen sit between two of the busiest United States ports and the cargo moving through them. That is the useful starting point for understanding the Local 26 dispute. Their number is small beside the volume around them, which is why access and dependency matter more than a simple headcount. A small group at a shared control point can affect many schedules when the next handoff depends on that point remaining open. Longshore workers and marine clerks could choose to honor a picket line, while rail and truck operations would feel the consequences through delayed access and appointments. The immediate issue is terminal security, yet the planning question is broader: how much recovery time does a critical shipment have if work at the terminal slows?

One contract, several terminal dependencies

The contract at issue covers Local 26 watchmen. Their prior agreement expired in July 2025. That agreement is separate from the coastwide longshore and marine clerk contract, which runs through 2028. Federal mediation is continuing. Other ILWU members may honor a picket line, so vessel work, yard moves and gates could be affected even though those workers are covered by another contract. That possibility deserves planning attention, but it does not describe a coastwide strike.

Terminal security also has a narrower meaning than general port protection. Watchmen provide security at six container terminals, according to the Pacific Maritime Association, or PMA. PMA estimates that those terminals handle roughly 85% of Long Beach cargo and 33% of Los Angeles cargo. It also estimates that the watchmen represent about 2% of the ILWU workforce at the two ports. Those percentages describe terminal exposure, not predicted cargo loss. They show where a stoppage could interrupt access if other ILWU members honor the line.

The distinction matters for customers. A security dispute does not mean the entire port is unguarded, and it does not mean every container would stop moving. It does mean that a terminal dependent on coordinated labor can lose its normal rhythm quickly. A planner should therefore check the specific terminal, the expected discharge window and the next rail handoff instead of applying a national or portwide assumption to every order.

Queues leave less room for recovery

The Port of Los Angeles operations report dated October 26 recorded 19,626 individual import containers on terminal awaiting on dock rail service. Of those, 8,133 had been there for nine days or more. The figures are containers, not TEU, and they are a dated snapshot rather than a count of every late container. The report shows how much terminal space and rail work may already be committed before any labor interruption.

Restart and recovery are different events. A gate or yard can reopen while older containers still need priority clearance. New containers may then wait for space, appointments or a confirmed train plan. Rail service depends on the terminal presenting the right box at the right time, so a pause can leave equipment and handoffs out of sequence. The watchmen headcount cannot tell a shipper how long that queue will take to clear.

In a hypothetical shipment review, a critical order is booked through Los Angeles and has little delivery buffer. The planner could ask the supplier and customer whether the delivery commitment can be adjusted, rather than assuming the supplier can simply change the consignee arrival. The alternative could be a booking change or another inventory action, if space, equipment and documents are available. The choice should reflect the order’s value, the cost of a missed date and the margin left after discharge.

That review should also identify what can be reversed. Asking about a revised delivery commitment may preserve flexibility. Changing a booking can create charges and another sequence of handoffs. Neither action is automatically right. The decision becomes specific when the team compares those costs with the shipment’s actual dependence on terminal access and rail release. A theoretical alternative offers little protection if the carrier cannot confirm it.

Make the response shipment specific

Start with the next critical shipment, not with a broad instruction to reroute everything. Record its planned terminal, discharge window, rail destination, promised delivery date and the cost of missing that date. Ask the carrier, forwarder or logistics provider what can change, by when, and with what confirmed capacity. Then assess customer criticality. A shipment supporting a production line or a hard customer commitment may deserve earlier protection than routine replenishment.

Set one review owner and a clear trigger. For a Los Angeles order, the trigger might be a change in terminal access, a missed rail plan or a dwell update that removes the delivery buffer. If work resumes, confirm the restart clearance priority and the rail plan at shipment level. That check is more useful than treating reopening as proof that the schedule has recovered. The practical action is to review the next critical order today and choose whether to hold the commitment, change the booking or protect inventory based on verified recovery slack.