Vessel Schedule Report

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/terminal sites, vessel schedule PDFs, or spreadsheets.

Track My TerminalsSee a Sample VSR

Tracking 40+ U.S. terminals · West Coast, Gulf, East Coast

Used by U.S. exporters, drayage providers, and freight forwarders

Tyson FoodsIMC LogisticsCapay Canyon RanchAvanti Nut

The schedule change arrives after the decision is already locked in.

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/terminal sites
  • downloading vessel schedule 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.

Garden City Terminal / Savannah / Week of March 15
VesselERD ShiftCY Cut ShiftOutcome
MSC VANESSA+2 days+3 daysLate expansion
EVER LIVING0 days0 daysStable
CMA CGM TIGRIS-1 day+2 daysMixed
HMM OSLO+1 day-2 daysMixed

Same terminal. Different behavior. Do not apply one planning rule across all vessels.

For Exporters

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.

For Drayage

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.

Operators are already changing how they plan and execute.

Tyson Foods

Planning runs on how schedules behave, not what they say.

Teams now

  • align planning to receiving window behavior
  • coordinate execution using schedule signals
  • treat instability as an operational input
Avanti Nut

Manual schedule checking has been removed.

Time is now spent on

  • execution decisions
  • timing adjustments
  • managing optionality
Drayage Provider in CA

The clerk-level morning reconciliation job has been displaced.

Now

  • delta-only change report at 7:30 AM replaces the morning copy/paste
  • timestamped evidence archive replaces the screenshot folder
  • dispatchers make decisions instead of finding information
IMC Logistics

Dispatch decisions are defensible across customers and disputes.

Dispatch teams now

  • capture terminal-source evidence at every gate attempt
  • reconcile carrier-terminal conflicts before the truck moves
  • coordinate across the customer book without losing the audit trail

This is not adoption of a tool. It is a shift in how teams operate.

Once visibility isn't enough, Ava tells you when the plan no longer holds.

EVER MACH

Oakland
Elevated
ERD drift expectation +1 to +7 days CY Cut behavior repeated movement Volatility elevated Recommended buffer +2 days
Risk posture: plan with +2 days buffer before committing execution. Monitor for terminal updates inside the final 72 hours.

This is not a dashboard. This is a decision.

From signal to execution.

Visibility -- Signal -- Decision -- Execution. Every product has a role.

Visibility

Exposure Intelligence

What is happening in my business

Signal

VSR

What changed

Decision

Ava

Is it safe to act

Execution

Lexi / Navi / Verra

A.I. agents that execute AES filings, Shipping Instructions, and BL proofing

By invitation only

The 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.

Operators already run their mornings on it

Reference accounts, in their own words.

Everyone thinks that it's really freaking cool that you knew that before we did.

Derek Roetzel, Tyson Foods

We stopped refreshing carrier pages. The alert comes to us.

Nina Solari, Avanti Nut

Knowing where and when the changes hit is what changed our routine.

Alex Velazquez, Capay Canyon Ranch

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.

Track My TerminalsSee My Booking Risk Profile