LA-Long Beach Strike Deadline Slips to Nov 20 as Talks Extend Again

The Analysis

A deadline that moves three times is not a deadline. It is a bargaining chip, and you should read it as one. On 7 November the Pacific Maritime Association and ILWU Local 26 agreed to extend their contract to 20 November, which is the third time the line has been pushed. The earlier dates were 1, 4 and 6 November. Three extensions inside a week is a pattern, and the pattern is the story.

Look at what the dispute is actually about, because the size of the thing will fool you in both directions. It covers roughly 250 security watchmen across six container terminals, about 2 per cent of the twin ports workforce. By headcount that sounds like nothing. By consequence it is a live grenade. If the watchmen walk out and the other longshore workers refuse to cross their picket lines, the PMA warns a stoppage would affect about 85 per cent of Long Beach cargo and 33 per cent of Los Angeles volumes. Two per cent of the people, most of the freight.

Now the number that should be sitting on your desk while you read this, and it is not the strike and it is not the deadline. Rail-bound import dwell at the twin ports reached 7.19 days in September. Remember that figure. It is the reason a three-day delay to a labour deadline matters far less than it looks, and far more, at the same time.

Let me take the extensions apart first, because reading them correctly changes what you do next.

A deadline that repeats is not a countdown to a strike. It is evidence of a negotiation that is still moving, and a negotiation that is still moving is doing one of two things. Either the two sides are close and each extension is the last procedural nudge before a deal, or one side is holding a position and using the clock to make the other feel it. From the outside you cannot tell which, and here is the part people get wrong: it does not matter for your risk exposure. What matters is that each extension resets the clock and leaves your underlying exposure exactly where it was. The port does not get safer because the line moved. Your cargo does not get more protected. All that changed is the date on a document.

There is a mechanical reason the deadline keeps slipping, and it is worth naming because it tells you when the next slip is likely. In this kind of local dispute, the extensions are usually procedural as much as substantive. A mediator wants more time. A side wants a document reviewed. A federal mediator asks both parties to hold off. None of those are progress on the wage or manning question; they are the machinery of a negotiation buying itself room. That is why I do not read extension number three as a signal that a deal is close. I read it as a signal that the machinery is still running, and machinery running is not the same as a problem solved.

The size mismatch is the second thing to get clear. Two hundred and fifty people is a rounding error against the longshore roster, and a forwarder looking at the headcount would reasonably conclude the risk is small. The conclusion is wrong for a reason that is entirely structural. Longshoremen do not cross picket lines, and that habit is not about the watchmen's grievance, it is about their own future contracts. Every other local on that waterfront has an interest in showing that a picket line is real, because their own leverage in their own negotiations depends on the line being respected. So a dispute about 250 watchmen can pull a workforce of thousands, because the 250 are standing in a line that the thousands need to protect. That is why the PMA's 85 per cent and 33 per cent figures are not alarmism. They are arithmetic.

Now the number the wire copy barely touched, and I think it is the one that decides your week. Rail-bound import dwell at Los Angeles and Long Beach was 7.19 days in September. Hold that against the typical dwell you are probably assuming in your planning, which for a healthy import container is measured in a small number of days, and you can see the problem before any strike happens. The ports are already running a queue that is longer than the surface story suggests, and that queue is the thing that turns a labour event from a two-day blip into a two-week hole. When dwell is already at 7.19 days, a three-day disruption does not add three days. It adds three days on top of a system that was already straining, and strained systems multiply, they do not add.

Here is where I stop summarizing and give you the point that is not in any headline. The common assumption is that the deadline slipping to 20 November is good news, because you get more time. The correct assumption is that each extension consumes the buffer you would need if the thing actually broke. And the buffer that gets consumed first is not your cargo's, it is the carrier's contingency tolerance.

Think about how a shipping line manages a strike risk. It does not keep a plan for every day. It makes a decision about whether to reroute, to hold, to slow-steam, to divert to an alternate port, and the decision has a cost and a deadline of its own. Rail carriers and drayage providers do the same. Each time the labour deadline moves, those plans are re-scored, and re-scoring is not free. After enough extensions, the people who have to execute a contingency stop paying full attention, because they have been burned by a deadline that did not materialise, three times now. This is the expense that does not show up on any invoice: attention. By extension number three, the market is tired, and a tired market responds to a real stoppage more slowly than a fresh one.

That is the asymmetry to trade on. There is a version of events where the contract settles on 19 November and everyone congratulates themselves for staying calm, and there is a version where the line is finally crossed on the 21st and the rerouting capacity that would have been available three weeks earlier is no longer available because everyone tried to book it at the same moment. The extensions make both outcomes more likely, not less. That is the trick of a rolling deadline. It lowers the daily drama and raises the tail risk.

Let me be concrete about the tail, because "tail risk" is an abstraction and a missed vessel is not. Suppose you have a rail-bound import programme into an inland US distribution centre, and suppose your normal port-to-door runs on a rail dwell of about four days plus a day of drayage. If a labour action of ten days lands, and the terminals freeze, your containers do not move at all for ten days, and then they join a backlog that is draining at a rate set by terminal productivity and rail capacity, not by the release date of the strike.

Take a modest programme of fifty containers a month, assume one third of them are on that vulnerable rail path, and assume the action adds ten days of dwell plus a week of backlog drain, which is seventeen days on the affected boxes. That is roughly 17 containers times 17 days, call it 289 container-days of extra dwell in one month. Value those containers at thirty thousand dollars of goods each, carry the inventory at twenty per cent a year, and the pure financing cost of the delay is on the order of 289 times 30,000 times 0.20 divided by 365, a little under 5,000 dollars.

Now add the real pain, which is not inventory carrying cost but the expedite premium on the boxes that carry the seasonal goods, the overtime to re-receive a backlog into a warehouse with fixed dock doors, and the demurrage and detention clock that does not pause for a labour action. The number balloons the moment you price the response, not the delay.

Which brings me to the clause everyone should read this week and almost nobody will. Demurrage and detention clocks are set by the tariff, and the standard tariff does not stop for a labour dispute at the terminal. You can be delayed by an event entirely outside your control and still accrue charges from the calendar, not from your ability to pick the box up. The force majeure language in a service contract may or may not cover a labour action depending on how it is drafted, and the difference between "may" and "does" is money. If your contract has a force majeure clause that lists strikes only when they affect the carrier's own operations, a terminal-level watchmen's dispute may not qualify, and you will argue about that after the fact with the fees already on the invoice. Check the clause before you need it. This is the check that costs an hour and can save a five-figure argument.

Now the counterfactual, because a one-sided story is a sales pitch. Suppose the parties settle quietly on 19 November, the watchmen get their language, the line never gets crossed, and all the contingency planning was wasted motion. I would still do the planning, for two reasons. The cost of the planning is low, a few phone calls and a clause review, and the cost of the event is high. And more importantly, the planning you do for a labour action is the same planning you need for the next port disruption, whether it is weather, congestion, a rail outage or a chassis shortage. You are not buying insurance against one date. You are building the muscle to move a box through a different door, and that muscle is valuable every quarter. The wasted-motion worry is what stops people from preparing, and it is the wrong worry. Prepare, and if the deadline slips a fourth time, prepare again, and be glad you did not have to use it.

Hold that against the opposite case, which is the one the rolling deadline makes more likely every time it rolls. If the line is finally crossed on the 21st, the market will discover, all at once, that the contingency capacity it counted on was never reserved, only assumed. The drayage that could have taken your box last week is already spoken for by whoever moved first. The alternate terminal that had space when the risk was theoretical is now a queue. And the rail ramp that had idle capacity is the same rail ramp that is absorbing everything the East Coast gateway cannot handle. In a normal disruption the market has a few days of slack to reorganise. A rolling deadline systematically removes that slack, because it teaches everyone to ignore the warning until the warning is real, and by then the reorganising room is gone.

There is one more layer, and it is the one that catches the careful planner. A lot of importers hedge port risk by routing some volume to the East Coast or the Gulf, and that hedge is only as good as the capacity that exists on the other side. If the whole market makes the same move at the same time, the alternate gateways fill, the rail ramps from the alternate ports back up, and your hedge arrives at a congested door. The peak-season window is exactly when the alternates are already busy with their own seasonal volume. So a diversion is not a free option, it is a capacity purchase, and capacity purchased late is capacity purchased dear. Decide now whether you are going to hold or divert, and understand that the answer for the boxes with hard delivery dates is different from the answer for the boxes with slack.

I want to put one more overlooked point on the table, because it is the kind of thing that only shows up in the aftermath. A strike at the twin ports is not a local event with a local boundary. It is a scheduled service problem that propagates forward, because the vessels that cannot discharge at Los Angeles and Long Beach will be late to their next port, and their next port is somebody else's loading port. The carriers will blank sailings and adjust rotations to recover the schedule, and when they do, the disruption lands on sailings that have nothing to do with the farm gate.

An importer in Europe or a shipper in Asia who never touched a San Pedro Bay container can be on a blanked sailing because the consortium has to rebalance a vessel that got stuck waiting for a berth. That is why the correct reading of a US West Coast labour risk is not "does it affect my port" but "does it affect my service loop", and those are different questions with different answers.

And the least visible cost of all is the one you impose on your own customer. Your delivery promise is the thing you sold, and a labour action converts it from a promise into a negotiation. Once you are late, you are not measuring yourself against the vessel's schedule any more, you are measuring yourself against a customer who has already built your delay into their own commitments, and that customer will remember which supplier warned them first. The shipper who calls a customer on 18 November to say "there is a risk on your boxes and here is my plan" and the shipper who calls on 24 November to say "there was a strike" are selling the same late box, but only one of them keeps the account.

So what do you do with a deadline that has moved three times. You roll your hedge with the deadline, and you do it on the calendar, not on the news.

Re-run your port-risk assessment every time the labour deadline moves, not once. Put a recurring task on the calendar for the day after each announced extension. Three days of forward notice, every time, is worth more than one big review that goes stale. The 20 November date is the next marker; the review should be scheduled for the 19th so the decision is made before the news is old.

Identify the cohort of containers that genuinely cannot miss its delivery date, and treat those differently from the rest. The ones with hard commitments get an alternate routing decision now, while the alternates are still bookable, and the ones with slack stay put and wait. Do not treat a mixed book as one book.

Get your force majeure, demurrage and detention terms in front of you. Confirm in writing whether a terminal-level labour action triggers your force majeure protection, and confirm whether the demurrage and detention clock pauses for a labour action. If it does not, plan to pull boxes to a transload point rather than let them sit and accrue. Ask the carrier the question in writing and keep the answer, because the party who has the answer in an email before the event is the party who wins the argument after it.

Keep a live account and a live relationship on at least one alternate gateway, and test it with a small volume, because an account you have never used is not a fallback, it is a phone number.

And watch the thing that tells you the real story, which is not the deadline but the dwell. If the median rail import dwell at the twin ports moves up from the September 7.19 days while the deadline is still slipping, the system is telling you that the buffer is being eaten. The deadline is a headline. Dwell is the invoice.

Do those things and a rolling deadline becomes a rolling opportunity to be ready, and you stop confusing a moving date with a solved problem. Skip them and you will learn the difference between a deadline and a decision the hard way, at the gate, on day three of a stoppage, watching the demurrage clock tick on boxes you could have moved last week. Show me the number, not the feeling, and this week the number is 7.19 days of dwell, a third extension, and about 250 people who can stop 85 per cent of Long Beach cargo.

↑ Back to the key points

— By Vivian Zhao