The part of your job nobody wrote down

The exec operating brief

One document. It holds the layer of your job that no handover checklist has ever captured: preferences, patterns, trust, history, landmines.

Two things worth getting straight about it.

A handover doc gets written in your last two weeks, in a bad mood, for someone else. You write this one now, and you are the primary user.

The reason it never gets written is that it feels like busywork done from memory on a Sunday. You already have the raw material, sitting in ninety days of sent mail, chat threads and calendar entries. You have simply never had a tool that could read it back to you and pull out the patterns. Now you do.

Where to put it depends on what you already use. If you are on Microsoft, Copilot Notebooks will now take Outlook emails as a reference source, so the brief can sit next to the actual threads it came from. If you work in ChatGPT or Claude, use a project or a persistent memory so the context loads every time instead of being re-pasted. Any of these is fine. A plain document you actually open beats a clever system you abandon.

One honest caveat before the moves. Writing this down makes you harder to replace, and you will feel it happen. When you try to put "how to handle the CFO" into words, you will find yourself writing four conditional rules and then giving up and writing "read the room." That gap between what you can document and what you actually do is the most concrete proof you will ever have that the judgment part stays yours. Nothing reassures you about that faster than trying to write it down.

1. Get AI to tell you what you already know

Start from evidence rather than a blank page. Pull the last ninety days of wherever your work actually happens: sent mail, Slack or Teams messages, your calendar, or whatever channel your team really runs on. Then ask:

Here is a sample of my work communication from the last 90 days. It may be sent email, Slack or Teams messages, calendar entries, or a mix: [paste]. I support an executive and I am building a written brief of the things I know that are not documented anywhere. Read this and tell me: (1) which people appear most often and in what context, (2) what recurring commitments, deadlines or rituals show up, (3) which topics I appear to handle myself versus route to my exec, and (4) anything that looks like a pattern I may not have noticed. Be specific and cite the evidence. Do not guess or fill in gaps. If something is unclear, list it as a question for me to answer.

That last instruction matters. What comes back will be roughly seventy percent right and thirty percent questions. The questions are the valuable half. They point directly at the knowledge that only exists in your head.

2. Build the relationship map

Names and titles are in the org chart. This is everything the org chart leaves out.

I am building a relationship map for my executive. I will describe each key person one at a time in plain, messy language, exactly as I would explain them to a colleague. Turn each one into a short structured entry with these fields: who they are and how they relate to my exec, how my exec actually feels about them, how they prefer to be contacted and how fast they respond, what has gone wrong before, and what to watch out for. Keep my wording and my judgment. Do not soften anything or make it sound more corporate. Ask me a follow-up question if a field is thin.

Then just talk. "The CFO is fine but never send him anything on a Friday afternoon." "She and my exec had a real disagreement in March and it still colors things." "He says yes to everything and delivers none of it, so I always confirm twice."

You will get through more people in twenty minutes of talking than in three hours of trying to write it properly. Speaking is the unlock.

3. Run the bus-factor audit

This is the one that changes how you see your own job.

Here is my exec operating brief and relationship map so far: [paste]. Act as an operations reviewer. Identify everything here that appears to depend entirely on one person's memory or personal relationships, meaning it would fail or degrade if I were unavailable with no notice. For each item, tell me what would break, roughly how long until someone noticed, and whether it could be documented or only handed over in person. Sort by consequence. Be blunt.

Two things come out of this list. The first is a real risk register you can act on. The second, and be honest that this is the point, is the clearest inventory of your value that you will ever hold. Every item on it is a thing the organization is quietly relying on you for and has never named.

You can benefit from that list without sending it to anyone. But when the review comes, or the recruiter calls, or an exec departs and a director makes assumptions in an elevator, you will be reading from a document.

4. Keep it alive with a five-minute Friday

A brief written once and abandoned is worse than none, because you will trust it and it will be wrong.

Here is my current exec operating brief: [paste]. Here is what happened this week: [paste a few lines, or a rough voice-to-text dump]. Update the brief. Add anything new, revise anything that changed, and show me a short list of exactly what you changed and why so I can check it. Do not rewrite sections that did not change.

Five minutes, once a week. That is the entire maintenance cost.

Notice what none of these four moves asks. None of them asks you to hand over your judgment. AI does the reading, the sorting, and the formatting. You supply every piece of knowledge that matters, because you are the only one who has it. The machine is a very fast scribe with a good memory. You are still the one who knows that the CFO should never get an email on a Friday.

1. The tools finally caught up to this specific job. Copilot Notebooks now takes Outlook emails as a reference source, so a brief can sit alongside the threads it came from instead of floating in a separate file nobody opens. And both ChatGPT and Claude reworked how persistent memory works this summer, moving toward entries you can edit and correct individually rather than one opaque summary. Translation: context you build once now stays built. That was the missing piece in every previous attempt to do this.

2. New EAs are being asked to invent the system from scratch. One posted this week that her CEO has never had an assistant before, asked on day one what they should do about her new work phone, and has since asked what she thinks should happen with email and the calendar. She wrote that every previous exec had a system she could fit herself into, and this time there is nothing to fit into. If that is you, the four moves above are your first thirty days. Build the brief as you learn instead of waiting until you are supposed to already know.

3. The knowledge nobody documents is exactly the knowledge that costs the most to lose. Every study of offboarding lands in the same place: the process context and relationship history walk out the door, and organizations consistently fail to capture them. Which is precisely why the person who has captured theirs is not interchangeable. The four prompts above are the whole template, so start there. If you want more prompts built for this job, the free AI Prompt Library for Executive Assistants is in the Digital Zen library: digitalzen.site/resources

This week, do move #2 and nothing else. Pick the five people who matter most to your executive. Talk through each one out loud into an AI, messy and unedited, the way you would explain them to a colleague over coffee. Let it structure what you said.

Twenty minutes. Five people. When you read it back, you will see the job you have actually been doing.

Then hit reply and tell me: what is the one thing you know about your executive's world that has never been written down anywhere? I read every reply.