Carrier Performance Scorecard: Rank Carriers on Facts, Not Relationships

The problem this kills

Ask three people which carrier is your "best" and you'll get three answers — and none of them will be backed by numbers. The lane gets awarded to whoever the dispatcher likes, whoever called last, or whoever didn't mess up the one shipment everybody remembers. Meanwhile the carrier that's quietly running 94% on-time with almost no claims keeps getting bumped down the routing list, and the one with a charming rep keeps getting tonnage despite a billing-variance problem that's bleeding your accruals.

The frustrating part is that the truth is already sitting in your shipment history. Every load you tendered has an on-time outcome, a claims record, an accept-or-reject, and an invoice that either matched the rate or didn't. You just need something that rolls all of that up per carrier, scores it fairly, and turns it into a scorecard you can actually defend in a routing-tier meeting. You do not need to be a developer to build that something.

What you'll build

A simple internal web tool for your traffic and procurement team. You import your shipment history — one row per shipment, with the carrier, an on-time flag (or the dates to compute it), claims, tender accept/reject, and billing variance. The tool computes the four core KPIs per carrier, normalizes them onto a common 0–100 scale, weights them the way you weight them, and produces a ranked scorecard. It handles small samples fairly so a carrier with five loads doesn't leapfrog one with five hundred on a lucky streak. Your traffic manager reviews the computed scores, makes any justified manual adjustments (each logged with a reason), and approves — and only then is the scorecard published and the quarterly summary emailed to stakeholders.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your current routing process, the system or spreadsheet your shipment data lives in, the exact columns and carrier-naming conventions in your data, your on-time tolerance, how you weight each metric, your typical and peak shipment volumes, and the messy edge cases (multi-stop loads, accessorials, carrier names spelled three ways). It reads a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks the agent through the data model, the CSV import with a shipment-ID dedupe guard, the KPI engine, the scoring-and-ranking logic with small-sample smoothing, the manager review-and-approve gate, the published scorecard, and the quarterly email. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real transportation function needs: login so only your team can use it, row-level security so people only see their own organization's data, a complete audit trail of every score computed, every manual adjustment, and every approval (who, what, when, and why), a hard human-approval gate so no scorecard is published or used to set routing tiers until your manager signs off, and duplicate guards keyed on shipment ID so the same load can't be counted twice and skew a carrier's numbers. The whole tool exists to make a defensible human decision easy — the math drafts the ranking, a person reviews and owns it.

Who it's for

Traffic managers, transportation procurement leads, and logistics analysts who set routing tiers and run carrier reviews, and who are tired of awarding lanes on gut feel. If you can export a list of your shipments and describe what "on-time" means in your world, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be ranking your real carriers on facts by the end of the weekend.