[solutions · by problem]

Seven jobs. One queue.

You arrive carrying a problem, not a category. Here are the three ways freight breaks and the four jobs each one leaves behind: what actually lands in the queue, and one number worth checking.

Book a demo Open the ROI calculator

[soc 2 type ii · 14-day trial · no card]

[01 / when freight breaks]

Which one is this morning's problem?

Three shapes cover most of what goes wrong between a tender and a dock. Each is a queue, a rule, and a close, tuned to that shape.

[late]

Catch the late shipment while the promise can still be kept.

A late load is only a crisis if you learn about it on Friday. Throughline reads the carrier's own 214 against the lane's tolerance and flags the slip in minutes, while the recovery window is still open. The rule attaches an owner and a deadline in the same second.

[median detection · illustrative]

38 min

[was the friday review]

[what lands in the queue]

SHP-48291 LATE owner K. Tan ORD → DFW Estes due 13:41

The 214 showed the slip at 09:03. This row existed by 09:41, owned and deadlined, before anyone opened a portal. [illustrative data]

[bites hardest in] food and beverage building products cs-01 · cs-04 · cs-06

[short-shipped]

File every short-ship claim inside the carrier's window.

Short shipments die in email threads: the window closes whether or not anyone finds the POD. Every SHORT row carries its BOL and POD from the moment it is flagged, so the claim files from the thread, not from a search.

[claims inside the window · illustrative]

100 %

[was 62%]

[what lands in the queue]

SHP-48312 SHORT owner A. Cho SAV → CLT XPO 22 / 26 pallets BOL + POD attached

Four pallets short at receiving. The paperwork rides on the row. [illustrative data]

[bites hardest in] industrial and machinery food and beverage cs-02 · cs-05

[misrouted]

Decide the reroute while the freight is still moving.

A misroute found in next week's carrier scorecard is a delivery failure. Found in transit, it is a decision: the row surfaces with reroute options attached and the cost of each, while turning the freight is still cheap.

[median reroute decision · illustrative]

3.2 h

[caught in transit · 88%]

[what lands in the queue]

SHP-48344 MISROUTE owner R. Malik LAX → PHX Knight scanned ABQ 2 reroute options

Wrong break-bulk. Both recovery routes are priced on the thread before the owner opens it. [illustrative data]

[bites hardest in] consumer packaged goods cs-03

[name the problem · it routes itself]

[02 / after the flag]

What happens after the flag?

Detection is the easy half. These four jobs are why the queue empties instead of scrolling.

[ownership]

Route every exception to a named owner with a deadline.

Escalation is the default wherever ownership is nobody's. Rules key the owner to lane, carrier, customer tier and value; an unmatched exception falls to a default owner, never to nobody.

[unowned exceptions]

[escalations reaching the vp · 2/mo, was 40 · illustrative]

[on the row]

routed by rule 07 owner K. Tan deadline +4 h escalation armed

[see also] the rule, on the platform tour industrial and machinery cs-06

[carrier accountability]

Walk into the QBR holding the carrier's own feed.

Every exception keeps its 214 timestamps, case reference and recovery record. The quarterly review starts from a shared ledger instead of a week of portal exports and a disputed spreadsheet.

[qbr prep · illustrative]

25 min

[was two days of portal exports]

[on the row]

carrier case E-77412 214 timeline attached recovery confirmed 10:31

[see also] consumer packaged goods building products the feed directory

[customer commitments]

Tell the customer before the customer calls.

The revised date is proposed from the thread with the recovery plan behind it, so the dock slot moves once, not three times, and the promise you re-make is one you can keep.

[promised-date hit rate · illustrative]

96.4 %

[peak weeks, tier-a customers]

[on the row]

revised eta Thu 08:00 proposed 10:31 accepted 10:52 dock slot moved once

[see also] building products food and beverage cs-04

[month-end reporting]

Close the month from an export, not a reconstruction.

Every exception, cause, owner and close time is already a ledger. Month-end is one CSV or Parquet export; the schema is documented in the docs and the connectors in the directory.

[month-end reporting · illustrative]

20 min

[was a 9 h reconstruction]

[on the row]

june-exceptions.csv 1,412 rows cause · owner · close time 19 columns

[see also] the export schema the roi model it feeds

[twenty minutes]

Bring the problem. Watch it land in the queue, owned.

Book a demo Open the ROI calculator

[03 / the intersection]

Where does each problem bite hardest?

The same exception carries a different cost by sector. Rows link back up this page; columns open the sector pages.

Where each exception type bites hardest, by industry
Exception	Food and beverage	Industrial and machinery	Consumer packaged goods	Building products
Late	++ bites hardest: shelf life burns while it slips	+ present, not primary	+ present, not primary	++ bites hardest: a crew is booked against it
Short-shipped	++ bites hardest: paying for cases already shipped	++ bites hardest: a missing kit stops the line	+ present, not primary	+ present, not primary
Misrouted	+ present, not primary	− rarely decisive	++ bites hardest: wrong DC, chargeback attached	− rarely decisive

[++ bites hardest · + present · − rarely decisive · illustrative]

Six entries in the case-study library are named by exactly these coordinates: sector and shape. Filter it by either axis.

[next step]

Put a number on this morning's problem.

The calculator prices the status quo in your volumes. The demo puts your carriers in the queue, live on the call.

Book a demo Open the ROI calculator