Absence Audit™
An Absence Audit reveals what stalls, breaks, or becomes invisible when a key person is unavailable — so you can see owner dependency before it becomes a crisis.
In owner-led organizations, critical knowledge, approvals, and workarounds often live in one person's head. The operation looks fine until that person is sick, traveling, or overloaded — then the hidden dependencies surface all at once.
Authored by David Runnels, Stories & Systems. Published October 3, 2026.
When this framework earns its keep.
Owners, operators, and leadership teams who suspect the business leans too hard on one person and want a concrete way to find where.
Use it when
- You cannot take a real week off without Slack lighting up
- Approvals, exceptions, or tribal knowledge route through one person
- A key hire or founder transition is approaching
- Growth is increasing chaos faster than headcount can absorb it
Skip it when
- You need a full software selection project (start with systems mapping instead)
- The issue is primarily market demand or pricing, not operational dependence
- You already have clear coverage plans and are optimizing for speed, not resilience
How to run it.
- 01
Name the person and the window
Pick the key person (often the owner) and a realistic absence window — a week, two weeks, or a month. The audit is only useful if the scenario is specific.
- 02
List what only they can do
Capture decisions, exceptions, client relationships, system access, and undocumented processes that currently require them. Separate preference from true necessity.
- 03
Trace the break points
For each item, ask what happens on day one, day three, and day ten of absence. Note where work queues, quality drops, or customers feel the gap.
- 04
Score dependence
Rank items by frequency, consequence, and how hard they are to cover. High-frequency, high-consequence, hard-to-cover items are your first redesign targets.
- 05
Design coverage
For the top items, choose the lightest durable fix: a checklist, a delegated decision rule, a shared inbox, an automation, or a documented exception path.
Illustrative example: the owner who approves every exception
Imagine a service business where quotes stall whenever the owner travels because discount exceptions require a verbal yes. An Absence Audit would rank that path as high-frequency and high-consequence. The first fix might not be a new CRM, but a written exception matrix, a dollar threshold for manager approval, and a same-day log the owner can review later.
Want help applying this inside your operation?
Start with the five-minute Friction Assessment, or talk through where the framework fits.
Start the Assessment