Why coverage fails at the handover
Covering another executive's desk looks simple until the first unexpected request arrives. The calendar shows meetings but not which ones are fragile, and the inbox shows messages but not which ones are waiting on a decision. A cover note that lists only passwords and phone numbers leaves the real work invisible. Most coverage failures start with what the note left out.
The person covering the desk also has their own principal and their own priorities. They need a short, prioritized view of what must happen and what can wait. A good handover note reduces the number of questions they have to ask during a busy day. It also protects the absent executive from returning to a pile of avoidable problems.
Start with the calendar and mailbox map
List the meetings that cannot be moved or missed during the cover period. For each one, note the owner, the preparation required, and whether the executive's attendance is essential. Mark the meetings where a delegate can attend and the meetings where a written update will do. The calendar map tells the cover desk where to spend attention.
For the mailbox, describe the folders and rules that matter rather than listing every label. Note which senders expect a same-day reply and which messages can wait for the executive's return. Identify the messages that are already in progress and need a nudge. The mailbox map should point to the decisions, not replicate the inbox.
Record open decisions and their owners
Write down every decision that is waiting on the executive, the person who asked, and the date it is needed. Include the options and any recommendation the desk has already prepared. That context lets the cover desk answer a follow-up or escalate with confidence. An open decision without an owner will drift during the absence.
Separate decisions that can wait from decisions that cannot. If a decision must be made during the cover period, record who has authority to make it and how to reach them. Do not leave the cover desk to infer authority from an email chain. A short authority note prevents both delay and overreach.
Include the questions the executive is likely to ask on return. A decision that was progressed may still need a verbal update, and a sensitive message may need a personal reply. Note those items separately from the operational handover. The cover desk can then prepare the right context instead of forwarding everything.
List recurring commitments and their dates
List the reports, briefings, payments, and meetings that recur during the cover period. Include the date, the format, the recipient, and the location of the template. Mark the ones that need input from another team so the cover desk can chase it early. Recurring commitments are easy to forget because they do not generate a new request.
For each commitment, note what good looks like and what to do if the input is late. A weekly report with a fixed template is easier to cover than a report that depends on a conversation. If the cover desk cannot produce the usual quality, agree in advance on a reduced version. A clear fallback is better than a late surprise.
Name the escalation path
Write down who the cover desk should call for each kind of problem. Include the executive's chief of staff, the finance lead, the IT contact, and any family or security contact that is relevant to the role. Put the order of escalation next to each name. A list of names without an order is not an escalation path.
Explain what counts as urgent enough to interrupt the absent executive. Give examples, such as a legal deadline, a security incident, or a board matter that cannot wait. For everything else, name the person who can decide. The cover desk should not have to judge urgency from scratch on every call.
Write a return handover before the cover ends
Before the executive returns, write a short note describing what happened, what was decided, and what still needs attention. Include the messages that were held, the commitments that were completed, and any change to the calendar. A return note lets the executive resume without reading every thread. It also gives the cover desk a clean finish.
Keep the return note factual and brief. Separate decisions that were made under delegated authority from items that were merely progressed. Flag anything that needs the executive's confirmation in the first days back. The note should reduce the return workload, not add another document to review.
Ask the cover desk for feedback before they leave. They will know which part of the note was unclear and which request took the most time. Add that feedback to the template for the next absence. A handover note improves through use, not through longer drafting.
Keep the note short enough to use
A cover note that runs to twenty pages will not be read during a busy week. Aim for a few pages with clear headings and the most important items first. Put reference material in an appendix rather than in the main note. The cover desk should be able to find the answer to a question in under a minute.
Store the note where the cover desk already works, such as a shared folder linked from the calendar. Update it before each absence rather than treating it as a one-time document. Delete details that no longer apply. For more coverage guidance, see our article on standardizing support across multiple executives.
Key takeaways
- Map the fragile meetings and the mailbox decisions, not just the files and passwords.
- Record every open decision with its requester, deadline, options, and authority.
- List recurring commitments with templates, recipients, and a fallback if input is late.
- Write an ordered escalation path with examples of what counts as urgent.
- Finish with a short factual return note and keep the cover note to a few pages.