The hard part of broker transparency was never willingness. It is that the transaction record for a single load lives in a dozen places. Regulators are about to test how quickly brokers can pull those pieces together.

On August 27, 2026, FMCSA sent its supplemental broker transparency proposal to the White House Office of Information and Regulatory Affairs for review (Transport Topics). The original proposal would require brokers to keep electronic records of each transaction and give carriers access to them within 48 hours of a request. Industry groups including ATA and TIA opposed parts of it, and the supplemental version is FMCSA's response.

OIRA review is a checkpoint, not a finish line. The next step is either publication in the Federal Register with a comment period, or a return to FMCSA for more work. Either way, the direction is clear: carriers asking to see the numbers behind their loads is becoming a formal process with a clock on it.

What would a 48-hour request actually require?

Think about what a carrier asking for "the record" of a load three months ago is really asking for:

• The original rate confirmation and the amount the shipper was billed
• Every change order — rate adjustments, added stops, appointment moves
• Accessorials approved and paid: detention, layover, lumper, TONU
• The emails, texts and call notes where those changes were agreed
• Proof of delivery and the final settlement

In most brokerages, the rate con is in the TMS. The change order is in a rep's inbox. The detention approval was a text message. The lumper receipt is a PDF attached to a reply-all thread. The final amount was keyed in by someone in accounting who is now on vacation.

Assembling that for one load is an hour of searching. Assembling it for 30 loads because a carrier with a billing dispute requests its full history is a week — and the rule's timeline is two days.

Why is the record scattered in the first place?

Because freight is negotiated in conversation, and conversations do not live in the system of record.

A dispatcher calls about detention. The rep says "fine, send the in/out times" and approves it by email. The TMS may show the final accessorial line, but not who approved it, when, or on what evidence. Multiply that by every load, every rep and every channel, and the "record" is really a reconstruction.

This is the same gap that makes documenting carrier selection so difficult when a claim or lawsuit lands. The decisions happened; the evidence is spread across people and inboxes.

How should brokers prepare before the rule is final?

Brokers should prepare by making every load's transaction record complete and retrievable as a single query — capturing rate cons, change orders, accessorial approvals and the messages behind them at the moment they happen, rather than reconstructing them after a request arrives. The rule's final wording may change; the need for a complete, timestamped record will not.

That means changing where the record gets built. Three practical steps:

1. Measure your retrieval time today. Pick five loads from last quarter and time how long it takes to produce the full record, including every change. That number is your real exposure.
2. Find where changes get agreed. For most teams it is email and phone. If a change can be approved in a channel that does not write back to the load, your record will always have holes.
3. Link documents to loads automatically. Every rate con, change order and receipt should be attached to the load it belongs to at the time it arrives, not filed by someone later.

Where AI agents change the math

The reason manual compliance is hard is volume. A mid-size brokerage generates thousands of load-related messages a week. Nobody has the hours to file each one correctly.

An AI agent that already handles those messages — reading carrier emails, confirming rate cons, processing change orders, approving or routing accessorial requests — can log each action against the load as it happens. The record is built as a side effect of doing the work.

• Rate confirmation — Manual process: In TMS, if entered · Agent-handled process: Sent, signed and attached to load automatically
• Change orders — Manual process: In rep's inbox · Agent-handled process: Parsed, reconciled and logged with timestamp
• Accessorial approvals — Manual process: Email or text, unlinked · Agent-handled process: Captured with evidence and approver
• Carrier communications — Manual process: Scattered across channels · Agent-handled process: Threaded to the load across email, SMS, WhatsApp
• Retrieval for a request — Manual process: Hours to days · Agent-handled process: A query against one load ID

This is what a proper AI agent audit trail looks like in practice: not a separate compliance project, but a log generated by the same system that sent the rate con and reconciled the change order.

It also helps with the less-discussed side of transparency — disputes. When a carrier challenges a settlement, a timestamped chain showing the agreed rate, each change and each approval usually resolves the question in minutes rather than escalating into a weeks-long argument.

What this does not solve

Automation does not decide your policy. Whether you share margin, how you respond to requests, and what counts as a complete record under the final rule are legal and commercial decisions. Talk to counsel once the supplemental text is published.

What automation does is remove the operational excuse. If the rule lands and your record is already complete, compliance becomes a report. If it is not, compliance becomes a staffing problem at the worst possible time.

Frequently asked questions

Is the FMCSA broker transparency rule final? No. As of late August 2026, FMCSA's supplemental proposal is under OIRA review at the White House. It must still be published in the Federal Register and go through public comment before a final rule is issued.

What records would brokers have to provide? The original proposal required brokers to keep electronic records of each transaction and make them available to the carrier within 48 hours of a request. The supplemental proposal may change specifics, so watch for the published text.

Do we need a new TMS to comply? Usually not. The gap is rarely the system of record itself; it is that changes and approvals agreed in email, text and phone never reach it. Fixing capture at the communication layer closes most of that gap.

How do AI agents help with broker compliance? Agents that handle rate cons, change orders and accessorial requests log every action against the load in real time, so producing a record becomes a lookup rather than a search across inboxes. For a wider view of where agents fit, see our complete guide to AI agents for freight brokers.

The bottom line

FMCSA's broker transparency proposal moved to White House review on August 27, and the original version would give carriers access to transaction records within 48 hours. Whatever the final wording, the operational test is the same: can you produce a complete record of any load, quickly?

Build the record at the moment each rate con, change order and approval happens — not after a request arrives. Brokers who do that will treat the rule as a report to run; brokers who do not will treat it as a fire drill.

Debales deploys AI agents for rate con and change-order reconciliation that log every load transaction as it happens, so a 48-hour records request becomes a query. Book a demo.