Most business continuity plans are written for companies with an IT department, a spare office, and a committee that meets quarterly. A solo founder needs something smaller and sharper: one sitting, a pen, and an honest answer to a single question — what actually happens to the business if you disappear for two weeks?
A business continuity plan is the written record of how your business keeps operating when you can't operate it. For most founders that record does not exist. It lives in your head, which makes your head the single point of failure behind every client, every invoice, and every promise you have made.
What follows is a ninety-minute tabletop exercise to fix that. Three functions, fifteen minutes each, one number at the end.
Key takeaways
- A solo business continuity plan is not a binder of emergency contacts; it is the written record of the decisions, tasks, and context your business needs in order to run without you.
- The two-week tabletop exercise tests three critical functions — usually client delivery, invoicing, and customer support — and finds the gaps before a real absence does.
- Every gap has a price: late deliverables, invoices that quietly stop going out, clients who don't renew, and emergency help hired at rush rates.
- Closing gaps is a sequence, not a sprint: document first, then delegate, then automate, and eliminate whatever should not exist at all.
Why continuity looks different when you are the only one
In a larger company, continuity is about redundancy — another server, another office, another person who knows the process. In a one-person business, the redundancy is you, and there is not any.
So the exercise cannot be about backup systems. It has to be about transferred judgment: what would someone else need to know in order to make the calls you currently make without thinking? "Could someone log in?" is the easy question. "Could someone decide?" is the real one.
How to run a business continuity plan tabletop exercise
Block ninety minutes. Open one document. Set a timer for each function and do not skip ahead.
Step 1: Name your three critical functions
Pick the three areas that, if they stalled for two weeks, would cost you money or a client. Client delivery, invoicing, and customer support are the common three. Yours might be the sales pipeline, fulfillment, or a recurring service commitment. Write them at the top of the page in plain language.
Step 2: Run the "I'm out for two weeks" simulation
Fifteen minutes per function, and start each one with the prompt written as though it has already happened: "I am unavailable for fourteen days starting tomorrow. What breaks first?"
Then walk it day by day — day one, day three, day seven, day fourteen. You are not solving anything during the timer; you are observing. Where does the first thing fall over? What does a client email on day four that nobody can answer?
Step 3: Capture three lists per function
For each function, write three short columns.
Decisions. The judgment calls only you make — approving a refund, changing a scope, discounting a renewal.
Tasks. The physical actions — sending the invoice, running the report, shipping the deliverable.
Knowledge. The context nobody else holds — where the files live, what the client actually cares about, which supplier is reliable.
Be specific. "Follow up on the Henderson account" is not a task. "Send the revised scope by Thursday and confirm the delivery date" is.
Step 4: Price the gaps
Now convert the list into money. For each gap, ask one question: if this gap held for a year, what would it cost? Use your own numbers — your rates, your contracts, your margins — because the point is not precision, it is honesty.
Group what you find into categories: deliverables that arrive late, revenue that never gets invoiced, clients who quietly do not renew, rush-rate help you hire in a panic, and the hours you spend rebuilding what a document would have preserved. Add them up.
If you want to see how that continuity number sits against the rest of your operational drag — urgent problems, missed revenue, tools you pay for and never use — put your figures into the free calculator at https://tools.exiuss.com/radar. It takes six inputs and returns a breakdown by category, so you can see how much of your annual cost of chaos is pure continuity exposure.
| Situation | What to do | Why |
|---|---|---|
| You can name the function but not the steps | Write the task list exactly as you would do it this week | Undocumented tasks are the first thing to stall |
| Only you can make the call | Write the decision rule, not the decision | A rule transfers judgment; an answer transfers nothing |
| Client work depends on context in your head | Record account history and current state | Context is the expensive thing to rebuild |
| Invoicing stops when you stop | Set a recurring trigger and name a backup | Revenue gaps compound quietly |
| A gap would cost real money | Price it, then assign it to one of four actions | Unpriced gaps never get fixed |
Step 5: Build the 30-day plan
Sort every gap into one of four actions, in this order:
- Document — write it down if it is knowledge or a repeatable task.
- Delegate — hand it to a contractor or part-time help if it does not need your judgment.
- Automate — put a trigger on it if it is recurring and rule-based.
- Eliminate — delete it if it produces nothing but habit.
Most founders jump straight to automate because it feels like progress. Document comes first because you cannot automate a process that has never been written down, and you cannot delegate a decision you have not defined.
Then assign roughly one gap per week for the next thirty days. That is your plan — not a project, a month.
The mistake almost everyone makes
The most common failure is turning the exercise into a documentation project. The output is not a beautiful library of standard operating procedures that nobody reads. The output is a short list of the two or three gaps that would actually hurt, each with an owner, an action, and a date.
The second mistake is guessing. The simulation only works if the inputs are real — if you write down the thing you would actually fumble, not the version that makes you look organised.
Put a number on it
Continuity exposure is the part of your chaos tax you can finally see clearly, because you just priced it yourself. If you want the full picture, the free diagnostic at https://tools.exiuss.com/radar takes six inputs and returns a breakdown by category in about five minutes. The full diagnosis is a one-time $7 — a chaos archetype, a sovereignty maturity level from Survivor to Sovereign, an executive analysis, and a prioritized 30-day recovery plan tagged Systemize, Delegate, Automate, or Eliminate. There is also a free 14-day EXIUSS trial if you would rather work the plan inside the tool, where SOP and RACI drafts are built from the inputs you supply.
Start with the number. The gaps you just named are cheaper to close now than to discover during the week you cannot work.
Quick checklist
- Block ninety minutes and open one document.
- Name your three most critical functions in plain language.
- Run fifteen minutes of "I'm out for two weeks" per function and log what breaks.
- Capture the decisions, tasks, and context each function depends on.
- Price every gap using your own rates and margins, then total the categories.
- Assign one gap per week for thirty days to document, delegate, automate, or eliminate.