A control tower lead does not win the day with more screens. They win when operations have one exception queue, a severity standard, and a system of record that does not depend on “the Excel Juan sent”.
This playbook covers, for Mexico shippers:
- Rituals and triage
- KPI targets
- WhatsApp vs TMS
Part of the same series as the warehouse manager, traffic lead, and freight CS lead. Also see what a control tower is.
Tower lead role: decide, do not only watch
The tower turns operational noise into decisions: reschedule? notify the customer? escalate security? ask traffic for cover? If the team only “monitors” without exception owners, you have a video wall, not a tower.
Daily exception ritual
OpenException queue
One list ranked by severity. No three Excels plus a WhatsApp group in parallel.
Cycle 1ETA breaches
Compare ETA vs commitment / appointment window. Flag what breaks OTIF today.
Cycle 2Carrier confirmation
Confirm ETA and location with evidence in the system, not only “ok” in chat.
ProactiveCS / customer update
Escalate material events to CS with fact + impact + new promise. No surprises.
End of windowCycle close
Actions, owners, dates. P1 exceptions do not sleep without an owner.
The tower that decides, not only refreshes
Detect, triage, confirm, and close: four verbs to govern exceptions. Without Close, the video wall is decoration.
Detect
Signal in a single queue: ETA, diversion, detention, GPS hush. Guiding question: what breaks the commitment today?
Triage
Assign P1–P3 with SLA and owner. Guiding question: what gets worked first and at what threshold?
Confirm
Carrier / dock / CS with evidence in-system. Guiding question: do chat and TMS tell the same story?
Close
Action, owner, date, and a trail for learning. Guiding question: who and by when?
WhatsApp vs TMS as system of record
WhatsApp as SoT
- Different versions of the same ETA
- No reliable timestamp or audit
- Escalation by who shouts loudest
TMS / track as SoT
- One event = one time = one owner
- History usable for claims and learning
- WhatsApp stays a channel, not the file
Severity triage (P1–P3)
P1
Examples: Theft / SOS, ETA break for a critical customer, sensitive cargo stopped
First-response SLA (target): Minutes, with a clear war-room
P2
Examples: Growing detention, diversion, same-day appointment at risk
First-response SLA (target): Same operating window
P3
Examples: Status noise, non-blocking documentation pending
First-response SLA (target): Within the day / next cycle
Mexico context: ETA, detention, sensitive lanes
Detention and appointments
Many “transit exceptions” start at the dock. Coordinate with warehouse and yard.
Corridors and security
The tower is not escort, but it escalates early using your matrix (P×I guide).
Real visibility
GPS + events + logistics visibility beat narrated status.
Tower KPIs (management targets)
- Minutes to first action
- P1
- ETAs confirmed vs commitment
- ↑
- Closes with evidence
- ≥
- Detention vs baseline
- ↓
| KPI | Example target | Why it matters |
|---|---|---|
| Time to first action on P1 | Minutes (set your threshold) | Avoids decorative tower |
| % ETAs confirmed vs commitment | Improving weekly | Promise quality |
| % exceptions closed with evidence | ≥ internal target | Ends “we saw it in chat” |
| Avg detention / events | Down vs baseline | Cost and dock relationship |
| Proactive CS pushes | Before the customer complaint | Loop with customer service |
Fit with warehouse, traffic, CS, procurement
Warehouse
Dock and ready-to-load feed (or break) the exception queue.
Traffic
Cover and reassignment when the exception cannot recover en route.
Freight CS
Gets facts + impact + new promise, not screenshots.
Procurement / audit
Documented detention and events support defendable disputes.
OCL adds track and exception agents so the queue does not return to Excel.
Does your tower decide… or only refresh screens?
In a demo we show an exception queue, alerts, and shipment file (GPS / events / POD) as a TMS complement.
Book a demoSources and further reading
Key takeaways5 points
- The tower does not live in Excel: it lives in an exception queue with severity, owner, and resolution ETA.
- WhatsApp is a channel; TMS/track is the system of record.
- Ritual: morning queue, carrier ETA confirmation, breaches vs promise, close with actions.
- In Mexico, detention, appointments, and sensitive corridors belong in triage.
- Golden rule: every tower cycle closes with actions, owners, and dates.
Frequently asked questions
Orchestrates in-transit exceptions: a severity-ranked queue, ETA breaches, carrier confirmation, and actionable updates to CS and traffic. They do not just “watch screens”; they decide what gets worked first and with what evidence.
Excel is a lagging snapshot. ETAs, detention, and diversions change in minutes. Without a live system of record (TMS/track), the team fights file versions while the customer waits for status.
No. WhatsApp is a contact channel; the TMS or track system is the source of truth. Chat accelerates, but without a file (event, time, owner) there is no audit trail or learning.
Define P1–P3: OTIF/customer impact, security/theft risk, cost (detention), and time to commitment. Each severity needs a first-response SLA and owner. Without triage, everything is “urgent” and nothing closes.
Beyond ETA: appointment confirmation, dock detention, high-risk corridors (escalate to security), and track-and-trace evidence. The tower is not a physical escort, but it must escalate early.
Track agents, exception alerts, and a unified shipment file (GPS, events, POD) so the queue lives outside Excel and chat. Complements your TMS; does not ask you to abandon what already works.