SAFE-TO-DISPATCH

Know whether it's safe to dispatch -- before the truck moves.

Safe-to-Dispatch evaluates the receiving window, the in-gate appointment, and the terminal's current state before you commit the dispatch -- so the truck moves only when the window is confirmed open.

Safe-to-Dispatch output card showing OOCL SEATTLE at Tacoma with Stable posture, ERD confirmed open, low vessel overlap, and a Proceed dispatch recommendation.

The dispatch board

You are not gating one box - you are sequencing a converging week

A dispatcher plans 30 to 50 loads per vessel across several vessels calling the same terminal. When their windows converge - 49% of Oakland days have 3 or more vessels opening at once - every load competes for the same finite gate hours, and the window compresses exactly when demand peaks. Safe-to-Dispatch sequences the week: which vessel's loads move first, which buffer, which appointment to reschedule.

Everport, Oakland - week of Mar 9
CONVERGENCE WEEK - 4 vessels stack Wednesday
Mon
Tue
Wed 4 vessels
Thu
Fri
MSC ARIA
38 loads
ERD Mon → CY Cut Wed
Dispatch
HAPAG BONN
29 loads
ERD Tue → CY Cut Wed
Dispatch
EVER FONT
42 loads
ERD Wed → CY Cut Fri
Buffer
OOCL ZURICH
31 loads · window compressing
ERD Wed → CY Cut Thu
Reschedule
ONE TRITON
45 loads
ERD Thu → CY Cut Fri
Buffer
Gate appointments
finite slots / hour
OPEN
SCARCE - stack demand
EASING
Demand spikes and the window shrinks at the same time: 120h solo → 105h on a 5 to 9 vessel stack (-15h). On the stack day, 185 loads chase the fewest open slots of the week.
Safe-to-Dispatch sequences the 185 loads - by window stability, not by gut feel
1
Move now - MSC ARIA + HAPAG BONN
Windows stable and the gate is open early in the week. Clear these before the stack forms.
67loads
2
Buffer - EVER FONT + ONE TRITON
Converging midweek. Hold for the confirmed slot rather than committing into the scarce day.
87loads
3
Reschedule appointment - OOCL ZURICH
CY Cut is advancing to Thursday; the slot you hold will not clear. Move the appointment before the truck rolls.
31loads

You do not find out it is a convergence week until Monday evening - after Friday's commit. Safe-to-Dispatch flags the stack days in advance and sequences the loads by window stability, so the week is planned, not fought.

49% of Oakland days: 3+ vessels open at once 28.5% of days: 5 or more 85.6% of stacks cross alliance lines - no coordination

Illustrative example. Vessels, loads, and windows shown are for illustration; convergence and compression figures are from West Coast terminal observations, Jan 2025 - Mar 2026.

The dispatch decision is a forced bet.

The dispatcher commits T-1 -- the afternoon before the move -- because the schedule will not hold further out. In-gate appointments are booked 2 to 3 days in advance under terminal appointment scarcity. Both clocks run independently. When the receiving window moves, both are misaligned simultaneously: the appointment is in the wrong slot and the dispatch call is based on stale data. Safe-to-Dispatch reconciles both before the truck leaves.

Is it safe to dispatch to this terminal, on this vessel, right now -- given the current window state and the appointment held?

The dispatch chain

You commit the move in one call - the afternoon before the gate

The dispatch is a forced bet. The appointment is booked 2 to 3 days out under gate scarcity; the dispatch call itself comes at T-1, the afternoon before the move. Both clocks run independently - and when the receiving window shifts, both are misaligned at once. Safe-to-Dispatch reconciles them before the truck moves.

Dispatch / T-1 call
the point of no return - Safe-to-Dispatch evaluates here
OOCL SEATTLE - TacomaDISPATCH
The recommendation is one of: Dispatch Buffer with risk Reschedule appointment
1
Appointment
Book the in-gate slot
2
Dispatch
Release the truck
3
Pull
Pull the container
4
Drive
Drive to the terminal
5
Terminal In-Gate
In before the CY Cut
APPT SLOT - terminalbooked 2 to 3 days out
DISPATCH - your callyour commit point
ERD - window openCY CUT - carrier
How late each clock commits you to the gate - and where the window is confirmed
Appointment - booked 2 to 3 days out
Dispatch - the T-1 call
IN-GATE
3 days out2 daysT-1in-gate
Shaded = window confirmed close-in (the final days) - strongest at the gate
Your steps and decisions
Terminal-controlled (appointment, ERD)
Carrier-controlled (CY Cut)

You commit the dispatch at T-1, but the appointment was locked 2 to 3 days earlier - if the window moved in between, both are in the wrong slot. Safe-to-Dispatch reconciles the window and the appointment before the truck moves, so you avoid a dry run and a wasted slot.

Illustrative example. The verdict, vessel, and lead times shown are for illustration; the confirmation window reflects the current model frontier.

What Safe-to-Dispatch produces.

One dispatch. One recommendation. Not a dashboard to interpret.

OOCL SEATTLE Tacoma
Stable
ERD status confirmed open CY Cut stable -- no late-stage movement Vessel overlap low Dispatch recommendation proceed
Risk posture: the window is confirmed open and no late-stage compression has been detected. Proceed with dispatch.

Safe-to-Dispatch. The window is confirmed open, the appointment slot is valid, and no late-stage compression has been detected -- with a record of what the schedule showed when the dispatch call was made.

What Safe-to-Dispatch evaluates.

Step 01

The receiving window

Safe-to-Dispatch evaluates the current ERD and CY cutoff against the terminal's live state and historical behavior on this service. Terminal-verified ERD -- not what the carrier publishes, what the terminal is actually showing.

Step 02

The appointment and capacity

Safe-to-Dispatch checks whether the appointment slot is still valid against the current window, flags bunched-vessel risk when multiple vessels have pushed ERDs onto the same day, and accounts for gate throughput constraints that determine whether an on-time arrival can actually in-gate.

Step 03

The decision

Safe-to-Dispatch or Hold. When the posture is Hold, the output includes the specific condition to monitor and the earliest re-evaluation point. Timestamped terminal-source evidence is captured automatically -- retained for per-diem dispute defense.

For export planning teams: Safe-to-Commit evaluates whether a booking is safe to commit before execution begins.

See Safe-to-Commit ->

Ready to see this on your dispatches?

Safe-to-Dispatch is part of the Ava decision layer. It evaluates your specific dispatch timing against terminal volatility patterns and live window state -- not carrier-aggregated data.

Talk to the Team See How Ava Works

Exporters and logistics partners already operating on TradeLanes

Tyson Foods IMC Logistics Capay Canyon Ranch Avanti Nut