Logistics — shipment tracking and on-time rate for a 3PL
15 minutes. Two CSVs. You play the ops manager at a third-party logistics company and find the hub that's killing your SLA.
The scenario
You’re the ops manager at Meridian 3PL, a mid-size third-party logistics provider operating 8 hubs across the US. Your customer contracts all specify a 92% on-time rate. Last month you missed it, and your biggest customer flagged it.
You need to know where you’re missing and why, fast. Four questions:
- What’s our on-time rate overall? — month-to-date, trending up or down?
- Which hub is the problem? — ranked by on-time rate.
- Is it the hub or the carrier? — decompose by both.
- Can we alert on breaches proactively — before customer complaints?
Download the sample data
What's our on-time rate?
Expected: overall ~89% last 30 days vs ~91% prior 30. Trend chart shows a clear decline starting ~14 days ago.
Keep it: + Save as Report — shared weekly with customers.
Which hub is the problem?
| Hub | Last 30d | Prior 30d | Target |
|---|---|---|---|
| ATL · Atlanta | 62% | 82% | 92% |
| DEN · Denver | 85% | 86% | 92% |
| ORD · Chicago | 89% | 88% | 92% |
| JFK · New York | 89% | 89% | 92% |
| DFW · Dallas | 92% | 90% | 92% |
| SFO · San Francisco | 93% | 92% | 92% |
| LAX · Los Angeles | 95% | 94% | 92% |
| BOS · Boston | 92% | 91% | 92% |
Is it the hub or the carrier?
The Agent returns: “All four carriers are down at ATL, not a carrier-specific problem. Likely a warehouse issue — consider a site visit or an op audit.” (The generator injected the signal on the hub side, not the carrier, which the Agent surfaces correctly.)
Keep it: + Save as Script — reusable when any hub trips the threshold.
Proactive SLA breach alerting
The Agent creates the Watch, runs it as a test once to verify, and confirms it’ll fire to Slack daily.
What you built in 15 minutes
- 1 Report — weekly on-time rate, customer-shareable.
- 1 Dashboard — hub-level live on-time map.
- 1 Script — hub deep-dive, reusable.
- 1 Watch — SLA breach alarm.
Your customers see the Report. Your ops team sees the Dashboard. You hear about problems from the Watch, not from the customer.
Next steps in this industry
- Connect real data — carrier APIs (UPS / FedEx / DHL all have tracking APIs), your WMS, your TMS.
- Add cost analysis — per-lane cost, per-shipment margin.
- Add customer SLA segmentation — Premium customers at 95%, standard at 92%, economy at 85%.
Nearby tutorials
- E-commerce — if you’re the merchant shipping, not the carrier.
- Manufacturing — if you own the production, not just the delivery.