Write a backup brief that another executive assistant can actually use

Executive support coverage often fails in one of two ways

Executive support coverage often fails in one of two ways. The backup receives a huge folder with no indication of what matters now, or the primary assistant keeps the real operating context in memory and private messages. A useful backup brief sits between those extremes. It gives an authorized colleague enough current context to protect time-sensitive commitments without transferring every detail of the role. The brief is a handoff for a defined coverage window, not a permanent biography of the executive. It should identify active responsibilities, next actions, decision boundaries, sources, timing, and escalation paths. For virtual executive assistant support, this record matters because overlap may be limited and the backup cannot rely on overhearing the day's context.

Open with the coverage contract

Open with the coverage contract. State the dates and working windows, primary and backup contacts, systems the backup may access, response expectations, and the event that returns control to the primary assistant. Name what is outside coverage. A colleague covering calendar changes may not have permission to read board correspondence or personal messages. Least privilege should survive an absence. Confirm access through the organization's approved method before the coverage window begins. Do not paste passwords, recovery codes, private contact details, or sensitive document contents into the brief. Point to controlled sources and state whom to contact when access fails.

List live commitments by responsible time, not by where

List live commitments by responsible time, not by where the message arrived. For each one, record the outcome being protected, current state, next safe action, decision owner, source link, deadline source, stakeholder waiting, and escalation condition. Use the executive's original wording when a promise could be misunderstood. Separate confirmed facts from the primary assistant's interpretation. If an item is waiting, say what will release it. "Waiting on finance for the approved figures by Tuesday noon" is useful; "pending" is not. Close stale items before handoff so the backup does not spend the first hour reconstructing work that is already finished.

Include operating rules the backup can apply without fresh

Include operating rules the backup can apply without fresh permission. Examples may cover protected calendar blocks, meeting acceptance criteria, travel change thresholds, routine acknowledgements, document routing, and follow-up reminders. Express each rule as trigger, allowed action, required source, record location, and stop condition. Temporary preferences should carry an expiry date. If the executive has not delegated a choice, the brief must not imply otherwise. The backup can prepare context and options while routing the decision through the named escalation path. Coverage pressure is not a reason to infer consent from silence.

Walk through three cases before coverage begins

Walk through three cases before coverage begins: a routine request, an incomplete request, and a sensitive or conflicting request. Ask the backup to explain what they would do and where they would record it. This rehearsal exposes missing access, ambiguous rules, and hidden knowledge more reliably than asking whether the document is clear. Correct the brief, not only the person's answer. If no backup could apply a rule without calling the primary assistant, the system still depends on availability. Some matters will appropriately require escalation, but that should be a designed boundary rather than a surprise.

End coverage with a return brief

End coverage with a return brief. The backup records actions taken, decisions made by authorized owners, changed dates, unresolved items, exceptions, and sources checked. The primary assistant reviews consequential cases and updates the standing playbook only when the responsible owner approves a lasting change. Measure continuity through missed commitments, unnecessary executive interruptions, access failures, duplicated work, late escalations, and items the returning assistant had to rediscover. Read the cases to distinguish a weak handoff from an unpredictable event. A successful backup period does not require the substitute to mimic every habit of the primary assistant. It requires safe action, honest uncertainty, contained access, and a record that allows the executive's work to continue without quietly moving judgment into the support role.

Keep the brief current through event-based updates rather

Keep the brief current through event-based updates rather than constant rewriting. A new external commitment, changed travel plan, shifted board deadline, access change, or temporary delegation should trigger a review of affected entries. Routine progress can remain in the source system. Assign one owner to confirm readiness before planned leave, and set a shorter emergency format for an unplanned absence. The emergency brief may cover only the next responsible actions and escalation contacts. It should not encourage colleagues to export whole mailboxes or duplicate sensitive folders. Leadership also has a part in continuity. Executives need to respect the backup's authority boundaries and avoid issuing conflicting instructions through private channels. If they make a new decision, it belongs in the shared record available to the authorized support team. When evaluating a managed or fractional executive support model, ask how backup coverage is activated, how permissions change, who reviews the handoff, and what happens when the backup encounters work outside scope. Answers should describe a process, not promise uninterrupted availability by an undefined group. A credible continuity model recognizes that some restricted matters will wait or escalate. The brief makes that boundary visible before an absence, when there is time to decide whether the coverage plan is sufficient. After access is no longer needed, remove temporary permissions through the approved process and verify ownership of shared files or meetings. Continuity is incomplete if the backup retains broad access indefinitely or if records remain locked in the substitute's account. Add those closure actions to the return checklist. Confirm that recurring invitations, delegated mail settings, and scheduled reminders have also returned to their intended owners. These small controls can continue acting after the coverage window even when the handoff document is closed.

Frequently asked questions