Freight RFP pricing mistakes brokers make

Published 6 October 2026. Updated 6 October 2026.

Many costly RFP errors have nothing to do with reading the market. They are handling errors: a rate typed into the wrong row, a lane matched to the wrong history, a margin applied twice. Small brokerages are exposed to them because the RFP is large, the deadline is fixed, and the same one or two people do the matching, the pricing and the submission.

This is a checklist of those mistakes, grouped by where they happen, with a way to catch each. If you want the full method first, read how to price a freight RFP from your rate history.

What goes wrong when reading the RFP?

Missing a tab. The lane list is on one tab, but volumes, accessorials or special requirements are on another. Pricing from the lane tab alone can leave out a cost.

Catch it: list every tab and write one line on what it contains before you start.

Misreading the volume. An annual figure read as weekly, or the reverse, changes which volume band the lane belongs to.

Catch it: check the column header and any notes for the unit, and confirm one lane by hand.

Ignoring the bid format. The shipper wants an all-in rate and you send linehaul and fuel separately, or wants per-mile and you send per-load.

Catch it: write the required format at the top of your working file.

What goes wrong when matching lanes to history?

Matching on city pair only. The same two cities with a different equipment type, number of stops or volume level are not the same lane.

Catch it: require every field to agree, not just origin and destination.

Using a blended average. Averaging a lane you run twice a month with the same lane at a much higher frequency produces a rate that is right for neither.

Catch it: keep volume bands separate in your history and match to the band the shipper expects.

Spelling and formatting differences. "Ft. Worth" in one file and "Fort Worth" in the other means a real match is missed and the lane looks like it has no history.

Catch it: normalize place names and equipment labels before matching. Then check any lane that came back with no history, in case a real match was missed.

Stale history. Using rates from a period when carrier costs were very different from today's.

Catch it: look at the date range behind each rate and compare against a recent load on the same lane.

What goes wrong with lanes that have no history?

Guessing and forgetting. A number copied from a nearby lane goes into the sheet and nobody remembers it was a guess.

Catch it: keep a separate, visible list of lanes with no history, and decide each one on purpose.

Bidding thin lanes at the same margin as proven ones. If your only basis is one quote, the risk is higher than on a lane with dozens of loads.

Catch it: decide your approach to unsupported lanes before the pricing starts, so it is a policy and not a late-night reaction.

What goes wrong in the arithmetic?

Applying margin twice. A margin added in the history sheet and again in the bid sheet.

Catch it: state in one place whether your history holds carrier buy rates or already includes your margin.

Mixing markup and margin. Calling a markup on cost a margin, then comparing it with a margin on price from a different report. The two differ, and the gap grows with the percentage. See markup versus margin in a freight bid for the details.

Hard-coded numbers. A rate typed over a formula in one cell means that lane does not move when you change your markup.

Catch it: have every lane read markup and fuel from one settings area, and scan for cells that are numbers where their neighbours are formulas.

Fuel handled inconsistently. Some lanes include fuel and others do not.

Catch it: confirm the shipper's fuel treatment in the instructions, and apply it the same way across the sheet.

What goes wrong when handing the file back?

Shifted rows or columns. A deleted row in the shipper's template, or a filter left on, puts every rate against the wrong lane.

Catch it: before sending, spot check five lanes from the top, middle and bottom against your working file.

Changing the template. Adding columns, renaming headers or changing the layout can break the shipper's own import.

Catch it: fill their file as given and keep your notes in a separate sheet.

Leaving questions unanswered. The non-rate questions are easy to skip when the rates take all your time.

Catch it: make a list of every question in the RFP and tick them off.

What should you check before you submit?

1. Every tab read, every question answered.
2. Every priced lane matched on origin, destination, equipment, stops and volume band.
3. No-history lanes listed separately, each with a decision.
4. Markup and fuel read from one settings area, applied once.
5. Rate per mile sorted and checked at both ends.
6. File in the shipper's format, five lanes spot checked.
7. Submitted ahead of the deadline, with a copy of exactly what was sent.

How LaneMapper does this step

LaneMapper helps with several of the matching and arithmetic mistakes above, not all of them. It matches each lane to the one history row with the same origin, stops, destination, equipment and volume band, so a dry-van lane is not used for a reefer lane and a one-stop lane is not used for a two-stop lane. A rate is released only when a lane exactly equals its cited history row, and every lane it cannot settle is flagged and listed for you, not filled with a guess.

The markup on your buy rate and the fuel percentage are applied once, by code, from one settings sheet, and rates are locked so a fix from the review model cannot overwrite one. Each lane shows the shipper's row beside the matched history row, so you can check any lane quickly. A second, stronger AI model reviews every result, fixes what it can, and lists what is left for you to decide. Results are model output checked by code and by a second model; they are not verified by a person. LaneMapper does not judge whether your history is stale, whether your buy rates already include a margin, or how the shipper wants fuel shown. You still read the flagged lanes, check those points and make the pricing decisions.

It costs 7 credits per lane, with no subscription. Create an account and upload your next RFP.

Questions

Which RFP mistake costs a small broker the most?

Often a wrong match that goes unnoticed, such as pricing a two-stop or reefer lane from a one-stop dry-van rate. If you win the lane at that rate, you either cover its loads at a loss or turn down the shipper's tenders, which hurts the relationship you bid to win.

Should I bid every lane in the RFP?

Not necessarily. You can limit your bid to the lanes you can support with history or a firm carrier quote. Check whether the shipper requires bids on all lanes or allows partial responses before you decide.

How long before the deadline should pricing be finished?

Leave at least a day for checking. Pricing finished an hour before the deadline leaves no time to catch a shifted column or a lane in the wrong order.