How to Draft Emails on Behalf of a CEO: A Guide for Executive Assistants
How to respond to emails on behalf of a CEO
Drafting emails for a CEO is one of the most trust-intensive tasks an executive assistant takes on. Done well, it protects the CEO's time, keeps relationships intact, and moves decisions forward without the CEO personally reading every message. Done poorly, it sends the wrong tone to an investor, a client, or a board member and can take weeks to repair.
This guide covers how to approach the task: how to capture the CEO's voice, how to build a reliable approval system, and how to know when to send independently versus when to escalate.
What "on behalf" actually means in practice
There are two models for handling CEO email replies. In the first, the EA drafts a response and the CEO reviews before it goes out. In the second, the EA sends directly, sometimes with a signature note indicating the reply came from the EA.
Both models are common and both can work. The right model for a given message depends on the relationship and the stakes involved.
Board members and major clients typically require CEO review before a reply goes out. Routine scheduling, vendor coordination, and general inquiries are strong candidates for direct EA sending, once the working relationship is well calibrated and the EA understands the CEO's standards for each type of contact.
Learning the CEO's voice
The hardest part of email drafting is voice matching. Every executive has characteristic patterns: how they open a message, how they frame a decision, how they phrase a deferral, and how they close.
The most effective way to learn those patterns is to read the CEO's sent messages from the past three to six months. Look for message length, greeting style, sign-off language, and how the CEO phrases a refusal or a follow-up.
Document what you find in a short reference file and update it whenever the CEO edits one of your drafts. An EA who can say "the CEO always opens with the person's first name and no preamble, signs off with just their own first name, and never uses 'please don't hesitate to reach out'" will produce far better drafts than one working from memory alone.
The four message types and how to handle each
Not every email needs the same approach. Most incoming messages that require a reply fall into one of four categories, each with a different default for who handles it and how.
| Message type | Who handles it | Default approach |
|---|---|---|
| Scheduling and logistics | EA independently | Coordinate slots, confirm details, send without CEO review |
| Information requests | EA with optional CEO scan | EA gathers the answer and drafts; CEO reviews if the stakes are moderate |
| Relationship-sensitive messages | EA drafts, CEO reviews | Investors, board members, long-standing clients; CEO approves before sending |
| Declines and redirects | EA drafts, CEO approves | Phrasing a refusal requires review; wrong tone to the wrong person is hard to undo |
The first category is where most EAs start building independent sending authority. The last category should almost always pass through a CEO review, at least until the EA has handled several similar situations successfully and the CEO has developed confidence in the phrasing.
Setting up the approval workflow
A reliable approval workflow removes guessing from both sides. The simplest version is a dedicated folder, typically called "Drafts for Review," where the EA deposits any reply that needs CEO eyes before it goes out.
The CEO checks this folder once a day, usually in a short focused block, and either approves with a brief reply, edits inline, or leaves a note about what needs adjusting. Every note from the CEO is calibration material for future drafts.
For messages with a time-sensitive reply window, set a protocol in advance. A common arrangement is that the EA flags urgent drafts through a direct channel, and the CEO clears the reply within a defined window rather than waiting for the daily folder review.
Building a phrase library
The most useful tool for consistent drafting is a phrase library: a shared document that collects the CEO's actual language patterns.
Useful entries include preferred greetings, sign-off style, how the CEO declines a meeting without leaving the door open, and how they phrase follow-ups on unanswered messages. Most of this content comes directly from the CEO's edits on early drafts.
When the CEO changes your wording, the new version belongs in the library. After a few months, the library becomes detailed enough that the EA can draft confidently even on message types they have not encountered before, by working from the documented patterns rather than guessing.
Building calibration together
The initial weeks of email drafting are a calibration period. Expect more CEO edits during this phase, and treat each edit as information rather than a correction.
When the CEO adds something to a draft, note what they added and why it matters in that relationship context. When they cut something you included, note that the CEO prefers brevity in that category. When they rewrite your opener, add the new opener to the phrase library with a tag for the type of contact it suits.
By the end of the first month, most routine message types should flow without much adjustment. Relationship-sensitive drafts will still require review, but the review cycles will be faster because the CEO will be editing fewer words per pass.
When to draft and when to escalate
Email drafting works on delegation authority: the EA acts independently within a defined scope and escalates outside it. Setting that scope clearly during onboarding saves a significant amount of friction later.
Standard escalation triggers include messages from contacts the CEO has never replied to before, messages involving financial commitments or resource allocation, anything with legal language, and messages where the sender's tone suggests the stakes are higher than the content makes obvious.
When in doubt, add the message to the review folder with a short note explaining what made you uncertain. That note also becomes useful calibration material: if the CEO replies "just draft it, this contact is fine," you have useful data about that contact's tier.
McKinsey Global Institute research found that professionals spend roughly 28 percent of the workweek on email. At the executive level, the volume is higher and the relationships are more consequential, which is exactly why moving the drafting layer to a trained EA can return hours to the CEO's week without any message slipping through. The executive inbox management guide covers how email drafting fits into the broader triage and routing system.
Common mistakes to avoid
The most common drafting mistake is a register mismatch: writing too formally for a CEO who communicates casually, or too casually for one who maintains formality with external contacts.
The second is adding information the CEO did not intend to share. If the CEO's intended reply was short, a longer EA draft creates an expectation of more detail than the CEO planned to provide and can open threads the CEO did not want open.
Third is delayed escalation. If a message makes you uncertain, it belongs in the review folder. The cost of the CEO reviewing one extra email is far lower than sending the wrong reply to the wrong person.
For tools that support this kind of drafting and review workflow in a remote setup, including shared draft environments and email management platforms, the executive assistant tools guide covers the most practical options.
Frequently asked questions
Can an EA send emails on behalf of a CEO without CEO review?
Yes, for routine categories like scheduling, logistics, and general inquiries. Most EAs and CEOs define a scope for independent sending during onboarding, with everything outside that scope going to a review folder before it goes out. That scope typically expands as the EA builds a track record.
How do you learn a CEO's email voice?
Start by reading the CEO's sent messages from the past several months. Look for patterns in greeting style, message length, sign-off language, and how the CEO phrases requests or refusals. Document those patterns in a short reference file and update it whenever the CEO edits one of your drafts.
What should an EA do when they are not sure how to respond?
Flag the message and put it in the drafts-for-review folder with a short note. Escalating one extra email costs almost nothing. Sending a poorly calibrated reply to a key contact can cost significantly more in time and relationship repair.
How long before email drafts feel natural to the CEO?
Most CEOs and EAs describe a four-to-six week calibration period. The first few weeks involve more feedback loops. By the end of the first month, routine messages typically flow without much correction, and the CEO's review time per draft drops noticeably.
How does an EA handle a message that needs an immediate reply?
Set the protocol in advance. A common arrangement is that the EA flags urgent drafts through a direct channel such as a phone call or a message app, and the CEO clears the reply within a defined window rather than waiting for the daily folder review.