What an auditor asks about a freight award

An audit of a freight award is rarely a challenge to the decision itself. Auditors do not usually think they know your carriers better than you do. What they test is narrower and harder to pass: whether the record behind the award supports the figures you reported. The judgement can be sound and the audit can still go badly, because a sound judgement with no traceable evidence looks, from the outside, identical to a guess.

The auditor's real question

Reduced to one line, the auditor asks: can you show how this number was produced. Every claimed saving, every awarded rate, every emissions or cost figure that flowed into a report — each needs a path back to the source data that produced it. The award is defensible when that path exists and reproducible when following it twice gives the same answer. Where the path breaks, the figure is not wrong so much as unsupported, and unsupported is the word an audit finding is built on.

It is worth sitting with how uncomfortable this is, because it runs against instinct. A procurement lead knows the award was sound — they made it, they remember the reasoning, they can feel that it was right. But an auditor cannot audit a feeling, and "I remember why" is not evidence. The gap an audit exposes is not between a good decision and a bad one; it is between a decision that was good and a decision that can be shown to have been good. Those are different properties, and only the second survives the person who made it leaving, forgetting, or being asked to prove it a year on.

Five things they will ask to see

1. 01The baseline — what the incumbent cost was, and how it was calculated, before any saving can be claimed against it.
2. 02The bids as received — the carrier submissions in their original form, not a summarised extract, so the inputs can be verified.
3. 03The calculation — how bids became an effective cost per lane, with the normalisation and assumptions visible rather than implied.
4. 04The overrides — where the human award departed from the scored result, and the stated reason for each.
5. 05The version history — who changed what and when, so the reported figure can be tied to a specific state of the data.

Where the record usually breaks

Awards rarely fail an audit at the decision. They fail at the seams between systems, where data was handed from one place to another and something was lost in the handoff. Three seams break most often. The first is between the raw bids and the working sheet, where an analyst's cleanup overwrote the original submission and no copy of what the carrier actually sent remains. The second is between the baseline and the saving, where the incumbent cost was estimated rather than sourced, so the denominator cannot be defended. The third is between the scored result and the final award, where overrides were applied directly to the output with no note of what changed or why.

Each seam is invisible while the tender is live and glaring once it is questioned. The defence is not more diligence at the seams; it is not having the seams at all — keeping the raw bids, the sourced baseline, and the recorded overrides as one continuous trail rather than three files that have to be stitched back together under questioning.

Building the record as you go

The mistake most teams make is treating the audit trail as something to assemble afterwards. By then the bid sheets have been overwritten, the baseline has been rebuilt twice, and the reasoning behind an override lives only in someone's memory. Reconstruction is slow, and worse, it is itself un-auditable — a record built after the fact cannot prove it reflects what actually happened.

The alternative is to let the record accumulate as a by-product of doing the work. When each upload, each scoring run, and each award is captured in an append-only trail as it happens, the evidence is already complete when the auditor arrives. Nothing is reconstructed because nothing was lost. Where a figure genuinely cannot be sourced, it is shown as an em-dash rather than filled with a plausible number, because an honest gap withstands an audit and a fabricated certainty does not.

None of this makes the auditor an adversary. A reviewer with a complete record in front of them is fast, because there is nothing to chase — the baseline is there, the bids are there, the overrides are explained. The friction in an audit comes almost entirely from the gaps: every missing figure becomes a request, every request becomes a delay, every delay erodes confidence in the figures that were present. A clean trail turns the audit from an investigation into a formality, which is the outcome everyone in the room actually wants.

An award you can defend to leadership and an award you can defend to an auditor are, in the end, the same award. Both rest on the same record; the auditor simply reads it more literally. Build that record while you decide, and the audit becomes a reading of work already done rather than an investigation into work you can no longer prove.