SHIPPING DEFINITIONS · PLAN TIMING
Why ERDs Move: And Why It is Not Random
DIRECT ANSWER
ERDs change because the published schedule reconciles continuously against operational reality. Previous-port slippage, vessel rotation changes, terminal yard capacity, labor, and manifest closure each translate into ERD revisions. The pattern is structural, not random.
Why do ERDs change in container shipping?
- Previous portWhen the prior call runs late, the vessel arrives later. Berthing slips. ERD pushes back.
- Vessel rotationWhen the carrier re-sequences calls (skipping a port, adding one), the entire downstream ERD pattern shifts.
- Yard capacityWhen the terminal yard fills up, ERD can be pulled forward or pushed back to manage container flow.
- LaborGang availability, shift coverage, and scheduled labor actions all influence when the terminal can receive cargo.
- Manifest closureAs the carrier reconciles bookings against actual tonnage, ERD moves to align cargo arrival with vessel loading.
A real-world example
A SINGLE VESSEL, FIVE ERD REVISIONS
A vessel scheduled for export-leg ERD of Tuesday morning has its previous port call delayed by 18 hours due to weather. The terminal pushes ERD to Tuesday afternoon. Yard capacity then constrains the receiving rate; ERD pushes again to Wednesday morning. The carrier re-sequences the rotation to recover transit time; ERD pulls forward to Tuesday evening. Berth assignments shift; ERD shifts back to Wednesday morning. Final shift to Wednesday at noon based on labor availability.
Five revisions on a single ERD before opening, each driven by a specific operational input. The shipper saw five different ERDs across one week. Each revision was rational; the cumulative effect is what feels chaotic.
How do ERD changes break the plan, by role?
EXPORTER
Production sequencing absorbs every revision
Each ERD revision pushes the production schedule. Fumigation re-books, lab certification re-times, equipment re-allocates. By the third revision, the sequence has no slack.
FREIGHT FORWARDER
Customer communication compounds the noise
Each revision is a customer call. The forwarder explains the change and confirms the new plan. By the fourth revision, the customer stops trusting the published date.
DRAYAGE OPERATOR
Each revision changes the dispatch math
Equipment availability, driver scheduling, and yard appointments are all sequenced against ERD. Each revision is a re-plan. The cost lands on the dispatcher.
ERDs do not move randomly. They move for reasons. The reasons are operational, structural, and continuous.
What does the data show about ERD revision patterns?
OBSERVED ACROSS U.S. EXPORT VESSEL SCHEDULES
Based on aggregated shipment observations across major U.S. ports:
- A meaningful share of vessels see at least one ERD revision before opening.
- Multiple revisions on a single vessel are not unusual.
- Revision frequency clusters by carrier-port pair, vessel rotation, and time of year.
- Late-stage revisions (inside the final 72 hours) are most consequential because they leave operators no recovery time.
ERD revisions are predictable in the aggregate, even when individual changes feel sudden. The structural pattern is identifiable; the operational consequence depends on when in the cycle a given exporter happens to commit.
TradeLanes analysis of U.S. export vessel schedules. Observed schedule behavior based on published carrier and terminal data.
IN SIMPLE TERMS
ERDs do not change randomly. Each revision reflects a specific operational input: a slipped previous port, a re-sequenced rotation, a yard-capacity shift, a labor change, or manifest closure. The schedule is a snapshot of a moving system.
How do ERDs revise across the final week before opening?
Caption: Each ERD revision corresponds to a specific operational input. The pattern is structural; the apparent randomness is a property of the operational network.
What do operators do differently when ERDs change?
- 01Plan against the cause, not just the date. The ERD that the carrier publishes reflects a state of the underlying operation. Knowing which inputs drove the most recent revision is more useful than knowing the date alone.
- 02Treat revision frequency as a property of the carrier-port pair. Some pairs revise rarely; some revise frequently. Plan against the frequency, not the booking-time ERD.
- 03Re-pull ERD inside the final 72 hours. Most revisions cluster late. The ERD at booking and the ERD at dispatch are often different dates because of revisions that occurred between them.
- 04Build slack against the published ERD on volatile pairs. On pairs that revise frequently, sequencing production with at least a day of slack against the published date converts a revision into an absorbed change rather than a missed cut.
- 05Capture the ERD at the moment of dispatch. A timestamped record of the ERD that was published when the dispatch decision was committed is the only defensible position when downstream costs surface.
Frequently asked questions
Why do ERDs change so often?
ERDs change because they are reconciled continuously against operational reality. Previous-port slippage, vessel rotation changes, terminal yard capacity, labor, and manifest closure each translate into ERD revisions.
Are ERD changes random?
No. Each revision corresponds to a specific operational input. The aggregate pattern is structural; what feels random is the timing relative to a single shipper. Revision frequency varies by carrier-port pair.
How much advance notice do shippers usually get on ERD changes?
Notice varies. The carrier portal and the terminal portal often update independently and at different speeds. The trucker at the gate is sometimes first to see the executable ERD.
Can ERDs move forward (earlier) as well as back (later)?
Yes. ERDs can pull forward when vessel arrival is earlier than expected or yard capacity opens up. Pull-forwards are operationally hazardous because they compress the receiving window unexpectedly.
Which revisions are most disruptive?
Late-stage revisions inside the final 72 hours leave the least time to re-plan production, dispatch, and gate appointments. The same revision earlier in the cycle has lower operational cost.
Do all carriers revise ERDs at the same rate?
No. Revision frequency varies by carrier and by port. Some carrier-port pairs are structurally more stable than others.
Can shippers prevent ERD revisions?
No. ERDs are not under shipper control. Shippers can plan against revision patterns, build slack, and re-check dates inside the final 72 hours, but they cannot prevent the underlying revisions.
Plan against ERD volatility, not just the published date.
TradeLanes is the system that determines whether a plan will hold before execution. Each booking is evaluated against observed ERD revision patterns on its specific carrier-port pair, and the call is delivered before the window closes.
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."