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.
This is not bad luck. It is not auditor pickiness. It is a specific, diagnosable pattern — and once you see it clearly, it is fixable.
The Pattern
A repeat finding almost always indicates the same thing: the corrective action was procedural, but the cause was structural.
Procedural Corrective Actions
These actions can produce a clean look for the auditor in the year they are implemented — but do not change the underlying system.
Additional training for staff
More frequent supervisor review
New documentation templates
A revised checklist
A quarterly committee meeting
Updated written policies
Structural Causes
When the cause is structural and the fix is procedural, the finding will repeat indefinitely.
A cost allocation methodology that no longer reflects how the organization operates
A subrecipient monitoring framework that exists only as a policy, not a workflow
A chart of accounts that cannot produce the visibility the compliance environment requires
A documentation flow that depends on individual memory
A system architecture where compliance lives separately from operations
This is not the auditor's fault. It is not the staff's fault. It is the corrective action plan that was written for the wrong layer of the problem.
Why Organizations Default to Procedural Fixes
Two reasons explain why organizations consistently choose the procedural path — even when the structural cause is clear.
Procedural fixes are cheaper, faster, and more controllable
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.
Procedural fixes look responsive
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.
How to Break the Cycle
If you are looking at a finding that has appeared in two or more consecutive single audit cycles, the diagnostic is straightforward:
Stop writing procedural corrective actions. Diagnose the structural cause.
The questions that surface the structure:
1
Is the system still in place?
Is the system that produced this finding still in place — even if the procedures around it have changed?
2
Person or system?
Is the cause of this finding something a person did, or something the system made inevitable?
3
Would perfect execution still fail?
If we trained every staff member perfectly and the documentation was flawless, would this finding still occur?
4
Is the architecture defensible?
Is the underlying methodology, framework, or architecture defensible — or are we managing around it?
If the system is still in place, the finding will repeat. The corrective action has to be at the layer of the cause.
The Opportunity
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.
Targeted by Definition
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.
Findings Stop Repeating
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.
Downstream Benefits
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.
The Question to Ask
If your organization is approaching another single audit cycle, the question is not "how do we close the finding this year."
What is the structural cause we have not yet addressed — and what would it take to rebuild it?
That is the question the Strategic Assessment is built to answer.
Diagnose the Structure
Identify the underlying methodology, framework, or architecture that is producing the finding — not just the surface-level procedure that failed.
Rebuild at the Right Layer
Implement corrective action at the layer of the cause. Address the system, not just the symptom — so the finding does not return next cycle.
Capture the Downstream Value
Structural rebuilds almost always produce benefits beyond the finding itself — improved cost recovery, faster reporting, and cleaner documentation organization-wide.