Job 03·Exceptions
The board surfaces only what needs you.
A dispatcher shouldn't scan a hundred healthy loads to find the one that's slipping. Tandem keeps the routine running on its own and raises only the exceptions — the off-route truck, the missed appointment, the missing POD.
Job 03·Exceptions
Every load,
one quiet board.
One row per load, the columns dispatchers actually live in — equipment, both appointments, live driver position, miles, and margin side by side. Healthy loads stay quiet; only the ones that need a decision rise to the top.
What you get
Less noise. Better calls.
Healthy loads stay quiet
A load on schedule needs no attention, so it gets none. The board doesn't shout about what's already fine.
Exceptions sorted by severity
Off-route, late, and at-risk loads rise to the top, ranked by what's most likely to cost money if it's missed.
Your whole operation on one surface
Every mode, every customer, every truck on one board — truckload, LTL, reefer, flatbed, drayage — not a tab per lane.
The routine runs itself
Tandem advances statuses, sends the check-ins, and chases the documents on every row, so the desk handles only the calls that need judgment.
How it works
How exception-based dispatch works
How Tandem turns a wall of loads into a short, ranked list of the ones that actually need you.
- 01
Every load is monitored
Tandem watches status, ETA, dwell, and documents on every active load at once.
- 02
Healthy loads are suppressed
A load tracking on schedule with its paperwork in stays off the alert surface — no noise.
- 03
Exceptions are raised and ranked
A drift, a missed window, or a missing document is flagged and sorted by severity, so the most consequential lands first.
- 04
Dispatch works the top of the board
The team spends its time on the loads that need a decision, and clears them from the surface as they're resolved.
Questions
Frequently asked
What is exception-based dispatch?
Exception-based dispatch is a workspace that hides the loads running normally and surfaces only the ones that need a human — off route, running late, or missing paperwork. Instead of scanning every load, a dispatcher works a short, ranked list of real problems.
How does Tandem decide what counts as an exception?
Tandem compares each load against its plan — the appointment windows, the expected route, the documents due — and flags the deviations. A drift off route, a slipping ETA, a long dwell, or a missing POD becomes an exception; a load meeting its plan stays quiet.
Can a manager still see every load?
Yes. The exception view is the default working surface, but the full board — every active load and its status — is always one click away for anyone who needs the whole picture.
Rate con to remittance
Bring control to your next load.
Exceptions is one of five jobs Tandem takes off the desk — intake, visibility, exceptions, drivers, and settlement, on one desk. See it on your freight.