ETA, ETD, ATA and ATD: read a container timeline correctly

What do ETA, ETD, ATA and ATD mean in shipping?

Read the event before the date. An arrival may concern a vessel at a port, a berth, a transshipment connection or cargo at a warehouse. Two timestamps cannot be compared meaningfully until they refer to the same object and place. In ocean schedules, ETD normally means estimated time of departure; an interface that uses it for delivery must make that meaning explicit.

DCSA distinguishes estimated, requested, planned and actual port-call events. A requested or planned time is part of coordination; it does not become an observed arrival merely because the parties agreed it. Maersk likewise separates its estimated sailing schedule from actual departure data.

• HBL or MBL: choose the right tracking reference
• Check the next action when the ETA changes

A worked timeline: forecast, arrival and pickup are different decisions

Illustrative example, not a customer record: one container moves to a destination terminal. All times below use the same destination time zone. The later update changes the planning assumption, while later actual events establish what happened. No universal free-time rule or guaranteed processing interval is implied.

On 9 September, the receiving team can reserve capacity provisionally. When the ETA moves, its owner checks the slot and downstream commitments. After vessel arrival, collection still waits for the actual container and release conditions. The source for the applicable last free day must be recorded separately; it is not calculated from this sample ATA.

Why is an arrived container not necessarily ready for pickup?

Treat vessel arrival, container discharge, cargo availability, customs release, carrier release, terminal collection and warehouse receipt as separate checkpoints. Some occur in parallel, and the order depends on the shipment. A general arrival status cannot stand in for the specific release evidence required by the trucker or terminal.

A carrier tracking page may provide movements and an expected schedule. It does not follow that every document, payment, hold, appointment and receiving condition is satisfied. Ask the responsible source for the precise missing event before dispatching a truck or confirming a warehouse slot. Maersk describes its public tracking view as location, previous movements and expected schedule; interpret that visibility within its stated scope.

Keep event time, update time and time zone separate

Record when the event is expected or occurred and when your team received the update. An actual departure received today may describe yesterday. Sorting only by receipt time can make old information appear to be a new movement. Preserve the originating source and its event identifier when supplied, so a forwarded email does not become a second independent observation.

Keep the source time zone or UTC offset with a timestamp. If a carrier supplies only a calendar date, retain that date and its precision; do not invent a midnight event or shift the date because a colleague opens the record in another country. When the source changes time-zone conventions, resolve that discrepancy before reporting a delay.

For a transshipment, keep each leg and port distinct. An ATD at the first loading port does not confirm departure from the connecting port. Vessel names, voyage references and container identifiers help prevent a schedule for another sailing from being attached to the current shipment.

How should the team handle missing or conflicting updates?

Choose a review owner and a next checkpoint based on the operational deadline. A missing scan is an information gap, not evidence of lost cargo. A later-looking estimate is not automatically more authoritative than a reported actual event. Keep both source records until the discrepancy is understood.

A tracking update should leave a usable handoff

Before passing a change to another team, make the record answer four questions: what changed, which commitment it affects, who decides next and what evidence will close the issue. Forwarding an entire timeline without that decision context transfers reading work rather than accountability.

The logistics owner verifies movement evidence. The warehouse owner checks receiving capacity. The document or customs coordinator verifies the outstanding evidence in their remit. Finance checks cost exposure when relevant. These are suggested responsibilities; an organization may combine roles, but each unresolved action still needs a named owner.

• Shipment, container and transport-leg references.
• Previous and current event values, including precision and time zone.
• Source link or retained message and time received.
• Planning assumption versus confirmed actual event.
• Affected collection, warehouse or customer commitment.
• Open blocker, responsible person, backup and response deadline.
• Decision and recipient acknowledgement.
• Closing evidence; a later estimate alone is not closure.

How can you measure ETA quality without rewriting history?

Freeze the forecast at a defined decision point, such as booking confirmation or a stated number of days before expected arrival. Compare it with the actual occurrence of the same event at the same location. Comparing an early forecast on one shipment with a last-minute update on another produces a misleading score.

For each matched observation, signed error equals actual time minus frozen forecast time. Mean absolute error equals the sum of absolute errors divided by the number of matched observations. Illustrative errors of +2, −6 and +1 hours yield (2 + 6 + 1) / 3 = 3 hours; this is arithmetic, not an industry benchmark.

Publish the sample size and coverage alongside the result: matched actual events divided by eligible shipments. Keep missing actuals visible instead of silently excluding difficult cases. Separate forecast error from time spent waiting after arrival, and report results by comparable lane, event and observation window.

Keep the timeline connected to the shipment record

In Tyllus, use the shipment record to connect tracking context with documents, partners, costs and the next work item. Review the information actually available for the shipment and carrier; do not assume a displayed ETA confirms a terminal release, customs decision or truck appointment.

A useful operating review starts with the exception and opens the supporting record. It should show what remains uncertain and who owns the next check. The record supports coordination; it does not replace carrier, terminal, customs or warehouse confirmation.

Common shipment-timeline questions

Is ETA the delivery date? Only if the source explicitly identifies the event as delivery at the agreed destination. A vessel ETA at a port is a different event from warehouse delivery.

Does ATA mean the container cleared customs? No. Actual arrival and customs release are separate facts from different responsible parties.

Can an actual timestamp be corrected? A source can correct an event. Retain the earlier value and the correction evidence instead of treating every actual timestamp as beyond review.

Should an overdue ETA automatically become ATA? No. Keep arrival unconfirmed until an appropriate actual-event report is available.