Lagging audit reports are no longer a leadership instrument

The finding that arrived on time and still arrived too late

An internal audit in March identifies a weakness in supplier verification. The report is issued in April. The finding is accepted in May, an action is assigned in June, and it is closed in September.

In July, a batch from that supplier reached a customer.

Nobody in that sequence did anything wrong. Every step followed the procedure, and every step was completed within its target. The procedure was the problem, because its cycle time was longer than the risk's.

This is repositioning, not abolition

Audit does something valuable and does it well. It provides independent confirmation that a system operates as described, by someone with no stake in the answer. Nothing else in an organisation does that, and removing it would be an act of vandalism.

What audit cannot do is tell you something while you can still change the outcome. It examines a period that has closed. That is not a flaw in execution — it is the nature of the instrument.

The error is not having audits. The error is using them as the primary control and then being surprised by failures they were never structurally capable of preventing.

Lagging and leading

Lagging measures describe events already paid for: findings, nonconformities, complaints, rework, returns, credits.

Leading signals move before the failure: a rising volume of expedited orders, a shift consistently finishing late, a training record quietly lapsing, an increase in corrections made on the spot and never recorded.

Most organisations hold a great deal of the first and almost none of the second. There is a structural reason for that. Lagging measures are required, so they get built. Leading signals have to be designed, and nobody audits you for not having them.

The part that is genuinely uncomfortable

A leading signal must be acted on while it is still ambiguous. That is its entire value and its entire cost.

Act on a leading indicator and you will sometimes act on nothing — you will have spent attention on a pattern that turned out to be noise, with no failure afterwards to justify the spend. There is no credit available for the incident that did not happen.

Organisations that cannot tolerate that will always drift back to lagging measures, because lagging measures are never wrong. They are only late.

What actually replaces the lagging report

Not real-time data. Faster data without a decision architecture produces faster noise, and a dashboard nobody acts on is a more expensive version of a report nobody reads.

What replaces it is an explicit answer to three questions: who sees which signal, at what threshold does it demand attention, and what is that person accountable to do about it. Evidence becomes action only where someone is named.

One thing to do this quarter

Take your most recent significant operational failure. Work backwards and find the earliest moment at which somebody in the organisation could have known something was wrong.

Then ask what would have had to be true for that person's knowledge to reach someone who could act.

The distance between those two points is your real finding. It will not appear in any audit report, because audit reports are written from the other end.