Blog · Board and management reporting · Freight brokers and 3PLs
A freight brokerage dashboard compares load margin and tender decisions by desk, shipper, and lane. Follow a worked export, spreadsheet formulas, and reconciliation checks before using the results in a desk review.
A freight brokerage dashboard compares completed-load margin and tender acceptance by desk, shipper, and lane. Start with separate load and tender exports, reconcile their totals, and then arrange the results around the decisions each desk owns. A chart is useful only when its denominator and cutoff are clear.
Use a load export with load ID, shipper ID, lane, desk, pickup date, delivery status, net shipper revenue, and carrier cost. Keep accessorial revenue and cost on the same basis. Specify whether the margin is provisional or closed and whether claims or other adjustments are included.
Use a separate tender export with offer ID, shipper ID, desk, offered date, final decision, and accepted load ID where available. Keep open offers visible but outside a final-decision acceptance rate until they receive a decision. Document any exclusions, such as offers canceled before a response was required.
For definitions beyond this dashboard layout, use the existing freight broker and 3PL sales KPIs. Agree on those definitions before comparing people or desks.
The example below is an illustrative US brokerage reviewing a fully resolved weekly cohort. All accepted offers in this small cohort have completed loads. In a live export, accepted freight may still be waiting for pickup or delivery; retain those statuses rather than forcing the counts to match.
Put this compact export on a worksheet named Loads, with the header in row 1. Amounts are USD. Column G is computed from E less F.
| Load ID | Shipper | Lane | Desk | Net revenue (USD) | Carrier cost (USD) | Margin (USD) |
|---|---|---|---|---|---|---|
| L101 | Atlas | Chicago-Dallas | Central | 2,400 | 2,000 | 400 |
| L102 | Atlas | Chicago-Dallas | Central | 2,600 | 2,300 | 300 |
| L103 | Beacon | Memphis-Atlanta | South | 1,800 | 1,500 | 300 |
| L104 | Beacon | Memphis-Atlanta | South | 2,200 | 1,900 | 300 |
| Total | 9,000 | 7,700 | 1,300 |
In G2, fill down through G5:
=E2-F2
The first row returns 2,400 - 2,000 = $400. The total check is 9,000 - 7,700 = $1,300, equal to the sum of G2:G5. Tie revenue and carrier cost separately to the corresponding source report totals before interpreting the difference.
For each desk, sum matching revenue and cost rows. With a desk name in summary cell A2, revenue is:
=SUMIFS(Loads!$E$2:$E$5,Loads!$D$2:$D$5,$A2)
Replace E with F for carrier cost and G for margin. Microsoft's SUMIFS documentation explains summing rows that meet criteria; additional criteria can select a shipper or lane without changing the measure.
The detailed margin per load by shipper and lane page owns the profitability interpretation. Here, the task is to make its numerator and load population reconcile across views.
On Tenders, enter these columns in A:E. A dash means there is no accepted load ID; leave that cell blank in the workbook.
| Offer ID | Shipper | Desk | Decision | Load ID |
|---|---|---|---|---|
| A01 | Atlas | Central | Accepted | L101 |
| A02 | Atlas | Central | Rejected | - |
| A03 | Atlas | Central | Accepted | L102 |
| A04 | Atlas | Central | Rejected | - |
| B01 | Beacon | South | Accepted | L103 |
| B02 | Beacon | South | Accepted | L104 |
| B03 | Beacon | South | Rejected | - |
These are unique eligible offers with final decisions. With the desk in summary A2, offered and accepted counts are:
=COUNTIF(Tenders!$C$2:$C$8,$A2)
=COUNTIFS(Tenders!$C$2:$C$8,$A2,Tenders!$D$2:$D$8,"Accepted")
Microsoft's counting guide documents using COUNTIFS when multiple conditions must hold. These formulas assume duplicate events and out-of-scope offers have already been removed from the analysis population.
If offered is B2 and accepted is C2, acceptance is:
=IF(B2=0,"",C2/B2)
Format that result as a percentage. A blank denominator result means no eligible offers, rather than a measured acceptance rate of zero. Primary tender share answers a separate question about routing position; acceptance alone does not reveal whether the broker was the first call.
The source rows produce this summary. Percentages are rounded to one decimal place; all calculations use unrounded amounts.
| Desk | Offered | Accepted | Acceptance | Completed loads | Revenue (USD) | Margin (USD) | Margin/load (USD) | Margin/revenue |
|---|---|---|---|---|---|---|---|---|
| Central | 4 | 2 | 50.0% | 2 | 5,000 | 700 | 350 | 14.0% |
| South | 3 | 2 | 66.7% | 2 | 4,000 | 600 | 300 | 15.0% |
| Total | 7 | 4 | 57.1% | 4 | 9,000 | 1,300 | 325 | 14.4% |
Total acceptance is 4 / 7 = 57.1%. Margin per load is 1,300 / 4 = $325; margin percentage is 1,300 / 9,000 = 14.4%. Recompute each total from its numerator and denominator instead of averaging the displayed desk percentages.
Keep the overview small: desk comparisons first, then the shipper and lane rows behind them, then unresolved reconciliation items. Central earns more margin per load, while South retains a larger share of revenue. The table establishes that difference; the individual loads explain what to investigate next.
Covirage is not affiliated with Microsoft.
Upload a load export and tender log with their cutoff dates and identifiers; Covirage maps the columns, and its tools compute and check the supplied margin and tender comparisons. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own export.
See Covirage for freight brokers and 3PLs for the supporting industry context.
Match the update to the decision. A desk can review tender decisions daily, while finance closes load margin after charges and carrier costs are complete. Show each export's cutoff and mark costs that remain provisional so a fresh dashboard does not imply final accounting.
Load margin is revenue less the carrier costs included in your definition. Margin percentage divides that amount by revenue. Margin per load divides the same amount by completed loads. Keep these labels separate because each answers a different question about desk performance.
Rejected tenders belong in the tender log even when they never become a load. A dashboard built only from completed shipments cannot measure acceptance reliably. Retain each eligible offer and its final decision, then connect accepted offers to their load identifiers where available.
Yes. Shipment mix, equipment, shipper terms, and the costs included can differ. Compare the same lane definition and equipment class, then inspect the underlying loads. A desk average alone cannot establish whether pricing, carrier procurement, or customer mix caused the difference.