THE METHOD

Watch. Classify. Re-baseline.Tell first. Close.

The event arrives raw — a discharge scan at a hub, a blanked departure, a hold code. What must leave is a customer who already knows the new plan. Five moves close that gap, with your approval on everything outbound.

01 · WATCH

Every box on the sweep.

The manual version of tracking is a morning ritual: a coordinator opens each carrier portal in turn, re-keys milestones into an Excel sheet, and hopes nothing moved since it saved. The desk replaces the ritual with a watch — resolving each shipment the way freight is actually numbered (booking number, then BL, then container), and holding every milestone current from empty gate-out to empty return. Nothing depends on someone remembering to look.

every milestone on the file · portals + spreadsheets retired

02 · CLASSIFY

Anomalies become named exceptions.

A raw event feed is homework, not an answer. The desk reads the pattern and names the exception — rollover, blank sailing, customs hold, transshipment delay — with its reasoning shown, not just its verdict. Rollovers are the proof case: carriers rarely announce them, so the desk infers them — your box discharged at the transshipment hub but never loaded onto the booked vessel. That mismatch is a rollover whether anyone said so or not, and it’s caught when it happens, not when your customer’s trucker turns up against the old ETA.

ROLL · BLANK · HOLD · T/S · discharge/load mismatch → ROLL

03 · RE-BASELINE

The dead ETA is replaced everywhere.

An exception makes the old ETA fiction — and fiction is what customers book truckers against. The desk recomputes the arrival from what actually happened: the vessel the box actually loaded on, the new rotation, the exam clock still running. Then it identifies everyone whose plans hung on the old date — the consignee’s delivery slot, the notify party, the downstream leg — so one new baseline replaces the dead one across the whole file, and no two people are working from different truths.

new ETA computed · affected parties identified

04 · TELL FIRST

The update lands before the question.

Every affected customer gets a drafted update on their own channel — email or WhatsApp — saying what happened, why, and what the new plan is. Cadence is configured per customer: some want every move, some a weekly digest. And it’s never a firehose — milestones that matter become updates (departed, arrived, out for delivery, exception, POD); internal noise doesn’t. Each draft waits for your approval until you dial that update type to auto. The desk earns autonomy the way a new hire does.

their channel · your approval until auto

05 · CLOSE

The chase starts at the milestone.

Delivered isn’t done. Many customers’ payment clocks start only when the signed POD reaches their accounts team — and that paper has historically surfaced days to weeks after the freight did. The delivery milestone triggers the customer update, and the POD chase runs on its own from there — on the milestone, not on a month-end sweep of what is missing. The file closes with its whole story attached: every event, every exception, every message sent.

delivery triggers the update · the POD chase runs on its own

HOW WE START

We scope the first workflow, integration requirements and implementation plan with your team.

DISCOVER

We map your live shipments, lanes and carriers, plus the customer map — who gets updates, on which channel, at what cadence.

DESIGN AND CONFIGURE

The watch, the exception set, the update types and the approval rules are configured around how your desk already runs — alongside CargoWise, Logi-Sys, Kale, Shipsy, Magaya, or no TMS at all.

VALIDATE

The desk shadows your live shipments — classifying exceptions and drafting updates your team grades against what actually happened. Nothing goes outbound.

IMPLEMENT AND EXPAND

Live under approval: real updates reach real customers after your sign-off. Update types earn their way to auto, and more of your traffic joins the watch.

Put a lane on the watch