Here’s why planning often reinforces existing constraints—and how to design for a different outcome.
By William Englehaupt
As one audit cycle closes and the next begins, firms invest significant effort into planning: updating timelines, assigning resources, and aligning on key milestones. On the surface, the process appears structured and deliberate. But beneath that structure, a quieter pattern persists.
Most audit teams believe they are planning for the future. In reality, they are often replaying the past. This is what many would label as SALY, “same as last year.”
MORE Audit process, audit planning
As a Prussian general once observed, “No plan survives first contact with the enemy.” In auditing, that “enemy” is reality: uneven client data, evolving judgment, and the rework that becomes visible once work begins. Most plans are not corrections; they are continuations.
This is why the issues identified in debriefs such as rework, review congestion, and late surprises, so often reappear. Not because teams failed to learn, but because the system that produced those outcomes was never redesigned. Planning, in this sense, is less about forecasting and more about design.
Most audit plans are built on idealized conditions. They assume steady capacity, linear progress, and clean handoffs between preparation, review, and completion.
In practice, audit work behaves very differently. Capacity fluctuates, client data arrives unevenly, and judgment evolves. Work that appears complete often returns for clarification or revision, and review is where expectations are frequently defined.
When plans assume ideal flow, the gap between expectation and reality is filled by rework, delay, and late pressure. The issue is not that plans are wrong in detail; it is that they are incomplete by design.
One of the most persistent gaps lies in how firms think about capacity. Planning models often assume near-full utilization, as if time spent equals progress achieved. In reality, a significant portion of capacity is consumed by iteration, such as clarifying expectations, responding to review notes, and revisiting work. This work is real, but it is rarely planned.
As a result, work is set up to exceed capacity from the outset. The response is predictable: extend hours, accelerate pace, and rely on experience to absorb variation. The appearance of productivity is maintained, but predictability declines.
A second gap lies in how completion is defined. In many plans, work is treated as complete once it is prepared or submitted for review. From a system perspective, that is not completion; it is work-in-process. Until work is complete, reviewed, accepted, and requires no further clarification, it continues to consume capacity. Plans that treat partially complete work as finished consistently understate workload and overstate progress.
This is why engagements can appear on track while teams feel overloaded. The plan reflects progress; the system reflects reality.
If planning is to produce different outcomes, it must begin with different assumptions. That means acknowledging real capacity rather than theoretical availability, explicitly accounting for rework, and defining “done” as true completion rather than interim handoffs. It also requires making trade-offs visible.
Every plan implicitly answers a question that is rarely asked directly: given the capacity available, what work will not get done? When that question remains unaddressed, the plan becomes an accumulation of commitments rather than a set of decisions.
More effective planning introduces shorter feedback cycles. Those periods where teams commit only to work that can be completed, reviewed, and accepted within a defined window. (Think agile sprints mindset) This surfaces constraints earlier and reduces partially completed work without attempting to eliminate the judgment inherent in audit work.
This is where planning connects directly back to the debrief. If the prior audit revealed that rework was driven by unclear expectations, planning must make those expectations explicit. If review became a bottleneck, its timing and structure must change. If issues surfaced late, escalation criteria must be defined earlier.
Without that connection, planning becomes an administrative exercise rather than a corrective one.
As W. Edwards Deming observed, systems produce the results they are designed to produce. Planning is where that design is set.
Most audit teams do not struggle because they lack effort or capability. They struggle because the system continues to generate the same patterns.
The opportunity at the start of a new audit cycle is not simply to plan the work. It is to decide whether the system that produced last year’s outcomes will be repeated or deliberately redesigned.