Why can audit scores be misleading without proper context?

A site scoring 92% isn't automatically better than one scoring 78%. We've watched leadership teams celebrate the wrong locations and chase the wrong sites for years because of this.

Three things break audit scores when you read them as a leaderboard:

1. Different auditors score differently. Two people walking the same site with the same checklist will land in different places. One marks a chipped tile "minor finding." The other marks it "non-conformance." This is called rater drift, and it's well documented in inter-rater reliability research. Without calibration sessions, your scores measure auditor personality as much as site performance.
2. Weighting hides the real story. A 95% audit can include a critical food safety failure if non-criticals outnumber it on the checklist. The FDA's Food Code priority classification splits priority items from non-priority for exactly this reason. If your scoring treats every item equally, one serious risk gets averaged into invisibility.
3. Pencil whipping inflates the top. The site scoring 98% every month either runs a flawless operation or has an auditor ticking the checklist from the parking lot. The site at 78% with detailed photos, specific findings, and assigned actions is almost always the one improving. Score velocity matters more than score level.

What to look at instead, in order:

1. Number of findings per audit. A 95% with zero findings logged is a red flag, not a win.
2. Time to close corrective actions. A site that fixes things in 3 days is healthier than a site with a higher score with 60-day closures.
3. Repeat findings. Same issue, three audits in a row, same site? That's your real problem, not the headline number.

The score is a starting point. The pattern underneath is the audit program.

If you're trying to build a more useful scoring system, this is a decent breakdown of retail audit KPIs that go beyond the headline score.