Write Defensible Trucking-Prospect Exclusion Reasons

Write a trucking-prospect exclusion reason by naming the offer, the specific requirement, the evidence that fails that requirement and the condition for reviewing the decision again. Keep unresolved facts in a hold state. A carrier excluded from one campaign has not been shown to be unsafe, uncreditworthy or unsuitable for every service.

This guide helps fleet-service sellers and sales-operations teams make research decisions that another teammate can understand and reverse when facts change. Its output is a small reason-code policy and an evidence record for each decision. It is an original editorial workflow for your existing business records, not a USDOTData scoring feature or an official eligibility test.

Define the scope of the decision first

A label such as “bad lead” conceals the most useful information. Did the team confirm a mismatch, fail to find a fact, discover an existing relationship or simply run out of review time? Each answer requires a different next action.

Name the campaign and its current boundaries before assigning reasons. For a local service, those boundaries might be the actual service location, supported equipment, work offered and appointment period. For software, they could be a mandatory integration or supported workflow. Write those conditions from your real capabilities, not from whatever fields happen to be easy to export.

Use a versioned rule such as: “Campaign R1, October shop-service offer, at our supported site, for the component families our technicians currently service.” The version identifies the rule applied; it does not establish that any particular carrier meets it. The lead-list building guide covers initial selection. This policy governs what happens when a reviewed account does not proceed.

Separate four boundaries in each decision:

• Entity: which carrier record was reviewed, with its resolved identifier.
• Offer: which service and campaign the decision concerns.
• Site or job: which actual work location or requirement was assessed.
• Period: the time window to which the evidence and decision apply.

If one fleet has two maintenance sites, a mismatch at one site should not silently exclude the other. If a group has several carriers, do not copy an exclusion across every affiliate without evidence that the same condition applies.

Match the evidence to the requirement

Public carrier fields are useful starting points, but each has a defined meaning. FMCSA's SAFER field help describes the physical address as the principal office and power units as a reported vehicle count that includes specified owned and leased categories. Neither field identifies every maintenance location or a current service request.

That distinction changes the wording of an exclusion. “Principal office is outside our selected search area” describes a database selection rule. “All relevant work occurs outside our service area” requires different, stronger evidence. Do not substitute the first for the second.

Use the carrier-data field dictionary to preserve source meanings and missing-value states. Record a retrieval date separately from the source-record date. FMCSA's Open Data Program states that the Company Census File is updated from a database that is 24 hours old and is not real-time data. Downloading a file today does not make every reported fact a fresh business confirmation.

An evidence record can contain three different statements:

1. Observed fact: the source reports a particular value or an authorized business record documents a statement.
2. Fit hypothesis: that fact suggests a possible match or mismatch for this offer.
3. Confirmed requirement or need: relevant business evidence establishes the actual task, constraint or current request.

Exclusion requires enough evidence for the criterion you chose. A confirmed mandatory requirement that your business cannot meet can justify a scoped exclusion. A missing field generally leaves the requirement unresolved.

Use a small set of reasons with different consequences

The following codes are an example policy, not an industry standard. Adapt the names to your existing process, but retain the evidence and re-entry conditions.

OUTSIDE_SCOPE: a supported boundary is not met

Use this when evidence establishes a mismatch with the declared service, site or period. Write the failed condition precisely: “Requested work at Site B is outside the current mobile-service area.” Avoid “wrong location” if all you know is a registered office address.

The re-entry trigger is a changed work site, service coverage or offer. A new campaign can review the carrier independently; it should not inherit the old exclusion automatically.

UNSUPPORTED_REQUIREMENT: a mandatory capability is absent

Use this when both sides are established: the account requires a specific capability, and your business does not support it. For example, a customer-confirmed component type may fall outside the shop's documented service capability.

An unknown component type belongs in a hold. A future product roadmap is not current support. Re-entry requires a verified change to the requirement or a genuinely available capability, followed by a fresh fit check.

IDENTITY_HOLD: the account boundary is unresolved

Use this when names, identifiers or purchasing scope do not reconcile. The allowed action is identity research, not a fraud allegation. State the missing link: “Two distinct USDOT entities appear under one brand; the requested service's contracting entity is unknown.”

A hold does not count as a confirmed mismatch. Do not attach adverse notes to the most similar company name while waiting for clarification.

OWNERSHIP_HOLD: another team already owns the relationship

Use this for routing, such as an account assigned to an existing service team. It prevents duplicate handling without describing the account as unsuitable. Record the internal relationship owner and the scope of the assignment in your authorized system.

Two export rows for the same resolved entity are a separate data issue. Merge or suppress duplicate working rows while preserving the source references; do not report a duplicate row as another rejected carrier.

NO_CURRENT_REQUEST: the relevant need is presently absent

Use this only when current business evidence supports it for the specified service and period. “No reply,” “no public announcement” and “phone field missing” do not establish that a business has no need.

If an account says its present requirement is already covered, record that limited conclusion. Do not infer unwillingness to use any future service. Retain any agreed review trigger in the existing relationship record; the research label itself does not authorize contact.

UNREVIEWED or FIT_HOLD: work or evidence is incomplete

Keep unstarted reviews separate from completed reviews with unresolved questions. Otherwise a busy week can appear to produce a worse market. For a fit hold, name the decisive missing fact and the next responsible reviewer. “Research later” without a question or owner is difficult to act on.

Apply reasons in an order that avoids misleading totals

Resolve the counting unit before reporting exclusions. Start with distinct carrier entities for an entity-level campaign. Preserve site and buying-account relationships without counting every task or duplicate export row as another carrier.

Then apply a short sequence:

1. Confirm the intended identity, or record an identity hold.
2. Check relationship ownership and route duplicate assignments.
3. Compare the actual requirement with current service boundaries.
4. Record confirmed mismatches separately from missing evidence.
5. Select one primary disposition and retain secondary reasons as notes.

The primary reason explains the next action. It does not erase other facts. An account may be outside the mobile area and require an unsupported repair. If the policy reports one primary disposition per entity, show it once in totals while keeping both conditions available for a later review.

Do not use this campaign workflow to create a carrier safety or credit decision. FMCSA describes the Company Snapshot as a concise identification and safety-information record. Your inability to serve an account is a different finding. A professional safety, insurance or financing review has its own scope and evidence requirements.

Worked example: six accounts in one repair campaign

The following companies, dates and operational details are fictional. No actual carrier is represented. Imagine a repair business reviewing six distinct carrier entities for an October shop-service campaign. Its scope is work brought to its existing shop on equipment it supports; it does not offer mobile service under this campaign.

Account A: distant office, local work confirmed. The registered office is outside the team's initial search area, but an existing authorized inquiry identifies a local maintenance site and asks about bringing a supported vehicle to the shop. Decision: retain for scope review. Excluding on office geography would answer the wrong question.

Account B: mobile attendance required. The inquiry confirms that the work must be performed at a remote yard and that bringing the asset to the shop will not meet this request. Decision: OUTSIDE_SCOPE for Campaign R1. Re-entry trigger: a different transport plan or an actual change to the seller's service offering.

Account C: equipment unknown. Its cargo category looks relevant, but the component and requested work are unconfirmed. Decision: FIT_HOLD. The next question concerns the asset and work scope, not whether the account “looks good.”

Account D: existing relationship. Another team already manages the same service relationship. Decision: OWNERSHIP_HOLD and route to that team. This is not a failed lead and should not inflate mismatch counts.

Account E: requirement unsupported. A documented request names a component family the shop does not service. Decision: UNSUPPORTED_REQUIREMENT for this work. Re-entry requires a changed requirement or available capability, not a larger reported fleet count.

Account F: relevant need currently absent. An existing business record confirms no additional shop work is requested for the stated October period. Decision: NO_CURRENT_REQUEST for that service and period. Do not broaden this into “never buys repairs.”

The six dispositions reconcile to one retained account, two confirmed offer mismatches, one unresolved fit hold, one routing hold and one current-need disposition. Reporting “five unsuitable carriers” would combine four different meanings and misdescribe the evidence. Two of six have a confirmed mismatch with this specific offer; that is not a market-wide rejection rate.

Use a decision card another reviewer can reopen

Keep the evidence in the business's existing authorized records. A public teaching example needs no personal contact information.

Decision ID / campaign version:
Carrier entity / USDOT reference:
Site or job / relevant period:
Requirement being evaluated:
Observed fact / evidence reference:
Source-record or event date / checked date:
Fit hypothesis / unresolved question:
Confirmed need, if any:
Primary disposition / secondary reasons:
Allowed next action / responsible owner:
Re-entry trigger / next review:
Prior decision superseded, if any:

For fictional Account B, the meaningful core is: “R1 offers shop service; current request requires work at the remote yard; OUTSIDE_SCOPE; reopen if the work can be brought to the shop.” The record tells a colleague what changed evidence would matter.

When a rule changes, create a new decision linked to the old one. Do not silently overwrite the reason that governed last month's campaign. If the original reasoning was wrong, label the correction and identify any handoffs that used it.

Review the policy before expanding research

Run a small manual check of ambiguous decisions. Include an office/work-site mismatch, a missing fact, a duplicate row, an existing relationship and a genuine unsupported requirement. Two reviewers should be able to explain the same next step even if they use different wording.

Use this release checklist for the research batch:

• Every exclusion names an offer and criterion.
• Confirmed mismatches point to evidence, not just a hypothesis.
• Unreviewed, unresolved, routed and excluded states remain distinct.
• Duplicate rows do not become rejected entities.
• Site and affiliate scope are preserved.
• Each reversible decision has an evidence-based re-entry trigger.
• Summary totals reconcile without adding overlapping reasons.
• Nothing upgrades a campaign decision into a safety, credit or buying-intent finding.

For results over time, use the fixed research-cohort method. Keep the original cohort and policy version visible; excluding difficult cases after seeing outcomes can make the research appear more effective without improving it.

Frequently asked questions

Is an unknown field a valid exclusion reason?

It can explain why the record cannot advance under a stated evidence requirement, but label that as an evidence hold. It does not establish that the carrier fails the underlying business condition. Identify what would resolve the unknown.

Can a carrier be excluded from one offer and retained for another?

Yes. Scope the decision to the service, site and period. A fleet that requires mobile work may not fit a shop-only campaign, yet a separate confirmed shop-service request can merit review under another offer.

Should safety or credit information become a sales reason code?

Do not invent adverse conclusions from a missing field, raw inspection count or commercial mismatch. Route a real specialist review through its established process and preserve its actual scope. This worksheet does not determine safety, insurance or financing eligibility.

How should duplicate assignments be counted?

Count the resolved entity once in an entity-level batch. Treat duplicate rows as data cleanup and conflicting ownership as routing work. Neither automatically establishes another unsuitable carrier.

Should excluded rows be deleted?

Preserve enough permitted evidence to explain the decision and avoid repeating the same work, following your existing retention and access policies. Retaining a decision does not mean keeping every private document indefinitely. Do not prescribe one universal retention period from this example.

What happens when the service area or capability changes?

Identify the decisions affected by that specific change, confirm current requirements and record new dispositions. Do not automatically reactivate every old account. Re-entry restores review eligibility; it does not prove present need or authorize outreach.

Make the next decision explainable

Use the USDOTData trucking company database to research carrier candidates, then keep your offer-specific decisions in your own worksheet. The useful result is a reason a teammate can verify, a limited consequence and a clear condition for looking again.

By John Hauler, USDOTData's editorial persona. Sources reviewed October 5, 2026. The example policy and six-account exercise are original editorial recommendations, not official determinations or real customer outcomes.