How Do Brokers Measure Margin Leakage on Spot Loads When Reported Margin and True Margin Diverge

Most brokers think they already know their margin. The buy rate and the sell rate are both in the TMS, so the spread looks like a solved problem. The question of how do brokers measure margin leakage on spot loads only gets interesting once you accept that the number on that screen is reported margin, not true margin, and that the two diverge by more than most desks realize. Accessorials are entered late or never. Claims surface weeks after delivery. Detention is tracked in a spreadsheet a different person owns. Each of those lives in a different system, reconciled monthly, which means a spot load can book at a healthy spread on Tuesday and quietly lose money by the time the month closes.

What is the difference between reported margin and true margin on a spot load?#

Reported margin is the buy-sell spread your TMS shows at booking; true margin is that same spread after every cost that arrives later has been subtracted. On a spot load the reported number is available the moment you cover the load: you bought capacity at one rate, you sold it at another, and the difference is what the desk celebrates. True margin is the number you can only know once the accessorials are entered, the claim is adjudicated, and the detention is either billed and collected or written off. The distance between those two numbers is margin leakage, and on spot freight it is structurally larger than anyone reporting off the TMS spread can see.

The reason the two diverge is timing and location. The buy and sell rates are in the TMS at booking. The lumper fee, the layover, the extra stop, and the detention hours arrive over the following days and weeks, often in a different system or a spreadsheet. The damage claim arrives weeks after that. By the time all of it is reconciled, usually at month-end, the load is closed in everyone's mind and the variance gets absorbed into a customer-level P&L that nobody traces back to the individual spot load that caused it. The leak is real, but it has been smeared across the month until it looks like noise.

How do brokers measure margin leakage on spot loads?#

Brokers measure margin leakage on spot loads by reconciling the booked buy-sell spread against the fully loaded cost of the load, then attributing the difference to its source: accessorials, claims, or detention. Doing it properly means three things have to be true at once. First, the accessorials, claims, and detention have to be attached to the specific load they belong to, not aggregated at the customer or the month. Second, they have to be subtracted from the reported spread as they arrive, not held until reconciliation. Third, the resulting true-margin number has to be comparable across loads so an outlier is obvious instead of buried.

Most desks cannot do this today, and not because they lack discipline. They lack the join. The TMS knows the rate. The claims system knows the damage. The detention tracker, frequently a shared spreadsheet, knows the hours. No single screen subtracts the second and third from the first against the live load record, so the measurement only happens once a month when a controller stitches the systems together by hand. The number that comes out is accurate and far too late to act on. The freight has moved, the customer relationship has set, and the lane has already been quoted again at the same leaky rate.

A real measurement reverses that order. Every accessorial, claim, and detention event resolves to the load it belongs to as it happens. The true-margin figure updates the moment a cost lands. And because the system holds the whole network, it can rank that load against its peers immediately: this Atlanta to Dallas dry van spot load returned 9 percent reported margin and 1 percent true margin, against a network median of 6 percent true margin on the same lane. That comparison is the measurement. Everything before it was just a spread.

Why do spot loads leak more margin than contract loads?#

Spot loads leak more margin than contract loads because they carry no negotiated accessorial schedule, so every surprise cost is unanticipated and every detention hour is a fight you did not price in. On a contract lane you have a rate agreement that names the free time, the detention rate, the layover terms, and the accessorial caps. The costs still happen, but they are expected, budgeted, and frequently passed through. On a spot load you bought capacity for one move at one price, and any cost beyond the linehaul is a deduction you did not plan for and often cannot recover.

The data says the spot market is where this hits hardest. The American Transportation Research Institute found that drivers reported being detained in 39.3 percent of all stops in 2023, rising to 42.5 percent among fleets operating in the spot market. The same research found that while 94.5 percent of fleets charge detention fees, those fees are paid on fewer than half the loads that incur them, and that detention cost the industry $3.6 billion in direct expenses plus $11.5 billion in lost productivity. A broker sitting between a shipper who will not pay detention and a carrier who will not eat it absorbs that gap directly, and on a spot load there is no contract clause to fall back on.

There is also a market reason the leak matters more right now. FreightWaves has documented that spot rates have averaged roughly 60 cents per mile below contract rates since May 2022, with the spread compressing toward 11 cents per mile as capacity tightens. When the spread between what you buy at and what you sell at narrows, the cushion that used to hide a layover or an unbilled detention hour disappears. A 200-dollar accessorial that was a rounding error on a fat 2022 spread is the entire margin on a thin 2026 one. The smaller the spread, the more a single unmeasured cost decides whether the load made money.

Where exactly does the margin leak when accessorials, claims, and detention live in different systems?#

The margin leaks in the gap between three systems that each track one cost accurately and none of which subtract it from the load's reported margin. Walk a single spot load through it. A broker covers a load of bottled beverages from a Central Valley shipper to a Dallas distribution center on the spot market. The buy rate is 1,900 dollars, the sell rate is 2,100 dollars, and the TMS reports a 200-dollar spread, a clean 9.5 percent margin. The desk moves on. By the reported number, this was a good load.

Now the other systems weigh in, over the next three weeks, each on its own clock. The carrier sat four hours at the Dallas dock waiting on a door, two hours past free time, and submits a 130-dollar detention invoice into a tracker the operations coordinator owns. A short shipment turns into a 90-dollar claim that posts to the claims system after adjudication. A lumper fee of 110 dollars was paid at the dock and entered late as an accessorial. Each of those numbers is correct in its own system. None of them was ever subtracted from the 200-dollar spread the broker recorded as the margin. The true margin on this load was not 200 dollars. It was a loss of 130 dollars, and nobody on the desk will know until the controller reconciles the month and the variance shows up at the customer level, blended with forty other loads.

This is the core of why the question is hard to answer. The leak is not a billing error and not anyone's mistake. The TMS recorded the spread accurately. The detention tracker recorded the hours accurately. The claims system recorded the damage accurately. The money left in the space between them, because no system holds the join and no person looks at all three against the same load until the books close. The Bureau of Transportation Statistics tracks roughly 54 million tons of freight worth about 52 billion dollars moving every day, with trucks carrying 72 percent of that value; a small per-load leak across that volume is an enormous number reconciled one month too late to change a single quote. This is the same fragmentation problem we walk through in detail in unifying TMS, ELD, and dock data without replacing your TMS, applied to the dollars rather than the timestamps.

How does BENCHMARK mode make spot-load margin leakage visible in real time?#

BENCHMARK mode makes leakage visible by unifying accessorials, claims, and detention against the live load record and then ranking every load's true margin against your own network, so an outlier surfaces the moment it forms instead of at month-end. The intelligence mode here is BENCHMARK, the one that answers show me how I compare. It is not enough to know a load lost money in isolation. The operator needs to see that this Atlanta to Dallas dry van spot load returned 1 percent true margin against a 6 percent network median on the same lane, that this shipper drives detention write-offs at three times your network rate, and that this carrier generates claims on spot freight at a rate no contract carrier matches. Comparison is what turns a number into a decision.

Three things have to hold for that comparison to be trustworthy, and all three map to how the Mithrilis platform is built. First, every cost resolves to the load it belongs to as it arrives, so the true-margin figure is live rather than monthly. Second, the comparison runs across your whole connected network, so the median and the outlier are real peers, not a gut feeling. Third, and the one most tools skip, every number links back to the source row it came from. The detention figure shows the tracker entry and the gate timestamps. The claim shows the adjudication record. The accessorial shows the TMS line. Sources are visible and the query is inspectable, because a true-margin number you cannot trace is just one more number to argue with in a margin dispute. This is the inspectability we wrote into our manifesto: you should be able to verify every result.

What changes operationally is that the leak moves from a backward-looking variance into a forward-looking signal. The shipper whose docks generate unbilled detention shows up before the next quote, not after the quarter. The lane that looks fat on reported spread and thin on true margin gets requoted at a rate that actually clears. The carrier that quietly drives claims on spot freight gets routed differently. None of this is automation closing a workflow. It is intelligence from connected data surfacing a pattern that no single system could show, which is the whole point of the solution we build for freight brokers.

Does the same margin-leakage problem apply to asset carriers?#

Yes, asset carriers run the identical reconciliation on revenue per load, and the leak hides in the same seams. A carrier looks at the linehaul revenue on a haul and books it as profitable, the same way a broker reads a buy-sell spread. But the true revenue per load is the linehaul minus the detention the carrier ate because the shipper would not pay it, minus the claim that posted to a different ledger, minus the deadhead and the extra stop that the dispatch system tracked separately from the billing system. The ATRI finding that detention invoices are paid on fewer than half the loads that charge them lands directly on the carrier's revenue, because the carrier is usually the party absorbing the unpaid hours.

The data patterns differ from a broker's. A carrier owns the trucks, the drivers, and the equipment, so its true-revenue calculation pulls from dispatch, telematics, and payroll rather than from a buy and a sell rate. But the structure is the same: a headline number that looks healthy, a set of costs that arrive later on different clocks and in different systems, and a true number that only assembles at month-end unless something unifies the sources against the load. BENCHMARK mode does the same work for an asset carrier that it does for a broker. It ranks true revenue per load against the carrier's own network so the lane that looks profitable on linehaul and bleeds on detention and deadhead is finally visible while there is still time to renegotiate the lane or fire the facility. Higher margin sensitivity on owned assets makes the comparison more valuable, not less.

See your true margin on a month of your own loads#

The fastest way to understand margin leakage is to stop reading about it and look at your own numbers. Bring a month of spot loads into Mithrilis and it will show you, load by load, where reported margin and true margin diverge once accessorials, claims, and detention are reconciled against the record.

That is possible because Mithrilis connects the systems the leakage hides in. It pulls your TMS, accounting, accessorial, and claims data into one shipment record, reconciles them continuously instead of monthly, and keeps every adjustment traceable to its source. The margin number stops being a Tuesday estimate and becomes something that holds at month close.

Then it goes further than a single number. Atlas answers margin questions in plain English, benchmarks them per customer and per lane, and flags the leaks while there is still time to act. Request a demo and we will show you the spread you are actually running.

Related Mithrilis capabilities

• The Mithrilis platform

  How connected data becomes verifiable true-margin intelligence.

• For freight brokers

  True margin per customer, per lane, and per carrier instead of a TMS spread.

• For asset carriers

  True revenue per load across dispatch, telematics, and payroll.

• Unify your data without replacing the TMS

  The connect-and-resolve foundation the true-margin view sits on.

Frequently asked questions

How do brokers calculate margin on a spot load?

Reported broker margin is the buy-sell spread: the rate you sold the load for minus the rate you paid for capacity, shown in the TMS at booking. True margin is that spread minus the accessorials, claims, and detention that arrive after the load is booked. Most brokers report the spread and never reconcile it down to true margin until month-end, which is where spot-load leakage hides.

What is margin leakage in freight brokerage?

Margin leakage is the gap between reported margin and true margin: the costs that land after a load is booked and erode the spread you thought you captured. On spot loads the usual culprits are unbilled detention, late-entered accessorials like lumper and layover fees, and claims that adjudicate weeks later. Because each lives in a different system and reconciles monthly, the leak is invisible at the desk until the books close.

Why is spot freight margin different from contract freight margin?

Contract freight carries a negotiated rate agreement that names free time, detention rates, and accessorial caps, so surprise costs are budgeted and often passed through. Spot freight has no such schedule, so every detention hour and every accessorial is an unanticipated deduction with no contract clause to recover it. ATRI found detention runs higher in the spot market, at 42.5 percent of stops, which is why spot margin erodes faster than contract margin.

How do you report freight margin accurately across systems?

Accurate freight margin reporting requires resolving every cost to the specific load it belongs to as it arrives, not aggregating costs at the customer or month level. That means the accessorial in the TMS, the claim in the claims system, and the detention in the tracker all subtract from the same load record in real time. A BENCHMARK-mode true-margin view does this and then ranks each load against your network, with every number linking back to its source row.

Why does reported margin look higher than actual margin?

Reported margin looks higher because it is captured at booking, before the costs that erode it have arrived. The buy-sell spread is known immediately, but detention, claims, and late accessorials post over the following days and weeks on separate clocks. Until those are subtracted from the specific load, the TMS spread overstates what the load actually earned, and the difference only reconciles at month-end.

What does BENCHMARK mode mean for measuring margin?

BENCHMARK is the intelligence mode that answers show me how I compare. For margin it means ranking each load's true margin against your own connected network so an outlier is obvious: this lane returns 1 percent true margin against a 6 percent median, this shipper drives detention write-offs at three times your network rate. Comparison turns an isolated number into a decision about which lanes, customers, and carriers to requote or drop.

Can asset carriers measure margin leakage the same way as brokers?

Yes. A carrier's true revenue per load is the linehaul minus the detention it absorbed, the claims that posted elsewhere, and the deadhead tracked in a separate system, exactly mirroring a broker's reconciliation from spread to true margin. The data sources differ, pulling from dispatch, telematics, and payroll rather than a buy and sell rate, but the structure and the BENCHMARK comparison against the carrier's own network are identical.