The Shipper's Carrier-Selection Policy: A Template You Can Actually Defend

A written carrier-selection policy is the single highest-leverage document a shipper can have after Montgomery v. Caribe. It converts "we're careful" — which a plaintiff's lawyer dismantles in one deposition — into "here is the standard we hold every carrier to, and here is the file showing we applied it to this load."

But a policy is a double-edged sword. A vague or unfollowed policy is worse than none, because the plaintiff will use your own document to prove you had a standard and ignored it. Here is how to write one that actually helps.

What an enforceable policy contains

1. Scope — who and what it covers

Define which shipments and which selection paths it governs: direct-to-carrier tenders, broker-routed loads, spot vs. contract. If you use brokers, say explicitly that broker vetting is part of the policy (negligent selection of the broker is its own theory of shipper liability).

2. Minimum carrier criteria

The concrete bar every carrier must clear before a load moves:

• Active FMCSA operating authority of the correct type.
• No "Unsatisfactory" safety rating; "Conditional" requires documented justification.
• Active insurance on file meeting your coverage minimum, with a COI on hand.
• Out-of-service rates within a defined threshold of national averages.
• Authority tenure minimums (or enhanced review for new authority).
• Identity match between booked entity, driver/truck, and remittance.

3. The exception process

Real operations have exceptions. A defensible policy doesn't pretend otherwise — it channels them: who can approve a below-threshold carrier, what justification must be written down, and that the approval is recorded. An exception with a documented reason is defensible. An undocumented one looks like the rule never existed.

4. The per-load record

State that, for every load, the company captures the FMCSA data reviewed, the criteria applied, the decision, and any exception reasoning — and retains it in a tamper-evident form. This is the part that turns the policy from a statement of intent into evidence.

5. Review cadence

Note who owns the policy and how often it's reviewed. A policy last touched in 2019 signals neglect.

The mistakes that sink a policy

• Aspirational language you don't follow. "We thoroughly vet every carrier" with no records behind it is an admission, not a defense.
• No per-load documentation. A policy with no file proving application is just paper.
• Inconsistent application. If you screened 8 of 10 loads, the plaintiff asks about the other 2.
• No exception trail. Exceptions happen; undocumented exceptions look like the policy is fiction.

How to make it real without adding headcount

The reason shippers don't keep per-load selection files is that doing it by hand doesn't scale. That's the gap DOTScreener closes: it applies your written policy automatically at the moment of selection, captures the live FMCSA snapshot, records exceptions with their justification, and produces a tamper-evident carrier-selection file for every load — so the policy you wrote is the policy you can prove you followed.

Start by looking up the carriers you already use and seeing how they measure against the criteria above.

---

Related reading

• Shipper Liability for Carrier Selection: Are You Next After Montgomery?
• How to Verify a Trucking Company Before You Ship
• Broker Negligent Selection — the post-Montgomery playbook