Port Labor Disruption: A Drayage Continuity Playbook

Why this topic matters to a trucking operation

Port Operations is not an isolated office task. It affects the driver’s available time, the truck’s utilization, customer service, document quality, safety exposure, and the final margin on the load. A weak decision at the beginning of the trip often creates several smaller problems later in the workflow.

The subject of “Port Labor Disruption: A Drayage Continuity Playbook” should therefore be handled as a repeatable operating process. The dispatcher needs reliable information, a clear owner for the next action, a deadline, and an escalation path when the plan changes.

Small fleets benefit from this discipline as much as large carriers. A documented process reduces dependence on one experienced employee and gives managers a consistent way to train new dispatchers, review exceptions, and improve performance.

Build the operating picture

A threatened port work stoppage creates operational risk before a single gate closes. Importers may accelerate pickups, terminals may change appointment availability, chassis and empty-return patterns can tighten, rail and vessel backlogs can compound, customers may request diversions, and dispatchers may face pressure to promise recovery times without a confirmed reopening plan. A carrier needs a controlled continuity process that separates a warning from an actual shutdown, identifies every exposed container and driver, preserves the evidence needed for demurrage and detention discussions, and gives customers dated facts instead of speculation. The objective is to protect people and cargo while keeping drayage decisions aligned with official terminal instructions, lawful driver hours, equipment availability, and the carrier's contractual authority. The practical goal is to make the next action obvious to the dispatcher, driver, and manager without searching across separate calls, messages, and spreadsheets.

A connected transportation management system gives the team one timeline for the load. That timeline should contain the current status, responsible person, supporting documents, and the next decision point.

Use this field playbook

Apply the process consistently to every applicable load, then make exceptions visible instead of keeping them in someone’s memory.

• Build an exposure register by terminal and container. Record the ocean carrier, vessel or rail connection, container and chassis identifiers, import or export status, availability and last-free-day dates, customs and freight release, terminal appointment, driver and tractor, empty-return location, customer delivery window, storage or demurrage terms, and the source and timestamp of every operational update.
• Monitor official sources on a fixed cadence. Assign one person to check terminal advisories, port notices, ocean-carrier alerts, appointment systems, rail updates, customer instructions, and verified labor or employer statements. Distinguish an authorized strike, an active picket line, a terminal-specific closure, reduced gate hours, and a normal operating day; do not dispatch from rumors or assume all terminals share the same condition.
• Create release, hold, and recovery rules for each move. A truck should proceed only when the container is released and available, the gate and appointment are confirmed, the assigned equipment is acceptable, the driver has legal time, and the destination or yard can receive the box. Define who can cancel, reschedule, divert, stage, or authorize an alternate terminal or depot.
• Protect drivers from unproductive or unsafe queues. Give drivers a verified gate destination, appointment and fallback contact; establish a maximum wait and hours-of-service review point; identify safe parking and fuel options; and instruct drivers not to cross a picket line, enter a closed facility, argue with workers, or make an unapproved container movement.
• Document every cost-producing exception in real time. Preserve terminal screenshots, closure notices, appointment changes, timestamps, geofence or ELD records, gate tickets, ingate and outgate events, chassis condition, driver arrival and departure, customer instructions, attempted returns, receipts, and notices sent under the applicable contract. Evidence supports a claim but does not guarantee reimbursement.
• Replan the network, not only the affected load. Review near-dock yard capacity, chassis pools, empty-return locations, transload options, rail connections, street-turn opportunities, alternate ports when commercially and legally feasible, customer inventory priority, driver schedules, and the order in which held containers should move when gates reopen.

Measure the result

Measure exposed containers, confirmed gate status, appointments kept or lost, driver wait, empty and loaded dwell, last-free-day risk, chassis exceptions, loads diverted or staged, storage and demurrage incurred, accessorial notices sent on time, costs recovered, on-time customer delivery, and time required to clear the backlog after normal operations resume. A continuity plan should help dispatchers make the next safe decision under uncertainty; it should not imply that a threatened strike is certain or that a carrier can bypass terminal, labor, customs, security, or contractual controls. Track a small number of outcomes such as on-time performance, empty miles, document cycle time, accessorial recovery, calls per load, and contribution per truck-day.

Review exceptions weekly. The purpose of measurement is not to create more reporting; it is to find the recurring handoff or missing field that causes preventable work.

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.

• Build an exposure register by terminal and container. Record the ocean carrier, vessel or rail connection, container and chassis identifiers, import or export status, availability and last-free-day dates, customs and freight release, terminal appointment, driver and tractor, empty-return location, customer delivery window, storage or demurrage terms, and the source and timestamp of every operational update.
• Monitor official sources on a fixed cadence. Assign one person to check terminal advisories, port notices, ocean-carrier alerts, appointment systems, rail updates, customer instructions, and verified labor or employer statements. Distinguish an authorized strike, an active picket line, a terminal-specific closure, reduced gate hours, and a normal operating day; do not dispatch from rumors or assume all terminals share the same condition.
• Create release, hold, and recovery rules for each move. A truck should proceed only when the container is released and available, the gate and appointment are confirmed, the assigned equipment is acceptable, the driver has legal time, and the destination or yard can receive the box. Define who can cancel, reschedule, divert, stage, or authorize an alternate terminal or depot.
• Protect drivers from unproductive or unsafe queues. Give drivers a verified gate destination, appointment and fallback contact; establish a maximum wait and hours-of-service review point; identify safe parking and fuel options; and instruct drivers not to cross a picket line, enter a closed facility, argue with workers, or make an unapproved container movement.
• Document every cost-producing exception in real time. Preserve terminal screenshots, closure notices, appointment changes, timestamps, geofence or ELD records, gate tickets, ingate and outgate events, chassis condition, driver arrival and departure, customer instructions, attempted returns, receipts, and notices sent under the applicable contract. Evidence supports a claim but does not guarantee reimbursement.
• Replan the network, not only the affected load. Review near-dock yard capacity, chassis pools, empty-return locations, transload options, rail connections, street-turn opportunities, alternate ports when commercially and legally feasible, customer inventory priority, driver schedules, and the order in which held containers should move when gates reopen.
• 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