On this page
The five-minute handoff that keeps an executive office honest

Published November 4, 2026
A handoff is usually written at the worst possible moment. The day is ending, the executive is between calls, and the assistant is trying to compress eight hours of context into a message that someone else can act on. The result is often a list of things that happened rather than a description of what is still true. The next person reads it, nods, and then spends the first hour of the next shift reconstructing the decisions that were never written down.
Remote executive support makes this weakness expensive because the next person may be in another time zone, with no hallway conversation to fill the gap. A short handoff can still be reliable, but only if it is built as a status report rather than a diary. The test is not whether the note is long. The test is whether the next assistant can tell what is settled, what is waiting, and what would count as done.
The end of the day is a control point
Most executive-office routines focus on the morning: the brief, the calendar review, the first pass through the inbox. The evening handoff gets less attention because it feels like cleanup. In practice, it is the point where the office decides what the next shift inherits. A missed detail does not disappear overnight. It becomes a question at 7 a.m., a meeting that starts without the right document, or a decision that gets made twice because nobody recorded the first one.
Treating the handoff as a control point changes what goes into it. The question is not "what did I do today?" but "what does the next person need in order to continue without asking me?" That framing favors a small number of explicit items over a comprehensive narrative. It also makes the handoff reviewable. A manager can look at the note and see whether the open items have owners, whether the decisions have evidence, and whether the next action is clear.
Write a status, not a diary
A useful handoff has three layers: what changed, what was decided, and what is still open. The first layer is factual. A meeting moved. A document was sent. A vendor confirmed a date. The second layer records choices that affect future work: the executive approved a revised agenda, declined a request, or asked for a different option. The third layer names the work that remains, with an owner and a next check.
The diary version blends all three into a timeline. It reads smoothly but forces the next person to infer which items matter. A status version is less elegant and more useful. It can be short: three bullets under each layer, with links to the underlying message or document. On a chaotic day, the status can still be short if it separates noise from consequences. The assistant does not need to narrate every interruption, only the ones that changed the plan.
Separate facts, decisions, and open questions
Facts are cheap to record and easy to verify. Decisions are harder because they often arrive informally: a nod in a meeting, a one-line reply, a comment in a thread. Open questions are hardest because they require the writer to admit that something is unresolved.
A simple convention helps. Put facts in the past tense with a source. Put decisions in the active voice with the decision owner. Put open questions as questions, with the person who can answer and the date by which the answer is needed. This convention keeps the note honest without making it formal. It also creates a record that can be checked later, which is useful when a decision is questioned or a deadline slips.
Confidentiality belongs in the same discipline. A handoff should carry the minimum context needed to continue the work, not a second copy of sensitive material. The NIST Privacy Framework is a useful reminder that data minimization and access control are design choices, not afterthoughts. Keep personal, legal, or board-sensitive details in the approved system and reference them rather than pasting them into a chat.
Make the next action testable
An open item is only useful if the next person can tell what would close it. "Follow up with finance" is not testable. "Ask finance to confirm the revised Q4 forecast by Thursday at noon; if no reply, escalate to the CFO's chief of staff" is testable. The difference is not verbosity. It is the presence of a completion condition.
Testable actions also make delegation safer. The next assistant knows what authority they have and when to stop. If the action requires a judgment the office has not authorized, the handoff should say so. That protects the executive from an overreach and the assistant from being blamed for a decision they were never empowered to make. The asynchronous decision log is a good companion for decisions that need a durable record rather than a one-line note.
Read the handoff before you act
A handoff is not complete when it is sent. It is complete when the next person has read it and confirmed the open items. That confirmation can be a short reply, a checklist, or a comment on the shared note. The form matters less than the habit. Without it, the writer assumes continuity and the reader assumes the writer handled everything.
The first fifteen minutes of the next shift are the right time for this check. Read the open items, verify the owners, and flag anything that is already stale. If a decision is missing its evidence, ask before acting. If an action has no completion condition, rewrite it. This is also the moment to notice patterns: the same vendor question every week, the same document arriving late, the same approval sitting in the wrong queue. Those patterns are candidates for a process fix, not just another handoff line.
The research brief on handoff completeness makes a similar point: the value of a handoff is not the volume of information it carries but the number of questions it prevents. A short note that closes the right questions beats a long note that leaves the next person guessing.
A routine that survives a bad week
The routine does not need to be elaborate. At the end of the shift, write three short blocks: changes, decisions, open items. For each open item, name an owner, a next action, and a check date. Link the source rather than pasting it. At the start of the next shift, read the note, confirm the open items, and flag anything that no longer makes sense.
On a bad week, shorten the note rather than skipping it. A five-minute handoff with three accurate lines is better than a polished summary that arrives two hours late. The point is continuity, not performance. When the office can hand off cleanly, the executive gets a team that behaves like one team across time zones, and the next assistant gets a starting point instead of a mystery.
That is the real promise of the five-minute handoff. It does not make the work smaller. It makes the work visible enough to continue.