Logistics and distribution
Shipper RFP and bid histories: what's licensable and what's confidential
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
In freight RFP data, confidentiality usually follows who supplied the information. Lane lists, volumes and requirements a shipper provides are typically confidential under the RFP terms or an NDA. Your own bid logic, rate models and win-loss outcomes are generally your records, though they often embed shipper details that must be removed before any license.
Key takeaways
- Shipper-provided lane lists, volumes and requirements are usually confidential under RFP terms or an NDA.
- Your own rate models, margin rules and bid outcomes are generally your records, subject to review.
- Bid files mix both, so separate shipper inputs from your own reasoning before scoping a license.
- Bid platforms add their own terms of use, which can limit what you do with data downloaded from them.
What's confidential and what's licensable in a freight RFP?#
What's confidential in a freight RFP is mostly what the shipper gave you: its lane list, volumes, facility details, accessorial requirements and service expectations. What may be licensable is what you produced: your rate model, cost assumptions, the bid you submitted, your decisions about which lanes to chase, and what happened afterward.
The split is rarely clean in practice. A bid spreadsheet usually starts as the shipper's template, gains your rates in the next column and your margin notes in a hidden tab. Licensing review starts by pulling those layers apart, file by file and shipper by shipper.
Bid archives tend to come up when a brokerage or carrier inventories its records for AI, or when a new pricing tool vendor asks for history to train on. Either way, the general counsel's first job is the same: establish which inputs came from shippers under terms that still bind the company, before anyone exports a single spreadsheet.
Who contributed each record in a bid history#
Each record in a bid history traces back to one of three contributors: the shipper, your company, or a third party such as a carrier or a bid platform. The contributor is the best first guide to the likely confidentiality position, though the documents themselves decide.
| Record | Contributed by | Typical position | Usual treatment |
|---|---|---|---|
| Lane list, volumes, facility details | Shipper | Confidential under RFP terms or NDA | Exclude, or keep only generalized lane descriptors if terms allow |
| Service requirements and accessorial schedules | Shipper | Confidential | Exclude the document; describe requirements generically if needed |
| Your submitted rates | Your company | Yours, but disclosed to the shipper under the RFP | Review RFP terms; often usable after de-identification and aging |
| Rate model, cost assumptions, margin rules | Your company | Yours | Licensable after review, with shipper identifiers stripped |
| Carrier buy rates and capacity commitments | Carriers | May be confidential under carrier agreements | Check carrier agreements; often generalized or excluded |
| Award letters and scorecards | Shipper | Often confidential | Keep the outcome as your own record; exclude the document |
| Post-award tender acceptance and service results | Your company and the shipper | Mixed | Your operational records are usually yours; shipper scorecards need review |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Where confidentiality obligations come from#
Confidentiality obligations in freight bidding come from several documents at once, and the strictest one controls. A general counsel reviewing a bid archive should collect each of them before deciding scope.
Bid platform terms deserve a separate read. When a shipper runs its RFP through a sourcing tool, the platform's terms of use may govern downloaded files, limit their use to the bid event or restrict automated extraction. Those terms bind the bidder as a platform user, independent of anything the shipper agreed.
- RFP terms of participation, which often define the whole RFP package as confidential and limit its use to preparing a response.
- Standalone NDAs signed before the shipper released lane data.
- Bid platform terms of use, where the RFP ran through a third-party sourcing tool.
- The transportation or brokerage agreement signed after award, with its own confidentiality and data clauses.
- Carrier agreements covering buy rates and capacity shared during bid preparation.
- Any shipper policy on AI use, which some shippers now attach to RFPs or contracts.
Your own bid logic and outcomes#
Your own bid logic and outcomes are usually the strongest licensable part of a bid history, because they record how your pricing team reasoned and what happened next. They include the rate model, the choice to bid hard on some lanes and pass on others, the award result and post-award performance.
The catch is that bid logic often embeds shipper inputs. A margin rule keyed to a lane's volume reveals the volume, and a note explaining a low rate may quote the shipper's requirements. Preparation separates the reasoning from the inputs, for example by replacing volumes with broad bands and facilities with regions.
Limits on use matter as much as limits on disclosure. A clause allowing use only to respond to the RFP may restrict internal analytics as well as licensing, even when nothing is disclosed. Win-loss outcomes recorded in your own TMS or CRM, in your own words, keep the fact while leaving the shipper's award letter out.
Preparation options for bid histories#
Preparation options for bid histories trade detail for safety, and the right level depends on what the RFP terms and the recipient's permitted use allow. Counsel and the pricing lead should agree the level before any file is assembled.
| Option | What it does | Trade-off |
|---|---|---|
| Remove shipper identity | Replaces shipper names, facilities and contacts with tokens | Keeps lane logic; a distinctive lane pattern may still point to a large shipper |
| Generalize lanes | Reduces origins and destinations to regions or zones | Loses some pricing precision |
| Band volumes | Replaces exact volumes with broad ranges | Hides shipper commitments; weakens volume-price analysis |
| Age the data | Includes only bids from older cycles | Less competitively sensitive, and less current |
| Exclude carrier costs | Drops buy rates and capacity commitments | Protects carrier terms; hides margin structure |
Competition concerns with rate data#
Rate data raises competition concerns because current prices are competitively sensitive, and sharing them in a way that could reach competitors can draw antitrust scrutiny. Licensing to an AI developer is not the same as sharing with a competitor, but license terms should still address who sees the data and how it may be used.
Common safeguards include aging the data, aggregating rates, restricting the recipient's permitted use and prohibiting redistribution. Which laws may apply, and which safeguards are enough, is assessed deal by deal with counsel.
Illustrative: a freight brokerage sorts its bid archive#
Illustrative: a fictional asset-light freight brokerage keeps years of RFP responses on a shared drive, with pricing models in spreadsheets and award results logged in McLeod. Its general counsel wants to know whether any of the archive could be part of a records license.
Counsel collects the RFP terms, NDAs and bid platform terms for each shipper. Shipper templates and award letters are excluded outright. The pricing team exports its own rate models, bid decisions and outcomes, replaces shipper names and facilities with tokens and regions, bands volumes and drops carrier buy rates. Bids for shippers whose terms limit use to the RFP response are left out. The remaining set, the brokerage's own reasoning and results, moves to preparation with counsel's sign-off.
How SourceX approaches RFP and bid records#
SourceX approaches RFP and bid records through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery, with the Rights step carrying most of the weight. The fit check collects metadata only, such as the systems that hold bids, the years available and the kinds of terms involved.
Each package that proceeds is documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization, so the permitted use and every exclusion are written down. The company approves each step and keeps ownership of its records.
Frequently asked questions
Does an expired NDA still restrict use of RFP data?
It may. Many NDAs keep confidentiality obligations in force for a period after expiry, or for as long as the information stays confidential. Read the survival clause and treat the data as confidential until counsel confirms otherwise.
Can we license bids for RFPs we lost?
Often, as far as your own rates and reasoning go, since no transportation agreement followed. The RFP terms and any NDA still govern the shipper's information, so the same separation of shipper inputs from your own work applies.
Are spot quotes treated like RFP bids?
Spot quotes usually carry fewer formal terms, but the load details still come from the shipper or from a load board whose terms may apply. Your quoted rate and whether you won the load are generally your own records.
What if a shipper's RFP terms ban AI use of the data?
Then that shipper's material stays out, including derived fields that would reveal it. Some brokerages also exclude their own bids for that shipper, to avoid any argument that the bid embeds restricted information.
Can carrier buy rates ever be part of a license?
Sometimes, in generalized form. Carrier agreements and rate confirmations may treat rates as confidential, so exact buy rates by carrier are usually excluded. Aggregated or aged cost bands, with carrier identities removed, are a common compromise when the carrier terms and counsel allow it.
Do we have to tell shippers before licensing our bid history?
Not always, if only your own de-identified reasoning and outcomes are included and the terms allow it. Some companies tell key shippers anyway for the sake of the relationship. Counsel can advise whether notice or consent is needed in a given case.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.