WORKFLOWS / KNOWLEDGE AND CONTINUITY
Prepare a handover someone can use.
Help the next person understand what needs attention, how to handle the usual exceptions, and when to ask for a decision.
WHAT THIS WORKFLOW PRODUCES
A working guide for the person taking over.
Give the replacement the information needed to handle the work they will encounter. Link to detailed instructions and records instead of copying the whole filing system into a document. The guide below covers the agreed work and dates; it does not grant new decision rights or access.
EXECUTIVE OPERATIONS COVER
ILLUSTRATIVE HANDOVER · 14 TO 18 SEPTEMBER
THE OPERATING METHOD
Understand the workflow without AI.
A useful handover gives someone a way to act when you are unavailable. Test that they can find the information and handle a real task before the handover is considered complete. AI is introduced only after the method makes sense on its own.
Define the cover
Agree on the dates, responsibilities, and decisions the replacement can make.
YOUList the live work
Identify upcoming commitments, unresolved items, and recurring tasks.
YOUExplain the exceptions
Record the situations where the normal process changes.
YOUTest the handover
Have the replacement find an answer and walk through a task.
YOUKeep it current
Update material changes until the cover ends or ownership transfers.
YOU"Everything is in the drive" is a starting point. A usable handover tells someone where to start and how to handle the work.
WHERE THE FACTS LIVE
Use the systems where the work already lives.
Choose records the replacement is allowed to see. Leave passwords, private personal information, and unrelated executive correspondence out of the handover. Named tools link to their pages in the library.
ACTIVE WORK
Open tasks, upcoming commitments, and unresolved decisions.
ACCESS AND CONTACTS
Approved shared access, escalation contacts, and permission requests.
The existing access register
The company password manager
THREE WAYS TO RUN IT
Choose how much machine.
Start with the information that is difficult to recover from a task list: judgment, exceptions, and working arrangements. Add connected search or an agent only where it helps maintain the handover. The tools named are examples. Use what your organization already runs, provided the connection is supported and approved.
LEVEL 1
Have AI interview you for the handover.
Tell AI what is being covered and answer a few questions at a time. It turns your answers into a short guide and points out missing information without inventing it.
Use this version when much of the work is in one person's head or existing notes are difficult to follow.
WHAT THIS VERSION REDUCES
Staring at a blank handover document and forgetting routine exceptions.
WHAT A PERSON STILL DOES
What the replacement may do and what needs escalation.
MAIN LIMITATION
A polished guide can still contain gaps. The replacement's walkthrough is part of the process.
Build this version, step by step 4 steps, one action each. Prompts carry a Copy button.
Tell the AI the shape of the handover.
WHO, WHAT, WHEN
The dates being covered, the responsibilities being handed over, and how experienced the replacement is. Leave out the private reason for the absence.
Ask it to interview you.
Help me prepare a practical handover. Ask three questions at a time about live work, recurring tasks, exceptions, access, and escalation. Ask what someone might get wrong. Use only my answers and mark anything missing.
Turn your answers into instructions someone can act on.
ACTION AND LOCATION
Each entry says what needs doing, where the record lives, and who can solve a problem with it. Long procedures stay where they are and get a link.
Have the replacement try it.
ONE REAL TASK
- They can find a current item.
- They can say what the next action is.
- They can say when they would ask for help.
Fix the guide wherever they got stuck.
LEVEL 2
Build the handover from current records.
Use a connected assistant to inspect selected working records. It drafts the handover and flags discrepancies, such as an overdue task or a procedure that points to the wrong owner.
Use this version when the records exist, but assembling the relevant parts is time-consuming.
WHAT THIS VERSION REDUCES
Pulling together scattered instructions and outstanding work.
WHAT A PERSON STILL DOES
Which records are reliable and which material the replacement is allowed to receive.
MAIN LIMITATION
Your own ability to read a document does not mean the replacement can open it.
TOOL OPTIONS
Notion is the example for a handover already held there. A connected assistant and approved Google Drive or SharePoint documents can serve the same purpose. Validate the selected connector's access and file support rather than moving the company knowledge base for this workflow.
Build this version, step by step 5 steps, one action each. Prompts carry a Copy button.
Choose the pages the guide may draw from.
NAMED PAGES ONLY
The current tasks, the procedures, and the working agreements that matter for the cover period. If the work already lives in Notion, start with its personal Agent.
Ask for a draft with a link beside every item.
THE DRAFT
It should cover live work, routine responsibilities, exceptions, contacts, and any access still to be granted, each with its source link. Where two sources disagree, it says so rather than quietly choosing one.
Add what the records do not say.
PRACTICAL EXCEPTIONS
The things only you know: how the executive prefers to be escalated to, or which approval has to happen before a meeting can move.
Check the sharing and the access.
THE CHECK
- The page's audience is only the people who should see it.
- The links open when tested with the replacement's own account.
- Any access still missing has been requested through the normal route.
Walk it through with the replacement.
READY OR MISSING
Let them try a real task and ask questions. The handover is ready only when the access works and the critical instructions are confirmed.
CAPABILITIES CHECKED AGAINST OFFICIAL DOCUMENTATION
Notion documents its personal Agent's capabilities and how its access follows the user's own permissions. Source, checked September 6, 2026.
LEVEL 3
Add a restricted handover assistant.
A small agent reads the approved handover material. It can find the relevant instruction, flag a missing answer, and put proposed updates in a review area. A named person keeps responsibility for the official handover.
Use this version when a handover covers changing work, several weeks, or a role transition with repeated questions.
WHAT THIS VERSION REDUCES
Repeated searches and manual checks for changes in a defined set of handover records.
WHAT A PERSON STILL DOES
Exceptions, new authority, and which updates become official instructions.
MAIN LIMITATION
The assistant cannot answer from an offline conversation or inaccessible record. It needs a clear route to the person who can help.
TOOL OPTIONS
Notion's native agent is the first option for a Notion-based handover. Make or n8n can coordinate a similar bounded process across apps, but add them only if important records cannot be handled through the native setup. Custom Agents may use separate credits; check what your account includes. Try it on non-sensitive test records first: the permissions, the review area, and what happens on the end date.
CUSTOM AGENTS HAVE THEIR OWN PERMISSIONS
Notion Custom Agents have their own permissions. Someone using an agent may receive information they could not otherwise open. Limit both its sources and its users. A personal Notion Agent's permission behavior is different, so do not reuse those assumptions here.
Build this version, step by step 6 steps, one action each. Prompts carry a Copy button.
Start from the approved handover guide.
SMALL SOURCE SET
In Notion, choose only the pages and records that everyone who will use the assistant is allowed to see. Keep the set to the responsibilities being covered.
Limit what the agent may change.
PROPOSALS ONLY
The Custom Agent can read those sources. It can write only in a separate area for proposed updates and unanswered questions. It cannot rewrite the approved guide or reassign work.
Tell it what to do when it is unsure.
ANSWER OR ASK
Every instruction it gives carries a source link. If the sources disagree or do not cover the question, it names the gap and the person to ask. It never guesses at a policy or an approval limit.
Choose when it runs.
QUESTIONS PLUS A DAILY CHECK
The replacement asks it questions whenever they need to. If records change often, add one scheduled check a day during the cover period. Do not let it re-read the whole workspace after every edit.
Review what it proposes.
THE CHECK
- The handover owner has read the proposed changes and updated the official guide where they agree.
- The list of unanswered questions is still open until every question is resolved.
Switch it off or hand it over when the cover ends.
COVERAGE ENDS
Turn off any schedules when the cover period ends. For a permanent move, transfer ownership and check the access before the outgoing person's account is closed.
CAPABILITIES CHECKED AGAINST OFFICIAL DOCUMENTATION
Notion documents Custom Agents: configured access, triggers, and activity management. Source, checked September 6, 2026.
Notion's Custom Agent security notes document independent permissions, sharing implications, and continuity of source access. Source, checked September 6, 2026.
WORKS EVEN BETTER WITH
A handover needs current work as well as instructions. Keep recurring procedures up to date, and give the next person a way to find answers or reach someone who can help.
Standard Operating Procedure → | Answer recurring internal questions from approved information →