By Vokrix Team

Manual carrier scorecard compilation takes about 22 hours per quarter, costing roughly $1,430 per quarterly cycle at $65/hour, versus about 2 hours when automated (Eyefreight 2024 TMS User Survey, cit
TL;DR: Compiling a quarterly 3PL carrier scorecard by hand takes about 22 hours per cycle — roughly $1,430 at $65 an hour — while an automated process does the same work in about 2 hours (Eyefreight 2024 TMS User Survey, cited in US Tech Automations, 2025). The gap isn't the analysis. It's the data wrangling before the analysis: exporting shipment events from a TMS, opening carrier PDFs, reconciling a spreadsheet one carrier insists on sending, and merging three name variants of the same trucking company into one row. This post covers how to build the scorecard, which KPIs and thresholds to use, how to automate the reporting pipeline, how to fix messy carrier names, and what on-time delivery and tender acceptance targets actually make sense.
A quarterly carrier review is supposed to be a decision meeting. Too often it becomes a data entry project. Someone on the logistics team blocks out a week, pulls shipment data, chases down invoices, copies numbers between tabs, and rebuilds formulas that broke when a column got sorted. By the time the scorecard is finished, the quarter is two weeks gone and nobody wants to relitigate it.
The cost is real and it's measurable. Twenty-two hours is more than half a work week, every quarter, forever. Multiply that across a year and a mid-size 3PL is burning a full week of analyst time on a report that mostly describes what already happened. Automation cuts it to about two hours, which is roughly 20 hours and $1,300 returned to the business every cycle — time that should go into carrier negotiations, lane rebalancing, and fixing the service problems the scorecard was built to surface.
Spreadsheets also fail in a specific, predictable way: nobody trusts them. Two analysts produce two different numbers for the same carrier because one filtered on delivered date and the other on ship date. A carrier disputes a 92% on-time figure and there's no audit trail to defend it. That argument eats the meeting. A scorecard only works if the numbers are consistent, sourced, and defensible enough that the conversation moves to what to do about a carrier instead of whether the data is right.
The scorecard itself doesn't need to be complicated. Pick the carriers that matter — usually the top 20 to 30 by spend, plus any carrier on a performance improvement plan. Choose five to seven KPIs that reflect what your shippers actually complain about. Weight them so the ranking reflects your priorities rather than a flat average. Set a grade scale with a clear line between "meets expectations" and "needs a conversation." And agree, in writing, on a single source of record for each metric before the quarter starts, because retroactively arguing about definitions is how scorecards die.
The messiest part is almost always carrier identity. Your TMS might call a carrier "Estes Express Lines," a PDF invoice says "ESTES EXP," and a regional spreadsheet says "Estes." Three rows for one vendor means three incomplete scorecards. Every meaningful automation effort starts with a normalized carrier master list and a mapping layer that resolves aliases, SCAC codes, and legacy names into one canonical record — and then flags new unmatched names as they appear instead of quietly dropping them.
Once names are stable, the pipeline is straightforward. The TMS feeds shipment and tender events through an API. PDFs get parsed, not retyped. Excel exports get ingested on a schedule. The scoring model applies the weights, and the dashboard refreshes monthly so the quarter builds itself instead of appearing in a panic at the end. That's the practical case for 3PL carrier scorecard software: not fancier charts, but a repeatable process that costs two hours instead of twenty-two.
Start with one clean quarter. Normalize the carrier list, lock the definitions, run the numbers manually once to validate the model, and then automate the same logic. After that, the quarterly review becomes what it was always meant to be — a decision about which carriers get more freight and which ones don't.
Start by defining scope: which carriers you're grading, which modes and lanes are in play, and which business units or shippers are affected. Then pick five to seven KPIs, assign weights that reflect your operational priorities, and set thresholds that translate raw numbers into grades or tiers. Before you pull any data, get agreement on a single source of record for each metric — typically the TMS for shipment and tender events, and your accounting or audit system for invoice accuracy. Build the scorecard on one quarter of historical data first so you can validate that the model produces rankings people recognize. Finally, put the review on the calendar: a fixed date each quarter, a fixed format, and a documented rule for what happens when a carrier falls below the threshold. The meeting and the consequences matter more than the spreadsheet.
The core set for most 3PLs is on-time delivery, tender acceptance, cost per mile or cost per shipment versus benchmark, invoice accuracy, damage and claims rate, and technology or EDI compliance. Capacity-related metrics like dwell time and detention charges are useful additions if you manage a lot of live loading or drop trailers. A reasonable weighting scheme is on-time delivery at 25 to 30 percent, tender acceptance at 20 percent, cost at 20 percent, invoice accuracy at 15 percent, damage and claims at 10 percent, and responsiveness or compliance at 5 percent. Adjust those weights to match what your shippers actually escalate. For grading, a five-tier scale from A to F is more useful than a raw score because it forces you to name the outcome, and it makes it obvious which carriers are in good standing and which ones need a corrective action plan.
Use software with connectors into your TMS so shipment, tender, and delivery events flow in through an API rather than a manual export. For carriers and brokers who still send PDF invoices or remittance files, use document parsing to extract the fields you need automatically, and set up scheduled ingestion for the Excel files some partners insist on sending. All three sources should land in the same normalized data model, keyed on a canonical carrier identifier, so the scoring logic runs once on combined data instead of three times on separate islands. Schedule the refresh monthly rather than quarterly so data quality problems surface early and the quarter-end scorecard is already assembled. Before you trust it, run one quarter in parallel with your manual process and reconcile the numbers — the differences will tell you exactly where your definitions were ambiguous.
Use SCAC codes as the primary key wherever they exist, since they're the only carrier identifier that's designed to be unambiguous. Build a master carrier table with one canonical name per legal entity, then create an alias mapping for every variant you've seen — abbreviations, legacy names, misspellings, and acquisition-related name changes. Fuzzy matching handles most of the remainder, but route anything below a high confidence threshold to a human rather than letting it auto-merge; a wrong merge silently corrupts two carriers' scores. Run the matching step every time new data lands, and review the unmatched list each month, because new carriers and renamed vendors appear constantly. Track the percentage of rows that resolve automatically as a data quality metric in its own right — if that number drops, your mapping table is going stale.
For on-time delivery, 95 percent is a solid contract standard for full truckload, with 90 percent as the floor below which a carrier should be flagged and 97 to 98 percent representing best-in-class performance. Less-than-truckload and multi-stop lanes typically run a few points lower because of consolidation and appointment variability, so grade those against their own baselines rather than the truckload standard. For tender acceptance, 95 percent or better is what you want from a primary contract carrier, 90 percent is a warning line, and anything below 85 percent signals a genuine capacity risk that will show up as service failures in a tight market. Set thresholds relative to lane and mode, not as universal absolutes, and revisit them each quarter — a carrier hitting 93 percent in a market where the lane average is 88 percent is performing better than the number suggests.
Ready to try it?