Skip to content

Logistics and distribution

Contributing rate data to benchmarks: what brokers have agreed to

By SourceX Editorial · Reviewed by Noah Loul ·

Short answer

Brokers who contribute freight rate data to a benchmark usually grant the provider a license to use, aggregate and keep that data, often with derived-data and survival clauses. Most contributions do not transfer ownership of your load history, but exclusivity, non-contribution and output-use clauses can limit licensing it elsewhere, so read those first.

Key takeaways

  • Contributing rate data is usually a license, not a sale; your TMS records stay yours unless a clause assigns them.
  • Derived-data clauses often let the provider keep benchmarks built from your rates after you stop contributing.
  • Non-contribution and exclusivity clauses are the terms most likely to conflict with licensing your own rate history.
  • Benchmark values pulled into your TMS belong to the provider and should be stripped from any dataset you license.
  • Contribution may have been switched on in an integration setting rather than in a contract your counsel negotiated.

What have brokers agreed to when they contribute rate data?#

Brokers who contribute rate data have usually agreed to let a benchmark provider receive load-level records, combine them with other contributors' data and publish aggregated market rates. In return the broker gets lane benchmarks, spot and contract indexes or rate prediction tools.

The data sent is often richer than people remember: lane, equipment, pickup date, linehaul, fuel and accessorials, and sometimes both the shipper rate and the carrier pay. Contribution is frequently enabled through a TMS integration or an onboarding checkbox, so the governing terms may sit in click-through product terms rather than in a negotiated contract.

Start by finding every place rate data leaves your TMS: benchmark tools, load boards, pricing software and visibility platforms. Each connection can carry its own contributor terms, and they rarely match.

Contributor clauses to read first#

Contributor clauses fall into a handful of types, and each one answers a different question about your own rate history. Read them in the master terms, the data addendum and any integration terms, and note which document controls if they conflict.

Contributor terms can also change during the relationship, often through updated online terms that apply on continued use. Keep dated copies of the terms in force for each period you contributed, because the version in effect when data was sent may govern how that data can be used.

Contributor clauses to read first
ClauseWhat it often saysWhy it matters for your history
License grantProvider may use, copy, aggregate and build works from contributed dataUsually non-exclusive, so you keep the right to use your own records
Derived dataBenchmarks, indexes and models built from contributions belong to the providerProvider keeps those outputs after you stop contributing
Exclusivity or non-contributionYou may not contribute the same data to competing aggregatorsCould be argued to reach other recipients of the same data
Output use limitsBenchmark values may not be redistributed, resold or used to build competing productsProvider fields inside your TMS cannot travel with your dataset
Confidentiality and anonymizationProvider will not identify you, your shippers or carriers in outputsMay support the reasonable measures that help keep rate data confidential
Survival and deletionLicense to past contributions survives termination; deletion is limitedPast data stays in the provider's aggregates indefinitely

Does contributing transfer ownership of your rate history?#

Contributing rate data rarely transfers ownership of your rate history; most contributor terms grant a license and leave the underlying records with the broker. The exceptions are clauses that say the contributor assigns rights, or that define contributed data as provider data once received, and those deserve a careful read.

Ownership and freedom to use are different questions. Even where you own every rate confirmation in your TMS, a non-contribution clause can still restrict whom you share those records with. A perpetual, irrevocable license to past contributions also means the provider's use continues whatever you decide next.

Confidentiality terms carry weight here. Under the Defend Trade Secrets Act, information qualifies as a trade secret only if its owner takes reasonable measures to keep it secret and it has economic value from not being generally known. Contributor terms that require anonymization and aggregation may help show those measures, but sending rates to any third party should still be weighed with counsel against the confidentiality you claim for them.

How exclusivity and non-contribution clauses are framed#

Exclusivity and non-contribution clauses usually stop a contributor from sending the same data to a competing benchmark or aggregator, not from using it internally. The definitions decide the scope: what counts as a competitor, an aggregator or a data product, and whether the clause covers your data itself or only the provider's outputs.

A license to an AI developer for model training is a different activity from feeding a rival rate index, but a broad definition can blur that line. Where the wording is ambiguous, counsel may recommend written confirmation from the provider before any license of the same history, kept with the rights file.

Watch also for clauses that bar the contributor from building or helping build competing products. Those can be read to cover a model trained to predict lane rates, so any later license should describe permitted use precisely: the record types, the purpose and whether the recipient may publish rate outputs.

Separating your records from the provider's outputs#

Separating your own records from provider outputs is the practical step that keeps rate history licensable. Many TMS screens store benchmark rates next to your quoted and covered rates, and once those fields sit in the same table, a plain export carries both.

Tag each field by source in a data dictionary, drop provider outputs and mixed fields from any licensed dataset, and keep the field map with the rights file. Quoted rates that your team set while looking at a benchmark are still your records; only the provider's numbers stay behind.

  • Own records: tenders, quotes, rate confirmations, carrier pay, accessorial approvals, invoices and claims.
  • Provider outputs: market rates, index values, forecast ranges and confidence scores pulled from a benchmark tool.
  • Mixed fields: margin targets or pricing rules calculated partly from benchmark values.
  • Third-party terms: shipper rate sheets and contract pricing covered by shipper confidentiality clauses.

Illustrative: a brokerage CFO reviews three contributor agreements#

Illustrative: a fictional truckload brokerage on McLeod PowerBroker has contributed to two rate benchmarks and a pricing tool for several years. Before considering a license of its load and rate history, the CFO and outside counsel pull every agreement and integration setting.

The first benchmark grants a non-exclusive license with a survival clause, which does not limit the broker's own use. The second bars contribution to competing aggregators, so counsel asks the provider to confirm in writing that a training license to an AI developer falls outside the clause, and the provider agrees. The pricing tool forbids reuse of its forecasts, so the team tags those columns in a data dictionary and drops them from the export.

The brokerage then reviews shipper agreements, removes shipper and carrier names, and proceeds with its own tenders, rate confirmations and carrier pay.

How SourceX reviews contributed rate data#

SourceX reviews contributed rate data in the Rights step of the SourceX five-step transaction, after Supply and before Preparation, Approval and Delivery. The review lists every benchmark, load board and pricing tool that receives the broker's data, the clauses that apply and any confirmations obtained.

Those findings go into the SourceX Evidence Packet with provenance, permitted use, the privacy record and release authorization, so a buyer can see that provider outputs were excluded and that the broker approved what was licensed. Data is licensed, not sold, and the broker keeps ownership.

Frequently asked questions

Can we take back rate data we already contributed?

Usually not in full. Many contributor terms keep a license to past contributions after termination and treat benchmarks built from them as provider property. You can normally stop future contributions and ask what deletion the provider offers, but plan on historical contributions remaining in its aggregates.

If our TMS vendor sends data to a benchmark, who agreed to the terms?

Check the TMS agreement and the integration settings. Sometimes the broker accepted the benchmark's terms when enabling the connector; sometimes the TMS vendor has its own data-sharing rights. Either way, the broker should know which terms apply, because they shape what it can promise shippers and future licensees.

Does anonymization by the provider satisfy our shipper confidentiality duties?

It helps, but it does not settle them. Shipper agreements may restrict sharing rates with anyone, aggregated or not. Compare each shipper contract's confidentiality clause with what you contribute, and ask counsel whether contributing lane-level rates for that shipper is permitted.

Do we need to tell a benchmark provider before licensing our own history?

Only if a clause requires it or is ambiguous enough that counsel recommends confirmation. A plain non-exclusive license generally leaves your own records free to use. Where a non-contribution clause exists, written confirmation that your planned license falls outside it reduces the risk of a later dispute.

Could sharing rate data raise antitrust questions?

It can, which is one reason benchmarks usually aggregate, delay and anonymize contributions. Sharing current, identifiable pricing with competitors is a different matter from licensing historical records to a developer. Antitrust analysis depends on the facts, so review any rate-sharing arrangement with counsel.

Sources

  • Under 18 U.S.C. 1839(3), information is a trade secret only if its owner has taken reasonable measures to keep it secret and it derives independent economic value from not being generally known. Source

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if you qualify