[solutions · by industry]
Four sectors. Four clocks.
An exception is a deadline with a cost attached, and what the deadline is anchored to differs by sector in kind, not in label. Four sectors where we can state the difference. Where we could not, we did not write the section.
[soc 2 type ii · 14-day trial · no card]
[01 / food and beverage]
What if the freight expires before it arrives?
A late reefer is not late. It is losing value by the hour, and below the receiver's shelf-life floor it is refused at the dock. The deadline here is physical, and no apology extends it.
- Tolerance keys to remaining shelf life at the revised ETA, not to the promised date
- A missed receiving appointment re-books at flag time: slots come back in 24 to 72 h while the shelf life keeps burning
- Dock rejections last quarter: 1, was 9
- [when]
- Issue is LATE by more than 8 h
- [and]
- Product class is REFRIGERATED
- [and]
- Remaining shelf life at revised ETA below 60%
- [then]
- Owner SR S. Rivera · deadline +2 h · price the re-book and the divert before the receiver's 55% floor
Matched 17 times in 30 days · median close 3.4 h · 1 divert to a closer DC
The receiver's floor is a contract term. Rule 12 works backward from it. [illustrative data]
[02 / industrial and machinery]
What if a $40 part stops the line?
Severity by declared value is the wrong key here. The cost of a short-shipped kit is the line it feeds: idle crew, missed sequence, overtime to recover. Throughline lets the work order set the severity.
- Severity keys to the work order the part feeds, not to the invoice value
- A line-down flag escalates to the plant scheduler with the recovery options attached
- Short-ship claims file from the thread inside the carrier window: 100%, was 62%
[freight-caused line stoppages · per quarter · illustrative]
2/qtr
[was 11 · severity keyed to the work order]
[the clock is different · the queue is the same]
[03 / consumer packaged goods]
What if the receiver writes the rules?
The retailer sets the delivery window, and a miss is not an apology. It is a deduction on remittance weeks later. The job is twofold: hit the window, and when you did hit it, prove it.
- Tolerances import per retailer routing guide, so the lane carries the retailer's window
- A misroute to the wrong DC surfaces while the freight can still turn: 88% caught in transit
- The thread is the dispute file: 214 timestamps, POD and the appointment record in one export
[disputed deductions recovered · illustrative]
71 %
[deductions disputed with the thread attached]
[what the dispute looks like]
DED-2214 retailer deduction $1,842 disputed with thread RECOVERED
The deduction arrived five weeks after the delivery. The evidence was already assembled. [illustrative data]
[04 / building products]
What if the delivery window is a crew on a roof?
Storm season triples volume in the exact week carrier performance dips. The promise is not to a dock. It is to a booked crew and a project sequence, and the person the customer calls is the sales rep.
- Surge mode tightens tier-A tolerances while volume spikes, instead of relaxing them
- Escalations copy the sales rep who owns the account, because that is who the customer calls
- Job-site rows carry the crew booking, so a reroute decision knows what an idle morning costs
- Promised-date hit rate, tier-A customers, peak weeks
- 96.4 %
- Volume the week after a storm, against baseline
- 3.1 x
- Escalations resolved before the customer called
- 9 of 10
[illustrative · consistent with the roi model defaults]
[why only four]
Where is your sector?
Possibly in one of the four above, under a different name. Possibly not here at all.
If a sector's exception management differs only in the noun, its page would be one of these with the words swapped, and you would notice. These four differ in what the deadline is anchored to. If yours differs in kind too, bring one lane to a demo and watch it modeled live.
[twenty minutes]
Your sector's lanes, live on the call.[next step]
See your sector in the queue.
The library's entries are named by sector and shape. The demo runs on your lanes instead.