2027 RFPs will reprice contracts upward: FreightWaves SONAR put contract truckload rates at roughly $2.72 per mile excluding fuel, up about 18% year over year (FreightWaves SONAR, Oct 9, 2026), and DAT reported September contract van linehaul at $2.40 per mile (DAT, Oct 13, 2026). The brokers who price these bids well will not be the ones with the best guess about the market. They will be the ones who know exactly what each lane has cost them, how often it moved, and how it performed.

Most brokers have that history. Very few have it in a form they can use in the two or three weeks an RFP gives them.

Why does lane history matter more this bid season?

In a flat market, last year's rate plus a small adjustment is a defensible bid. In a market where contract rates have moved double digits in a year, last year's rate is a liability. Price too low and you either eat the margin or fail tenders, the problem we described in our post on contract rates hitting a 52-week high and mid-contract repricing. Price too high without evidence and you lose the lane.

Clean lane history is the evidence. It lets you bid each lane on what it actually cost, not on an average, and it gives you something concrete to show the shipper when your number is higher than last year's.

Shippers are also running more mini-bids and shorter award cycles, which makes this a recurring task rather than an annual one. We covered that pattern in our analysis of the mini-bid season and the contract-spot gap.

What does clean lane history include?

For every lane you are likely to bid, you want one row with numbers you trust:

• Load count by month — Where it usually lives: TMS · Common problem: Lanes split across slightly different city names or zip codes
• Actual carrier cost (linehaul and fuel separately) — Where it usually lives: TMS, carrier invoices · Common problem: Fuel and linehaul combined; accessorials missing
• Accessorials paid and billed — Where it usually lives: Carrier invoices, billing · Common problem: Detention and layover recorded inconsistently or only in email
• On-time pickup and delivery — Where it usually lives: TMS, tracking emails · Common problem: Status updated late or not at all
• Tender acceptance and fall-offs — Where it usually lives: Emails, TMS notes · Common problem: Rarely recorded as data
• Margin per load — Where it usually lives: TMS and billing · Common problem: Not reconciled after accessorial disputes

The problem is rarely that the data does not exist. It is that much of it lives in emails and PDFs, and the rest has inconsistencies that make lane-level analysis unreliable. A lane from "Chicago, IL" and "Elk Grove Village, IL" to the same destination might be the same lane for pricing purposes and two lanes in your TMS.

Separating linehaul and fuel matters especially this cycle, because fuel has moved a lot and a bid that bundles them can hide where your cost actually changed. That is the same margin analysis we laid out in our post on fixing freight broker margins per load.

How do you clean lane history before RFPs land?

Clean lane history by normalizing lane definitions, separating linehaul, fuel and accessorials on every load, pulling missing accessorial and service data out of emails and carrier invoices, and reconciling margin after disputes. Then keep it current weekly so the next bid starts from clean data.

1. Normalize lanes. Group origins and destinations into the level shippers bid at, usually three-digit zip, city or market area. Merge duplicates. Decide how to handle multi-stop loads.

2. Split the cost. For every load, separate linehaul, fuel surcharge and each accessorial. If your TMS stores an all-in number, pull the breakdown from the carrier invoice or rate confirmation.

3. Recover what lives in email. Detention approvals, layover agreements, rate changes and tender rejections often exist only in email threads. An agent can read those threads, match them to loads and write the data into the lane record.

4. Reconcile margin. Adjust each load's margin for disputes, short pays and accessorials that were billed late or not at all. Your bid should start from realized margin, not booked margin.

5. Add service metrics. On-time pickup, on-time delivery and tender acceptance per lane. Shippers ask for these in RFPs, and they also tell you which lanes cost more to service than the rate suggests.

6. Flag thin lanes. Lanes with only a handful of loads need market data alongside your history. Mark them so the pricing team knows where history is not enough.

How do agents speed up the RFP response itself?

Once the lane history is clean, the RFP is mostly an assembly job. An agent can read the shipper's lane list, match each lane to your history, pull current market references, apply your pricing rules, and fill the shipper's template. Reps then review the lanes that matter: the high-volume ones, the ones where history and market disagree, and the ones you want to win or walk away from. We went through the end-to-end process in our guide to freight RFP automation for bid season.

The same approach applies to surge and project RFQs, which arrive with dozens of lanes and short deadlines. We covered those in our post on peak project freight and rep capacity.

An illustrative example: an RFP with 300 lanes, where each lane takes a rep 5 minutes to look up and price, is 25 hours of work before anyone has thought about strategy. If an agent pre-fills every lane from clean history, the team can spend that time on the 30 lanes that decide the bid.

What to do in the next two weeks

1. List the shippers likely to bid in Q4 and Q1 and the lanes you currently run for them.
2. Normalize and clean those lanes first. Do not try to fix your entire history at once.
3. Separate fuel from linehaul on at least the last 12 months of loads on those lanes.
4. Pull detention and accessorial history out of email for your top lanes.
5. Set a weekly refresh so the data stays clean after this bid cycle.

Frequently asked questions

What is lane history in freight bidding?

It is the record of every load on a lane: volume, carrier cost, accessorials, service performance and margin. Brokers use it to price contract bids on actual cost rather than estimates.

Why separate fuel from linehaul in bid data?

Because fuel and linehaul move independently. Bundling them can hide whether a lane's cost increase came from capacity or from fuel, which leads to mispriced bids.

How long does it take to clean lane history?

It depends on how much data lives outside the TMS. Starting with the lanes for your next few bids, rather than your entire history, keeps the work manageable.

Can AI agents fill in RFP templates?

Yes. An agent can read the shipper's lane list and template, match lanes to your history, apply pricing rules and fill the template, leaving reps to review the lanes that need judgment.

The bottom line

Contract rates are up sharply, and 2027 bids will be priced on evidence. Normalize your lanes, split linehaul, fuel and accessorials, pull the missing history out of email and reconcile realized margin now, so when the RFPs land you are pricing from facts instead of last year's rate.

Debales deploys AI agents for lane history extraction, accessorial reconciliation, margin tracking and RFP response assembly. Book a demo.