What continuity planning can protect when the primary assistant is unavailable

Abstract

An executive office can lose its primary assistant to illness, leave, or turnover with little warning. This article applies public continuity guidance to executive support work, identifies the tasks that cannot wait, and sets a coverage test that can be run before a real absence. It explains what a plan can protect and where it depends on authority decisions outside the desk. The emphasis is on a small plan that has been practiced rather than a large document [1][2][3].

Methodology

The review uses federal contingency planning guidance and small-business emergency guidance as public sources. It maps continuity principles to support tasks and treats a short planned absence as the test. The method does not claim to cover every emergency and separates operational continuity from succession or legal authority. It also distinguishes a temporary coverage plan from a permanent change in role design [1][2][4].

The coverage question before the absence

Most executive offices assume the primary assistant will be available. The assumption holds until a sudden illness, a family emergency, or a resignation makes it false. At that point the desk has to reconstruct the calendar, the inbox, and the relationships under time pressure. A continuity plan answers the coverage question before it becomes urgent [1][2].

The plan should start with the work that cannot pause, not with a full job description. A payroll approval, a board deadline, and a security contact are different from a routine filing task. Ranking the work by consequence gives the office a realistic view of what a backup must cover. It also shows what can wait for the primary assistant to return [2][3].

The plan should also cover the executive's own expectations. A principal who is used to a same-day response may need a temporary standard during an absence. Agree on that standard in advance so the backup is not judged against an impossible baseline. A short written note to the principal prevents misunderstandings later.

Map the work that cannot wait

List the recurring tasks with a fixed deadline and an external dependency. Include board papers, regulatory filings, payroll inputs, executive travel, and any approval that blocks another team. For each task, record the deadline, the system, the approver, and the evidence of completion. The list should be short enough to use during a crisis [1][2].

Separate tasks that require judgement from tasks that require access. A backup may be able to submit a form but not decide how to answer a sensitive request. That distinction determines whether the plan needs a delegate, an escalation, or a delay. Do not assume that technical access equals authority [2][3].

Include the relationships that need a personal message. A board chair, a key client, or a regulator may expect to hear about a change in coverage. Draft a short note that the executive can send or approve. Relationship continuity is part of the plan, not a public relations afterthought.

The map should also identify the work that can be paused without harm. A filing that is due next month, a routine report, and a non-urgent request can wait for the primary assistant's return. Naming the pausable work protects the backup from trying to do everything. It also gives the executive a realistic view of what the desk will and will not cover.

Name a primary and a backup for each function

Assign a named backup for each critical function, not a generic team. The backup should know where the work lives, what good looks like, and who to ask. Record the assignment in a place the whole office can see. A plan that names nobody is a hope rather than a control [1][3].

Give the backup a chance to practice the task while the primary assistant is still available. A short walkthrough is better than a document read for the first time during an absence. Update the assignment when roles change. The backup list should be reviewed at the same time as the access list [2][4].

The backup should know which tasks they must not attempt. A sensitive personnel matter or a legal filing may need to wait for the primary assistant or move to a qualified owner. Write those boundaries down and give the backup a route to ask. A clear limit is safer than an optimistic attempt.

Keep the access and authority plan current

Access is the most common failure point in a coverage plan. A backup may have the knowledge but not the system permission, the signing authority, or the mailbox delegation. Review access quarterly and after any role change. Remove access promptly when it is no longer needed [1][3].

Authority needs the same review. A delegate may be able to send an email but not approve an expense or sign a document. Record the limits in plain language and confirm them with the accountable executive. If a limit cannot be delegated, name the escalation route. The plan should not force a backup to guess [2][4].

Keep the access review tied to a calendar event so it is not forgotten. A quarterly check before the next board cycle is easier to remember than an abstract annual review. Record who reviewed the access and what changed. The record is evidence that the control is alive.

Test the plan with a short absence

Run a short planned absence, such as a day or half a day, and let the backup handle the critical tasks. Observe where the plan breaks and note the questions the backup had to ask. A test reveals missing access, unclear instructions, and relationships that depend on one person. It is more useful than a tabletop discussion [1][2].

Debrief the test while it is fresh and make one or two changes. Do not rewrite the entire plan after a single test. Repeat the test when a new backup is assigned or a critical system changes. The goal is a plan that has been used, not a document that looks complete [3][4].

Choose a test period that includes at least one recurring deadline. A quiet day may not exercise the parts of the plan that matter. If a real deadline is too risky to test, simulate the preparation steps with a mock input. The point is to practice the handoff, not to create a crisis.

Invite the backup to write down the questions they had during the test. Those questions are the raw material for the next version of the plan. Do not rely on a verbal debrief that disappears after the meeting. A short written list is easier to act on and easier to compare with the next test.

Review after every real absence

After a real absence, ask what worked and what caused avoidable stress. Record the answers next to the relevant function and update the backup assignment or the instructions. If the same gap appears twice, treat it as a design problem rather than a performance issue. The review should be short and blame-free [2][3].

Share the lessons with the executive and the people who depend on the desk. A small change to a deadline or a delegation can remove a recurring failure. Keep the continuity plan with the other office procedures and review it at least annually. The plan is part of normal operations, not a document for the shelf [1][4].

Keep the continuity plan short enough to read during an absence. A one-page summary with links to detailed procedures is more useful than a long manual. Put the summary at the top and the detail below it. The person covering the desk should not have to read the whole document to find the first step.

The plan should name the date it was last tested and the person who owns the next review. A plan without a review date tends to describe an office that no longer exists. Put the review on the same calendar as the access check so the two controls stay together. A short dated note is enough to show the plan is maintained.

Key findings

  • Start continuity with the work that cannot pause, ranked by consequence rather than by task volume [1][2].
  • Separate judgement tasks from access tasks when deciding what a backup can cover [2][3].
  • Name a specific backup for each critical function and let them practice the task [1][3].
  • Review access and delegated authority quarterly and after every role change [1][4].
  • Test the plan with a short planned absence and change one or two things afterward [2][4].

Sources

  1. Contingency Planning Guide for Federal Information Systems (SP 800-34 Rev. 1), National Institute of Standards and Technology
  2. Ready Business, U.S. Federal Emergency Management Agency
  3. Prepare for Emergencies, U.S. Small Business Administration
  4. NIST Cybersecurity Framework, National Institute of Standards and Technology

Return to the Research Content library