In short. Inspected files do not fail because the audit team was wrong. They fail because the file does not visibly contain the reasoning that produced the right answer. The remedy is documentation discipline, not training, and it is solvable with templates and tooling rather than personnel changes.
1. The reports say the same thing every year
If you stack the FRC’s audit-quality inspection reports from the last several cycles, the language varies and the substance does not. The headline categories that drive inspection grades are remarkably stable: revenue recognition, going concern, group audit oversight, and the auditor’s response to identified risks. Within those categories the recurring criticism is more specific than people remember. It is rarely “the auditor reached the wrong conclusion”. It is almost always “the auditor’s file does not contain sufficient evidence that they considered X”.
The distinction matters. The first claim is about judgment. The second is about documentation. They have different fixes.
2. What “insufficient documentation” usually means in practice
When the FRC concludes that a file is insufficiently documented, it is almost never claiming the workpapers are sparse. Modern files are not sparse. They are voluminous. The complaint is more precise: a specific judgment is asserted in a memorandum, and the underlying evidence either is not in the file at all or is in the file but not connected to the assertion.
A typical pattern: the engagement leader concludes that management’s estimate of expected credit loss is reasonable. The file contains the management estimate, a comparator from a sector benchmark study, and a sensitivity table. What the file does not contain is a written analysis of why the difference between the management estimate and the comparator does not warrant a challenge. The conclusion is right. The reasoning is in the engagement leader’s head. The file is silent.
That is the gap that drives inspection findings. Not absent work; absent trace.
3. Why the gap is structural
The gap is not laziness and it is rarely time pressure. It is structural to how senior auditors work. Senior auditors do their best thinking in conversation: a partner-and-manager review, a phone call with the technical desk, an audit-committee discussion. The conclusion that emerges from that thinking is recorded; the conversation that produced it is not.
For decades the response to this has been “document better”. That instruction has not worked at scale because writing up a conversation after the fact is genuinely hard, and because the engagement team’s incentive structure pulls them toward the next caption rather than back to the last one. Telling people to write more, more carefully, after they have already moved on, is not a fix. It is a wish.
4. The two real fixes
What does work, in my experience signing off and remediating files, comes down to two structural moves.
First, capture the reasoning at the moment it is formed. Standardised judgment templates, owned by the partner, completed during the review meeting rather than after it. One page per significant judgment: the matter, the management position, the auditor’s expectation, the difference, the reasons it is or is not a challenge, the conclusion. Five minutes during the meeting; ten if the matter is contentious. The output is a workpaper that records what actually happened in the room, in the words the room used. Inspection reviewers find these because they are signed and dated; they survive because the reasoning is contemporaneous.
Second, enforce a citation discipline on every concluding memorandum. No assertion in a partner-signed memorandum may exist without a working-paper reference. Tools matter here. A linked-citation system, whether bespoke or built on top of an existing file structure, turns documentation discipline from a writing problem into a navigation problem. The engagement team becomes accountable for traceability, not for prose.
5. Why tooling helps and where it cannot
This is where the tooling discussion enters honestly. Workpaper generation tools, including AuditEngine which I built, are well-suited to the deterministic half of this problem. Citation enforcement, template consistency, evidence indexing, walkthrough drafting: these are problems that benefit from automation. Two competent auditors given the same inputs produce documents that differ only in prose style; tooling reduces the variance and frees senior time for the judgmental half.
The judgmental half does not yield to tooling, and any honest tool will refuse to pretend otherwise. The reasoning behind a sufficiency conclusion, the weighting between two pieces of contradictory evidence, the partner’s read on management’s tone, the going-concern call: these are not pattern-matching tasks. The right architectural response is to handle the deterministic part automatically and to design the template so that the judgmental part has a dedicated visible place to live.
6. The remediation cycle, observed
A remediation engagement that follows a poor inspection grade usually unfolds in three predictable phases.
Phase one, weeks one and two: the firm wants to retrain. This is the wrong instinct. The auditors involved are not unskilled. They are working in a system that does not capture what they know.
Phase two, weeks three to six: the firm wants to add a new layer of review. This is also the wrong instinct. New review layers slow the file and rarely surface evidence gaps; what they surface is conclusion disagreements, which is a different problem and not the one inspection flagged.
Phase three, when remediation finally lands: the firm changes its file architecture. Templates change. Citation discipline becomes enforced rather than encouraged. Significant-judgment workpapers move from optional appendices to mandatory front-of-file artefacts. Six months later inspection grades move.
The lesson is that competence is rarely the problem and culture is rarely the cure. The problem is the file architecture and the cure is structural change to how reasoning gets captured.
7. The implication for firms that have not yet been inspected
If a firm is not yet on the FRC’s inspection cycle, the temptation is to wait. That is misjudged. The cost of changing file architecture under inspection pressure is materially higher than the cost of changing it before. The work is the same; the audit committee conversation is much harder when it happens after a public grade.
The reasonable position is to assume the inspection arrives, write the file as if a reviewer who has never met the team will read it cold, and design the templates so that the senior thinking which actually produces the conclusion is the thinking that ends up in the file. That is the steady-state move. It is unspectacular. It is also the move that, in observed cases, closes the gap between the audit that was done and the audit that the file shows.
— DK Buledi, March 2026