The Owner Absence Readiness SOP

Purpose

To hold the shop in a standing state where the owner's absence, planned or sudden, does not stop work, stop payroll, or stop money coming in. A planned week off can be prepared for over six weeks. A broken ankle, a family emergency, or a hospital stay gives you no notice at all, and the difference between a shop that absorbs that and one that seizes up is whether four things were maintained before it happened: a packet, an authority matrix, an access register, and a standing-answer file. This SOP maintains those four and tests them once a quarter.

This is the readiness state, not the trip. Preparing a specific planned absence is a separate procedure that runs off this baseline.

Scope

Applies to any shop where the owner holds authority, access, or knowledge that the business needs within a single working week. Covers absences of one working day or more.

Excluded: the specific countdown for a planned vacation, which builds on this baseline rather than replacing it. Also excluded: succession and permanent transfer of ownership, which is a different body of work with legal and tax dimensions this SOP does not touch.

Roles and responsibilities

Where a shop has fewer people than roles, one person may hold two lanes, but the access register verification must be performed by someone who is not the owner. A register only the owner has ever opened has not been tested.

Procedure

1. Maintain the absence packet

One document, reviewed quarterly, holding:

• The lane map: which lanes exist and who covers each one during an absence.
• The tiebreaker: who decides when lanes disagree or something falls between them.
• The money calendar for the next 90 days: payroll dates, tax deposit dates, insurance and licence renewals, supplier terms, and the invoice batch dates that keep collections moving.
• The emergency definition: what genuinely warrants contacting an absent owner. Written before it is needed, because a definition negotiated in the moment is not a definition.
• The customer notice template and the vendor notice template.

Because federal employment tax deposits fall due on the schedule the IRS assigned your business, monthly or semiweekly based on your lookback-period liability, any absence spanning a deposit date requires a named person with the standing authority to make that deposit, recorded in the packet and not arranged after the fact.

2. Maintain the authority matrix

For each recurring decision that would otherwise wait for the owner, record: who decides, up to what boundary, and what the boundary is measured against.

Every boundary is a number or a band measured against something observable, not a judgment word. "Approve reasonable additions" is not a boundary. "Approve added work up to a stated multiple of the original quote" is. Wherever a historical baseline exists, set the boundary against it: a payroll run within a stated percentage of the trailing four-run average, a purchase within the shop's normal weekly spend for that category.

Review the matrix quarterly against the escalation log from the test in step 5. Any decision that escalated twice in one quarter and was approved both times without change belongs inside a boundary, not outside one.

3. Maintain the access register

A list of what the shop needs to get into, who can get into it, and how, covering at minimum: banking, payroll system, insurance portal, supplier accounts, the scheduling and job system, the building, the vehicles, and the phone and email accounts customers use.

Credentials do not live in this document. The register records where each credential lives and who is authorized to retrieve it. Use a password manager with a named emergency-access delegate rather than a shared list, because a shared plaintext list of every account the shop owns is a larger risk than the absence it protects against.

4. Maintain the standing-answer file

The questions that reach the owner, with their answers written down. Sourced from two places: the escalation log from each quarterly test, and the interruption tally from the owner's weekly review if one is running.

Add one standing answer per quarter, from the largest class in the log. Not all of them. A file that grows by one useful page a quarter gets read; a file that grows by ten pages in one sitting does not.

5. Run the quarterly readiness test

Two consecutive working days, once a quarter, where the owner is unreachable except under the packet's written emergency definition. Covering people log every escalation with its lane and how it resolved, including the ones they handled themselves.

Two consecutive days is the minimum unit. A single day gives you one day's traffic, and one unusually busy or unusually quiet day will misread the shop in either direction.

6. Score the quarter

Readiness is green only when both gates pass:

• The test rate is at or below 1.5 escalations per working day (unit: per working day, over the two-day test), AND
• The access register has been retrieved and verified by someone other than the owner within the last 2 quarters.

Both, not either. The Boolean matters because the two gates fail differently: a high escalation rate makes a planned absence uncomfortable, while a stale access register makes a sudden absence a stoppage.

Anything else is amber or red. Amber is one gate failing. Red is both failing, or any test where an escalation could not be resolved at all within the two days.

7. Remediate exactly one gap per quarter

One. The gap you pick is the one whose failure mode is worse under a sudden absence rather than the one that is most annoying under a planned one.

Record the chosen gap, the fix, and the date, in the packet. A remediation that is not written down is re-discovered next quarter as a new finding.

8. Sudden-absence activation

When an absence starts without notice, the person who learns first notifies the covering lead and the outside bookkeeper or advisor. The covering lead opens the packet, sends the customer and vendor notices from the templates, and checks the money calendar for anything falling due inside the expected absence window. The authority matrix is in force from that moment without further approval, which is the entire reason it is written in advance.

If the absence is expected to exceed two weeks, the covering lead escalates to the outside advisor to review anything requiring the owner's signature, since those items are the ones that cannot be resolved internally under any matrix.

A worked quarter

Q2 test. Two working days, 5 escalations logged: 2 pricing, 1 supplier credit, 1 scheduling conflict between lanes, 1 payroll question. That is 2.5 escalations per working day. Against the gate of 1.5, it fails. The access register was last verified three quarters ago, which is more than 2, so that gate fails too. Both gates fail, so the quarter scores red.

The remediation choice. Two candidates and only one gets fixed this quarter.

Fixing the escalation rate means writing a pricing authority boundary, which addresses 2 of the 5 escalations, about 40% of the test's traffic.

Fixing the register means having the outside bookkeeper actually retrieve and verify access to banking, payroll, and the supplier accounts.

The register wins, and the reasoning is what makes this rule useful rather than arbitrary. An escalation rate of 2.5 per working day means a planned week off is uncomfortable and a sudden absence produces a queue of decisions that wait. A stale access register means that during a sudden absence nobody can run payroll or make a tax deposit, and a shop that misses payroll has a personnel crisis on top of whatever caused the absence. The worse failure under the worse scenario gets the quarter.

The verification finds something. The bookkeeper retrieves banking access without trouble and finds that the payroll system access recorded for the office coordinator had lapsed when the provider forced a re-enrolment eight months earlier. Nobody noticed because the owner had been running payroll himself the whole time. That is the exact shape of failure the register exists to catch, and it would not have surfaced in an escalation log, because it was never escalated. It was never even encountered.

Q3 test. Register verified within the quarter, so that gate passes. Two working days, 3 escalations, which is 1.5 per working day. The gate is at or below 1.5, so 1.5 passes. Both gates pass, so the quarter scores green.

Q3 remediation. Green does not mean nothing gets fixed. The rule is one gap per quarter regardless of score, and the Q3 log's largest class was pricing again, so pricing gets its authority boundary this cycle and its standing answer added to the file.

Reading the trend rather than the quarter

A single quarter's number is noisy. Four quarters of the same measurement is a trend, and the trend carries more information than any single reading.

Watch two things. First, whether the escalation rate falls across quarters. Second, and more useful, whether the composition changes. A log that drops from 5 escalations to 3 but is still dominated by the same class means the boundary you wrote described a process instead of granting an authority. A log that drops to 3 unrelated one-offs is a shop where coverage genuinely works and the residue is the irreducible part.

The failure this SOP is most likely to hit is not a failed test. It is a quarter that gets skipped because nothing was wrong, then two, and then a sudden absence lands against a packet that is fourteen months old, a covering lead who left in the interim, and a supplier account nobody can open. Readiness is a maintained state. It expires quietly and it expires on exactly the timeline you stop testing it.

References

• See related: How to Take a Week Off Without the Shop Stopping
• See related: Planning for the Unexpected: Continuity
• See related: The Tasks Only the Owner Can Actually Do
• IRS Publication 15 (Circular E), Employer's Tax Guide, for federal employment tax deposit schedules
• SBA guidance on business continuity planning for small businesses