Container ETA response
What should an import team do when a container ETA changes?
When a container ETA changes, record the source and time, identify the decision it affects, assign the next action to one owner, and keep the confirmation with the shipment. Tyllus gives that response a shared operating context instead of leaving it across updates, files, and inboxes.
By Ayhan Karaca, Co-Founder · Updated: August 19, 2026
An ETA change is a decision signal, not a completed update
A new estimated arrival time can affect pickup planning, document readiness, broker coordination, customer communication, equipment return, or a cost review. It does not determine the right action by itself. The useful question is: which commitment, deadline, or dependency must now be reviewed?
The Federal Maritime Commission distinguishes demurrage from detention and explains that the applicable terms depend on the carrier and the circumstances. That makes a durable record of the changed signal and its follow-up more useful than treating every ETA change as the same type of risk.
| What to capture | Why it matters | What not to assume |
|---|---|---|
| Source and timestamp | Shows what changed and when it was seen | That an estimate is a confirmed arrival |
| Affected shipment reference | Keeps the update with the correct cargo context | That one identifier answers every partner question |
| Next decision and owner | Makes follow-up accountable | That visibility alone completes the work |
| Outcome or exception | Preserves the reason for the response | That a charge or delay was avoided |
Use four checks before escalating the update
First, confirm the source and whether the time is estimated, scheduled, actual, or still awaiting partner confirmation. Second, identify which downstream decision changes: documentation, pickup, delivery, empty return, customer promise, or cost exposure. Third, assign the next contact or decision to one owner. Fourth, record the received answer or reviewed exception so the shipment story does not restart in the next inbox.
Read the ETA change-response model
Capture the changed ETA and its source. Check the affected decision. Assign one owner for the next action. Retain the confirmation or reviewed exception with the shipment.
Where Tyllus fits
Tyllus connects ETA context with the shipment, documents, partner follow-up, exceptions, and cost evidence that the team needs for its next decision. It helps people see what changed, what is waiting, and who owns the response without rebuilding the shipment story from separate messages.
Tyllus does not control carrier schedules, carrier terms, terminal operations, or a partner's response. It does not promise an arrival date, free-time outcome, or avoided charge.
Measure the response before claiming the result
If an ETA-change workflow is important to your team, measure the time from source update to owned action, the age of unanswered partner requests, and any documented downstream charge or service exception. Keep estimates, external causes, and confirmed outcomes separate. That produces a credible improvement baseline without inventing a universal savings number.
Make every changed signal actionable.
See how Tyllus connects shipment context, owners, partner follow-up, and evidence around the next operating decision.