Essential work usually runs through one person, quietly, until that person is unavailable. The Continuity Audit finds those rows on purpose, before a bad Tuesday does, by naming the functions an organization depends on and who each one actually depends on.
Why continuity gaps stay invisible until they break
Most organizations only discover a single point of failure the week it fails. Someone is out, and a function everyone assumed was covered simply stops. Nobody planned for it because nobody wrote it down while things were still working.
Through Impactedia, I have watched this play out the same way more than once. A founder or a director carries three or four functions nobody else touches, and the organization treats that as normal until an absence, planned or not, exposes the gap. The fix is not more hours from that person. It is naming the dependency while there is still time to build an escape route.
Who this is for, and how long it takes
About 20 minutes. For a founder, director, or team lead who suspects too much runs through too few people, and wants a clear list instead of a vague worry.
What’s inside
- A five-row audit table: essential function, who it stops without, and the escape route.
- The Tuesday absence test, a single question that surfaces the row you have been avoiding.
- A quarterly fix field, so the audit turns into action instead of a list you file away.
How to get the most out of it
List real functions from your organization, not hypothetical ones. Include this system’s own functions, the audit itself included, since the person who runs it is also a dependency. Fill one empty escape route per quarter, starting with the worst row, the one with no plan at all.
What changes if you actually do this
The output is a five-row map of where the organization actually depends on individuals. The outcome is a queue of fixes, worked one per quarter instead of all at once. The impact is fewer weeks where one absence quietly stops something essential.
Download The Continuity Audit
Next step: The Four-Pillar Recall pulls this alongside your Intention, Mastery, and Impact pieces into one page.
FAQ
What counts as an essential function?
Anything that would visibly stop or degrade if the person behind it were out for a month. That includes obvious roles like finance or delivery, and quieter ones like the one person who knows how a key partner likes to be communicated with.
What if every row has no escape route?
That is common, and it is the finding, not a failure of the exercise. Start with the single worst row this quarter. An escape route built for one function is still real progress.
Is this only for organizations with staff?
No. Solo founders and small teams depend on individuals just as much, often more. The audit works the same way, it just may include external partners or contractors alongside internal roles.
