Broker risk
How Long Should Brokers Keep Carrier Vetting Records?
· 6 min read
The federal three-year transaction-record rule is not a universal deletion date for carrier vetting evidence.
By LongMile
Statutes of limitation do not care that you cleaned out your drive last spring. A carrier check deleted during routine housekeeping may become relevant after a crash, cargo dispute, or insurance notice.
Carrier vetting record retention requires two separate decisions: what federal rules require you to preserve, and how long your brokerage needs evidence supporting its carrier-selection decisions.
Quick answer: three years is not a universal deletion date
49 CFR §371.3 requires brokers to retain specified transaction records for three years. It does not establish a universal three-year retention period for SAFER screenshots, insurance correspondence, selection exceptions, or every document associated with a load.
A practical starting proposal for counsel and your insurer is seven years after delivery or cancellation for load-linked vetting evidence, subject to longer contractual requirements and legal holds. Seven years is an internal policy choice—not a federal mandate or guaranteed safe harbor.
This is operational risk guidance, not legal advice.
Why carrier vetting record retention matters
The federal transaction record identifies the consignor, originating carrier, bill-of-lading or freight-bill number, brokerage compensation, certain additional services, and freight charges collected and paid, including payment dates.
That record answers who arranged and paid for transportation. It does not necessarily answer why your team accepted a carrier with a Conditional safety rating or unresolved insurance discrepancy.
Operator note: Section 371.3 also gives each party to a brokered transaction a right to review that transaction’s required record. Do not assume those records are inaccessible internal bookkeeping, or that this access provision automatically covers every internal vetting note.
Which deadlines should shape your schedule?
Different claims run on different clocks. Personal-injury examples illustrate why “the statute of limitations” is not one number:
- California: generally two years under Code of Civil Procedure §335.1.
- Texas: generally two years under Civil Practice and Remedies Code §16.003.
- New York: generally three years under CPLR §214(5).
Written-contract claims can run longer: generally four years in California under §337, four in Texas under §16.004, and six in New York under CPLR §213(2).
These examples are not a state-by-state deletion schedule. Accrual, tolling, minors, governing law, and claim characterization can change the analysis. A shipment’s origin state alone does not determine every applicable deadline.
For qualifying Carmack cargo claims, 49 USC §14706(e) bars carriers from setting less than nine months to file a claim or less than two years to sue following written disallowance. Those limits do not govern every claim against a broker.
Build a retention schedule by record type
| What to check | Why it matters | Risk if ignored |
|---|---|---|
| §371.3 transaction data | Federal three-year minimum | Required records disappear |
| Load-linked vetting evidence | Supports selection decision | Only current data survives |
| Shipper and insurer terms | May require longer retention | Contract breach or coverage dispute |
| Incident and claim files | Separate preservation needs | Evidence deleted during dispute |
| Legal-hold status | Suspends routine deletion | Spoliation exposure |
Keep onboarding checks and subsequent load-specific checks connected. A carrier-level folder with a rolling seven-year deletion date can destroy an older snapshot still relevant to a retained load.
Use a load-to-document index instead: load ID, USDOT number, MC number, document ID, capture time, retention trigger, scheduled deletion date, and hold status.
A workable retention checklist
- ☐ Inventory TMS attachments, email, shared drives, monitoring exports, and vendor portals.
- ☐ Separate transaction records from vetting, insurance, contract, and claim records.
- ☐ Assign each category an owner, retention period, and start event.
- ☐ Link each selection decision to the evidence available when it was made.
- ☐ Preserve superseded snapshots rather than overwriting them.
- ☐ Obtain counsel and insurer review before enabling automatic deletion.
- ☐ Test retrieval using a closed load and its carrier-selection evidence.
- ☐ Require a hold check and logged approval before destruction.
For an illustrative storage budget, 1,000 loads annually at 2 MB of retained evidence per load equals roughly 14 GB over seven years, excluding backups and video. Measure actual file sizes before buying storage.
Red flags: what overrides routine deletion?
Use this preservation triage—not a carrier safety score:
| Trigger | Priority | Action |
|---|---|---|
| Routine completed load | Scheduled | Follow approved retention policy |
| Damage allegation or insurance reservation | Urgent review | Preserve related evidence; notify owner |
| Injury crash, demand, or threatened suit | Immediate escalation | Contact counsel; suspend relevant deletion |
A lawsuit does not need to be filed before preservation duties arise. Counsel should determine the hold’s scope, including email, messages, call recordings, vendor data, and employee devices containing business records.
Manual versus automated retention
A small brokerage can operate with a controlled archive, retention register, and monthly review. Save source documents as dated files; record the source URL, capture time and time zone, carrier identifiers, reviewer, and related loads.
For SAFER, preserve the displayed snapshot date and underlying data dates where available. For insurance, retain the COI plus producer correspondence and relevant BMC-91/BMC-91X filing-status evidence—not merely a link to today’s record.
Automation should calculate deletion dates, preserve versions, enforce holds, and log exports and destruction. Object-lock or WORM storage can prevent alteration during a configured period; it does not decide the legally correct retention period.
Longmile can support saved verification documentation. Evaluate how those records export into your retention process, including whether timestamps, historical versions, and load references survive the export.
Common mistakes brokers make
Confusing monitoring with archiving. Today’s authority or insurance status does not reproduce yesterday’s selection evidence.
Trusting backups as the archive. A rolling backup can expire or overwrite the only historical copy.
Keeping everything indefinitely. Uncontrolled duplication increases privacy exposure and makes retrieval harder. Use approved retention periods, access controls, and documented destruction after holds clear.
FAQ
Does FMCSA require seven years of vetting records?
No. Section 371.3 requires three years for specified transaction records. Seven years here is a proposed internal baseline requiring review.
Can a screenshot replace the underlying record?
It preserves what was displayed, but may omit linked filings or correspondence. Retain the supporting material used in the decision.
Can we delete records once a claim closes?
Not automatically. Confirm hold release, remaining disputes, contractual obligations, and the applicable schedule before deletion.
Make retention testable
Choose one load from three years ago. Retrieve the carrier check, exception approval, insurance evidence, and transaction record without relying on an employee’s memory. Use that test to improve carrier vetting record retention—and, if useful, assess where Longmile fits your archive.
Tags: carrier vetting record retention, broker record retention requirements, carrier compliance records, freight broker litigation hold