A client audit came back low: what happens next

A low audit score tends to land harder than it probably should, especially for a contract manager who genuinely believes the site is generally well run. The instinct is often either to explain it away — the auditor caught a bad day, one team member was off sick — or to over-correct with a burst of visible activity that fades once attention moves elsewhere. Neither response tends to land well with the client, and neither is what actually fixes the underlying issue.

Reading the result properly first

Before responding to anyone, it's worth actually reading the scoring breakdown rather than reacting to the headline number. Is the low score spread evenly across categories, or concentrated in one or two? Is it a first occurrence or part of a pattern across recent audits? That distinction changes what an honest, useful response actually looks like — a scattered one-off dip calls for a different conversation than a specific category failing consistently.

What a good response actually looks like

Clients auditing a contract have generally seen a low score handled badly before, which makes a straightforward response stand out more than it might seem to deserve credit for. Acknowledging the specific findings, explaining plainly what's being done differently, and giving a realistic timeframe for improvement tends to land far better than disputing the score or promising an immediate, dramatic fix that isn't credible.

• –Read the category breakdown before responding, not just the overall score
• –Check whether this is a one-off dip or part of a pattern across recent audits
• –Acknowledge specific findings plainly rather than disputing the result or offering excuses
• –Set out a concrete, realistic plan with owners and dates, not a vague commitment to "do better"
• –Follow up proactively before the next scheduled audit, rather than waiting for the client to ask whether anything changed

Following up before the client has to ask

The strongest position after a poor audit isn't a perfect score next time — it's the client seeing, unprompted, that something changed in response. A short update a few weeks later, showing what's been fixed and what's still in progress, does more for the relationship than silence followed by an improved number at the next scheduled audit. It also gives the contractor a natural, low-pressure moment to raise the finding directly, similar to how issues get raised and closed properly rather than left open until someone asks again.

When it's a genuine specification mismatch

Occasionally a low score reflects a real gap between what the client's specification asks for and what's commercially or practically being delivered — not a quality failure so much as a drift that's crept in unnoticed. That's a harder, more structural conversation, and worth having directly rather than trying to close through operational fixes alone; it usually surfaces properly at a quarterly business review rather than in response to a single audit.