Logistics and supply chain
From delayed loads to audited freight bills
Works delays, damage claims and freight bill audits

Agents check the documents on every load
- Late deliveries that lose customers
- Damage claims that wipe out the margin
- Overpaid carriers and unbilled accessorials
- 01
Order intake
Take customer orders and check addresses, volumes and delivery windows
Orders arrive in every format, and one wrong field sends a truck to the wrong dock
Agents takeTurns emailed orders and spreadsheets into clean orders
Owner · Customer service
- 02
Dispatch
Match loads to trucks and book carriers by lane
Last-minute loads mean phoning around for capacity
Owner · Carriers and settlement
- 03
In transit
Watch milestones and ETAs, and handle delays and reroutes
When a load slips, every affected order and customer is checked by hand
Agents takeLists affected orders and prices the reroute options
Owner · Control tower
- 04
Proof of delivery
Collect signed PODs and note shortages, damage and wait time
Missing PODs leave accessorials unbilled and settlement stalled
Agents takeChecks PODs and builds the accessorial evidence
Owner · Carriers and settlement
- 05
Claims
Open damage and shortage claims, pay customers and recover from carriers
Photos, PODs and contract terms have to be pieced into one file
Agents takeBuilds the claim file and the contract liability cap
Owner · Customer service
- 06
Freight settlement
Reconcile with customers and carriers every month
Carrier bills are checked line by line, and overcharges slip through
Agents takeChecks every line against loads, rates and accessorials
Owner · Carriers and settlement
Three teams, one organization context
These teams and flows are illustrative, not a specific customer.
Work agents take on
Request
KX-4820 is held at the Omaha hub by a weather closure. Pull every order on the truck with its promised delivery time, work out which ones trigger late penalties under contract, and compare waiting it out with switching to rail on time and cost
- Open API · TMS exception trigger
- TMS loads (HTTP plugin, read-only)
- Ops · Customer delivery terms
- Ops · Exception playbook
- Exception log

Run
- Pull every order on the load with its promised delivery time
- Check delivery terms and find orders facing penalties in code
- Compare waiting and rail on arrival time and cost
- Choose the option and approve any extra costDispatch lead Ryan Cooper
- Draft a notice for each customer on the chosen plan for service to send

Run
- Pull every order on the load with its promised delivery time
- Check delivery terms and find orders facing penalties in code
- Compare waiting and rail on arrival time and cost
- Choose the option and approve any extra costDispatch lead Ryan Cooper
- Draft a notice for each customer on the chosen plan for service to send
Every step is in the run trace

Where people decide
Agents prepare the work. Key decisions stay with people.
- 01
The dispatch lead decides reroutes, expedites and any extra cost
- 02
The claims lead decides settlement amounts and whether to pursue the carrier
- 03
Carrier disputes, payments and customer charges go through the settlement lead and finance
Start with one pilot
Try one workflow first, measure it, then roll it out.
Carrier bill audit
Bills arrive every month, rates are written into contracts and every exception traces back to a load
Before you start
- Three months of carrier bills with matching load exports
- Current carrier rate agreements and accessorial rules
- One auditor named by the settlement lead to review every exception
Measure first
- Days from the last bill arriving to a finished audit
- Share of flagged exceptions confirmed as valid
- Overpayments found after payment
When to stop
- Stop and return to manual audit if load matching fails in batches


















