Freight KPIs Worth Tracking (Even Without a TMS)
The freight KPIs worth tracking without a TMS — OTIF, damage rate, invoice accuracy and POD turnaround — with plain definitions and simple ways to measure.

You don’t need a transportation management system to know whether your freight is performing — you need a spreadsheet, a definition for each number, and the discipline to log every shipment the same way. Four KPIs cover most of what matters for a regional B2B shipper: on-time in-full (OTIF), damage and claims rate, invoice accuracy, and POD turnaround. This post defines each one precisely, shows how to compute it from paperwork you already have, and — deliberately — quotes no industry benchmarks, because the comparison that improves your operation is against your own last quarter.
The spreadsheet comes first
Every KPI below is computed from a single shipment log. One row per shipment, entered when the shipment closes out:
- Date booked, date shipped, date delivered
- Origin, destination, carrier, service level
- Promised window (what you or your customer expected)
- Delivered complete? (yes/no) On time? (yes/no)
- Damage or shortage noted? (yes/no, with a word of detail)
- Invoice matched quote? (yes/no/corrected)
- Date POD received
That’s the whole system. The inputs already exist — the booking confirmation, the proof of delivery, the invoice. The log just puts them in one place, and fifteen seconds per shipment is the entire ongoing cost. Every number below is a formula over these columns.
OTIF: the promise-keeping number
On-time in-full (OTIF) is the percentage of shipments that arrived within the promised window with every piece present and accepted. It’s the closest thing freight has to a single service-quality number, because it measures the two ways a delivery can fail a customer at once — late, or incomplete.
Two definitions have to be pinned down before the number means anything:
- On time against what? Use the window that was actually communicated — the delivery day for a next-day shipment, the agreed window for a scheduled run. If no window was ever set, the shipment can’t be scored, which is itself worth noticing: freight without a defined expectation can’t be late, but it can’t be on time either. Tightening how you set expectations is half the value of tracking OTIF, and it starts with understanding what a service level actually commits to.
- In full against what? The piece count on the paperwork, delivered without rejected or missing pieces.
Score each shipment yes/no, divide the yeses by the total, and track it monthly. When OTIF dips, the log tells you where to look: one lane, one receiver, one carrier, one day of the week.
Damage and claims rate: the handling number
Damage rate is the percentage of shipments where the receiver noted damage or shortage at delivery; claims rate is the percentage that became an actual freight claim. Track both, because the gap between them is informative — plenty of noted damage never becomes a claim, and a rising noted-damage rate is the early warning that arrives before the claims do.
The critical dependency is discipline at the receiving dock: damage only enters your data if receivers check freight and note exceptions on the POD at signing. If your damage rate is a suspiciously perfect zero, the first question isn’t about the freight — it’s whether anyone is looking. Our answer page on what a freight claim is covers what happens after a notation, but the KPI lives or dies at the signature line.
When the rate moves, segment it: by lane, by packaging type, by carrier, by product. Damage patterns are rarely random — they usually point at one packaging decision, one handling step, or one route.
Invoice accuracy: the billing-hygiene number
Invoice accuracy is the percentage of freight invoices that matched the quote or agreed rate without correction. It’s the KPI that pays for the whole exercise, because every miss found is money, and because the pattern behind the misses — accessorials that keep appearing, re-rates that keep happening — points at process problems upstream at booking.
Computing it requires actually checking invoices, which is its own small discipline; the manual process in our guide to freight invoice auditing produces exactly the yes/no/corrected column this KPI needs. Log disputed lines and their outcomes too: an invoice corrected without friction is a different signal than one fought over for a month. Recurring detention and wait-time charges deserve their own tally, because they’re usually a dock problem wearing a billing costume.
POD turnaround: the closure number
POD turnaround is the time from delivery to the proof of delivery being in your hands. It’s the least glamorous KPI here and the one that quietly governs the others: until the POD arrives, you can’t confirm on-time, can’t verify in-full, can’t audit the invoice, and can’t invoice your own customer if your billing waits on delivery confirmation.
Measure it in days from the delivery date to the POD-received date in your log. If turnaround is slow or erratic, raise it with the carrier as a service item — how PODs get back to you is a communication arrangement, part of the same expectations covered in our post on shipment communication, and a carrier that closes every run promptly makes every other number on this page easier to trust.
Reading the numbers without fooling yourself
Three habits keep a homegrown KPI sheet honest. First, mind the volume: percentages jump around wildly on small counts, so with a handful of shipments a week, read raw events and stories, not rates. Second, never change a definition mid-stream without marking it — an OTIF that “improved” because the window definition loosened is a lie you told yourself. Third, review on a rhythm: a short monthly look, and a quarterly conversation with your carrier built on the shared data. Numbers that no meeting ever reads stop being collected honestly within a quarter.
Where the KPIs shine brightest is on recurring freight. One-off shipments produce anecdotes; a standing lane produces a real time series, where a drifting OTIF or a creeping damage rate is visible early and fixable cheaply. If a chunk of your freight runs weekly, putting it on a scheduled route gives you both steadier performance to measure and cleaner data to measure it with.
Sonic Transport closes every run with a POD and shipment updates as standard, quotes that spell out what’s included, and a person who knows your account when a number needs explaining — the raw material of every KPI on this page. If you want freight that’s easy to measure and easier to trust, tell us about your lanes and we’ll get you a baseline worth beating.
Frequently asked questions
What is a good OTIF score?
There's no universal benchmark worth quoting — targets vary by industry, lane and how strictly on-time and in-full are defined. The useful move is to measure your own baseline for a couple of months, agree internally on what counts as a miss, and then work the number upward against your own history.
How many shipments do we need before freight KPIs mean anything?
Trends need volume, so read percentages cautiously until you have at least a few dozen shipments in the window. With low volume, track the raw events instead — every late delivery, every damage, every invoice correction — and read them as individual stories rather than rates.
Should we share these KPIs with our carrier?
Yes, if you want the numbers to improve. A carrier can't fix a pattern nobody shows them, and a quarterly conversation built on shared data — what was late, what was damaged, what was disputed — turns the KPI sheet from a scorecard into a working agenda.