How to Use Reported Fleet Size and Power Units for Prospecting

Reported power units help you group motor carriers by approximate operating scale. They do not tell you how many trucks are available today, how much equipment the business owns, or what it plans to buy. For prospect research, keep the count, its definition and its reporting date together, then verify the equipment and purchasing facts your service actually depends on.

This guide helps equipment sellers, fleet-service businesses and software teams build a defensible size segment. The output is a shortlist with a reason for inclusion and a specific next question.

What does “power units” mean in a carrier record?

FMCSA's SAFER field definitions count powered vehicle categories including trucks, truck tractors, hazardous-material tank trucks and several passenger-vehicle types. The count includes vehicles owned, term leased or trip leased by the carrier. Trailers are not included in that power-unit definition.

Three consequences matter when researching prospects:

• A carrier reporting 12 power units does not necessarily own 12 vehicles.
• A power-unit total does not establish the number or type of trailers.
• The field is broader than a count of long-haul tractors; check the carrier's operation and actual equipment.

The MCS-150 instructions show separate vehicle categories and acquisition methods. Use that reporting context to interpret the field, rather than treating a directory label such as “fleet size” as a complete equipment inventory.

Choose a size range for a business reason

Begin with what you can deliver. A workshop's useful range might depend on appointment capacity. A software provider's range might reflect its onboarding capacity and supported workflow. A dealer may care more about a particular equipment type than the total count.

Write the selection rule before searching: “Research carriers in our service area whose reported size is compatible with the work we can support.” Add the actual minimum and maximum only when your business can explain them. There is no universal best fleet-size range for trucking leads.

Use the USDOTData trucking company database to explore fleet and geography filters. Guest searches provide a limited preview, and contact details are available through a one-time CSV purchase. Signed-in exports use the account's available access and credits; check the displayed terms before designing your workflow around an export.

Read the count with its date and identity

Retain the USDOT number and legal name so later observations refer to the same carrier. Similar names or a shared address are insufficient for combining two entities' fleet counts.

For every candidate, record these fields:

• Carrier identity: preserve the USDOT number and legal name to keep comparisons attached to the same entity.
• Exact count field: save the original label and numeric value so power units are not mixed with drivers or trailers.
• Reporting context: save the MCS-150 date or other supplied source date to identify the dated record supporting the value.
• Retrieval time: record when you checked the page or obtained the export. This documents your observation without replacing the source date.
• Source: save the record URL or named dataset/snapshot so the observation is reproducible.
• Service fit: mark equipment and location facts as confirmed or unknown to connect the number to your offer.

SAFER identifies the MCS-150 Form Date as a date from that registration form. FMCSA explains that the MCS-150 updates an existing company record. A recently retrieved count can therefore belong to an older reporting context. If a source provides no usable date, write “source date unavailable” instead of silently substituting today's date.

Turn the number into the next research question

A fleet count is useful when it changes what you investigate:

• Truck maintenance: use the count to organize approximate account scale. Verify equipment serviced locally, scheduling needs and who arranges maintenance.
• Equipment sales: use it to form a potential size segment. Verify the current equipment mix, replacement plans and who owns or leases it.
• Fleet software: use it to investigate possible implementation scope. Verify vehicles and users in scope, existing systems and the decision process.
• Tires or parts: use it to select accounts for equipment research. Verify actual vehicle specifications, service locations and purchasing arrangements.

Do not multiply reported power units by your price and label the result forecast revenue. That assumes every unit is relevant, covered by the same buying decision and available to your offer. Those are separate qualification questions.

For local service, the repair-shop prospecting use case adds a maintenance-location worksheet. A carrier's registration address alone cannot establish where its equipment receives service.

Compare two counts without inventing a growth story

First confirm that both observations use the same USDOT entity, field definition and source methodology. Keep both source dates and both retrieval dates. Two exports downloaded a month apart might repeat the same underlying filing.

If comparable observations differ, record the difference as a reported count change. Then investigate whether it reflects an operational change, a correction, reporting lag or another explanation. A dataset comparison by itself does not establish the cause or timing of an equipment transaction.

If you only have today's count, you do not have evidence of an increase. Do not substitute a company description, a guess about its age or an earlier search-result snippet for a comparable historical record.

A worked hypothetical example

Suppose a fictional carrier has 8 reported power units in an earlier dated record and 12 in a later comparable record. The arithmetic is a difference of 4, or a 50% increase in the reported count.

That is a statement about the observations. It does not establish that the carrier bought four trucks between your checks, owns all 12, or needs new software. The percentage also sounds more dramatic than the absolute change, so preserve both counts.

An equipment seller could record: “Reported power units changed from 8 to 12; equipment composition and cause unconfirmed.” The next useful question is whether there was a real change in operations and, if so, which equipment or service needs followed. Until confirmed, the candidate remains a research opportunity.

If the earlier value were zero, do not calculate percentage growth by dividing by zero. Keep the absolute values and investigate the earlier record's context. A blank value should remain unknown; it must not be converted to zero merely to make a calculation work.

Checklist before prioritizing the account

1. Match the legal entity and USDOT number.
2. Save the exact fleet field, count, source date and retrieval date.
3. Check that the operation and equipment could fit your service.
4. Mark ownership, location and purchasing responsibility as unknown unless verified.
5. For a claimed change, retain comparable evidence for both observations.
6. Write one next action that can resolve the most important unknown.

For a broader list workflow, use the trucking-company lead-list guide. Keep fleet segmentation separate from carrier onboarding or load-booking approval.

Frequently asked questions

Are trailers included in power units?

No. SAFER's power-unit definition covers specified powered vehicles. Do not use the count as a trailer total or infer a one-to-one tractor/trailer relationship.

Does the number show vehicles owned by the carrier?

Not by itself. The definition includes owned, term-leased and trip-leased vehicles. Establish the ownership or leasing arrangement separately when it affects your offer.

Does a larger fleet mean more buying potential?

It may justify a different research segment, but budget, purchasing authority, contract timing and need remain unconfirmed. A smaller account with a verified problem can be more relevant to your service.

What should I do when two sources disagree?

Save both values, definitions and dates. Check the exact entity and current official record, then seek clarification if the difference matters. Do not average conflicting counts and present the result as a verified fleet size.

Can I call a fleet-count increase a buying signal?

Call it a reason to investigate. Confirm the operational change and service need before treating it as an opportunity. A reported increase alone does not reveal a purchase, dissatisfaction with a vendor or willingness to change suppliers.

How often should I recheck fleet size?

Recheck when the count materially affects a decision and when your source or business context indicates a change. Choose a cadence your team can maintain; a new download is useful only if you understand the underlying record's freshness.