How to Build a Carrier-Verification Evidence Record

Before booking a load, create a carrier-verification record that connects the exact company, the shipment, each source checked, the time of the observation, unresolved questions and the person responsible for the decision. Save what the evidence actually showed. A folder of screenshots or an undated “approved” label cannot explain whether the checks covered this carrier and this job.

This guide helps broker and shipper teams build a reusable record and hand it to another reviewer. The worksheet is an editorial workflow recommendation, not a prescribed FMCSA form, a legal retention schedule or a guarantee against fraud.

Start with the decision the record must support

Give the record a load or tender reference. Identify the proposed contracting carrier by legal name, any doing-business-as name, USDOT number and relevant docket number. Describe the service being assessed: shipment date, cargo, route, equipment requirements and any customer-specific conditions.

This prevents a common documentation failure: checking one entity while the paperwork or actual service names another. Keep the information supplied by the prospective carrier separate from the details you independently find. Matching two copies of the same carrier packet is not independent corroboration.

A USDOTData carrier lookup can help locate the company. Use the resulting identifiers to check official sources; do not treat discovery of a matching profile as the completed decision.

Build six evidence sections

1. Company identity

Record legal name, USDOT number, relevant docket number, address and the contact details you compared. Save the source URL, lookup key and observed result. The SAFER Company Snapshot provides company identification and safety-related information and accepts searches by USDOT number, MC/MX number or company name.

Write “legal name and USDOT number match the tender” when that is what you observed. Avoid “identity verified” if you have not established that the person arranging the load is authorized to represent that business.

2. Registration and applicable authority

Record the selected authority type, its identifier, displayed status and any explanation or effective date relevant to the shipment. A bare “active” without naming the field leaves the next reviewer guessing what was checked.

Use the current official registration source. FMCSA's Move into Motus guidance directs public users to Motus for registration records. Its current L&I FAQ says legacy Licensing & Insurance has been historical-only since May 14, 2026 and does not reflect Motus filings. Label any legacy evidence as historical.

For the lookup steps, use our Motus authority and insurance guide. This record preserves the result of that check; it does not replace determining which authority the operation requires.

3. Insurance questions

Separate the federal filing result from the shipment's coverage questions. FMCSA says insurance requirements vary with entity type, authority, cargo and vehicle type. Its filing chart is not a substitute for reviewing the policy and contractual requirements for a specific load.

Record the filing information reviewed and relevant effective or cancellation dates. Separately record who is checking named insured, coverage period, cargo applicability and any material limitation with the insurer or authorized representative. Do not convert “certificate received” into “this shipment is covered.”

4. Safety information in context

Preserve the displayed safety rating, if any, and the period and counts behind inspection or crash information you use. The snapshot's safety fields answer a different question from authority and insurance filings. Document which question each field informed instead of creating a homemade all-purpose safety score.

For a figure that concerns your team, record the follow-up it requires and who will interpret it under your carrier-selection policy. A missing value should remain “not shown,” rather than becoming a favorable result.

5. Contact and transaction corroboration

Record where a callback number came from, when contact occurred and the specific load details confirmed. FMCSA's fraud-prevention guidance advises calling the SAFER-listed number when a supplied number differs; it also warns that insurance certificates can be fraudulent.

A useful note identifies what the callback resolved. “Called carrier” is weak evidence if it does not say which number was independently obtained or whether the representative confirmed the dispatcher and load. Keep unnecessary personal information out of the working summary.

6. Open questions and decision ownership

Give each unresolved issue an owner, next action and decision consequence. Use explicit states such as not checked, observed, conflicting, clarification pending and resolved with evidence. Reserve approved for this load for the accountable person's decision under your company's policy.

“Unknown” is useful information. It tells the next person where work remains. An empty cell is ambiguous: nobody knows whether the check was omitted, unavailable or considered unnecessary.

Keep three kinds of date separate

For each important observation, preserve:

1. Source date: the data-as-of, update or reporting-period date displayed by the source, if available.
2. Effective date: when the particular filing, status or change takes effect, if shown.
3. Observation time: when your reviewer accessed the record, including time zone.

If the source does not show a date, write “not displayed.” Your browser's clock cannot fill that gap. The SAFER FAQ describes daily Company Snapshot updates and weekly inspection/crash count updates; a lookup performed this minute is not proof that every underlying event is current to this minute.

The distinction also matters when someone calls a carrier “new.” Our guide to first-seen, registration and authority dates explains why these dates answer different questions.

Copy this compact evidence worksheet

Use one record per decision, with a repeatable evidence block for every important check. This plain-text format works in a document or existing case-management system without a new tool.

DECISION RECORD
Load/tender reference:
Proposed carrier legal name:
USDOT / applicable authority identifier:
Service, cargo and shipment date:
Reviewer / decision owner:

EVIDENCE BLOCK (repeat for each check)
Question being answered:
Source URL / lookup key:
Source date or reporting period:
Effective date, if relevant:
Observed at (date, time, zone):
Exact result / evidence-file reference:
What this establishes:
What remains unknown or conflicting:
Next action / owner / trigger:

DECISION
State: pending / declined / approved for stated scope
Reason and supporting evidence references:
Open conditions preventing booking or release:
Decision owner / timestamp:
Recheck time or change that triggers review:

Save a readable capture or permitted export alongside its URL and lookup key when appropriate. A URL alone may later display a changed record. Use your organization's access controls and retention rules; do not place carrier packets or identity documents in a public shared folder.

Worked example: a shift handoff with one unresolved check

Hypothetical example; no real carrier or transaction is represented. A broker is assessing a carrier for a dry-van shipment the following morning. At 15:10 Eastern time, the reviewer records matching company identifiers and the applicable authority result. The insurance evidence block remains open because the shipment-specific coverage question has been referred for confirmation.

At 15:25, the reviewer calls the independently sourced business number. The company representative confirms the dispatcher's relationship to the business and the load reference. That resolves the contact question; it does not resolve the separate coverage question.

The handoff records three different conclusions:

• Observed fact: the identified official record displayed the recorded status at 15:10.
• Service-fit hypothesis: the carrier may be suitable for this dry-van job, pending the remaining checks.
• Business confirmation: the contacted representative confirmed the dispatcher and proposed shipment. Coverage confirmation remains outstanding.

The review state is pending, with the coverage reviewer named as owner. The decision owner sets a recheck before booking and another trigger for any change to the performing carrier or shipment details. The incoming colleague can see exactly what remains to be done without repeating every completed check or treating the whole packet as approved.

Review the record before handing it over

Confirm that the carrier identifiers are consistent across the decision and evidence blocks. Check that every conclusion points to evidence, every unknown has an owner, and every approval identifies its scope. Keep later observations as new entries rather than overwriting the history.

Choose recheck triggers that matter: a changed contracting entity, different dispatcher, revised pickup information, a relevant filing date or a changed shipment requirement. A record is a dated basis for a decision, not a permanent clearance badge.

Frequently asked questions

Is a screenshot enough for the verification file?

A screenshot can preserve what was displayed, but add the source URL, lookup identifier, observation time and question it answered. A cropped status label without the company or field name cannot support a reliable handoff.

Should I replace yesterday's record with today's lookup?

Keep the earlier decision evidence and add a dated observation. Identify what changed and whether it affects the new load. Overwriting the earlier result removes the context needed to explain a previous decision.

What should I write when two sources disagree?

Record both results, their sources and dates. Mark the issue conflicting, assign clarification and state which decision is waiting. Different coverage or update times can explain a mismatch; do not select the more convenient result without resolving it.

Does a completed checklist mean the carrier is approved?

No. It shows that the listed checks were documented. Approval belongs to the accountable decision owner under the organization's policy, after considering unresolved issues and the actual shipment requirements.

How long is a verification record valid?

This worksheet sets no universal validity period. Preserve the observation time and define a recheck appropriate to the decision, relevant dates and material changes. A prior approval does not establish that today's contact or proposed transaction is unchanged.

What if an official source cannot be reached?

Record the failed check and time, retain prior evidence with its original date, and leave current status unconfirmed. Assign a retry or authoritative clarification. An unavailable page is neither a favorable result nor proof of a problem with the carrier.

Start your next evidence record

Start the next record by locating the carrier's identifiers, then complete the official checks and assign every unresolved question before booking.

By John Hauler, USDOTData's editorial persona. Source review: September 26, 2026. This article provides an editorial documentation workflow; it does not claim personal trucking experience or official FMCSA endorsement.