No category
Who owns a freight exception? A responsibility matrix
Key Takeaways
Freight exceptions stall when ownership is unclear, not when information is missing. Logistics, customer service, sales and finance all hear about the problem, and each assumes another team is acting.
A RACI matrix answers 4 questions per exception: who does the work (Responsible), who owns the outcome (Accountable), who is asked first (Consulted) and who is told (Informed). Each row gets exactly one Accountable.
6 exceptions cover most of a logistics team's day: missed pickup, delay, cancellation, partial delivery, missing POD and invoice mismatch.
Wilson, by Cartage, is an AI logistics agent that does much of the Responsible work on these rows, such as contacting carriers, notifying the right people, rebooking from approved carriers, chasing PODs and auditing invoices, under approval rules the company sets.
The Accountable column stays with people: claims, customer commitments, carrier approvals and charges outside the rules.
Why do freight exceptions sit without an owner?
Freight exceptions sit without an owner because the news reaches several teams at once and nobody agreed in advance who acts and who only needs to know. A responsibility matrix settles that before the exception happens, so the first person who hears about it knows whether to act or forward it.
This affects manufacturers and distributors that coordinate their own carriers by email, phone and spreadsheets, where the shipment record lives in several inboxes. An exception is any event that pushes a load off plan: a missed pickup, a delay, a cancellation, a short delivery, a missing POD (proof of delivery, the signed receipt from the consignee) or an invoice that doesn't match the booking. Every hour without an owner adds cost on the road. ATRI found truck drivers were detained at 39.3% of stops in 2023, with $11.5 billion in lost productivity.
One late load, five teams
Monday 8:10 a.m. A load to a key customer was due at 10:00. The carrier dispatcher emails the logistics coordinator: the truck is stuck behind a closure, new ETA unknown.
Monday 9:30 a.m. The coordinator is on carrier follow-up for three other loads (the calls and emails needed to get answers from carriers) and hasn't replied.
Monday 10:45 a.m. The customer's receiving manager calls customer service. Customer service checks the order system, sees "in transit" and promises an update.
Monday 11:15 a.m. The account manager in sales asks a group chat whether anyone has a new date. Two people answer with different times.
Monday 2:00 p.m. The truck arrives after the receiving cutoff and waits until Tuesday morning.
Three weeks later. Accounts payable gets the carrier's invoice with a detention charge, an accessorial (a charge on top of the linehaul rate, such as detention or liftgate) that nobody approved. Finance doesn't know why it's there and pays it.
Everyone saw part of the problem. Nobody owned the whole thing.
Who is responsible for each freight exception?
Use this as a starting matrix, then adjust it to your company. R = Responsible (does the work), A = Accountable (owns the outcome), C = Consulted, I = Informed.
Exception | Logistics | Carrier | Customer service | Sales | Finance |
|---|---|---|---|---|---|
Missed pickup | A, R | R | I | I | – |
Delay | A, R | R | R | I | – |
Cancellation | A, R | C | I | I | C |
Partial delivery | A, R | R | R | I | C |
Missing POD | A, R | R | I | – | I |
Invoice mismatch | R | C | – | – | A |
The rule that matters is one A per row. Two accountable teams usually means each waits for the other. Logistics owns most rows because it holds the booking and the carrier relationship; finance owns the invoice row because it owns the payment.
Customer service shows up as Responsible on delays and partial deliveries because it carries the customer conversation. That holds only if logistics passes it a reason and a new time; without those, customer service becomes a relay that guesses. Finance is Consulted on cancellations and partial deliveries because both can change what the final invoice should be.
If sales owns key accounts directly, move it from I to R on delays for those customers.
How do you build a responsibility matrix for your team?
Build the matrix in 5 steps, then review it against real exceptions every month. A matrix that never changes usually means nobody is checking it.
List your exceptions. Start with the 6 above and add any that recur on your lanes, such as a pickup address change after booking.
Name one Accountable owner per row, by role, not by person, so it survives vacations.
Separate doing from deciding. Write down who sends the messages and who approves money, carrier changes or customer promises. Most of the Responsible work is follow-up; most of the Accountable work is judgment.
Set notice rules. For each Informed cell, decide the channel (Slack, Teams, email) and the trigger: at the first sign of a problem, or only once there’s a reason and a new time.
Review monthly. Pull the exceptions that stalled longest and find the row that failed.
For approval rules when something goes wrong, see who approves when a shipment goes wrong.
Common mistakes when assigning exception ownership
Making customer service accountable for delays. It owns the conversation, not the carrier, so it can only promise what logistics tells it.
Leaving invoice mismatches with logistics alone. The coordinator who booked the load rarely sees the invoice, so extra charges get paid by default.
Informing everyone about everything. When sales gets every status change, it stops reading them and misses the one that matters.
How does Wilson, by Cartage, take on the work in each row?
Wilson, by Cartage, takes on most of the Responsible work in the matrix (carrier contact, notices, rebooking, POD collection and invoice audit) and escalates to the Accountable owner when a decision falls outside the company’s rules. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Step | Trigger | What Wilson does | When a person steps in |
|---|---|---|---|
Missed pickup | Pickup window passes | Contacts the carrier, notifies the team, notifies the customer if configured, initiates rebooking from approved carriers | If rebooking needs approval or no approved carrier accepts |
Delay | Load is running late | Gets the new ETA and the reason, then tells the team and anyone else set to be notified | To decide on changes for the customer or production |
Cancellation | Carrier cancels | Follows the same order as a missed pickup and moves to the next approved carrier | If no approved carrier accepts |
Partial delivery | Consignee reports missing freight | Contacts the carrier and updates the team | To decide on a reshipment, claim or credit |
Missing POD | POD not received after delivery | Requests the POD, follows up and files it | If it’s still missing past the set window |
Invoice mismatch | Invoice differs from what was booked | Audits and reconciles the invoice against the booking | To approve or dispute charges outside the rules |
The company decides where the line sits. Wilson starts with assisted execution, and the company sets approvals on any action it chooses, for example rebookings above a cost threshold, carrier selections or customer notifications. Actions within the rules proceed; the rest wait for a person. Each company also chooses who’s notified and how, so the Informed column maps directly to Wilson’s notices: the team in Slack or Teams, the shipper by email and the consignee by email or SMS.
Escalation goes to people, not around them. Wilson escalates when a carrier can’t confirm, no approved carrier accepts or a decision exceeds the approval rules. Every message, confirmation and change on each shipment is recorded in a change history, so the Accountable owner sees what was already done before deciding.
Wilson books only carriers the company has approved; Cartage can introduce carriers from its network, but they’re usable only after approval. Wilson doesn’t decide claims or make customer commitments. For how a delay alert becomes an owned plan, see a delay alert needs a recovery plan and an owner.
Which parts of the matrix stay with people, and what should a demo prove?
The Accountable column stays with people, along with every decision about money, customers, claims and carrier approvals. A demo should prove the software does the follow-up and hands those decisions to the right owner with the facts attached.
Customer promises: new delivery dates, credits and priority calls stay with customer service and sales.
Claims and reshipments: what to do about missing freight stays with logistics and finance.
Charges outside the rules: finance approves or disputes them.
Carrier relationships: Wilson scores carriers on service and cost, but people decide which carriers to approve. See which freight decisions stay with a human.
What to ask a vendor to show in a demo
A delay on one of your loads, from the carrier’s first email to the notice your customer service team receives, with the reason and new ETA.
The Informed column in action: who gets which notice, through which channel, and how you change it.
An escalation: a rebooking above your threshold landing with the named approver.
A missing POD past your window, and who gets it.
An invoice with an unplanned accessorial, and how it reaches finance before payment.
FAQs
Who should own a freight exception? One accountable role per exception type, usually logistics, with finance accountable for invoice mismatches. Wilson, by Cartage, can do much of the follow-up while that role keeps the decision.
What is a RACI matrix for freight? A table that shows, for each exception, who does the work, who owns the outcome, who is consulted and who is informed. Its main job is making sure each exception has exactly one accountable owner.
Which freight exceptions should the matrix cover? At least missed pickups, delays, cancellations, partial deliveries, missing PODs and invoice mismatches. Add any exception that recurs on your lanes.
Can Wilson handle exceptions without a person? Some steps, yes, within the company’s rules. Wilson starts with assisted execution, and autonomy expands step by step as trust builds.
Who decides what Wilson can do on its own? The company. It sets approvals on any action it chooses, such as rebookings above a cost threshold or customer notifications.
Who does Wilson notify during an exception? Whoever the company configures. That can include the team in Slack or Teams, the shipper by email and the consignee by email or SMS.
What happens when Wilson can’t resolve an exception? It escalates to the team, for example when a carrier can’t confirm or no approved carrier accepts. The change history shows what was already tried. See what freight execution means.
How is Wilson priced? There’s no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson.
Conclusion
Exceptions don't stall because people don't care. They stall because nobody agreed who acts. A RACI matrix with one accountable owner per exception fixes that, and separating follow-up work from decisions shows exactly where help fits: most Responsible cells are calls, emails and notices, while the Accountable cells are judgment.
Wilson, by Cartage, does that follow-up on missed pickups, delays, cancellations, missing PODs and invoice mismatches, and hands decisions on money, customers and claims to the owner you name. Bring one exception that bounced between teams last week and watch Wilson run its follow-up in a demo at cartage.ai.
Sources
American Transportation Research Institute (ATRI), September 2024: https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
Cartage, Wilson product FAQ, October 2026: https://cartage.ai
Other latest news and success stories
January 25, 2022
Best AI Tools for Carrier Follow-Up in 2026
Read more →
January 25, 2022
Best Bill of Lading (BOL) Software for Manufacturers in 2026
Read more →
