AI Field Manual
FM-EA-01 · Guide

Executive Assistants  ·  Fundamentals

Triage an email backlog into decisions and drafts

Your executive is back from five days of travel and the inbox holds 212 unread messages. Somewhere in there are the three that matter today, the eleven you can answer yourself, and one that should never go anywhere near an AI tool. This guide sorts the pile into those groups and drafts the replies, while every send, and every judgment about people, stays with you.

Status
Published
Reading time
About 13 minutes
You'll need
A batch of email you are allowed to process with your organization's approved AI tool, this week's priorities, and five to ten emails your executive has written
Last reviewed
November 2026
Before you start

What AI is for here, and what it isn't

Inbox triage is mostly pattern recognition: this is a request, that is a newsletter, this one is the board chair and needs to be seen today. AI is quick and consistent at that first sort, and good at drafting routine replies once it has seen how your executive writes.

It can't know the things that make you good at this job: that the "quick question" from the CFO is really about last week's argument, that a particular investor must never wait more than an hour, or that a friendly note from a former colleague is a job approach your executive hasn't told anyone about. It doesn't know who is upset, who is being careful, or what was said in the corridor.

So the division is simple. AI sorts and drafts. You decide what your executive sees, what gets said, and what gets sent. Nothing leaves the mailbox without you reading it.

Step 1

Build a voice card once

Draft replies only save time if they already sound like your executive. Instead of correcting tone in every draft, write down how they write, once, and reuse it.

Collect five to ten emails your executive wrote themselves: a few quick replies, a decline, a thank-you, and one firmer message. Remove anything confidential, then ask for a description of the style, not a copy of it.

The voice card prompt
Below are emails written by one executive. Describe how they write so
an assistant can draft replies in the same voice. Do not quote whole
sentences back; describe the patterns.

COVER:
1. Greeting and sign-off habits, by type of recipient.
2. Typical length and structure (e.g., answer first, then context).
3. Tone with peers, with their own team, with external contacts.
4. Phrases they use often, and phrases they never use.
5. How they decline, delay, and delegate.
6. Formatting habits (bullets, bold, signatures, emoji).

EMAILS:
[paste 5–10 emails, redacted]

Edit the result yourself. You know things the samples don't show: that they never use exclamation marks with the board, or always copy their chief of staff on anything about headcount. Keep the finished card short (half a page), and add a line for your own replies: how you sign when writing on their behalf, and what you're authorized to commit them to.

Step 2

Screen out what never goes to the AI

Before you process anything, take out the messages that stay with you. This is a screening step in its own right, done before the batch goes near any AI tool, and it takes two passes.

Pass 1: sender and subject. Scan the list and pull out the obvious ones:

  • People matters. Performance, pay, complaints, resignations, investigations, anything from HR or about a named employee.
  • Legal and confidential. Messages from counsel, anything marked privileged, deal or merger material, board-confidential items.
  • Personal. Your executive's health, family, finances, or anything clearly personal.

Pass 2: content and attachments. Sender and subject aren't enough. A routine-looking message from a vendor can carry a contract, a salary figure or a customer's personal data in its body or an attachment. So:

  • Use your organization's classification if it has one. If your email carries sensitivity labels or a data loss prevention policy covers AI tools, apply it, and exclude anything labelled confidential or higher. An approved, automatic classification is more reliable than a person scanning.
  • Otherwise, review the bodies yourself. Skim each remaining message's text and the names of its attachments before it goes into the batch.
  • Leave attachments out by default. The batch is message text only. Add an attachment only after you've opened it and confirmed it's safe to process.
  • When in doubt, hold it. If you'd hesitate to tell your executive "I ran that through an AI tool", don't.

Everything screened out goes to a "Hold" list that you read and handle yourself. The AI never sees it, so it can't misfile it, quote it, or draft a reply to it.

Step 3

Sort the batch

Give the AI the remaining messages, your executive's priorities for the week, and the people who always get priority. Ask for a sort, with reasons, not decisions.

The triage prompt
You are helping an executive assistant triage email. You sort and
explain; the assistant decides.

THIS WEEK'S PRIORITIES: [3–5 items, e.g., board meeting Thursday,
  Series C diligence, hiring a CFO]
ALWAYS PRIORITY: [roles, e.g., board chair, top 5 clients, CEO's direct reports]
ASSISTANT CAN HANDLE: [e.g., scheduling, travel, routine vendor replies,
  requests for documents we've already shared]

SORT EACH MESSAGE INTO ONE GROUP:
A. NEEDS EXECUTIVE: a decision, an opinion, or a relationship only
   they can handle. Say what they need to decide, in one line.
B. ASSISTANT CAN HANDLE: say what the reply needs to do.
C. FYI: worth knowing, no action. One-line summary.
D. ARCHIVE: newsletters, notifications, resolved threads.
E. UNSURE: anything you can't place confidently. Say why.

For each message give: group, sender, subject, one-line reason, and
any deadline stated in the message.

RULES: Don't infer feelings or motives. Don't guess deadlines that
aren't written down. If a thread was answered later in the batch,
say so.

EMAILS:
[paste batch]

The "unsure" group is the important one. A good sort puts five or six messages there, not zero. Read every one yourself.

Step 4

Draft the replies you can send

For the "assistant can handle" group, draft replies in batches of five to ten, with the voice card.

The reply-drafting prompt
Draft replies to the emails below, in the voice described in the voice
card. I am the executive's assistant and will review every draft.

VOICE CARD: [paste]
WHO IS SENDING: [the executive's name / me on their behalf]

FOR EACH EMAIL I'll tell you what the reply needs to do. Draft only
that. Do not:
- agree to meetings, dates, money, or introductions I haven't listed
- promise anything on the executive's behalf
- add facts that aren't in the email or my notes; write [CHECK] where
  you need one

EMAILS AND WHAT EACH REPLY SHOULD DO:
1. [email] → [e.g., decline politely, offer a call in March]
2. ...

Read each draft as if you were the recipient. Check every name, date, title and attachment reference, and look for the [CHECK] markers before anything goes out.

Step 5

Worked example: the Monday after a trip

Fictional example. Elena, a chief executive, is back from five days of meetings. Her assistant, Sam, has 212 unread messages. This week's priorities: Thursday's board meeting, the shortlist for a new CFO, and a client renewal.

Sam's first pass, by sender and subject, holds back nine messages: two from HR about a manager's leave, one from outside counsel, the CFO search firm's candidate notes (personal data about candidates), and five personal messages. The second pass, skimming the bodies, catches one more: a routine-looking invoice query from a recruitment vendor whose attachment lists the salaries of three placed candidates. Those ten never leave the mailbox, and the rest go in as message text only, without attachments.

The triage prompt sorts the remaining 202:

  • Needs Elena (7): among them, the board chair asking whether the strategy paper can move to the top of the agenda, and a client asking for a renewal call this week.
  • Sam can handle (31): scheduling requests, two requests for last quarter's deck, a vendor asking to reschedule.
  • FYI (22) and archive (137).
  • Unsure (5). One of them is a short note from a former colleague: "Would love to catch up about something that might interest you." The AI can't tell whether it's social or a job approach. Sam can, and moves it to Elena's personal folder without a reply.

Sam drafts the 31 replies in four batches with the voice card, fixes two that offered dates Sam hadn't listed, and sends them over the morning. Elena gets a short list of seven, each with one line on what she needs to decide. She's done in twenty minutes.

Step 6

Record your triage rules

Voice card and triage rules
[Executive name] — Voice card and triage rules, v[number], [date]

VOICE
Greeting / sign-off: [by recipient type]
Length and structure: [e.g., answer first, one paragraph]
Tone: [peers / team / external]
Uses: [phrases]          Never uses: [phrases]
Declines like this: [pattern]

ALWAYS PRIORITY
- [role or name]

NEVER TO AN AI TOOL (hold for me)
- [sender, subject or category]
Content screening: [organization's classification / manual review of bodies]
Attachments: excluded unless opened and cleared

I CAN HANDLE WITHOUT ASKING
- [e.g., scheduling inside agreed hours, document requests]

NEVER WITHOUT ASKING
- [e.g., speaking invitations, introductions, anything to the press]

Approved AI tool: [name]     Reviewed with executive: [date]

What stays with you: what your executive sees, everything about people, and every message that goes out under their name.

Esc

Saved in this browser

Reading list

Contents

Reference

Keyboard shortcuts

/ or Ctrl K
Search the manual
↑ ↓
Move through search results and index entries
Enter
Open the selected result
← →
Switch discipline tabs; previous / next entry in a workflow card
Esc
Close any dialog
?
Show this list