Truckload Tender Rejection Analysis: A Research Method for Carriers

Tender rejection is useful only when its boundary is understood. An index may summarize electronic tenders in a selected network, while a carrier's dispatch system contains booked loads, rejected loads, equipment constraints, and customer commitments. Those are related observations, not interchangeable denominators.

Methodology

Record the index publisher, covered mode, geography, tender type, observation date, retrieval date, and revision policy. Pair the market series with internal counts by lane, equipment type, appointment window, customer, and reason code. Keep accepted and rejected tenders in the same denominator so the rate can be reproduced.

Findings

Question	Market context	Internal evidence
Is capacity tightening?	Tender rejection trend	rejected tenders by lane
Is a lane workable?	Freight and fuel context	revenue, miles, deadhead
Is service at risk?	Network volatility	appointment and dwell records

The practical signal is the intersection of market movement and company constraint. A higher rejection rate may reflect low rates, unavailable equipment, weather, or a deliberate service decision. It does not identify the cause by itself.

Operational interpretation

Create a weekly exception table with the ten largest changes, the reason code, and the decision owner. Preserve the original export and annotate later revisions. Do not use a public index to promise a rate, accept unsafe work, or replace a lane-level margin review.

Limitations

Commercial indexes may use proprietary samples and definitions. Public freight measures are revised and may describe national flows rather than a carrier's book. Internal records can omit phone tenders or contain duplicate updates.

Method and population

The unit is one tender-response event for one lane, equipment type, customer, and requested pickup window. The population must include offered, accepted, rejected, expired, withdrawn, and reassigned tenders in a stated period. Report tender rejection as rejected divided by eligible tenders after excluding only documented technical duplicates or customer withdrawals. Keep those exclusions visible. A lane-level percentage without its denominator, response clock, and equipment scope is not a reproducible capacity measure.

Preserve tender identifier, offered time, response time, status, reason code, lane endpoints, distance, equipment, appointment window, customer, replacement outcome, and source-system revision. Separate “could not cover,” “declined commercial terms,” “out of network,” “equipment unavailable,” “driver unavailable,” “weather,” and “late tender” when the source actually records them. Do not infer a reason from a rejection alone. Measure replacement success, time to cover, service outcome, and empty repositioning separately.

Public evidence and internal inference

BTS and FHWA freight statistics provide flow, mode, and network context. FMCSA safety, registration, and HOS resources provide regulatory context for carrier availability and operations. Public index series such as fuel or freight-price measures may explain conditions around a period, but none proves why a carrier rejected an individual tender. Internal tender events, dispatch notes, equipment status, and movement outcomes establish the carrier-specific finding.

Use median and 90th percentile response time, rejection share, cover time, and replacement failure share. Segment by lane, customer, equipment, lead time, day, and reason only when sample size supports it. A high rejection rate may be a deliberate network choice, a pricing decision, a timing problem, or a real capacity constraint. Compare the response period with the same definition in a prior period and retain revisions. A changed reason-code menu can create a false trend.

Boundaries

Tender rejection is not the same as tender failure, late delivery, or market tightness. An accepted tender can still fail, and a rejected tender can be replaced successfully without a service miss. Do not publish confidential customer or driver details. Commercial decisions, rate commitments, and safety judgments remain with authorized owners. A public benchmark should never be presented as a promise for a lane.

The method transfers to brokers, carriers, and private fleets when the event ledger is complete. It is weaker where email offers are not captured or when a tender is overwritten after reassignment. The bounded conclusion is that rejection analysis can describe response behavior and replacement workload, but it cannot alone identify the cause of a capacity signal or predict future service.

Worked interpretation

The same rejection percentage can describe very different operating conditions. A carrier may reject a tender because its equipment is committed, because the pickup window is infeasible, because the commercial terms are outside policy, or because a duplicate offer was withdrawn. Only the event ledger and documented reason can separate those cases. Report replacement success and service result beside rejection so a high rejection rate is not incorrectly treated as a delivery failure.

Market context should be aligned by date, geography, mode, and revision status. National freight or fuel series are useful background but can move differently from a specialized lane. Use them to formulate a bounded question, then test the question against tender and movement records. If the internal series changes after a TMS migration, create a break marker and do not compare pre- and post-change values as if the instrument were constant.

Additional limitation

Tender data can be duplicated across a broker, TMS, and carrier portal. Deduplicate by a stable tender identifier and keep a record of withdrawn or superseded offers. Otherwise the denominator can inflate and make rejection look lower than it was.

Reporting standard

Include eligible tender count, status categories, reason coverage, response clock, replacement outcome, and any TMS break. Report lane and equipment scope with the period. This keeps a rejection rate from becoming an unsupported claim about national capacity or a promise for a customer.

Reproducibility note

Freeze tender events before assigning a status or reason correction. Preserve duplicates, withdrawals, reassignment, and TMS-version markers. Recalculate the denominator from the same eligibility rule each period so an apparent capacity trend is not an artifact of changing data capture.

Lane and lead-time controls

Tender rates are sensitive to the time offered, requested equipment, pickup flexibility, and lane direction. Compare like tenders before interpreting a weekly change. A lane with a narrow appointment window is not equivalent to one offered several days ahead. Report missing lead-time fields and avoid assigning a default value. Re-tenders should retain their relationship to the original shipment so one load does not become several independent opportunities.

Use event time consistently. A rejection recorded after the response deadline may be an expiration rather than an explicit refusal. A replacement carrier acceptance can show coverage, but it does not show that the original tender was economically or operationally feasible. Match final delivery and service events when assessing outcomes. Keep customer cancellations and invalid tenders separate because they do not measure carrier capacity in the same way.

The defensible output is a defined rejection distribution with event completeness and relevant strata. It cannot be used as a universal market rate, a profitability measure, or proof that one party caused a service problem. Public market indicators provide context only; the carrier's tender and shipment records establish the local observation.

Reporting the rate

Publish tender population, lane and lead-time boundaries, rejection categories, re-tenders, coverage outcomes, missing events, and cutoff. Keep customer cancellations and expirations distinct from explicit capacity refusals. A reader should be able to reproduce the denominator and understand what the rate does not establish. The bounded conclusion is a local capacity-response observation, not a market-wide rate or profitability claim.

Sources

1. FRED Truck Tonnage Index
2. BTS Freight Facts and Figures
3. BTS Freight Analysis Framework
4. FMCSA SAFER
5. FMCSA safety resources
6. Census Commodity Flow Survey
7. EIA Weekly Petroleum Status Report
8. BLS Producer Price Index
9. FHWA Freight Management
10. FreightWaves SONAR

Tender cohort and event meaning

A tender rejection is meaningful only when the tender, response deadline, rejection code, accepted replacement, and final movement can be linked. Define the unit as a tender or shipment, not a carrier-day, and state whether duplicate tenders, re-tenders, canceled orders, and customer-initiated changes are included. Separate explicit rejection from expiration, no response, capacity unavailable, and invalid tender. These categories may have different operational causes and should not be collapsed into one rate.

For a bounded analysis, select a geography, mode, lane family, customer, and period before calculating. Report tender count, accepted count, rejected count, re-tender count, covered load count, and missing event count. Segment by lead time, day of week, equipment, and requested pickup window only when the dataset supports those fields. A higher rejection rate can result from tighter appointment windows or a shift toward difficult freight. A lower rate can reflect more advance notice or a customer mix change.

DAT, BTS, and other public indicators may frame market conditions, but they do not explain a carrier's individual response. Rejection is not the same as service failure when a replacement covers the shipment, and acceptance is not proof of profitable execution. The bounded conclusion is that tender data can describe capacity response for a defined event population; causal claims require matched operational, pricing, and service evidence and should remain explicitly limited.