Loading…
Vetting a carrier before you tender a load is about running a fixed sequence of checks in the right order, knowing which failures are hard stops and which are judgement calls, and doing it fast enough that it fits into the booking workflow. This guide lays out the pre-tender vetting sequence, separates the hard fails from the soft signals, and shows how to document the workflow so it protects you if something goes wrong.
Before tendering a load, run the vetting checks in a fixed order: confirm operating authority is active, confirm insurance is in force today, read the safety profile, confirm the carrier observably runs the lane with the right equipment, and match the identity end to end. Treat a handful of these as hard fails that stop the tender outright — revoked authority, an active out-of-service order, lapsed insurance, an identity mismatch, or wrong equipment for the load. Everything else — a borderline BASIC, an old isolated violation, a thin lane footprint — is a soft signal you weigh in context. Document the workflow at tender so it protects you in a later dispute.
Onboarding a carrier and tendering a specific load are two different decisions, and the second one is where the real risk lives. A carrier can pass onboarding cleanly and then, weeks later, have lapsed insurance, a fresh out-of-service order, or a newly surfaced fraud flag by the time you actually hand it a load. The pre-tender check is the gate that catches what changed between onboarding and dispatch.
The pre-tender check also has to be fast. It happens in the booking flow, often under time pressure, sometimes on the carrier's last-minute availability. A workflow that takes fifteen minutes won't get run; a workflow that takes under a minute will. The goal is a sequence tight enough to run every single time without slowing the desk down.
Vetting at onboarding establishes the relationship. Vetting at tender protects the specific freight. The two are not interchangeable — insurance lapses, OOS orders, and fraud flags all surface in the gap between them. Run the pre-tender check on every load, not just on new carriers.
Run the checks in a fixed order so nothing gets skipped under pressure. Each step gates the next: there's no point reading a carrier's safety profile if its authority is revoked.
Knowhaul runs this whole sequence in parallel on any DOT or MC — authority, insurance, safety, observed lanes and equipment, and identity-graph fraud signals — so the pre-tender check is a single lookup rather than five separate dashboards.
Some failures are not judgement calls. A hard fail on any of these means the tender stops and you find another carrier — there is almost always one available on the lane.
A hard fail isn't a deduction from a risk score you can offset elsewhere. A carrier with a spotless safety record and a revoked authority is still a no. Treat the hard-fail list as a set of gates: any single one stops the tender outright.
Most of what you'll encounter is not a hard fail. Soft signals are real risk information that you weigh against the load, the rate, and the alternatives — not automatic disqualifiers.
The discipline is to read soft signals in combination and in context. One soft signal is usually noise; several stacking together on the same carrier is a pattern that may tip a judgement call toward declining or pricing in the risk.
The final, often-skipped step is recording what you checked and when. Brokers increasingly face negligent-selection claims when a carrier they tendered to causes a crash or a loss, and a timestamped record of the pre-tender vetting workflow is the broker's strongest defense. The record should show that authority and insurance were verified at tender, that the safety profile was reviewed, and that the identity matched.
Documentation also disciplines the workflow itself. A vetting process you have to log is a vetting process you actually run every time. Keep the record for the duration of the load plus your jurisdiction's statute-of-limitations window. A tool that logs the lookup automatically removes the friction — the act of running the check creates the record.
Onboarding establishes the relationship — collecting documents, setting up the carrier in your system, running an initial check. Pre-tender vetting protects a specific load at the moment you hand it over. The distinction matters because conditions change in the gap: insurance lapses, out-of-service orders are issued, and fraud flags surface between onboarding and dispatch. Running the pre-tender check on every load, not just new carriers, is what catches those changes before they become your problem.
Hard fails stop the tender outright: revoked or inactive authority, an active out-of-service order, lapsed liability or cargo insurance, an identity mismatch, or equipment that physically can't carry the load. These are gates — a strong record elsewhere doesn't offset them. Soft signals are judgement calls you weigh in context: a borderline BASIC, an old isolated violation, a thin observed lane footprint, a recently granted authority, or a free-webmail contact. One soft signal is usually noise; several stacking together is a pattern worth acting on.
Manually, running authority, insurance, safety, lane/equipment, and identity across separate public dashboards takes ten to fifteen minutes — too slow to run on every load under booking pressure, which is why it often gets skipped. A tool that runs all the checks in parallel on a single DOT or MC lookup brings it under a minute, fast enough to fit into the booking flow. The goal is a sequence tight enough to run every time without slowing the desk down.
Because brokers face negligent-selection lawsuits when carriers they tendered to cause crashes or losses, and a timestamped record of the pre-tender vetting workflow is the broker's strongest defense. The record should show that authority and insurance were verified at tender, the safety profile was reviewed, and the identity matched. Documentation also disciplines the workflow — a check you have to log is a check you actually run. Keep the record for the duration of the load plus your jurisdiction's statute-of-limitations window.
Yes. Insurance is the check most likely to change between onboarding and tender — policies lapse mid-month when premiums go unpaid, and the public record updates on a feed cadence rather than in real time. Onboarding-time verification is necessary but not sufficient. Re-confirm that liability and cargo coverage are in force on the day of tender, with limits that still meet the load and your shipper's requirements, before you dispatch.
Paste an MC, DOT, or VIN to verify a carrier in one card. Free, no signup.
Free, no signup. Paste a DOT, MC, or VIN — verify right away.
Step-by-step checklist for vetting any motor carrier before tendering a load — operating authority, insurance, safety scores, inspection history, and identity flags.
The carrier packet checklist: which documents to request from a new carrier, what each one verifies, and the cross-checks that turn a stack of paper into actual fraud protection.
An out-of-service order is a federal enforcement action that prohibits a whole carrier from operating until it fixes a serious deficiency. Learn how it differs from a revocation, how to read its status, and why it's a hard stop.
The out-of-service rate is the share of a carrier's inspections that put a vehicle or driver out of service. Learn how it's calculated, how to read it against the national average, and why it's a leading safety signal.
Open one of these profiles in a new tab to see how the checklist applies to a live carrier record.
Run the whole pre-tender sequence — authority, insurance, safety, lane, identity — in a single lookup, with the record logged for you.