Posted Truck Availability: Confirm the Offer

A posted truck is a lead about possible availability, not proof that a distinct vehicle is free for your load. Check what the listing describes, which time it displays and who represents the carrier. Then obtain an answer for the exact shipment, including conditions and validity, before recording a scoped offer. Keep booking acceptance and pickup verification as separate steps.

This signal guide is for a broker capacity desk evaluating one truck-availability claim. Its output is a short evidence card that prevents a refreshed listing, a duplicate advertisement or a broad equipment label from becoming an unsupported “load covered” entry.

Start by identifying what was actually posted

Confirm that you are looking at a truck offered for freight, rather than a load seeking a truck, a general carrier profile or an advertisement for a recurring service. Similar route and equipment labels can describe different sides of the transaction.

For a concrete platform example, DAT One's truck-posting help describes an availability advertisement. Its fields include an available date, an origin, destinations the poster is willing to consider, trailer type, full or partial load preference, length and weight. It also allows an optional reference ID and expected minimum per-mile rate. These are the poster's supplied details, not a shipment-specific acceptance.

Record the actual field labels and values you saw. A destination zone is not the same as agreement to your delivery facility. A full-load preference does not establish that the trailer is empty now. A listed rate should not silently become the agreed price for a movement with unconfirmed stops, appointments or handling.

The question is narrower than choosing a platform or researching a network. For a longer-term carrier product or route launch, use the service-announcement analysis. For candidates to invite into a lane quotation process, use the shipper's lane shortlist.

Separate listing freshness from truck readiness

DAT One's refresh instructions explain that refreshing makes an existing truck posting appear newly posted. That is a useful reason to inspect the meaning of a displayed age. A recent refresh does not, by itself, establish a new truck, a new location observation or a fresh answer to your shipment request.

Keep four kinds of time distinct:

Original posting time: when the advertisement was first created, if the source actually supplies it. Otherwise mark it unknown.
Refresh or displayed age: the listing's visibility timestamp or age, using the platform's documented meaning. Do not infer an original time by subtracting an age whose meaning is unresolved.
Availability date and window: when the poster says the offered equipment could be used, including a time zone when a clock time matters.
Direct confirmation time and validity: when the carrier answered your actual request, what conditions applied, and when that answer must be checked again.

Add your own observation time so another researcher can distinguish “seen at 09:10” from “available at 09:10.” If the carrier says the truck will become empty after another delivery, retain that prerequisite and any uncertainty about its completion. Do not rewrite “expected to be empty” as “empty.”

Listing expiry is another separate clock. DAT's public expiry help describes different rules for website/REST postings and older integration methods. A listing's permitted time on a board is not the period for which the carrier has reserved equipment for you. Use the platform's applicable documentation for listing mechanics and the actual carrier response for the offer's validity.

Resolve whether several rows describe the same offered equipment

Count listing observations separately from confirmed shipment options. Two rows can be two advertisements for one offering; matching locations can also belong to different vehicles. Neither automatically merging nor automatically adding the rows is defensible.

Compare the represented carrier, availability window, equipment description, lane preferences and any supplied reference. Treat similarities as a reason to ask whether the postings refer to the same offering. A reference is useful for that conversation, but an optional board identifier is not an independently verified vehicle identity or a universal identifier across platforms.

Use a simple relationship field: same offering confirmed, distinct offerings confirmed, or relationship unresolved. Keep both source observations even if they resolve to one offering. This preserves the evidence without double-counting it.

If the answer is “we can find another truck,” create a separate conditional option. Ask who would supply it and what remains to be confirmed. Do not record it as a second available truck merely because the original listing stays visible.

Authenticate the representative before relying on the answer

A genuine carrier's name and USDOT number can appear in a claim made by someone who does not represent it. FMCSA's fraud guidance recommends confirming broker and carrier phone numbers through SAFER and calling the listed number to discuss the load when supplied details differ. It also warns that even insurance certificates can be fraudulent.

Use that independent contact route to establish the intended business and the person handling the offer. Record how the connection was confirmed and their role. A reply through the same unverified listing contact does not resolve the question merely because it repeats the public carrier details.

Treat a discrepancy as unresolved evidence requiring the relevant check, not an automatic accusation of fraud. If identity cannot be resolved in time, the listing has not earned a usable confirmation state. Urgency changes the decision deadline; it does not supply the missing evidence. The urgent-pickup verification guide covers the wider booking and release workflow.

This article's evidence card does not replace current official authority checks, shipment-specific insurance review or your organization's carrier approval process. Nor does a platform presence establish any of those outcomes.

Ask for an answer to one version of the shipment

Give the confirmed representative the same shipment reference and requirements that operations will use: facilities, pickup and delivery windows with time zones, commodity, quantity, weight and dimensions, equipment, loading method and material handling conditions. Keep unresolved shipment facts visible.

Then obtain answers to the missing operational questions:

What is being offered? Identify the proposed equipment arrangement and performing carrier. Establish whether the response concerns this offering or a promise to search elsewhere.
What has to happen first? Record prior unloading, repositioning, equipment preparation or other stated prerequisites, with their confirmation owner. Ask the carrier to confirm schedule feasibility rather than deriving it from a map distance alone.
Which requirements were accepted in the answer? Preserve any exceptions. A broad “yes” should not conceal an unanswered appointment or handling condition.
How long is the answer usable? Record its stated validity and any hold terms, or explicitly record that no hold has been confirmed. Use the actual arrangement; there is no universal safe age for every availability answer.
What constitutes the next booking step? Record the responsible person, acceptance channel and reference your established process requires. Do not upgrade the state because a request has been sent.

These are editorial research controls, not a universal contracting rule or a legal conclusion about whether particular communications form an agreement. Preserve the real terms and escalate contractual questions through the responsible reviewer.

Worked example: two refreshed listings, one scoped offer

Fictional example. All listings, entities, responses and times below are invented. They do not represent activity on DAT or another actual marketplace. All clock times are Eastern Time on the stated dates.

A broker needs one dry van for Shipment S-18, picking up at a specified Columbus, Ohio facility on October 9, 2026, between 13:00 and 14:00. The delivery facility, appointment, packaged non-hazardous freight details, dimensions and handling requirements are recorded in requirement version 2.

At 09:00 on October 8, the researcher sees Listing A for Carrier C, a 53-foot van advertised near Columbus for October 9. Its displayed refresh time is 08:55; its original creation time is not shown. At 09:05, Listing B on another fictional board shows the same carrier and similar details, refreshed at 09:02. The optional references differ.

The defensible initial tally is two listing observations, an unresolved relationship and zero shipment-specific offers confirmed. It is not two trucks. The recent refreshes justify a timely inquiry, not a capacity count.

At 09:15, an independently confirmed Carrier C representative explains that both advertisements concern the same offered equipment. The truck is expected to finish an earlier job on October 9 before the proposed pickup. The researcher links A and B to one offering and retains the prerequisite. There are now two observations and one identified offering, but the carrier has not yet answered S-18 version 2 in full.

At 09:25, the representative supplies a scoped offer for S-18 version 2, explicitly addressing the facility windows, freight and handling details. The offer remains conditional on the stated earlier-job completion, is open for acceptance until 10:00, and does not include a confirmed reservation while the broker decides. The operational record becomes one conditional scoped offer; booking not accepted.

At 09:40, the shipper moves pickup to October 10. The earlier answer no longer covers the current requirement. The broker creates version 3 and asks for a new answer. A fresh refresh of Listing A would not fix that mismatch: the unconfirmed fact is whether the same offering can serve the revised date.

This example supplies no real-world truck count or result. Its value is the reconciliation: two observations can resolve to one offering, and one offer can cease to answer the current request without either source listing disappearing.

Copyable availability-claim card

Use one card per offering under investigation, with separate references for every associated listing. This is a worksheet for your existing process, not a USDOTData dispatch or reservation feature.

CLAIM
Listing source / URL or permitted reference:
Truck advertisement / load advertisement / other:
Represented carrier / identifiers:
Observed at / time zone:
Original posting time, or unknown:
Displayed refresh time or age / documented meaning:
Stated equipment / origin / destination preference:
Stated available date / window / time zone:
Other listing references / relationship unresolved:

CONFIRMATION
Independent contact route / confirmed representative:
Same or distinct offering / supporting answer:
Shipment reference / requirement version answered:
Current location or readiness claim / source time:
Preceding job or other prerequisite / owner:
Equipment and shipment requirements addressed:
Conditions / unresolved facts:
Answer time / offer validity / hold terms, if any:

HANDOFF
Observed claim / unanswered / conditional offer:
Scoped offer / booking accepted / expired or superseded:
Acceptance evidence and reference, if obtained:
Next action / owner / decision deadline:
Changes requiring a new answer:

Before using the card, complete this checklist:

The listing type is clear, and source observation time is separate from availability time.
The displayed age has a documented meaning or is marked unresolved.
Multiple rows have not become multiple trucks without confirmation.
The business contact connection has independent support.
The answer covers the current shipment version, with exceptions visible.
Offer validity, any hold and booking state are recorded separately.
Operations knows which change or deadline requires a new answer.

Once booking is accepted through the applicable process, retain the actual confirmation. Continue the approved pickup checks. FMCSA's same fraud guidance recommends checking that the name and numbers on the arriving truck match the carrier with which you contracted. A well-documented availability inquiry cannot establish who later arrives at the dock.

Frequently asked questions

Is a refresh time the original posting time?

Do not assume so. DAT's documented refresh function can make an existing truck posting appear newly posted. Preserve the field's actual meaning and mark the original time unknown if it is unavailable. Neither timestamp proves that a truck just became empty.

Can two listings represent one truck?

Yes, that is a possibility to resolve. Similar details are not enough to prove duplication, and different references are not enough to prove separate vehicles. Ask the confirmed carrier representative whether the rows concern the same offered equipment, then preserve both observations under the resolved relationship.

Does a listing verify the poster's authority to represent the carrier?

The listing alone does not establish that connection. Independently confirm the business contact and the representative's role before relying on their answer. Keep this separate from checking the carrier's official operating authority; they answer different questions.

Can a broad equipment label establish shipment fit?

No. Use it for an initial match, then provide the actual freight, dimensions, weight, facility and handling requirements. Record the carrier's scoped answer and exceptions. A label cannot resolve a missing specification or promise an appointment.

Is a confirmed offer a completed booking?

Record the actual state supported by the communications and applicable process. An offer can have conditions, an acceptance deadline or no reservation while you decide. Retain separate acceptance evidence before labeling the shipment booked; contractual interpretation belongs with the responsible reviewer.

What must be rechecked when the loading date changes?

Obtain a new answer for the revised shipment version, including equipment readiness, preceding-job dependencies, appointments, delivery feasibility, terms and validity as affected. Preserve the earlier answer with its original scope. A listing refresh does not extend it to a different date.

Give operations an evidence state, not a row count

Use a USDOTData carrier lookup to research the intended entity, then resolve the operational claim with the carrier through a confirmed channel. Hand over the current shipment version, the answer that addresses it and any remaining conditions. The useful result is knowing exactly what can be acted on now and what still requires confirmation.

By John Hauler, USDOTData's editorial persona. Sources reviewed October 8, 2026. USDOTData is an independent information service, not FMCSA. The example and worksheet are original editorial analysis; they do not report an actual listing, carrier commitment or customer outcome.

Posted Truck Availability: What Confirms an Offer for Your Load?