Map the work that cannot pause
Start with a list of recurring duties that would stall if the coordinator disappeared for a week. Include the unglamorous items: intake triage, vendor check-ins, the weekly status note, and the approval queue that only one person knows how to clear. Group the list by the day or hour it must happen, because a daily task needs a different backup than a monthly report. This map is the foundation of the plan, and it should live where the team can edit it.
Separate the work into three buckets: must run every day, must run weekly, and can wait until the coordinator returns. The third bucket matters most, because many coverage plans fail by trying to preserve every task at full speed. Explicitly parking low-value work protects the backup from drowning in busywork. Publish the parked list so senders know which requests will wait rather than guessing.
Name a primary and a fallback for each lane
Assign coverage by workflow lane rather than by job title. One person might own vendor follow-ups, another the intake queue, and a third the weekly reporting pack. A lane owner should be able to describe the current state of that work without opening the coordinator's private notes. When a single person is named for everything, the plan collapses as soon as that person catches a cold.
Name a fallback for each lane even when the primary seems reliable. The fallback needs enough context to act on a normal day, not just a phone number for emergencies. Pair the two people for one cycle before the leave so the fallback sees the real messages and deadlines. A fallback who has never touched the work is a name on a slide, not a control.
Transfer access before the first day off
Inventory every system the coordinator touches, from the ticketing tool to the vendor portal to the shared drive. Request delegated access in advance, because some platforms take days to approve a new user. Never pass around a personal password or a shared login, since that creates an audit problem and leaves access behind after the leave ends. A short access table with owner, system, and expiry date keeps the transfer visible.
Test each permission with the backup account rather than assuming the request worked. Ask the backup to open the queue, post a test comment, and retrieve a file from the folder they will need. Check calendar delegation and the out-of-office rule at the same time, because a forwarded inbox is useless if the backup cannot see the attachments. Record the test date and the person who confirmed it so the next leave starts from a known state.
Write a standing coverage note
Keep the coverage note to one page and organize it around decisions rather than history. Include the current priorities, the recurring calendar, the names of the people who can unblock each lane, and the three situations that require an escalation. Link to the live tracker instead of pasting a status that will be stale by tomorrow. The note should answer the question a backup asks at 9 a.m. on day one.
Distinguish stable facts from live status, because mixing them makes the note age badly. Stable facts include vendor contacts, approval thresholds, and the location of the source files. Live status belongs in the tracker, where it can change without anyone editing the note. Add a short section on known quirks, such as a report that must be exported before a certain hour or a client who prefers a phone call.
Set decision limits for the backup
Write down what the backup may approve without asking anyone. Common limits cover spending up to a set amount, routine vendor rescheduling, and moving a deadline within an agreed window. Everything above the limit should have a named escalation contact and a response expectation. Clear limits let the backup act quickly instead of holding a queue while waiting for permission.
Decide how reachable the coordinator will actually be during the leave. A plan that assumes full availability is not a vacation plan, and a plan that assumes zero contact can strand the backup on a real decision. Set one daily window for urgent questions and route everything else to the escalation contact. Tell the team which channel to use and what counts as urgent, then hold that boundary.
Brief the teams who send work
Send a short notice to every team that sends requests, not just to the coordinator's direct colleagues. State the leave dates, the named receiver for each lane, the changed cutoff for new work, and the list of items that will wait. Put the same information in the intake form and the auto-reply so people encounter it at the moment they act. A notice sent once in a meeting will be forgotten by the next morning.
Update group aliases and routing rules before the first day off. A request sent to a dormant alias looks handled to the sender and invisible to the backup. Test one live request through each updated route and confirm that it reaches the named person. If a sender bypasses the route, the backup should know how to redirect the request without hunting for the owner.
Run a two-day dry run
Ask the backup to handle live work for two days while the coordinator observes from a distance. The coordinator should not rescue every task, because the point is to expose gaps in the note and the access setup. Record the questions the backup had to ask and the places where the note was wrong. Fix those gaps before the actual leave rather than discovering them on a beach.
Use the dry run to check volume as well as knowledge. If the backup cannot finish the daily queue in the available hours, the plan needs fewer active lanes or more temporary help. Compare the expected request volume with the hours the backup has reserved for coverage. Adjust the scope now, while there is still time to negotiate with the sending teams.
Review the plan after return
Hold a short debrief within two days of returning, while the details are still fresh. Ask the backup what took longer than expected, which request arrived through the wrong channel, and which decision limit caused a delay. Update the coverage note and the access table with the answers. Thank the backup in the same conversation, because coverage is extra work even when it is planned.
Treat the plan as a living document and test it again each quarter. Role changes, new vendors, and tool migrations all invalidate parts of the map. A plan that is reviewed only before a holiday will drift for the rest of the year. The shift handoff checklist offers a compact way to keep the daily transfer sharp between full coverage reviews.
Sources
- U.S. Small Business Administration, Prepare for emergencies, reviewed November 20, 2026.
- National Institute of Standards and Technology, Contingency Planning Guide for Federal Information Systems (SP 800-34 Rev. 1), reviewed November 20, 2026.
- U.S. Department of Labor, Family and Medical Leave Act employer guide, reviewed November 20, 2026.
- U.S. Government Accountability Office, Standards for Internal Control in the Federal Government, reviewed November 20, 2026.
