[platform]
A list that ends.
Throughline is three screens: a queue of what broke, a rule that names an owner and a deadline, and a thread that closes itself. This page walks all three.
[soc 2 type ii · 14-day trial · no card]
[01 / the queue]
What lands in the queue?
Only exceptions. A shipment tracking on time never appears here, so the queue is short, and short means it gets read.
- 5 min polling on every connected feed
- 38 min median from carrier signal to flagged row
- Tolerance is set per lane, not globally: ORD → DFW forgives what ORD → DFW can afford
| Shipment | Issue | Owner | Lane | Carrier | Due by | Action |
|---|---|---|---|---|---|---|
| SHP-48211 | LATE | KT | ORD → DFW | Estes | 13:41 | Thread |
| SHP-48207 | SHORT | JL | ATL → MEM | Saia | 15:30 | Triage |
| SHP-48198 | MISROUTE | RM | LAX → PHX | Knight | 12:00 | Reroute |
| SHP-48187 | LATE | JL | ORD → MSP | Dayton | 17:00 | Watch |
| SHP-48173 | LATE | AC | DFW → ELP | Averitt | 16:15 | Triage |
| SHP-48160 | SHORT | AC | SAV → CLT | XPO | 15:00 | Resolve |
[02 / the rule]
Who fixes it, and by when?
Rules are plain fields: lane, carrier, customer tier, dollar value. The first match wins, and the queue shows its work.
- Owner and deadline attach in the same second as the flag
- 94% of exceptions resolve without paging a human
- An unmatched exception falls to a default owner, never to nobody
- [when]
- Issue is LATE by more than 12 h
- [and]
- Declared value at or above $25,000
- [and]
- Customer tier is A
- [then]
- Owner KT K. Tan · deadline +4 h · escalate to M. Osei at the deadline
Matched 41 times in 30 days · median close 5.1 h · 2 escalations, both answered
Rule 07 assigned SHP-48211 to K. Tan at 09:41. It has done the same 41 times this month. [illustrative data]
[the queue at zero is the whole point]
[03 / the close]
What does resolved actually mean?
Closed by criteria, not by mood: the carrier has a confirmed recovery plan and the customer accepted the revised date. The row leaves the queue on its own.
The thread stays queryable for the life of the account. Retention and export terms live on the trust page.
-
09:41
Flagged. Estes 214 shows arrival +38 h against ORD → DFW lane tolerance.
severity high · declared value $31,400
-
09:41
Routed by rule 07. Owner K. Tan · deadline 13:41 · escalation armed.
-
09:58
Carrier case opened. Estes ref E-77412, recovery options requested.
-
10:31
Recovery confirmed. Reload on the next linehaul, revised ETA Thursday 08:00.
-
10:52
Customer notified. Revised date accepted; receiving dock slot moved.
-
11:04
Closed. Both criteria met. RESOLVED
carrier plan confirmed · customer accepted · no human needed after 10:52
flag → resolved 1 h 23 m · deadline margin 2 h 37 m · thread archived
[twenty minutes]
Watch a week of your own freight run through it.[04 / plumbing]
What does it read?
[no tms required to start]
-
[start here]
No TMS integration requiredCarrier credentials or an EDI 214/990 feed is enough to go live. SAP and NetSuite connectors are additive, never prerequisites.
-
[edi]
EDI 214 / 990Status and tender responses read directly off the wire.
-
[api]
Carrier APIsEvery connected feed polled on a 5 minute cycle.
-
[email]
Email ingestForwarded status emails parsed into the same tolerance model.
-
[out]
Exports + webhooksCSV, Parquet and webhooks out. The full directory lists every connector.
[illustrative integration set · vendors named as integrations only]
[what changes]
What actually changes?
Buyer-side numbers from the modeled default case: 12,000 shipments a month at a 6% exception rate. The calculator shows every formula.
[median detection]
38 min
[resolve without paging]
94 %
[unowned exceptions]
0
[saved per exception]
11.2 h
[illustrative product metrics · defaults from the roi model]
[next step]
See your carriers in it.
Twenty minutes with your carrier list, live on the call. Or put a number on the status quo first.