The Broker QBR That Takes 20 Minutes, Not Three Days
A tactical playbook for preparing a freight broker quarterly business review from one unified operational record, with every figure traceable to source.
Mithrilis Team
10 min read
Last updated: July 2, 2026.
If you want to know how to prepare a freight broker quarterly business review without burning three days on it, start with the data, not the deck. The quarterly business review with a top customer is where you defend the account, justify your rate, and set up the next twelve months. It should be your strongest meeting of the quarter. Instead it is usually a scramble: someone exports the TMS, someone else pulls accounting, a third person chases the tracking platform and the accessorial log, and the numbers never quite reconcile. By the time the deck is built, two or three days are gone and half the figures are guesses. This playbook fixes that. The prep should take twenty minutes, and every number in the deck should trace back to the load it came from.
TL;DR
A QBR takes two to three days to prep because the data it needs lives in four or five systems that were never built to reconcile: the TMS holds the buy and the sell, accounting holds fuel surcharges and lumpers and claims, the tracking platform holds service events, and detention sits in an accessorial log nobody reads. Stitching them by hand is slow and the totals rarely agree. When those systems are unified against one operational record, the prep becomes a twenty-minute pull instead of a three-day project. You show true margin to the customer, service and on-time performance, detention and facility cost by site, lane-level results, carrier mix, and how every exception was resolved, with each figure traceable to its source row. The picture is already built. The human still runs the meeting and owns the account.
Key takeaways
- A QBR takes days because its six core views (true margin, service, detention, lane performance, carrier mix, exceptions) each live in a different system that was never built to reconcile with the others.
- The reported margin in your TMS is not the true margin to the customer; fuel surcharges, detention, lumpers, and claims land later in accounting and quietly change the number.
- Detention is a real, measurable facility cost: ATRI found drivers were detained in 39.3 percent of all stops in 2023, at a cost the industry measures in billions, yet most of it never makes it back onto the load.
- A unified operational record turns QBR prep into a twenty-minute pull because the TMS, accounting, tracking, and accessorial data are already reconciled against one shipment record.
- The QBR gets fast because the operational picture is already unified and every number traces to source, not because software writes the deck; the human still runs the meeting.
- Asset carriers run the same review with their shippers, and with owned trucks and drivers their margin is even more sensitive to detention and facility cost.
Why prep eats three days#
Nothing about a QBR is conceptually hard. You are answering six questions a good customer will always ask. Did you make money on my freight, and did I? Were my loads on time? How much am I costing you in detention at my own docks? Which of my lanes work and which do not? Who is actually hauling my freight? And when something broke, how did you handle it? The problem is not the questions. It is that the answers live in systems that were never designed to talk to each other, so assembling them is a manual reconciliation job every single quarter.
Here is where each answer actually hides today, and why pulling it by hand is slow.
| What the QBR must show | Where the data actually lives | Why it is hard to pull |
|---|---|---|
| True margin to the customer | TMS (buy and sell) plus accounting for fuel, lumpers, claims | Trailing costs land days later, in a different system |
| Service and on-time performance | Tracking or visibility platform plus TMS status events | Pickup and delivery events split across tools |
| Detention and facility cost by site | Accessorial billing plus driver dwell from tracking | Unbilled detention never gets tied back to the load |
| Lane-level performance | TMS, one row per load | Cost to cover versus quote is not summed by lane |
| Carrier mix and reliability | TMS assignments plus carrier scorecards | Safety and service live outside the TMS |
| Exceptions and resolution | Email, chat, notes | Rarely captured in any structured system |
None of this is a slide-design problem. It is a data problem. FreightWaves put it plainly in its 2026 guide for brokers: many brokerages still rely on a messy collection of tools that do not integrate or share data, which leads to slow or missed quotes, rating and invoicing errors, and a team working harder than it needs to. The QBR is where that fragmentation gets expensive, because it is the one meeting where all of it has to reconcile at once, in front of the customer.
The fix is not a better spreadsheet template. It is a single operational record that unifies those systems continuously, so the reconciliation is already done before you open the deck. That is the whole idea behind the Mithrilis platform: intelligence from connected data, not automation of a single workflow. Here is the twenty-minute build.
The 20-minute build#
Anchor everything to one unified operational record
Do this once, not every quarter. Connect the systems the QBR pulls from (your TMS, your accounting or AP ledger, your tracking or visibility feed, and your accessorial records) to one shipment record, so each load carries its buy, its sell, its service events, and its trailing costs in the same place. You do not rip out the TMS to do this. You connect to what you already run and unify the data on top, which is the approach we walk through in unifying your TMS data without a rip and replace. Once this record exists, every later step is a filter on it, not a fresh export. This is the SEE layer: the unified operational picture you could never assemble from any single tool.
Pull true margin to the customer, not the TMS spread
Filter the record to this customer and this quarter, then read true margin, not the buy-sell spread the TMS showed at booking. True margin is that spread after the fuel surcharge reconciles, after detention and lumper fees post, and after any claim adjudicates, costs that land days or weeks after the load delivered, in accounting rather than the TMS. On a healthy book the two numbers sit close. On a thin-spread lane a single unbilled accessorial can erase the margin, and reported margin will have flattered you all quarter. Show the customer both the revenue you ran on their freight and the true margin underneath it. The gap between reported and true margin is the exact problem we break down in spot-load margin leakage.
Report service and on-time performance by lane
Pull pickup and delivery on-time performance from the same record, broken out by lane and by facility, not as a single blended number. A 94 percent on-time average can hide one lane running at 70 that is quietly putting the account at risk. Because the service events and the financials sit on the same shipment record, you can show on-time performance next to margin for each lane, which is the view the customer actually wants: not just were you on time, but what did on-time (or late) cost both of us. Service is the number a customer feels every week, so it is the number they trust least when it arrives without the loads behind it.
Break out detention and facility cost by site
This is the slide that changes the conversation, and it is the one nobody builds by hand because the data is scattered. Dwell comes from the tracking feed, detention billing from the accessorial log, lumper fees from AP, and they rarely get tied back to the load. Detention is not a rounding error: ATRI found drivers were detained in 39.3 percent of all stops in 2023, costing the industry an estimated $3.6 billion in direct expenses and $11.5 billion in lost productivity. When you can show a shipper which of their own facilities are burning driver hours and money, you turn a rate defense into a joint problem-solving session. The recovery mechanics are in detention and demurrage recovery for brokers.
Rank lane performance and show the carrier mix
Now compare. Rank the customer's lanes by true margin and by service, and show which carriers actually moved their freight and how those carriers performed. This is the BENCHMARK layer: each lane and facility measured against your own connected network, so you can tell the customer not just how a lane did in isolation but how it compares to similar freight. It is also where you spot the lanes to reprice before you walk into the room, instead of discovering them mid-meeting. Cost to cover has been climbing against static quotes all year, and FreightWaves notes brokers are caught between margin sacrifice and customer retention as carrier rates firm faster than shipper pricing. The QBR is where you get ahead of that, with numbers instead of a gut feel.
Show the exceptions and how they were resolved
Every account had loads go sideways: a missed pickup, a reconsigned load, a claim. These usually live in email and chat and never make it into a report, so the customer only remembers the ones that hurt. Pull the quarter's exceptions from the record, and for each one show what happened and how it was resolved. This is the slide that renews accounts, because it reframes the quarter around how you handle trouble, not whether trouble happened. Handled well, an exception is evidence you are worth the margin, and it is far more persuasive than any headline service percentage.
Assemble the deck and pressure-test every number to source
The last step is the one that used to be impossible: verify. Because every figure came from one record, each number on each slide traces back to the specific loads behind it. Before you present, spot-check the ones that matter (true margin on the top lane, the detention total for the worst facility) by clicking through to the underlying rows. When a customer challenges a number in the room, and they will, you can show the loads it came from instead of promising to follow up. That is the difference between a QBR you defend and one you survive.
Twenty minutes, because the reconciliation already happened
The prep is fast because the hard part (making the TMS, accounting, tracking, and accessorial data agree) is done continuously in the background, not the night before the meeting. What used to be three days of exporting and reconciling becomes twenty minutes of filtering a record that is already reconciled. The deck is not written for you. The picture is already built, and you assemble the story you want to tell.
Why every figure has to trace to its source#
There is a reason each step ends at the source row. A QBR number you cannot defend is worse than no number, because the moment a customer catches one figure that does not reconcile, they stop trusting all of them, and you spend the rest of the meeting on the back foot. This is why the operational record keeps every figure traceable: true margin ties to the specific loads and the specific accessorials behind it, on-time performance ties to the actual pickup and delivery events, and detention ties to the dwell and the billing on each stop. You should be able to verify every result, a principle we wrote into our manifesto. In practice that means Atlas can answer a QBR question in plain freight terms (what was true margin on the Dallas to Atlanta lane for this customer last quarter, and which facilities drove the detention) and show its work, so the number and its sources arrive together instead of the answer arriving now and the proof arriving after the meeting.
Brokers and carriers both run the review#
This playbook is written in broker language, but asset carriers run the same review with their shippers, and the stakes are higher. A freight broker is defending a spread, so the QBR is where you prove the margin bought the customer real service and real problem-solving. An asset carrier is defending revenue per load against owned trucks, drivers, and fuel, so detention at a shipper's dock is not just a fee, it is driver hours and equipment sitting idle that the carrier pays for directly. When a carrier can show a shipper, facility by facility, what dwell is costing both of them, the business review becomes the lever for fixing the dock, not just repricing the lane. The mechanism is the same for both. The data has to be unified, and every figure has to trace to source. Only where it bites differs.
The 20-minute QBR is a data problem, not a slide problem#
The reason your QBR takes three days is not that you are slow. It is that the data was never in one place, so you rebuild it by hand every quarter. Fix that once and the prep collapses to twenty minutes, permanently. US business logistics costs ran $2.4 trillion in 2025, about 7.8 percent of GDP, in a market FreightWaves and CSCMP now describe as permanently volatile. In a market like that, the broker or carrier who walks into every business review with true margin, real service, and traceable numbers keeps the account. The one still stitching spreadsheets the night before does not. Mithrilis connects the systems the QBR hides in, unifies them against one operational record, reconciles them continuously, and keeps every figure traceable to its source. Request a demo and we will build a sample QBR view on your own loads, so you can see the twenty-minute version before your next quarter closes.
Related Mithrilis capabilities
The Mithrilis platform
How connected data becomes verifiable, QBR-ready intelligence.
Ask Atlas in plain freight terms
Answer margin, service, and detention questions with sources attached.
For freight brokers
True margin, service, and lane performance per customer.
Spot-load margin leakage
Where reported margin and true margin diverge on a QBR.
Frequently asked questions
Prepare from one unified operational record instead of exporting and reconciling four systems by hand. When your TMS, accounting, tracking, and accessorial data are already reconciled against a single shipment record, QBR prep becomes a twenty-minute filter for the customer and quarter rather than a two or three day rebuild. You pull true margin, service, detention by facility, lane performance, carrier mix, and exception resolution as views on the same record, with each figure traceable to the loads behind it.
Six views the customer will always want: true margin (yours and theirs, after trailing costs), on-time service by lane and facility, detention and facility cost by site, lane-level performance ranked by margin and service, the carrier mix that actually moved the freight, and the quarter's exceptions with how each was resolved. The exception view is the one that renews accounts, because it reframes the review around how you handle trouble rather than whether trouble happened.
Because each view lives in a different system. The TMS holds the buy and the sell, accounting holds fuel surcharges and lumpers and claims, the tracking platform holds service events, and detention sits in an accessorial log. None were built to reconcile with the others, so assembling a QBR is a manual reconciliation job every quarter, and the totals rarely agree on the first pass.
True margin is the buy-sell spread after every trailing cost lands: fuel surcharge reconciliation, detention, lumper fees, and claims that post to accounting days or weeks after the load delivered. The TMS shows reported margin at booking, which flatters you on thin-spread lanes. Showing true margin in the QBR is honest and it is defensible, because each number ties back to the specific loads and accessorials behind it.
No. The QBR gets fast because the operational picture is already unified and every number traces to source, not because a bot writes the deck. Mithrilis surfaces the pattern no single tool can show and keeps it verifiable. You still run the meeting, own the account, and tell the story. The tool removes the days of manual reconciliation, not the judgment.
Yes. Asset carriers run the same review with their shippers, and with owned trucks, drivers, and fuel their margin is more sensitive to detention and facility cost than a broker's is. A carrier that can show a shipper, dock by dock, what dwell is costing both sides turns the review into a lever for fixing the facility, not just repricing the lane.
Topics
Keep reading
Beyond On-Time Percentage: What a Real Carrier Scorecard Measures
Read→On-time percentage grades the past. A real carrier scorecard weighs tender acceptance, dwell, claims, POD timeliness, and performance drift, per lane and per facility.
Customer Concentration Risk: What a Freight Brokerage Loses When Its Biggest Customer Leaves
Read→Revenue share is the wrong way to size customer concentration. Measure the top account's share of true profit, plus the carriers, lanes, and people that leave with it.
The Quotes You Shouldn't Be Winning: Margin-Aware Pricing for Freight Brokers
Read→Win rate and quote speed are vanity metrics. Margin-aware quoting prices each load against what the lane, customer, and carrier actually returned on a true-margin basis, and walks the quotes you would regret winning.