FreightWaves reported on October 28 that approximately 250 watchmen represented by International Longshore and Warehouse Union Local 26 have authorized a possible strike at the ports of Los Angeles and Long Beach beginning as early as 5 p.m. Pacific on Sunday, November 1. The Pacific Maritime Association, which represents employers, said negotiations are continuing with federal mediators and that it remains committed to bargaining through the deadline and beyond. The strike has not begun, and a work stoppage is not certain. The potential impact could exceed the size of the watchmen unit because employers expect other ILWU workers may honor picket lines. PMA said the affected facilities handle roughly 85% of Long Beach cargo and 33% of Los Angeles cargo, so vessel, yard, and truck-gate operations at those terminals could be disrupted. The Local 26 agreement is separate from the coastwide contract covering longshore workers and marine clerks through 2028. The threat also arrives while the port complex is managing a large backlog of import containers awaiting inland rail service, increasing the importance of terminal-specific verification rather than broad assumptions about the entire gateway.
About 250 union watchmen could strike at Los Angeles–Long Beach terminals from 5 p.m. Pacific on November 1 if ongoing negotiations do not produce an agreement.
- Treat November 1 as a contingency trigger, not a confirmed shutdown date. Verify the latest status through the affected terminal, port, ocean carrier, appointment system, and customer before assigning a driver, changing a route, or canceling a move.
- Identify every exposed import, export, empty, and chassis move by terminal. Confirm release, availability, appointment, last free day, gate hours, driver hours, equipment, delivery or return location, and the person authorized to approve a change before prioritizing early pickups or post-disruption recovery.
- Do not assume both ports or every terminal will close. Local 26's agreement is separate from the broader coastwide labor contract, and actual effects may differ by facility, shift, gate, vessel, rail connection, or picket-line response.
- Prepare drivers for a safe hold. Provide verified contacts and a maximum queue threshold, monitor hours of service and fuel, identify lawful parking, and instruct drivers not to enter a closed gate, cross a picket line, confront workers, or accept an unverified diversion.
Why this development matters
Port Operations can influence pricing, lane selection, capacity, customer expectations, and the level of operating risk carried by a motor carrier. The headline matters only after a team understands which loads, drivers, customers, or markets may actually be affected.
The development covered in “LA–Long Beach Port Watchmen Authorize Possible Nov. 1 Strike” should be evaluated against the carrier’s real network. National trends can create useful direction, but individual results still depend on equipment type, geography, contract terms, driver availability, fuel exposure, and service requirements.
Dispatchers should separate verified facts from forecasts and commentary. Regulatory proposals are not final rules, market averages are not guaranteed lane rates, and a single company announcement does not automatically represent the entire trucking industry.
What happened
FreightWaves reported on October 28 that approximately 250 watchmen represented by International Longshore and Warehouse Union Local 26 have authorized a possible strike at the ports of Los Angeles and Long Beach beginning as early as 5 p.m. Pacific on Sunday, November 1. The Pacific Maritime Association, which represents employers, said negotiations are continuing with federal mediators and that it remains committed to bargaining through the deadline and beyond. The strike has not begun, and a work stoppage is not certain. The potential impact could exceed the size of the watchmen unit because employers expect other ILWU workers may honor picket lines. PMA said the affected facilities handle roughly 85% of Long Beach cargo and 33% of Los Angeles cargo, so vessel, yard, and truck-gate operations at those terminals could be disrupted. The Local 26 agreement is separate from the coastwide contract covering longshore workers and marine clerks through 2028. The threat also arrives while the port complex is managing a large backlog of import containers awaiting inland rail service, increasing the importance of terminal-specific verification rather than broad assumptions about the entire gateway.
The development matters when it changes load planning, pricing, communication, safety, or the daily decisions made by carriers and dispatch teams.
What dispatch teams should do
The development is most useful when it becomes a specific operating check instead of another headline.
- Treat November 1 as a contingency trigger, not a confirmed shutdown date. Verify the latest status through the affected terminal, port, ocean carrier, appointment system, and customer before assigning a driver, changing a route, or canceling a move.
- Identify every exposed import, export, empty, and chassis move by terminal. Confirm release, availability, appointment, last free day, gate hours, driver hours, equipment, delivery or return location, and the person authorized to approve a change before prioritizing early pickups or post-disruption recovery.
- Do not assume both ports or every terminal will close. Local 26's agreement is separate from the broader coastwide labor contract, and actual effects may differ by facility, shift, gate, vessel, rail connection, or picket-line response.
- Prepare drivers for a safe hold. Provide verified contacts and a maximum queue threshold, monitor hours of service and fuel, identify lawful parking, and instruct drivers not to enter a closed gate, cross a picket line, confront workers, or accept an unverified diversion.
- Send timely written notices under the applicable customer and carrier agreements. Record terminal advisories, appointment failures, gate attempts, timestamps, driver wait, chassis and empty-return problems, storage or demurrage exposure, customer decisions, and mitigation steps without promising that every cost will be waived or reimbursed.
- Plan the restart before a disruption occurs. Rank containers by release and last-free-day risk, customer need, cargo sensitivity, appointment availability, driver and chassis capacity, delivery readiness, and total truck-day economics so the first reopening does not create an uncontrolled dispatch rush.
The Dispatch Control view
Carriers should verify the underlying source, identify the lanes or workflows actually affected, and avoid changing policy based on a headline alone. Market reports and regulatory announcements can signal risk before they create a direct requirement.
Keep rate, route, driver, equipment, documents, and customer communication connected so the team can respond quickly when conditions change.
How to put the information into daily practice
Start by identifying where port operations appears in the current dispatch workflow. Review what information is collected, who confirms it, where it is stored, and what event triggers the next action. If the answer depends on a private text message or someone’s memory, the process is difficult to audit and difficult to scale.
Use one load timeline to connect the booking decision, driver assignment, route and appointment plan, status updates, exceptions, supporting documents, accessorial approvals, and invoice readiness. Each update should answer three questions: what changed, who owns the response, and when the next update is due.
Introduce the improvement on a small group of active loads before applying it to the whole fleet. Review the exceptions at the end of each shift, correct unclear fields or instructions, and then make the successful version the standard operating procedure.
- Treat November 1 as a contingency trigger, not a confirmed shutdown date. Verify the latest status through the affected terminal, port, ocean carrier, appointment system, and customer before assigning a driver, changing a route, or canceling a move.
- Identify every exposed import, export, empty, and chassis move by terminal. Confirm release, availability, appointment, last free day, gate hours, driver hours, equipment, delivery or return location, and the person authorized to approve a change before prioritizing early pickups or post-disruption recovery.
- Do not assume both ports or every terminal will close. Local 26's agreement is separate from the broader coastwide labor contract, and actual effects may differ by facility, shift, gate, vessel, rail connection, or picket-line response.
- Prepare drivers for a safe hold. Provide verified contacts and a maximum queue threshold, monitor hours of service and fuel, identify lawful parking, and instruct drivers not to enter a closed gate, cross a picket line, confront workers, or accept an unverified diversion.
- Send timely written notices under the applicable customer and carrier agreements. Record terminal advisories, appointment failures, gate attempts, timestamps, driver wait, chassis and empty-return problems, storage or demurrage exposure, customer decisions, and mitigation steps without promising that every cost will be waived or reimbursed.
- Plan the restart before a disruption occurs. Rank containers by release and last-free-day risk, customer need, cargo sensitivity, appointment availability, driver and chassis capacity, delivery readiness, and total truck-day economics so the first reopening does not create an uncontrolled dispatch rush.
- Assign a named owner and a due time for every unresolved exception.
- Keep customer and driver communication attached to the load record.
- Review the result after delivery and carry the lesson into the next similar load.
Common mistakes and practical risk controls
The most common mistake is acting with incomplete information because the load feels urgent. Speed is useful only when the basic facts are verified. Before committing the truck, confirm the parties, rate or cost exposure, equipment, timing, route constraints, required documents, and the person authorized to approve changes.
Another mistake is allowing an exception to remain inside a phone call. If detention, a missed appointment, an equipment problem, a route change, a rejected shipment, or a compliance concern is not recorded, the next person cannot make a fully informed decision. Written timestamps and supporting documents protect both service and payment.
Finally, avoid measuring activity instead of outcomes. More calls, messages, or status entries do not necessarily mean better control. The useful question is whether the process produced a safer trip, an on-time delivery, a complete document set, a satisfied customer, and an acceptable contribution margin.
- Do not promise an appointment before checking realistic transit and driver hours.
- Do not rely on an unverified email, changed phone number, or altered payment instruction.
- Do not close the load while documents, accessorials, or customer exceptions remain unresolved.
- Do not change a compliance process based only on a headline; confirm the official requirement first.
What managers should measure
A useful scorecard for port operations should be short enough to review every week. Combine service, cost, workflow, and safety measures so that one improvement does not hide damage somewhere else.
Compare performance by customer, lane, dispatcher, equipment type, and exception reason. Trends become actionable when the team can see where a delay or cost begins, not only the final monthly total.
- On-time pickup and delivery percentage, including the documented cause of every miss.
- Loaded and empty miles, revenue per total mile, and contribution per truck-day.
- Average check-in, loading, unloading, and detention time by facility.
- Time from delivery to verified POD and time from verified POD to invoice.
- Number of avoidable exceptions, repeated data corrections, and unresolved driver issues.
- Safety or compliance events that required a dispatch change or management review.
A simple implementation checklist
Use this checklist during a dispatch meeting or process review. Each item should be visible in the company’s transportation management workflow and understandable to the person covering the desk after hours.
- The load has a verified customer or broker, rate, commodity, equipment type, weight, and reference number.
- Every stop has an address, appointment, contact, instructions, service-time allowance, and required document.
- The assigned driver and equipment can complete the plan safely and legally.
- Fuel, toll, deadhead, parking, and likely delay exposure are reflected in the operating decision.
- The driver knows the next action, expected updates, and the exceptions requiring immediate escalation.
- Delivery paperwork and accessorial evidence will flow directly into review and invoicing.
- A manager can reconstruct the load history without searching personal messages or separate spreadsheets.
Frequently asked questions
Does this news item change a carrier’s legal requirements immediately?
Not necessarily. A news report may describe a proposal, pilot, market development, enforcement trend, or company announcement. Confirm final regulatory requirements through the responsible government agency before changing compliance policy.
How should a dispatcher use national freight-market data?
Use it as context for direction and risk. The operating decision should still use current lane data, equipment availability, driver hours, deadhead, fuel, appointments, and the carrier’s own accepted-load history.
When should customers receive an update?
Send an update when the development materially changes price, capacity, transit, appointment reliability, documentation, or regulatory handling for their shipment. Explain the specific impact and the next action.
What should the carrier monitor next?
Monitor the original source, current port operations indicators, lane-level results, customer requests, and any official implementation or enforcement date.