If a broker or shipper is named in litigation after a serious truck crash, discovery typically begins with a request for documents. This is a practical, document-by-document inventory of what tends to be requested, why each item matters, and how to be in a position to produce a clean, dated record rather than a reconstruction.

When a broker or shipper is named as a defendant after a catastrophic truck crash, the case usually does not begin with a dramatic courtroom scene. It begins with a **request for production of documents** — a written list of records the other side is entitled to ask you to produce. How that request goes is shaped less by what you *did* and more by what you can *show*, in a clean and dated form, years after the load moved.

This article is a practical inventory of the documents that are commonly requested in these cases, why each one tends to matter, and what "being ready" actually looks like. It's written for operations and compliance leaders who would rather understand the landscape in advance than learn it under deadline.

*A note before we start: this is general information for planning purposes, not legal advice. The exact scope of discovery varies by jurisdiction, by the facts of the case, and by the judge. For advice on your specific situation, talk to qualified transportation counsel.*

The organizing idea: discovery rewards contemporaneous records

One theme runs through everything below. Discovery tends to favor **contemporaneous records** — documents created at the time the decision was made — over later recollections or reconstructions. A dated artifact created on the tender date is simply easier to rely on than a witness's memory of what they "always" do. Keep that lens as you read the list; the goal isn't to have *more* paper, it's to have the *right* paper, created at the right moment, and retrievable later.

The document checklist

1. Carrier-selection records

What it is: The record of what you reviewed about this specific carrier before you tendered this specific load — the safety profile, authority, insurance status, and any flags you considered.

Why it's requested: This is the heart of a negligent-selection inquiry. The question is whether you exercised reasonable care in selecting the carrier, judged on what was knowable at the time. The selection record is the most direct evidence on that question.

How to be ready: Maintain a per-load record of the carrier's safety picture as it existed on the tender date — not just at onboarding. A screen captured at tender is far more responsive to this request than a general "we vet our carriers" policy.

2. Timestamps and metadata

What it is: Evidence of *when* a record was created or a check was performed — file timestamps, system logs, email headers.

Why it's requested: Timing is often the pivotal fact. A safety review dated the morning of the tender supports a different narrative than one with no verifiable date, or one that appears to postdate the crash. Modern discovery routinely reaches metadata, not just the document text.

How to be ready: Use a system that records an immutable, server-side timestamp on each screening — something more durable than a file's "date modified" attribute, which is easy to question.

3. Saved reports and screenshots

What it is: The actual artifacts of the safety review — the saved FMCSA report, the screening output, any screenshots.

Why it's requested: To see what you actually looked at, not just what you say you looked at. An empty file here is conspicuous.

How to be ready: Save the report, not just the decision. A loose screenshot on someone's desktop is better than nothing, but it's also easy to characterize as incomplete or selectively kept. A consistently generated, retained report is sturdier.

4. Internal communications and notes

What it is: Emails, chat messages, CRM/TMS notes, and call logs that mention the carrier or the load.

Why it's requested: Internal communications can reveal the real basis for a decision. This is also where offhand remarks — the kind nobody expects a stranger to read — surface. (It's worth periodically reminding teams that internal messages about carrier selection are discoverable.)

How to be ready: Encourage the substantive selection reasoning to live in the screening record itself, where it's structured and intentional, rather than scattered across informal channels.

5. Onboarding and qualification file

What it is: The carrier packet — W-9, operating authority, certificate of insurance, signed agreement — collected when the carrier was set up.

Why it's requested: It establishes the carrier relationship and what was on file. But note its limit: it documents the onboarding date, which may be long before the tender. (We've written separately on why [a carrier packet and a tender-time screen are different things](/blog/your-carrier-packet-is-not-legal-protection).)

How to be ready: Keep the packet current, and pair it with tender-date screening so the file reflects the carrier's status at selection, not only at setup.

6. Insurance verification records

What it is: The certificate of insurance, records of how and when coverage was confirmed, and any review of FMCSA insurance filings (including pending-cancellation dates).

Why it's requested: Coverage adequacy and currency are frequently at issue, particularly when a carrier's limits turn out to be thin or lapsed.

How to be ready: Retain the COI obtained from the carrier's agent and any record of verifying it, alongside the FMCSA filing status as of the tender date. Coverage is a status that changes, so the date of confirmation matters.

7. Carrier-selection policies and SOPs

What it is: Your written standard for how carriers are selected and what is checked.

Why it's requested: A written standard tends to define the yardstick against which your actual conduct is measured. Its *absence* can leave the standard to be defined by an opposing expert.

How to be ready: Have a concise written carrier-selection standard, and — importantly — make sure day-to-day practice matches it, since the gap between policy and practice is a common point of focus.

8. Records of alternative carriers and how this one was chosen

What it is: Rate comparisons, load-board records, and anything showing which carriers were available and why this one was selected.

Why it's requested: When a safer option appears to have been available, the *basis* for the choice becomes relevant. A record that the decision rested only on price reads differently than one showing a safety-first selection.

How to be ready: Where practical, capture the operational reasoning for the selection — not just the rate. (This is the subject of a companion piece: [being able to explain *why* this carrier](/blog/can-you-explain-why-you-selected-this-carrier).)

9. Monitoring records

What it is: Evidence of whether and how the carrier's status was tracked over time.

Why it's requested: To assess whether a carrier that deteriorated after onboarding was caught.

How to be ready: Re-screen at tender and/or use monitoring, and retain the records.

Why "we checked SAFER" is weak on its own

A point worth dwelling on, because it surprises people: saying "we checked the carrier's record on SAFER" is, by itself, a relatively weak position — not because checking SAFER is wrong (it's exactly right), but because an *uncorroborated recollection of having checked* is hard to lean on. Without a saved, dated artifact, the statement depends on memory and habit, both of which are easy to probe.

The fix is not to check *more* — it's to **preserve the check**. A frozen, timestamped snapshot of what the FMCSA record showed on the tender date converts "we always look" into "here is what we saw, and here is when we saw it." That distinction is the difference between a recollection and evidence.

Why immutable snapshots matter

This is where the *form* of your records earns its keep. An **immutable, timestamped snapshot** — a record that captures the carrier's safety picture at the moment of selection and is preserved in a tamper-evident way — addresses several of the requests above at once: it is the saved report (#3), it carries the timestamp (#2), and it is the core of the selection record (#1). Equally important, it is difficult to characterize as reconstructed after the fact, because its date and integrity are established by the system, not by a file attribute or a witness's memory.

DOTScreener is a documentation platform, not just a lookup tool

It's worth being precise about the category here. Plenty of tools let you *look up* a carrier's FMCSA data — that's useful, but a lookup leaves no durable, defensible artifact behind. The need that discovery exposes is different: it's the need to **preserve** the diligence as evidence.

That's the role DOTScreener is built for. Each screening produces a saved, immutably-timestamped report of the carrier's FMCSA safety picture as of the tender date, captures the carrier's attestation, records who ran it, and retains it in an audit-logged file. In other words, it's designed to produce the artifacts that map directly to the requests above — not to replace your judgment or your counsel, but to make your diligence *retrievable and durable* if the day ever comes that someone asks to see it.

The practical takeaway is calm rather than alarming: know what tends to be requested, and arrange your process so that producing a clean, dated record is the natural byproduct of booking a load — not a scramble years later.

— Mason Lavallet

Founder, DOTScreener.com

---

Sources

[Federal Rules of Civil Procedure — Rule 34 (Producing Documents & Electronically Stored Information)](https://www.law.cornell.edu/rules/frcp/rule_34) and [Rule 26 (Scope of Discovery)](https://www.law.cornell.edu/rules/frcp/rule_26)
[Restatement (Second) of Torts § 411 — Negligent Selection of an Independent Contractor](https://www.law.cornell.edu/wex/negligent_hiring)
[FMCSA SAFER Company Snapshot](https://safer.fmcsa.dot.gov/CompanySnapshot.aspx)
[FMCSA Licensing & Insurance (L&I)](https://li-public.fmcsa.dot.gov/LIVIEW/pkg_menu.prc_menu)

What Plaintiff Attorneys Will Subpoena After a Truck Accident