The day an assistant calls in sick is the wrong day to discover that nobody else can open the board folder. Work that seemed routine becomes urgent when the person who owns it is unavailable. A coverage card captures the handful of tasks, contacts, and access paths that a backup needs in the first two hours. It is short by design because nobody reads a manual during a scramble.
Operations
Create a coverage card for the day an assistant calls in sick
A one-page coverage card that tells a backup exactly what cannot wait, who can approve access, and how to reach the executive.
Table of contents
Why absence plans fail at the last minute
Most absence plans are written for planned leave, not for a sudden sick day. A planned vacation allows a handover meeting, a checklist, and a week of reminders. A sick day starts with a message at seven in the morning and no time to prepare. The plan has to work without the absent person's participation.
The second failure is access. A backup may know what to do but cannot log in to the calendar, the board portal, or the finance system. Permissions often sit with one person because that was simpler at setup. The coverage card should name the access path and the person who can grant it before the absence happens.
List the work that cannot wait a day
Start with the commitments that have a hard deadline in the next 24 hours. A board packet due at noon, a flight change, a payroll approval, or a client signature may not survive a day of silence. List each one with the time, the owner, and the minimum action the backup must take. Do not list every recurring task; the card is for urgency, not completeness.
For each item, say what happens if it waits. That consequence helps the backup decide whether to act or escalate. A meeting that can be moved is different from a filing that has a legal deadline. The card should make the difference obvious without requiring a long explanation.
Name a deputy for each access path
Every critical system needs a named deputy who can act when the primary is unavailable. That includes the calendar, the inbox, the board portal, the travel booking tool, and the expense system. Record the deputy, the access method, and the person who can restore access if it fails. A deputy without credentials is only a name on a slide.
Test the access before an absence, not during one. A quarterly login check catches expired credentials and changed policies. The deputy should also know where the coverage card lives and how to reach the executive. If the card is stored only in the absent assistant's drive, it is not a coverage plan.
Write the first two hours as a script
The first two hours should be a short sequence: check the executive's calendar for the day, scan the urgent inbox folder, confirm the hard deadlines, and send a status note to the executive. Then contact the named deputies for any blocked item. The script gives a backup a starting point without requiring them to understand the whole role.
Include the exact folders, labels, and links the backup should open. Avoid instructions such as "check the usual places" because the backup does not have the usual places. A screen-by-screen script is more useful than a description of the job. The script should fit on one page and use plain language.
Include the contacts who need notice
Some people need to know about the absence even if no task is due. The executive, the chief of staff, the board secretary, and a key client contact may need a short note. Record who should be told, who should send the note, and what it should say. The message should be brief and should not disclose personal medical details.
Keep the notice list short. A broad announcement creates more questions than it answers. The backup should be able to send a standard note that says the desk is covered and names the temporary contact. If the absence will last more than a day, the chief of staff can decide on a wider message.
Test the card during a planned absence
Use the next planned leave as a rehearsal. Ask the backup to follow the card for one day while the primary is still reachable for questions. Note where the card is unclear, which access path fails, and which urgent item was missing. Update the card before the next real absence.
A rehearsal also tests the executive's expectations. Some leaders will escalate immediately when a familiar name is unavailable, even if the backup is competent. A short introduction before the leave helps. The goal is to make coverage normal, not to pretend the primary is irreplaceable.
Update the card when systems change
Review the card whenever a system, role, or major commitment changes. A new board portal, a different travel agency, or a reorganized leadership team can invalidate the access paths and the contact list. Put the review on the same calendar as the quarterly access check. A stale card is worse than no card because it creates false confidence.
Keep the card in a shared location that the backup and the chief of staff can reach. Version it with the same naming standard as other documents. For the travel side of coverage, see our guide to writing a pre-trip risk brief. For hands-on help with this work, review our executive support services. The U.S. Department of Labor FMLA guidance explains the leave framework that may apply when an absence extends beyond a short sick day.
Key takeaways
- List only the work with a hard deadline in the next 24 hours and state the consequence of delay.
- Name a deputy and an access method for every critical system, and test the login quarterly.
- Write the first two hours as a one-page script with exact folders, labels, and links.
- Keep a short notice list for the executive, chief of staff, board secretary, and key contacts.
- Rehearse during a planned leave and update the card whenever a system or role changes.
Frequently asked questions
What belongs on an assistant coverage card?
How do you prepare a backup for an unplanned sick day?
How often should the coverage card be updated?
Keep reading
Related executive support guides.
Build a travel disruption playbook for a multi-city week
A playbook for flight changes, hotel gaps, and meeting overruns that keeps a multi-city executive week recoverable.
Map executive inbox decisions without reading private mail
A routing map that helps an assistant sort decisions, delegations, and sensitive messages while respecting the executive's private correspondence.
Run a monthly vendor renewal watchlist without spreadsheet sprawl
A single renewal watchlist that tracks notice windows, owners, usage, and risk so vendor contracts do not surprise the executive office.