Test a bounded founder absence
Authorise deputies, test essential operations without founder rescue, and convert interruptions into owned improvements.
- Preparation
- One dependency-mapping session, a short agreed absence test, and a review.
- Difficulty
- Advanced
- Task
- Prepare for founder absence
Before you start
Get what you need before you start
- Choose a safe test window and define the essential functions that must continue.
- Identify the founder, deputies, risk owners, and emergency interruption route.
- Review every proposed access change under the organisation’s security policy.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Map essential dependencies
For each essential function, record its output, owner, acceptable interruption, founder dependency, required access, source instruction, recovery target, deputy load, and backup.
Why it matters: A general claim that the business can run hides the specific work and decisions that still stop.
- Input
- The operating calendar, active responsibilities, systems, vendor contacts, and recent founder interruptions.
- Output
- A continuity map of essential functions and founder dependencies.
Tools in this stepGoogle SheetsEvidence for this step
A named owner reports that managers continued client work during a two-week absence, while one deputy became overloaded and the team needed clearer accountability.
Financial Snickens: Transcript lines 78–87Current continuity guidance covers essential functions, delegated authority, communications, records and systems, exercises, access, alerts, and return to normal operation.
Rhode Island Emergency Management Agency: Continuity planning guidance, lines 104–132
Authorise deputies and limits
Assign each function a deputy, backup, decision limit, access, contact, escalation route, and handback rule. Check each deputy’s capacity before the test and have the relevant owner approve the authority in writing.
Why it matters: Naming a deputy does not grant system access or authority for legal, financial, security, or employment decisions.
- Input
- The continuity map, authority policies, access requests, and named deputies.
- Output
- An approved deputy matrix with access, decision limits, escalation, and handback.
Tools in this stepGoogle SheetsEvidence for this step
Current continuity guidance covers essential functions, delegated authority, communications, records and systems, exercises, access, alerts, and return to normal operation.
Rhode Island Emergency Management Agency: Continuity planning guidance, lines 104–132
Run the controlled absence test
During the agreed window, route work to deputies and record every interruption, blocked task, access failure, and out-of-scope decision. Use the emergency route only for its defined conditions.
Why it matters: A test reveals hidden dependencies only when ordinary questions do not return silently to the founder.
- Input
- The approved deputy matrix, test window, live essential work, and emergency criteria.
- Output
- A timed test record of continued work, interruptions, failures, and decisions.
Tools in this stepGoogle SheetsEvidence for this step
A named owner reports that managers continued client work during a two-week absence, while one deputy became overloaded and the team needed clearer accountability.
Financial Snickens: Transcript lines 78–87
Repair gaps and hand back
Review each interruption with the deputy and owner. Assign an improvement, repair access or instructions, confirm any live decision, and complete the return handback.
Why it matters: An absence test creates value when each failed handoff changes the operating system.
- Input
- The test record, source-system state, deputies, and relevant risk owners.
- Output
- An owned improvement list, repaired continuity record, and completed handback.
Tools in this stepGoogle SheetsEvidence for this step
Current continuity guidance covers essential functions, delegated authority, communications, records and systems, exercises, access, alerts, and return to normal operation.
Rhode Island Emergency Management Agency: Continuity planning guidance, lines 104–132
Success checks
Check the result before you finish
- Every essential function has a deputy, limit, access path, and escalation route.
- Relevant owners approved authority before the test.
- The test records every interruption and blocked dependency.
- Each failed handoff has an owner and review date.
- Essential work did not concentrate on one overloaded deputy, and the return handback is complete.
Failure modes
Watch for these problems
- The founder answers routine questions privately. Add them to the test record and route them back to the deputy.
- A deputy receives a password. Stop and provision named least-privilege access.
- The test includes a high-risk decision without qualified cover. Exclude it or schedule the proper owner.
- Work continues but no handback occurs. Reconcile live state and decisions before closing the test.
Tools
Choose the tools you need
Tool
Google Sheets
A shared spreadsheet for source-linked research, decisions, and operating records that people can inspect and correct.
Check fit, limits and pricingSources
Read the sources behind this practice
Check what each source supports and where the advice has limits.
- Financial Snickens: Small business owner vacation: how my business ran without meFirst-hand named business-owner transcript · Publication date unavailable
- Rhode Island Emergency Management Agency: Continuity planningOfficial government continuity guidance · Publication date unavailable
- FEMA Ready Business: Business Continuity PlanUS government planning template · Published 1 March 2020
- Google Workspace: Collaborative, AI-powered spreadsheetsOfficial product page · Publication date unavailable