Broker risk

What a Defensible Carrier Vetting File Looks Like (With Free Template)

· 6 min read

A usable vetting file connects the carrier, the source records, the booking decision, and the person who approved it. Here is the structure to copy.

By LongMile

A stack of thick folders on a white surface
Photo by Beatriz Pérez Moya on Unsplash

If you got sued tomorrow, what would be in your carrier vetting file? Browser history is not a decision record. Neither is a carrier packet containing an unsigned agreement and last year's insurance certificate.

The operational problem is retrieval: can someone outside dispatch reconstruct exactly which carrier you selected, what information you reviewed, and why you released that particular load?

Quick answer: build two connected records

Keep a carrier master file for identity and onboarding documents, plus a load-specific decision record for the evidence used at booking. Link them with the USDOT number and your internal carrier ID.

A defensible file is not a guarantee against liability. It is an organized explanation of a decision, supported by preserved source material. This is practical risk guidance, not legal advice.

Why the carrier vetting file needs two layers

A carrier agreement might remain unchanged for years. Authority, insurance filings, pickup contacts, and the equipment assigned to a shipment can change between loads.

Putting everything in one folder creates two predictable failures: dispatch reuses stale documents, or newer documents overwrite the evidence supporting an earlier booking.

Use this structure instead:

  • Master: identity records, agreement, W-9, onboarding history, approved contacts.
  • Load: dated source captures, shipment requirements, reviewer, decision, exceptions, release authorization.
  • Policy: the SOP version effective when that decision was made.

Operator note: An MCS-150 filing date is not an authority grant date. FMCSA's biennial registration update and operating-authority history answer different questions. Label them separately rather than recording one ambiguous “carrier age.”

What belongs in each file

What to saveWhy it mattersRisk if missing
USDOT and MC identifiersConnects recordsWrong entity reviewed
SAFER snapshotPreserves safety contextFindings cannot be reconstructed
L&I authority recordEstablishes authority checkedRegistration mistaken for authority
Insurance confirmationDocuments coverage reviewedCOI treated as policy
SOP versionIdentifies applicable rulesStandard cannot be established
Exception approvalExplains departureOverride has no owner
Load decision recordConnects evidence to shipmentOnboarding mistaken for release

Save the actual source output, not just a hyperlink. Include the retrieval time and time zone. If a page fails to load, record that failure; do not mark the check complete.

Free carrier vetting template

Copy this into your TMS form or shared document. It is a record structure, not a universal carrier-acceptance policy.

Carrier master record

  • ☐ Legal name, DBA, USDOT, MC number, internal carrier ID
  • ☐ W-9 and executed carrier agreement
  • ☐ Approved contact details and independent callback source
  • ☐ Onboarding reviewer and completion date
  • ☐ Insurance producer contact and verification evidence
  • ☐ Document version history; superseded documents preserved

Load-specific selection record

  • ☐ Load ID, commodity, declared value, equipment requirements
  • ☐ Carrier identifiers matched to master record
  • ☐ SAFER capture: operating status, safety rating, rating date, inspection and crash summaries
  • ☐ FMCSA Licensing & Insurance capture: relevant authority and insurance filing status
  • ☐ Cargo coverage evidence matched to shipment requirements
  • ☐ Pickup contact and assigned equipment verification
  • ☐ SOP version and each required check marked complete, failed, or unavailable
  • ☐ Decision: approve, hold, or reject
  • ☐ Reviewer, decision timestamp, and supporting attachment IDs
  • ☐ Exception reason, approver, restrictions, and expiration
  • ☐ Recheck trigger, owner, and completion record

Use attachment IDs rather than “see email.” A reviewer should reach the supporting record without searching an employee's inbox.

Prioritize gaps before dispatch

This is a workflow matrix, not a safety score or legal standard.

PriorityFile conditionNext action
StopRelevant authority not activeDo not release
HoldIdentity or coverage unresolvedResolve before approval
EscalateSOP exception requestedObtain designated approval
CompleteRequired evidence attachedRecord release decision

Federal minimum financial responsibility is not a substitute for shipment-specific insurance review. Under 49 CFR 387.9, the minimum for many interstate, nonhazardous property carriers operating vehicles of 10,001 pounds or more is $750,000. That is public-liability protection—not proof of cargo coverage for your load.

Red flags in an otherwise complete file

Watch for a SAFER capture under one USDOT number and insurance evidence under another. Also flag approvals entered after pickup, identical exception language across unrelated loads, and documents replaced without revision history.

A BMC-91X filing documents qualifying public-liability insurance; it does not establish cargo-policy terms. A BOC-3 designates process agents; it is not safety approval. Keep document names precise so a full folder does not create false confidence.

An “unrated” carrier also should not be recorded as “satisfactory.” FMCSA defines safety ratings in 49 CFR 385.3; absence of a rating is not an affirmative rating.

Manual versus automated recordkeeping

A manual system can work: use a required form, restricted folders, standardized filenames, and a release gate that prevents booking approval with missing attachments.

Use a filename such as USDOT_LoadID_Source_20261102T143000Z.pdf. Preserve the original and add corrections as new versions.

Automation becomes valuable when it links changing source records to the actual load decision. Longmile can support verification using authority, insurance, FMCSA/SAFER information, risk indicators, and saved compliance documentation. Confirm how your workflow preserves timestamps, exceptions, and retrievable exports rather than assuming a dashboard supplies them.

Common mistakes and retention boundaries

Do not overwrite an earlier approval with today's data, accept a manager's verbal override, or treat a completed checklist as proof that every attachment was reviewed.

Also separate regulatory retention from litigation preservation. 49 CFR 371.3 requires specified broker transaction records to be kept for three years. It does not define a complete vetting file or settle every retention obligation. Establish a written schedule with counsel and suspend deletion when preservation duties arise.

FAQ

Is a screenshot enough?

It can preserve a finding, but include the carrier identifier, source, retrieval time, and connection to the booking decision. A cropped status label alone lacks context.

Must every load duplicate the master file?

No. Reference preserved versions of master documents. Save fresh evidence for checks your SOP requires at booking or after a defined change.

Who should approve exceptions?

Name the role in the SOP. Record the actual approver, rationale, restrictions, and expiration—not merely “management approved.”

Make one file reconstructable

Choose one completed shipment and rebuild its carrier vetting file using this template. If the reviewer must ask dispatch what happened, improve the record structure. Then assess whether Longmile fits the verification and documentation steps your team needs to repeat.

Tags: carrier vetting file, carrier selection documentation, carrier vetting template, broker compliance records, carrier exception log

← All articles