Your approved carriers should stay approved when booking becomes automated
Key Takeaways
- Automated booking should change who sends the tender, not who decides which carriers are allowed to haul the freight.
- Approval needs a scope: a carrier can be approved for one lane, mode or equipment type and not for others.
- Every change to the list needs a named owner, a reason and a date, including suspensions and reinstatements.
- Carriers that Cartage introduces stay off the list until the company approves them; the software should never treat an introduction as an approval.
- Wilson, by Cartage, books only carriers the company has approved, tenders them first and escalates to the team when no approved carrier accepts.
How do you keep carrier approval under your control once booking is automated?
Keep approval as a company-owned list with scope, owners and status, and require the booking software to read that list on every tender and rebooking. The software executes inside the list; it never edits it on its own.
Before automation, approval is enforced by habit. A coordinator knows that one carrier is fine for dry van from the Ohio plant but not for reefer, that another was suspended after a claim, and that a third is only used when the regular two decline. Once software sends the tenders, that knowledge has to be written down, or the first rebooking on a busy afternoon may go to a carrier nobody would have chosen.
The question is not which approved carrier wins a given load. That is a selection rule, covered in approved carrier selection rules. The question here is who controls membership of the list itself, how it changes, and what keeps everyone else out.
Four controls that keep the approved list in the company's hands
Carrier-approval governance rests on four controls. Each should be written before the first automated tender.
Scope of approval. Record each carrier's approval by lane or region, mode (LTL, FTL, parcel, ocean, drayage, cross-border) and equipment. "Approved" with no scope lets a regional LTL carrier receive a long-haul truckload tender.
Change control. Decide who can add, suspend, reinstate or remove a carrier, and what evidence they need: signed agreement, insurance certificate, operating authority, rate agreement. Usually procurement or the logistics manager owns additions and anyone in operations can request a suspension.
Introductions. Decide how new carriers enter. A carrier the team found, a carrier a customer requires and a carrier Cartage introduces all go through the same approval step before they can receive a tender.
Status and expiry. Each carrier carries a status, such as active, suspended or expired, and the dates that drive it: insurance expiry, agreement renewal, a review date after a service failure. Only active carriers within scope are eligible.
Contracts and account ownership are a related but separate question; who owns the carrier relationship when software sends the tender covers that side.
What changes to the approved list look like in practice
Most list changes are small and frequent, and each one should leave a record of who made it and why.
Adding a carrier for a new lane. A distributor opens a new customer in Phoenix. Procurement approves an existing LTL carrier for the new lane only. The carrier's scope expands for that lane; its approval elsewhere stays as it was.
Suspending after an incident. A carrier misses two pickups in a week on a key customer's loads. The logistics manager suspends it for that customer's lanes pending a review. Open loads stay with the carrier unless someone decides to move them; new tenders skip it.
Expiring paperwork. An insurance certificate lapses at month end. If nobody updates the status, an automated system will keep tendering to a carrier the company would not use. Expiry dates belong on the list, and the person who tracks them should know the list feeds live booking.
A capacity gap. Every approved carrier declines a lane for three weeks. The answer is a decision, not a workaround: approve another carrier, widen an existing carrier's scope, or accept that some loads will be escalated. If Cartage introduces carriers for that lane, they wait for the same approval as anyone else.
When the list changes, the people who rely on it should hear about it. A coordinator who still expects a suspended carrier to appear in tenders will spend time chasing a load that will never be offered to it.
Exceptions where approval control usually slips
Approval control rarely fails on the routine tender. It fails under pressure, when the fastest option is outside the list.
- Rebooking after a cancellation. The replacement carrier must come from the same approved list, under the same scope. If none accepts, the load escalates to a person instead of going to whoever answers first. Test this case, because it is where shortcuts appear; your carriers or a shared network covers who gets the first tender.
- A carrier subcontracts the load. Approval covers the carrier the company approved. A carrier that hands the load to another company is a contract matter the company should address in its carrier agreements; software cannot see it on its own.
- A sales rep or customer names a carrier. A customer-required carrier still needs approval and a scope before it is tendered.
- A suspended carrier replies to an old tender. Late acceptances from a carrier that has since been suspended should be declined or escalated, not booked.
- Emergency overrides. If the company allows them, an override should require a named approver and be recorded on the shipment, so the exception does not quietly become the rule.
A good evaluation question is simple: can the software ever tender a carrier that is not active and in scope on the company's list? The only acceptable answer is no, with escalation as the fallback.
A carrier-approval governance checklist
Use this before automated booking goes live on any lane, and again whenever the list changes materially.
| Control | Question to answer | Typical owner | How to test it |
|---|---|---|---|
| Scope | Is each carrier approved by lane, mode and equipment? | Procurement | Tender a load outside a carrier's scope; it should not go to that carrier |
| Additions | Who can approve a new carrier, and what evidence is required? | Procurement or logistics manager | Ask the software to use an unlisted carrier; it should refuse and escalate |
| Introduced carriers | Do carriers introduced by Cartage wait for company approval? | Logistics manager | Confirm an introduced carrier receives no tender before approval |
| Suspensions | Can operations suspend a carrier immediately for some or all lanes? | Logistics manager | Suspend a carrier, then create a load on its lane |
| Expiry | Are insurance and agreement dates tracked and acted on? | Procurement or compliance | Let a date pass on a test carrier and check its status |
| Rebooking | Does rebooking use only active, in-scope carriers? | Operations | Cancel a booked load and watch the replacement tender |
| No acceptance | What happens when no approved carrier accepts? | Operations | Decline every tender on a test load; it should escalate |
| Change record | Is every list change dated, attributed and explained? | Logistics manager | Review the last five changes and who made them |
A row without an owner is a row nobody maintains.
How Wilson, by Cartage, keeps booking inside your approved list
Wilson is an AI logistics agent that replaces the TMS for freight execution, and it books only carriers the company has approved.
- Tender order. Wilson tenders the company's approved carriers first, by email, API, EDI where the carrier supports it, or phone calls where configured, and negotiates against the company's rate targets under configured rules and approval limits.
- No self-onboarding. Wilson never onboards carriers on its own. Cartage can introduce additional carrier capacity, but the company approves any carrier before Wilson uses it.
- Rebooking. When a carrier cancels or misses a pickup, Wilson initiates rebooking from the approved carrier list, automatically within the rules or with approval, depending on configuration. If no approved carrier accepts, Wilson escalates to the team.
- Who maintains the list. The company owns its carriers, rules, approval limits and contacts. Checking insurance and authority stays with the company's own process; Wilson works from the list the company maintains.
- Record. Messages, confirmations and changes are recorded in shipment history, so the team can see which carriers were tendered on each load.
Wilson starts with assisted execution, and the scope of execution can expand step by step as the company gains confidence in the workflow. Bring your approved carrier list for one lane, including a carrier you suspended this year, and see Wilson keep a live booking and its rebooking inside that list.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai