Why one of the most critical audit procedures quietly becomes one of the least effective
By William Englehaupt
Walkthroughs sit at the center of audit quality. They are the mechanism through which auditors develop an understanding of processes, identify control points, and assess risk in context. Yet in practice, they are frequently one of the least controlled and most inefficient parts of the engagement.
They tend to run late, produce incomplete evidence, and generate follow-up cycles that extend months beyond the initial meeting. By the time year-end arrives, teams are often still resolving questions that should have been addressed months earlier. This is not a failure of technical capability; it is a failure of process design.
MORE Productivity | MORE Audit and Assurance
Most audit teams do not manage walkthroughs as a defined system of work. Instead, they are treated as a sequence of meetings—scheduled, conducted, and documented with varying degrees of rigor. That approach creates the appearance of progress without delivering the underlying objective: a complete, evidence-based understanding of the transaction flow from initiation through financial statement impact.
In theory, the workflow is straightforward. A meeting is scheduled, the process is discussed, and documentation is completed. In reality, the inputs required for that sequence are often missing or misaligned. Meetings are scheduled before the client is prepared. Key process owners are unavailable or unable to address control-level questions. Supporting documentation arrives after the fact, if at all. Audit teams, under time pressure, default to prior-year workpapers to fill in gaps rather than building current-period understanding.
The result is a fragmented picture of the process. Inquiry begins to substitute for evidence, documentation lags behind execution, and follow-up requests multiply. What should have been a structured “cradle-to-grave” walkthrough becomes a series of partial insights stitched together over time.
The downstream impact is more significant than it appears. Much of the rework that surfaces during testing and review can be traced back to weaknesses in walkthrough execution. Missing documentation triggers additional PBC requests. Unresolved control questions delay testing. Review notes accumulate as engagement teams attempt to reconcile incomplete or inconsistent narratives. These are not isolated inefficiencies; they are symptoms of a system that generates ambiguity early and attempts to resolve it late.
Three structural issues tend to drive this pattern. First, audit plans are typically built at a high level and do not define the day-to-day mechanics required to execute walkthroughs effectively. Second, client readiness is often assumed rather than managed, leaving process owners unclear on expectations, deliverables, and their role in the meeting. Third, once walkthroughs begin, there is limited real-time visibility into progress, dependencies, and emerging delays. Issues surface only after they have already affected the timeline.
Despite these inefficiencies, most audits are still completed on schedule. Deadlines are met, opinions are issued, and the engagement moves forward. That outcome can obscure the underlying cost. The work requires more effort than necessary, places additional pressure on teams, and introduces avoidable friction into client relationships. In effect, the audit succeeds, but at a level of strain and rework that is treated as normal.
The distinction between teams that experience this pattern and those that avoid it is not technical sophistication. It is how they conceptualize the work. High-performing teams do not treat walkthroughs as meetings to be completed; they treat them as a process to be managed. That shift creates the conditions for consistency, visibility, and control—elements that are largely absent in the traditional approach.
Part 2 examines what that process looks like in practice and how teams can execute walkthroughs with the same level of discipline applied to other core phases of the audit.