Reading an RFQ like a carrier, answering like a partner

An RFQ arrives as a spreadsheet attached to an email: a dozen lanes, monthly volumes by weight and pallet count, a service-level table, and a submission window of ten working days. Somewhere below the volumes sits a line that decides more of the contract’s economics than anything above it — an exclusivity clause, a “guarantee” that turns out to be a ceiling, a penalty schedule with no matching compensation clause — and it is easy to read past it on the way to the price column, because the price column is what the form asks you to fill in first.

Contract freight RFQs are not auctions for the lowest number, whatever the spreadsheet format suggests. A buyer running a formal tender is buying certainty at a price, and certainty is demonstrated with data, not asserted with confidence. Two bidders can quote the identical rate and lose and win the same tender, because one of them showed the volumes they actually moved on that lane last year and the other estimated.

What the document is actually asking

Read the RFQ as a list of questions rather than a form to complete. Underneath “price per pallet, Gothenburg–Hamburg, three times weekly” sits the real question: can you actually run this lane, at this frequency, without it becoming the exception that eats your dispatcher’s Monday. Underneath the service-level table sits a second one: what happens when you miss it, and does that clause ruin the contract for you or just annoy the customer. Underneath the volume forecast sits a third: is this a real, seasoned number from the buyer’s own shipping data, or a guess dressed as a forecast because nobody at their end has looked at last year’s actual freight spend.

None of these are printed as questions, because a buyer who has run several tenders has learned that a bidder asked outright will answer optimistically. The tender format is designed to make the honest answer visible in the data rather than in the covering letter — which is exactly why turning up with data changes the outcome more than turning up with confidence.

The data that answers it

Three things carry more weight in a contract-freight bid than the number in the price column:

• Lane history. Not “we cover this corridor” — the actual volumes you moved on it, or one close enough, over the last twelve months. A bidder who can show a lane running near capacity is telling the buyer their truck will actually be there; a bidder with no history on it is asking to be trusted on a route they have never proven.
• Performance, not promise. On-time percentage, claims rate, and how detention and delay were actually handled the last time a customer’s dock ran two hours late. A buyer scoring several bids against the same service-level table is comparing your history against a number everyone else is also promising to hit.
• Structured pricing. A rate that comes out of a price sheet — by weight, distance, time window or zone — reads as considered. A rate typed straight into the RFQ’s price column with nothing behind it reads as a guess with three decimal places, and an experienced buyer can usually tell which is which from how consistently the numbers move across the lane list.

None of this needs to be elaborate. A one-page appendix with last year’s volumes on the lanes in question and your on-time figure for the same period says more than a paragraph of assurances, because it is the kind of thing a bidder without the data cannot fabricate convincingly under a ten-day deadline.

Red flags that predict an unprofitable contract

Some RFQs are asking you to lose money slowly rather than testing your capability, and the tell is usually in the clauses around the price table rather than in the price table itself.

• Volume with no commitment, exclusivity with no minimum. A forecast of “up to 200 pallets a month” with no floor is a ceiling you are being asked to plan capacity for and a floor you cannot rely on — and if the same RFQ asks you not to carry competing freight on the lane, you have taken on the fixed cost of a dedicated service with the demand risk of a spot market.
• Penalties with no matching compensation. A service-level breach that costs you a fee is a normal clause. One with no corresponding payment when the customer’s own dock causes the delay — no detention pay, no waiting-time clause — puts the entire risk of somebody else’s yard on your own account.
• A rate locked for a year against a cost base that is not. Fuel, tolls and driver wages move; a rate fixed for twelve months with no index clause is a bet that they will move in the buyer’s favour, and it is a bet only one side of the contract is taking.
• Payment terms buried in an appendix, not the headline. Sixty or ninety days is workable if you know about it before you price the lane. Finding it in clause fourteen after you have already committed capacity turns a profitable rate into an expensive one, because the financing cost of the terms was never in your number.
• A service level built for a network you are not. Two-hour delivery windows and next-day everywhere reads well in a tender document written for a national carrier, and is a standing breach if you run three trucks. Answer against the service you can actually run, or answer against the smaller piece of the tender that you can.

None of these disqualify a tender outright. They are terms that need pricing into the rate rather than accepted as boilerplate, and a bidder who prices them correctly usually loses the lowest-headline-number comparison and wins the contract that is still profitable eighteen months in.

Answering honestly at small-fleet scale

A small fleet’s honest answer to a large tender is often a partial one, and the temptation is to round up rather than say so. It is better to bid the lanes you can genuinely commit capacity to at the frequency asked, decline or flag the ones you cannot, and state plainly where your volume ceiling sits. A buyer running a formal process has seen enough over-promised capacity fail mid-contract to value a bidder who states a limit before it becomes a missed pickup.

The same discipline applies to the numbers in the appendix. A volume figure that is close but honestly caveated — “measured over nine months, not twelve; this lane started in March” — survives a follow-up question. A rounder number that cannot survive being asked where it came from costs more credibility than the gap it was covering.

Where navichain stands

Answering a tender with data is easier when the data already exists as a by-product of running the business, rather than something assembled for the occasion. navichain turns quotations into bookings on confirmation with no re-typing between the offer and the job, and keeps per-customer price sheets by weight, distance, time or geographic zone rather than a rate typed once and forgotten. A customer portal scoped to a single organization lets the buyer watching a contract track their own half of it instead of ringing for a status. The solutions page covers what that looks like for a forwarder selling capacity or a haulier running it; pricing is monthly, with every feature on every plan, so winning the tender does not also mean signing a new contract with us to run it.