Why audit outcomes are set earlier than most teams think—and how to design for a cleaner execution
By William Englehaupt
By the time audit work is under pressure, most of the outcome has already been determined.
Deadlines tighten. Review queues build. Questions surface late. Client pressure magnifies. Teams respond the only way they can: by working longer, moving faster, and relying on experience to close the gap. It feels like execution is the problem. In reality, execution is where earlier decisions show up.
MORE Audit & Assurance
Across audits, the same pattern repeats. Work that seemed straightforward becomes iterative. Review expands from validation to correction. Issues that could have been resolved early surface when time is limited, and options are fewer.
These moments are often treated as unavoidable. They are not. They are the downstream effects of how the audit was set up months earlier.
Planning defines scope and timing. But setup defines how the work will actually behave once it begins. It establishes what “good” looks like, how judgment will be applied, when issues are expected to surface, and how review will function in practice.
When those elements are left implicit, teams fill the gaps under pressure. That is where most audits begin to break.
Expectations are one of the first fault lines. Preparers start work without a clear understanding of what “done” means beyond completing a task or submitting it for review. Reviewers, operating with a different standard, use review to clarify what should have been defined upfront.
The result is predictable. Work returns for revision. Review expands. Time is consumed not by complexity, but by misalignment. The same dynamic applies to escalation.
In theory, issues should surface early, when they are easier to resolve. In practice, uncertainty is often held because expectations around escalation are unclear, or because raising questions feels premature. By the time issues are raised, the engagement is under pressure and flexibility is limited. The issue is not judgment. It is timing.
Work also suffers when review is treated as a phase rather than a continuous process. Large volumes of work are submitted at once, and reviewers are expected to process them under time constraints. Feedback arrives late, often after downstream work has already progressed based on incomplete or incorrect assumptions. This is not a capacity problem. It is a design problem.
As W. Edwards Deming observed, systems produce the results they are designed to produce. Once fieldwork begins, the system is already in motion. The question is whether your audit was designed to surface issues early or to defer them until later.
More effective teams treat setup as a critical part of the audit, not an administrative step before it. And it’s more than just building the schedule. They make expectations explicit before work begins. “Done” is defined as complete, reviewed, and accepted—not simply prepared. Review is positioned as an ongoing process, with smaller batches and earlier feedback. Escalation is clarified so that raising uncertainty is expected, not deferred.
These are not cultural aspirations. They are operational choices. They determine whether coaching happens upfront or during review. Whether issues surface early or late. Whether work flows cleanly or cycles back under pressure.
Importantly, these choices are available before the audit starts. They do not require new tools or additional resources. They require clarity, alignment, and a willingness to design the system deliberately.
This is where the prior steps in the cycle—debriefing and planning—come together. If the debrief identified rework driven by unclear expectations, setup must define those expectations explicitly. If planning acknowledged capacity constraints, setup must ensure that work is structured to fit within them. If issues surfaced late, setup must create conditions for earlier escalation.
Without that connection, teams enter fieldwork with the same ambiguity and produce the same outcomes.
The pattern is consistent across firms. Under pressure, teams do not revert to best practices. They revert to how the system was set up. As a result, the final stages of an audit often feel like a test of endurance. In reality, they reflect earlier design decisions.
The opportunity is straightforward. Before fieldwork begins, decide how the work will behave:
- Decide what “done” means.
- Decide how review will function.
- Decide when issues must be raised.
Then design the work to support those decisions. Because once pressure arrives, it is too late to redesign the system. And by then, the outcome is already in motion.