Guide
How to set up a Tender for Logistics Services

Most shippers only run a logistics tender once every few years, which is exactly why it goes wrong so often. The process gets improvised: a spreadsheet of rates, a handful of calls, a decision made mostly on price. Six months later, the provider that looked cheapest on paper turns out to be the one causing the most exceptions, delays, and disputes.
A tender is how you put structure around that decision. Done properly, it forces you to define what you actually need before you start comparing providers, and it gives every bidder the same information to respond to, so you're comparing like with like. Here's how to set one up.
Step 1: Define the scope before you define the criteria
Before writing a single requirement, get clear on what's actually being tendered. Is this the full transport and warehousing operation, or a single lane or service line? Are you replacing an incumbent or bringing in a new capability? What volumes, routes, and service levels are you working with today, and how do you expect them to change over the next two to three years?
This scope becomes the backbone of the tender. Every requirement, every evaluation criterion, and every question you ask bidders should trace back to it. Skip this step and you end up with a tender that reads like a wish list instead of a specification.
Step 2: Choose the right format
Not every sourcing exercise needs a full Request for Proposal. Three formats cover most situations:
An RFI (Request for Information) is useful when you're not yet sure who the credible providers even are, and you want to shortlist before asking anyone to invest time in a full response. An RFQ (Request for Quotation) works when the service is well defined and price is the main variable, such as a single lane with clear volumes. An RFP (Request for Proposal) is the right choice when you need providers to propose how they'd solve the problem, not just what it costs, because service model, technology, and account setup all matter to the outcome.
Most logistics tenders for an ongoing service relationship should be run as an RFP. It's the format that lets you evaluate capability, not just cost.
Step 3: Set requirements and evaluation criteria together
This is where most tenders lose rigor. Requirements get written first, then someone works out how to score them later, and the two never quite line up. Build them at the same time instead: for every requirement, decide upfront how you'll verify a bidder meets it and how much weight it carries in the final decision.
A well-built scorecard usually covers five areas: price and commercial terms, operational capability and network fit, compliance and insurance, references and financial stability, and visibility, inspections, and reporting. That last category is worth naming explicitly rather than folding into "operations," because it's the one shippers most often forget to ask about, and the one that causes the most friction later. Ask providers how they inspect cargo at pickup, in transit, and on delivery, not just at the final handover. A provider that only checks condition at the end has no record of where a deviation actually happened, which makes damage claims and disputes far harder to resolve. Ask how they document proof of delivery, how they handle damage and exceptions when they occur, and how much of that is visible to you in real time versus buried in someone's inbox after the fact. Some providers run this through a dedicated system, such as Cargosnap, that captures inspections and documentation at every handover point; others still do it on paper or over email. Either way, it's worth knowing before you sign, not after the first disputed claim. A provider who can't show you what happens to your freight while it's out of your hands is a provider you'll be chasing for updates for the life of the contract.
Weight the criteria before the proposals come in, not after. It's the only way to stop the final decision from quietly becoming "whoever was cheapest" by default.
Step 4: Brief bidders clearly and give everyone the same information
Send every bidder the same document, on the same timeline, with the same access to ask questions. If one provider gets a follow-up call and another doesn't, your comparison is already compromised. A short kickoff call or written Q&A round, open to all bidders and answered in writing to all of them, keeps the process fair and saves you from ambiguous responses later.
Give bidders enough time to respond properly. Two to three weeks is typical for an RFP of moderate complexity. Rushed timelines produce generic proposals that tell you very little about how a provider would actually perform.
Step 5: Score, shortlist, and verify
Score submissions against the criteria you set in Step 3, not against your gut reaction to the pricing page. Shortlist two or three providers for deeper conversations: a site visit, a reference call, a walkthrough of their systems. This is where claims made on paper get tested. If a provider says they offer full shipment visibility, ask to see it, not just hear about it.
Step 6: Contract with the details that were promised
Once you've selected a provider, make sure the requirements and commitments from the tender make it into the contract, not just the price. Service levels, reporting cadence, and any technology commitments should be written down, because they're the details that get quietly dropped once the deal is signed and the relationship moves into delivery.
Common mistakes to avoid
Tenders tend to go wrong in the same few ways: scope that's too vague to compare responses against, evaluation criteria decided after the fact to justify a decision already made, timelines too short for a fair response, and requirements that stop at "on time and on budget" without asking how a provider will prove it. Building your scope, criteria, and timeline deliberately, in that order, solves most of it.


