A business continuity plan is a written record of what happens when a person, a tool, or a process your business depends on stops working: who steps in, what happens first, and what can wait. Most founders file it under someday. That filing decision has a price, and it shows up every week as hours lost to repetitive firefighting, urgent problems that arrive on schedule, revenue that quietly slips, and software you pay for and never open.
This article gives you a way to put a number on that price. Call it the continuity gap: the share of your existing operational cost that exists purely because nothing is written down, and would disappear if it were.
Key takeaways
- The continuity gap is the portion of your current chaos cost that a proper business continuity plan would remove, calculated by assigning a percentage to each of your cost inputs and multiplying.
- You do not need a complete plan to start. You need the three inputs carrying the most continuity-related cost, and one fix for each.
- Most fixes are one of three moves — document it, delegate it, or automate it — plus a fourth founders forget: eliminate it.
- The calculation is only as honest as your inputs, so estimate from last month rather than from what you wish were true.
What a business continuity plan actually protects
Continuity planning gets framed as disaster prep: the server dies, the office floods, the key person quits. Those are real, but they are rare. For most small businesses the expensive failures are small and constant. Only one person knows how to onboard a new client. The invoice run lives in someone's memory. A vendor log-in exists in a browser and nowhere else. A project stalls because the decision-maker is in back-to-back calls and one answer sits unsent for three days.
None of that is dramatic. All of it is recurring. A business continuity plan addresses the recurring version of failure, not just the catastrophic one, which is why it belongs in this month's work rather than in some distant quarter.
The business continuity plan gap calculator: six inputs, one number
Start with the same inputs a bottleneck cost diagnostic uses, then ask one question of each: if I had a proper business continuity plan, what percentage of this cost would disappear?
- Weekly chaos hours — hours spent on work that repeats because it is not written down.
- Your internal hourly value — what an hour of your time is worth inside the business.
- Urgent problems — the annual cost of the things that interrupt the week on a schedule.
- Missed revenue — deals and follow-ups lost to slow or forgotten response.
- Decision fatigue — the hours consumed by choices that should have a default.
- Wasted tools — software bought, paid for, and never adopted.
The percentage is the whole method. You are not guessing a new number; you are deciding how much of a cost you already carry is structural. Be strict. If a cost would survive a week of good documentation, it is not continuity-related.
EXIUSS RADAR runs this calculation for free at https://tools.exiuss.com/radar — six inputs, one annual figure, broken out by category so you can see which line is largest before you decide anything.
The worksheet: mapping each input to a continuity fix
| Input | Continuity question | Fix type | | Weekly chaos hours | Would this task still exist if the process were written down? | Document | | Urgent problems | Which of these arrived because a decision had no owner? | Delegate | | Missed revenue | What did we fail to respond to fast enough? | Automate | | Decision fatigue | How many choices reach me only because there is no default? | Document | | Wasted tools | Why was this bought and never adopted? | Eliminate |
Print that table, fill in your own numbers, and the largest continuity cost announces itself. It usually is not the one you expected.
Worked example: a three-person agency
This is an illustration, not a benchmark. Say a three-person agency owner runs the numbers. She values her internal hours at $60. Her inputs come back like this:
- Weekly chaos hours: 10, or about $30,000 a year
- Urgent problems: about $6,000 a year
- Missed revenue: about $10,000 a year
- Wasted tools: about $2,000 a year
- Decision fatigue: 2 hours a week, about $7,000 a year
Total: roughly $55,000 a year of chaos tax.
Now the percentage question. She decides that 60% of the chaos hours would vanish with written processes. She traces 75% of urgent problems back to decisions with no owner. She judges 60% of missed revenue came from slow response and 75% of tool spend was avoidable. She puts decision fatigue at 45%, because some of it is hers regardless.
Multiply and add: $18,000 + $4,500 + $6,000 + $1,500 + $3,150 lands near $33,000. About 60% of her chaos tax. That reframes the whole situation. The agency does not have a discipline problem or a hustle problem. It has a continuity problem, and the three largest line items are exactly where the next thirty days go.
The common mistake
Founders treat continuity planning as a document to be written, so they sit down to write the whole thing. Two hours in it is a half-finished template nobody opens again.
The fix is order. Calculate the gap first, rank the inputs, then write only the part of the plan that addresses the top three. A business continuity plan covering your three most expensive failure modes beats a comprehensive document that covers none of them in practice.
The 30-day plan to close the gap
Week 1 — Document. Take the largest input and write one process as steps someone else could follow. Not a policy. A procedure.
Week 2 — Delegate. Hand that documented process to a person or a contractor and watch it run once end to end.
Week 3 — Automate. Put a trigger on the third input: a form, a template, a scheduled reminder, a saved reply. The goal is that the step happens without you remembering it.
Week 4 — Recalculate. Rerun the same inputs and the same percentages. The number should move. If it does not, you produced documentation theatre rather than continuity.
Eliminate as you go. Any tool or recurring task that produced no continuity value gets cancelled rather than documented.
Quick checklist
- List your six inputs using last month's real numbers
- Assign a continuity percentage to each and multiply
- Rank the inputs by the size of the continuity-related cost
- Write one procedure for the largest input, as steps, not policy
- Delegate or automate the second and third, then eliminate what earns nothing
- Rerun the calculation at day 30 and compare
The Chaos Tax stops when the plan starts. Run your own numbers free at https://tools.exiuss.com/radar, then decide whether the $7 full diagnosis is worth it — it returns a chaos archetype, a sovereignty maturity level, and a 30-day recovery plan tagged Systemize, Delegate, Automate, or Eliminate, with SOP and RACI tools drafted from the inputs you already entered.
