Day 20 operational checklist
An ETA change is a signal. The response needs an owner and evidence.
Use this seven-stage checklist to verify the change, review operational impact, assign decisions, escalate missing responses, notify affected teams, and retain closure evidence without treating a feed estimate as a guaranteed arrival.
By Ayhan Karaca, Co-Founder · Updated: September 6, 2026
Private in this tab · no upload
Build the ETA exception-response record
Set a status for each control. Use not applicable only with a bounded reason; verify critical controls before closure.
Detect
Capture the change without turning it into an unverified conclusion.
Compare
Preserve what changed and the reference used for the response.
Assess
Review linked evidence and clocks before selecting an action.
Assign
Make the decision owner, partner question, and response clock explicit.
Escalate
Use the response deadline and material impact to trigger action.
Decide and notify
Approve the action and align every affected team to one record.
Close or monitor
Retain the decision trail and define the next observation condition.
What should happen when a container ETA changes?
Capture the source and prior baseline, verify that the event belongs to the correct shipment, then decide which commitments, documents, cost clocks, and teams may be affected. A changed timestamp alone is not a completed response.
Keep observed carrier or terminal evidence separate from internal decisions. Record who approved the operating change and which confirmation is still missing.
| Stage | Primary responsibility | Decision evidence |
|---|---|---|
| Detect and verify | Tracking or logistics owner | Source, observation time, prior ETA, new ETA |
| Assess impact | Operations with delivery, document, and cost owners | Affected commitment and required action |
| Assign and request | Named decision owner | Partner question, response deadline, fallback |
| Escalate and decide | Escalation owner | Decision, approval, notification list |
| Close or monitor | Shipment record owner | Resolution evidence and next monitoring condition |
Which decisions should not be inferred from the ETA feed?
Do not infer customs release, pickup availability, free-time, delivery appointment viability, partner acceptance, charge liability, or a guaranteed arrival from one ETA value. Verify each material decision with the appropriate carrier, terminal, broker, partner, contract, or authority source.
FMC detention and demurrage materials provide deadline and billing context, not a universal rule that every ETA shift creates a charge. The checklist therefore asks for a cost-clock review without predicting or assigning liability.
When should the exception be escalated?
Escalate when a critical source cannot be verified, a delivery or document decision lacks an owner, a partner misses the recorded response deadline, a cost or filing clock may be affected, or teams act on conflicting timestamps. The correct escalation path depends on the shipment and contracts.
Closure requires a recorded decision and either a resolved action or an explicit monitoring condition. A quiet inbox is not closure.
Where can workflow software help?
Tyllus can keep ETA observations, partner follow-ups, document state, costs, owners, and decisions in one shipment context. It cannot guarantee carrier data, terminal availability, customs outcomes, partner responses, or prevention of charges.
Give the next ETA decision an owner.
Bring one exception path to a Tyllus workflow review and map the source, response deadline, decision, and closure evidence.