A shipment rarely starts to fail at the moment a deadline is missed. The delay usually begins earlier: cargo is not truly ready, a permit still lacks technical data, document drafts remain unapproved, a vessel schedule changes without an owner updating the plan, or the remaining time becomes shorter than the time required to recover. A reminder sent on the final day is therefore not an early-warning system. For sea-import shipments—especially machinery, electrical and electronic equipment, and multi-SKU components—warnings should cover cargo readiness, booking, SI/VGM, documents, permits, ETA, customs filing, delivery order, cargo availability, free time and warehouse delivery. This article explains how to build a milestone register, risk thresholds, authoritative data sources, ownership and escalation so that an alert drives action instead of generating more email.

Operational reference for Importers, Procurement, Logistics, Customs, Accounting and Warehouse | Updated 20 July 2026

QUICK FACTS

WARN BEFORE RECOVERY BECOMES IMPOSSIBLE

The trigger must preserve recovery time, decision/data latency and a safety allowance for document amendments, rebooking, permits, trucking or contingency switching.

EACH MILESTONE NEEDS AN AUTHORITATIVE SOURCE

ETA comes from the carrier; permit status from the competent portal; cargo readiness from the supplier. The internal tracker consolidates but does not invent status.

ALERT ON EXCEPTIONS, NOT CONSTANT NOISE

Trigger when inputs are missing, an expected event does not occur, data conflict, or the remaining time enters the risk window.

EVERY ALERT NEEDS AN OWNER AND NEXT ACTION

A useful alert states the gap, threatened deadline, impact, accountable person, next action and escalation time.

Illustration for How to Set Up Early Warnings for Logistics Milestones at Risk of Delay — Illustration of the logistics topic, document or operation discussed in the article.

SCOPE OF APPLICATION

This article primarily applies to FCL/LCL sea-import shipments for trading and manufacturing companies, especially machinery, electrical and electronic equipment, technical components and multi-SKU cargo. The framework can be adapted to air, road and rail by replacing cut-offs, event sources and recovery times.

Boundary: T-7, T-3, T-1 or hourly thresholds are internal configurations, not universal standards. They must be calibrated from actual lead times by route, carrier, cargo and regulatory process.

KEY TERMS

TERM	MEANING	ROLE IN EARLY WARNING
Milestone	An operational point with a clearly defined completion condition.	Defines what must happen and what evidence closes the step.
Hard Deadline	An external deadline set by law, carrier, terminal, customer or contract.	Should not be the first alert time.
Internal Deadline	An earlier internal completion time.	Creates a buffer for correction or contingency.
Recovery Time	The realistic time required to resolve an exception.	Basis for amber and red thresholds.
Safety Allowance	Additional allowance for uncertainty after recovery time and decision/data latency have been measured.	Prevents the amber and red thresholds from overlapping and avoids over-optimistic planning.
Trigger	A time-, event- or data-based condition that creates an alert.	Supports exception management rather than repetitive reminders.
Escalation	Routing an unresolved alert to a higher decision authority.	Prevents alerts from remaining idle in one inbox.
Control Tower	A central mechanism for data, exception visibility and coordination.	It may be a process plus dashboard, not necessarily a specific software product.

HOW EARLY WARNING WORKS

1. A DEADLINE IS NOT THE FIRST SIGNAL

The deadline is the endpoint. Early warning monitors the conditions leading to it. SI cut-off may still be open, but a warning is already justified when the supplier has not confirmed package count, gross weight or consignee and there is insufficient time for draft review and correction.

2. THRESHOLDS MUST REFLECT RECOVERY TIME

Separate three components: recovery time to execute the corrective action, decision/data latency while waiting for authority or reliable data, and a safety allowance for uncertainty. A practical control formula is: AMBER trigger = hard deadline – (recovery time + decision/data latency + safety allowance). The internal deadline is the company’s required completion point and does not automatically equal the alert trigger.

3. USE THREE TRIGGER TYPES

Time: remaining time enters the risk window while the milestone is incomplete.
Event: ETA changes, cargo is rolled, booking is cancelled, gate-in does not occur, or a permit is returned for supplementation.
Data: model, package count, weight, consignee, expected HS classification or Incoterms conflicts across sources.

4. AN ALERT MUST SUPPORT A DECISION

A “due soon” message without accountability, response logic and escalation only creates noise. The minimum payload should include shipment ID, milestone, requested–planned–estimated–actual time/event classification where supported, event time, source-update time, deadline and time zone, expected impact, owner, next action, closure evidence and escalation time.

MILESTONE RISK MATRIX

MILESTONE	EARLY SIGNAL	AUTHORITATIVE SOURCE	POTENTIAL IMPACT	ACTION
Cargo Ready Date	QC, packing, labels or final packing data are incomplete.	Supplier, QC record, loading photos, packing data.	Lost booking, rolled shipment, truck waiting or production disruption.	Confirm remaining tasks and evidenced ready date; hold a backup sailing.
Permit/specialised inspection	Model, catalogue, test report or application data are missing or returned.	Specialised portal, competent authority, technical file.	Cargo arrives before regulatory readiness.	Set an internal deadline from actual processing lead time; escalate technical gaps.
Booking and cut-off	No confirmed booking; cut-off, depot or terminal changes.	Carrier, forwarder, terminal.	No container, missed CY/CFS cut-off or vessel roll.	Reconfirm local time and retain a next-sailing option.
SI/VGM/draft B/L	Package count, gross weight, party data or approval is missing.	SI, packing data, carrier portal, draft B/L.	B/L or manifest amendment and release delay.	Lock master data, use four-eye review and obtain accepted/processed evidence.
Pre-alert/import documents	Invoice, packing list, B/L/AWB, C/O or revisions are incomplete.	Supplier, forwarder, bank, issuing authority.	Late customs preparation, C/O issues or delayed release.	Open a discrepancy log and prioritise fields affecting declaration and title/release.
ETA/ATA/cargo availability	ETA moves; vessel arrives but cargo is not discharged or deconsolidated.	Carrier, terminal/CFS, arrival notice.	Wrong truck or warehouse plan.	Track ETA, ATA, discharge and cargo availability as separate milestones.
Customs filing	Classification, policy, value or file readiness remains open.	Company records, customs system, broker.	Late filing, supplementary declaration or clearance delay.	Create a file-ready gate before planned filing; do not use ETA as the only trigger.
D/O/eDO and local charges	Release condition, invoice, authority or payment is pending.	Carrier/NVOCC/forwarder, bank, accounting.	No delivery order despite customs progress.	Separate release, payment and eDO status controls.
Free time and warehouse delivery	No separate Last Free Day for DEM/DET/Storage; no truck or warehouse slot.	Carrier tariff/confirmation, terminal, depot, warehouse, transporter.	Charges, truck waiting or late empty return.	Backward-plan from each Last Free Day and hold backup slots.

ALERT LEVELS AND THRESHOLDS

LEVEL	TRIGGER	REQUIRED RESPONSE	CLOSE WHEN
GREEN – CONTROLLED	Remaining time exceeds recovery time + decision/data latency + safety allowance; inputs, source and owner are confirmed.	Monitor at the defined update cadence without mass email.	The milestone completes with valid evidence or remains outside the alert window.
AMBER – AT RISK	Remaining time has entered the total buffer but is not below recovery time; or inputs are incomplete, confirmation is missing or the source update is stale.	Owner confirms cause, dependencies, action and next update time.	Completion evidence is obtained, or an approved action restores sufficient buffer and the system recalculates Green.
RED – HIGH RISK	Remaining time is below recovery time, or a critical dependency/data conflict blocks the current plan while the hard deadline has not yet passed.	Escalate to decision authority; approve contingency, cost, risk and decision deadline.	Contingency is executed, a new baseline is confirmed and the alert/incident remains auditable.
CRITICAL – MISSED/NO RECOVERY	The hard deadline has passed or no feasible option remains to protect the original plan.	Open an incident log, notify stakeholders and control cost, claims and related legal/contractual obligations.	Impact is contained, the new plan is accepted, accountability and root cause are recorded.

DATA AND RECORDS REQUIRED

A milestone register requires more than a deadline column.

DATA GROUP	REQUIRED FIELDS	CONTROL PRINCIPLE
Identification	Shipment ID, PO, booking, B/L/AWB, container, SKU/model.	Use one shipment identifier across functions.
Milestone	Name, completion rule, event classifier (requested/planned/estimated/actual where supported), event time, source-update time, time zone and calendar basis.	Do not let estimated overwrite actual; distinguish event time from the source update time.
Source	Issuer/source, link/email/portal, source-update time, system-receipt time and confirmation status.	The tracker records status; it must control data freshness and trace back to the source used for confirmation.
Dependencies	Required input, prior milestone and external response.	Alert dependencies as well as final deadlines.
Responsibility	Owner, backup, reviewer, escalation owner.	Assign named people, not only a department.
Threshold	Recovery time, decision/data latency, safety allowance, internal deadline and amber/red triggers.	Keep thresholds non-overlapping; calibrate with actual data and update after incidents.
Evidence	Confirmation, accepted status, declaration number, eDO, gate event, record.	Do not close an alert with “handled”.
Exception	Cause, impact, action, new deadline and cost.	Use history to improve buffers and supplier evaluation.

IMPLEMENTATION PROCESS

Map the shipment journey: pre-shipment, pre-carriage, main carriage, arrival, customs and delivery.
Select decisive milestones: hard deadlines, external dependencies, high delay cost or low recoverability.
Define completion: “booking confirmed” requires booking number, vessel/voyage, cut-off and location—not a verbal promise.
Assign source and time semantics: identify the source used to confirm each event; separate requested/planned/estimated/actual, event time, source-update time, time zone and calendar/working-day basis.
Measure recovery time and latency: use prior shipments to separately measure execution time, decision/data-response latency and uncertainty requiring a safety allowance.
Set non-overlapping internal deadlines and triggers: use Amber when the total buffer is entered and Red when remaining time is below recovery time or a critical dependency is blocked; also retain event- and data-conflict triggers.
Assign owner, backup and escalation: define response times and decision authority.
Design the alert payload: shipment, milestone, gap, impact, next action, owner and due time.
Pilot by route: measure true alerts, false alerts, response time and saved deadlines.
Review after shipment: update buffers, remove non-actionable alerts and add new root-cause triggers.

Control point: Do not automatically close an alert when a new email or ETA update appears. Verify the correct shipment ID, evidence, revision and event classifier, and never allow estimated/planned data to overwrite an actual event.

RISKS AND COMMON ERRORS

ERROR	CAUSE	IMPACT	CONTROL
Alert only on the deadline date	Recovery time not considered.	The issue is known but no longer recoverable.	Set an internal deadline from recovery time.
One threshold for every route	Rigid template.	Alerts are too early or too late.	Segment by mode, route, carrier, cargo and supplier.
Track ETA but not dependencies	Focus on vehicle location.	Cargo arrives without permits, D/O or warehouse slot.	Track document, release, customs and delivery readiness.
No alert owner	Group email only.	Everyone knows; nobody acts.	Assign one owner and one backup.
Internal data replaces source data	Manual copy or old schedule.	Wrong cut-off, ETA or free time.	Store source, timestamp and confirmation status.
Estimated/planned is merged with actual	The system stores only one timestamp and overwrites previous values.	A new ETA is treated as ATA; a milestone may close or trucking may be dispatched incorrectly.	Store event classifier, event time, source-update time and change history; actual events are not overwritten.
Too many alerts	Every change creates email.	Users ignore material warnings.	Alert only actionable exceptions and classify severity.
Close by verbal confirmation	No evidence rule.	Problem reappears downstream.	Define closure evidence for every milestone.
No incident review	Focus only on current shipment.	Buffers and triggers remain inaccurate.	Record root cause and actual recovery time.

LEGAL AND REFERENCE SOURCES

Early warning is an internal governance mechanism. It does not replace legal deadlines, carrier/terminal terms or authority confirmations.

SOURCE	STATUS / ROLE	USE
DCSA Track & Trace standards	Container event-data standards. Public documentation lists T&T 2.2; the 2026 Roadmap states that 3.0 is in alpha/beta.	Use event vocabulary, classifiers and shipment phases from the stable version actually implemented by the provider; do not treat roadmap/beta material as operational status.
GS1 EPCIS	Event-based visibility standard describing what–when–where–why–how.	Reference event structure, time, location, status and business context; it does not establish legal deadlines.
WCO Data Model	Cross-border data model; WCO announced Version 4.2.0 on 15 July 2025.	Reference harmonised fields and interoperability; it is not a mandatory enterprise milestone or alert-threshold framework.
WCO–IAPH Guidelines	Guidance on Customs–port cooperation, digitalisation, governance and interoperability.	Reference coordination and data-governance design at ports; it does not replace official carrier, terminal or Customs status.
54/VBHN-VPQH dated 23 March 2026	Consolidated Customs Law, Office of the National Assembly.	Points c and dd of Clause 2 Article 18 support accuracy, consistency and record-retention controls; the law does not prescribe internal Amber/Red thresholds.
Circular 121/2025/TT-BTC	Ministry of Finance; issued 18 December 2025; effective 1 February 2026.	Check current customs procedures and documents for compliance milestones; do not infer a deadline without identifying the applicable provision.

DCSA TRACK & TRACE DCSA ROADMAP 2026 GS1 EPCIS WCO DATA MODEL WCO–IAPH GUIDELINES 54/VBHN-VPQH CIRCULAR 121/2025

FAQ

1. Should every shipment use T-7, T-3 and T-1 alerts?

No. These are labels only. Thresholds must reflect recovery time, route, mode, cargo, weekends, time zones and stakeholder response.

2. How much ETA change should trigger an alert?

Do not use a fixed number of days alone. First identify whether the timestamp is requested, planned, estimated or actual, when the source was updated, and whether the new ETA affects permits, filing, warehouse/truck slots, free time, customer delivery or production.

3. Is a calendar reminder enough?

Only for simple milestones. Dynamic milestones require status-, source- and exception-based triggers.

4. Who should own an alert?

The person able to drive the milestone and provide closure evidence. A manager with cost or contingency authority may be the escalation owner.

5. Should management receive every alert?

No. Management should receive red/critical alerts or issues beyond the owner’s authority.

6. Can free time use one common Last Free Day?

Do not assume so. DEM, DET and Storage may have different start events, terms and charging parties.

7. Which KPIs show warning quality?

On-time internal milestones, rescued deadlines, response time, false-alert rate, red-alert duration and avoidable delay cost.

APPLICATION NOTE: Milestones, cut-offs, document deadlines and free time depend on the contract, transport mode, carrier, terminal, competent authority, time zone and actual shipment file. Confirm the source, completion rule and decision authority before automation.

TGIMEX IMPLEMENTATION SUPPORT

TGIMEX helps businesses turn the article into a shipment-ready checklist, covering input-data review, dossier preparation, milestone control, and coordination with the relevant parties.

Convert guidance into checks

Assign an owner and deadline to every operational control point.

Reconcile shipment data

Compare booking, transport, commercial, customs, and delivery evidence.

Manage operational risk

Record discrepancies, actions, and decision evidence to prevent recurrence.

Discuss your shipment dossier

ELECTRICAL – ELECTRONICS – IT EQUIPMENT

F&B

MACHINERY

HOUSEHOLD GOODS

COSMETICS – PERSONAL CARE