Broker transparency: what shippers and carriers can request from your records

What does the broker transparency rule cover?#

The broker transparency rule covers the record a licensed property broker must keep for each shipment it arranges, and the right of the parties to that shipment to review the record. It sits in FMCSA's regulations for property brokers.

In general terms, the record identifies the shipper and the carrier, references the bill of lading or freight bill, and shows the compensation the broker received, the freight charges collected and what was paid to the carrier. Non-brokerage services the broker performed are also described. The rule also sets how long the record must be kept, so check the current text for the retention period rather than relying on habit.

For a brokerage, these records already exist in the TMS: the customer load, the carrier load, the rate confirmation, the customer invoice and the carrier payment. The question is rarely whether the data exists. It is whether the brokerage can produce one clean transaction record on request.

Who can request what from a brokerage?#

Parties to the brokered transaction can request the transaction record, and in practice that means carriers far more often than shippers. Other requesters may have rights from a different source, such as a subpoena or a regulator's investigative authority, or no right at all.

Timing, format and the pending changes#

FMCSA has been working on changes to the broker transparency rule, and the proposals discussed in the trade press concern electronic records and how quickly brokers must respond. Whether, when and in what form any change takes effect is something to confirm on the day you rely on this article.

A low-regret step is to test whether your TMS can produce a single transaction record on demand, in electronic form, without a person stitching together screenshots. If it can, any new timing or format requirement becomes an operational change rather than a scramble. If it cannot, the fix usually involves a saved report joining the customer and carrier sides of a load by load number.

Waivers, confidentiality and the margin question#

Waiver clauses are the center of most transparency disputes. Many broker-carrier agreements ask the carrier to waive its right to review transaction records, and carriers and their advocates have long argued that such waivers should not hold. How a waiver is treated may depend on the current rule text, any pending changes and the facts of the dispute.

Shipper agreements add a second layer. A shipper contract may treat its rates as confidential, while the carrier's request is aimed at exactly those rates. Counsel reconciles the two, usually by checking whether the rule's disclosure obligation overrides the contract, what the carrier actually needs, and whether the response can be limited to the load in question.

The margin is the sensitive figure on both sides. Brokers worry that a pattern of disclosed margins becomes a negotiating tool. That concern is commercial rather than legal, and it should not drive the response to a valid request.

How transparency rights interact with licensing your records#

Transparency rights and data licensing touch the same records but run on separate tracks. The load-level history a carrier can request, including shipper rate, carrier rate and accessorials, is also what an AI developer building pricing or procurement tools would want. Licensing a prepared copy does not change any party's right to review the original.

The practical rules are simple. Never alter or prune the original transaction records while preparing a licensed copy. Remove counterparty identities and band or remove rates where shipper contracts or carrier agreements call for it. And record the confidentiality analysis, because the clauses that matter for transparency requests are the same clauses that limit what can be licensed.

Illustrative: a brokerage fields a request while scoping a license#

Illustrative: a fictional truckload brokerage with a TMS, an accounting system and a carrier onboarding portal is scoping a package of load history for an AI developer. In the same month, a carrier's attorney requests the transaction records for a set of loads the carrier hauled.

The general counsel handles the two on separate tracks. The attorney's authorization is verified, the brokerage confirms the carrier was a party to each load, and the records come from the original TMS data, not the prepared copy. Meanwhile the licensing package removes shipper and carrier names, bands rates by lane and month, and documents the confidentiality clauses reviewed. Neither process touches the other's data.

A response checklist for transparency requests#

A short, written procedure keeps responses consistent and defensible. The steps below are a starting point for counsel to adapt.

• 1Log the request with the date received, the requester and the loads named.
• 2Confirm the requester was a party to each load, or holds written authority from one.
• 3Check the governing agreement for waiver and confidentiality clauses and flag them for counsel.
• 4Pull the record from the original TMS and accounting data, matched by load number.
• 5Limit the response to the loads requested and the fields the rule covers.
• 6Keep a copy of what was sent and when, alongside the original request.

How SourceX handles brokerage records#

SourceX treats a brokerage's load history as a rights-sensitive package within the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The Rights step reviews shipper contracts and carrier agreements, and Preparation works only on copies. The SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and the brokerage's release authorization.