If the same finding closes every year and reopens the next, the corrective action is procedural. The cause is structural.
There is a pattern inside federally funded organizations — local governments, nonprofits, and tribal organizations alike — that finance leaders recognize the moment it is named: the repeat single audit finding.
The auditor flags an issue. The team writes a corrective action plan. The plan is implemented. The finding closes administratively. The next cycle, the same finding appears again, often in a slightly different form. Another corrective action plan is written. The cycle repeats.
A repeat finding almost always indicates the same thing: the corrective action was procedural, but the cause was structural.
These actions can produce a clean look for the auditor in the year they are implemented — but do not change the underlying system.
When the cause is structural and the fix is procedural, the finding will repeat indefinitely.
Two reasons explain why organizations consistently choose the procedural path — even when the structural cause is clear.
A training session or a new checklist can be implemented in weeks. A structural rebuild takes months and requires expertise the organization may not have in-house. The path of least resistance is the path most taken.
They demonstrate to the auditor, the board, and the funder that the organization took the finding seriously. A structural rebuild requires acknowledging that the issue is bigger than the corrective action plan can address — which is a harder conversation with leadership.
So organizations choose the procedural path. The auditor accepts it. The finding closes. The structure stays broken.
If you are looking at a finding that has appeared in two or more consecutive single audit cycles, the diagnostic is straightforward:
The questions that surface the structure:
Is the system that produced this finding still in place — even if the procedures around it have changed?
Is the cause of this finding something a person did, or something the system made inevitable?
If we trained every staff member perfectly and the documentation was flawless, would this finding still occur?
Is the underlying methodology, framework, or architecture defensible — or are we managing around it?
A repeat finding is, paradoxically, one of the clearest signals an organization can have. It is the system telling you exactly where the structure has failed. Most signals from inside a complex organization are ambiguous. This one is not.
When we engage with organizations carrying repeat findings, the rebuild we deliver is targeted by definition. The finding has already identified the structural failure. The work is to address the structure — not to write a better corrective action plan.
Once the structural cause is addressed, the cycle breaks. The corrective action holds because it operates at the right layer of the problem — not just the surface.
Almost always, the structural rebuild produces other downstream benefits the original finding did not anticipate — improved cost recovery, faster reporting cycles, cleaner documentation across the organization.
Because the structural cause was rarely producing only one symptom.
If your organization is approaching another single audit cycle, the question is not "how do we close the finding this year."
That is the question the Strategic Assessment is built to answer.
Identify the underlying methodology, framework, or architecture that is producing the finding — not just the surface-level procedure that failed.
Implement corrective action at the layer of the cause. Address the system, not just the symptom — so the finding does not return next cycle.
Structural rebuilds almost always produce benefits beyond the finding itself — improved cost recovery, faster reporting, and cleaner documentation organization-wide.
Why Single Audit Findings Repeat