What are the Key Takeaways from this Executive Summary?
Quick answer
- A vague scope is the most expensive mistake in logistics buying. It invites proposals that do not match, prices padded against the unknown, and months of renegotiation after the award.
- Ask for the cost structure and the service levels in the same document. Cost-plus, fixed or gain-share, with the service targets and what happens when they are missed.
- Take the scope from your records, not from memory. Then score the replies against your own cost per unit by lane — a figure a bidder cannot dispute and an outside index cannot replace.
Why Do Most Logistics RFPs Fail Before a Single Proposal Arrives?
Quick answer
The third-party logistics market in North America alone exceeds $300 billion, according to Armstrong & Associates. You would expect careful buying. The typical RFP has the same four faults.
Vague or inflated scope. Without real shipment volumes, the split by mode, the seasonal peaks and the lane detail, nobody can price it. Bidders either pad the price to cover the unknown, or bid low to win and make it back later. Both spoil the relationship before it starts.
Price weighted over capability. A slightly better rate is worth nothing if the provider cannot send status updates into your transport system, has no cross-dock near your sites, or cannot tell you where a load is.
Silence on systems. The RFP asks about fleet size and warehouse space but not about how the two systems will exchange an order. After the award, IT finds a six-month integration nobody budgeted for.
No service targets. Without agreed targets for on-time-in-full, waiting time, damage and claims — and a consequence for missing them — there is no way to hold a provider to anything once the first year is over.
These are not edge cases. Count your own: list the third-party logistics relationships you have signed in the last five years and mark which were renegotiated or ended inside two. Most operations find the share uncomfortable, and it is a better number than any published average because it is about your contracts and your selection process.
What Does the Logistics RFP Lifecycle Actually Look Like?
Quick answer
1. Work out what you need. Before writing anything, get operations, finance, IT and the commercial team to agree what problem this is solving. Fewer providers? A replacement warehouse system? New lanes? The answer shapes everything after it.
2. Write the scope. Turn that into numbers: annual volumes by mode, the lane pairs in and out, product profiles, storage needs, extra services such as kitting or labelling, and the seasonal shape of the year.
3. Pick a shortlist. Use what you know — market reviews, referrals, and how your current providers actually perform — to get to five to eight names. A longer list means nobody reads any reply properly.
4. Draft the document. Use the six sections below. Ask only as many questions as your team will genuinely read and score. Write the scoring rule for each question before you send it.
5. Score the replies. Score against agreed weights, written down in advance. Not in a meeting, and not by whoever argues hardest.
6. Visit sites and call references. Go and see the finalists’ sites. Speak to their customers, ideally of similar size and trade. Ask what the first six months were like, not what steady state is like.
7. Negotiate. Settle the service levels, the pricing mechanism, the review meetings and the exit terms before you sign. The contract should say what the RFP promised.
What Should a High-Quality Logistics RFP Actually Contain?
Quick answer
Who you are and what you ship. Give bidders what they need to price: order volumes, shipment counts by mode, a typical order profile, your biggest origin-destination pairs and your peak weeks. “High-volume e-commerce” is not a volume.
Services and lanes. Say exactly which services are in scope — warehousing, transport management, drayage, cross-docking, final delivery, freight broking, customs — and which lanes or regions. State the delivery terms, such as FOB or CIF, where they apply.
What your systems need. Spell it out: which warehouse, transport and yard systems must connect, which EDI messages, whether an interface is available, how current the tracking has to be, what reporting you expect, and your data security requirements.
Service levels and consequences. Name the measures: on-time-in-full, order accuracy, dock-to-stock time, waiting time limits, damage rate, claims turnaround, stock accuracy. Attach money to them, both ways.
Pricing. Ask for the same work priced three ways so you can compare: cost-plus, which is transparent but variable; fixed rate, which is predictable but rigid; and gain-share, which aligns interests but takes work to administer. Ask for rates by lane, by mode, and for accessorial charges.
Moving the work across. Require a dated plan: who does what, which system work happens when, and whether there is a period of running both in parallel. Handovers are where these arrangements fail, so a provider’s plan for the first 90 days tells you more than their promises about year two.
How Should You Score the Replies Without Bias?
Quick answer
Scoring is usually slow and subjective. A team compares spreadsheets, argues about the written answers, and ends up with the incumbent or the cheapest bid because a real comparison felt impossible.
The fix has less to do with tools than with where the scope came from. The volume, lane and service data behind an RFP already exist in the systems that moved last year’s freight. Taking the scope from that record removes the most common cause of mid-contract disputes — a scope built from what the business believes it ships — and it is faster than rebuilding it in workshops.
When the replies arrive, compare them against your own history rather than a market index. Your actual cost per unit by lane last year is harder to argue with than a published rate, and it is the figure a gain-share model should be tested against. Be careful with any benchmark you cannot inspect: an outlier flagged against a number you cannot see is an assertion, not a finding.
Then make the scoring mechanical. Write the weights and the rule for each question before the replies arrive. Score each reply against the rule, record the score, and keep the working. The point is not that a score is objective. It is that a decision you can reconstruct in a year survives the turnover of the people who made it.
Conclusion
Quick answer
Every pound of logistics spend is under pressure. Demurrage charges rise, capacity tightens, and customers’ delivery expectations only move one way. A multi-year contract awarded on a vague document and a good feeling is an expensive thing to correct.
So build the RFP on your own records: real volumes, real lanes, real service targets. Score the replies with the rigour you would apply to your own operation.
And before you issue it, answer one question internally: can you state your own cost per unit, by lane, for last year? If not, that is the work to do first, because every bid you receive will be scored against a number you do not have. Talk to us if it would help to establish it.
The right logistics partner is out there. Your RFP just has to be good enough to find them.
Sources
- Armstrong & Associates — Source for the North American third-party logistics market size quoted above
- Council of Supply Chain Management Professionals (CSCMP) — Research on how long third-party logistics relationships last, and the annual State of Logistics reports
- Gartner Magic Quadrant for TMS/WMS — Vendor reviews for transport and warehouse systems, used when building a shortlist
- Chartered Institute of Procurement & Supply (CIPS) — Procurement standards covering RFP design, supplier evaluation and sourcing
