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.
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?
What Safe-to-Dispatch produces.
One dispatch. One recommendation. Not a dashboard to interpret.
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.
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.
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.
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.
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.
Frey Commodities
"TradeLanes gives us control over the entire load order process, in real time. I highly recommended signing up to try their new early access product."