Know what changed at the terminals you depend on.
Vessel Schedule Report (VSR) shows what changed. Ava tells you when the plan no longer holds.
VSR by Terminal gives exporters and drayage teams a daily view of ERD and CY cutoff changes, without checking carrier sites, terminal PDFs, or spreadsheets.
Used by U.S. exporters and drayage teams across West Coast, Gulf, and East Coast ports.
Planning is a decision you are already making. VSR and Ava give you a system that holds under change.
Act before the cargo receiving window collapses. Protect commitments across production, drayage, and documentation. Avoid rolled bookings and the cascade that follows.
Dispatch is a bet you are already placing. Ava makes the bet visible, defensible, and earlier.
Dispatch only when it is safe. Avoid failed gates and wasted moves. Win per-diem disputes with timestamped evidence.
Most teams don't know what actually changed until it's too late.
ERDs move overnight. CY cutoffs shift mid-week. Carriers and terminals disagree. Multiple vessels open at the same terminal at the same time.
So teams compensate:
- checking carrier websites
- downloading terminal PDFs
- refreshing 3 to 4 terminal portals every day
- running the morning copy/paste: yesterday's schedule under today's, finding changes by eye
- screenshotting for evidence
The problem is not effort.
The problem is timing.
A window looks stable. ERD posted. CY cutoff posted. Plan committed.
What the plan sees
- ERD posted
- CY cutoff posted
- Plan committed
What actually happens
- ERD shifts
- cutoff moves
- decision is already locked
The signal arrives after the decision. That is when you get rolled bookings, re-dispatched trucks, and storage costs.
VSR by Terminal shows what changed.
For the terminals you select, VSR gives you:
- delta-only ERD and CY cutoff changes, what moved since the last report, not a republished full schedule
- vessel-level schedule movement
- Verified Windows: a single confidence-scored view when carrier and terminal disagree
- AIS signals to close the carrier-terminal schedule data lag
- timestamped snapshots, captured automatically and retained for per-diem dispute defense
- booking-quantity decrement detection before dispatch
You stop asking "Did anything change?" because you can see it.
Same terminal. Same week. Different outcomes.
Four vessels at Garden City Terminal, week of March 15. Four different behaviors. One planning rule will not cover all of them.
| Vessel | ERD Shift | CY Cut Shift | Outcome |
|---|---|---|---|
| MSC VANESSA | +2 days | +3 days | Late expansion |
| EVER LIVING | 0 days | 0 days | Stable |
| CMA CGM TIGRIS | -1 day | +2 days | Mixed |
| HMM OSLO | +1 day | -2 days | Mixed |
Same terminal. Different behavior. Do not apply one planning rule across all vessels.
Once visibility isn't enough, Ava tells you when the plan no longer holds.
EVER MACH
OaklandThis is not a dashboard. This is a decision.
From signal to execution.
Visibility -- Signal -- Decision -- Execution. Every product has a role.
Export Intel
What is happening in my business
VSR
What changed
Ava
Is it safe to act
Lexi / Navi / Verra
Execute correctly
Coming nextThe metrics exporters actually need.
Receiving-window reliability. Not carrier marketing metrics.
ERD Drift Index
How much the earliest receiving date has moved, by vessel and by terminal, over the prior 30 days.
Cutoff Stability Score
How often CY Cut holds its originally published position through the final 72 hours before ERD.
Terminal vs Carrier Accuracy
Where terminal-posted values and carrier-posted values disagree, and which side tends to hold.
72-Hour Volatility Profile
Concentration of CRW changes arriving inside the critical execution window.
Start with visibility. Upgrade when decisions depend on it.
VSR gives you the signal. Ava gives you the decision. The record of what you knew when you decided gives you the defense.
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."