ExecutiveSupportStaff Editorial Team | Published
Writing emails on behalf of an executive is one of the highest-leverage skills an executive assistant can develop. Done well, it reduces the executive email burden significantly across a typical week without sacrificing communication quality or relationship trust.
Done poorly, it introduces real risk. A reply that sounds wrong damages the executive brand in a way that is hard to trace and harder to repair. A message sent at the wrong level of formality signals that the executive does not pay attention to the recipient relationship.
Harvard Business Review research on what makes business writing strong found that clarity and specificity are the primary predictors of reader engagement, not polish or sophistication. The same principle holds for executive correspondence: clear, direct, and appropriately toned outperforms elaborate and comprehensive.
The first mistake is writing in the assistant voice rather than the executive voice. The assistant defaults to their own communication style, which the recipient notices even if they cannot name why the email feels off. Voice consistency is what makes ghostwritten correspondence invisible.
The second mistake is over-formality. Assistants unfamiliar with the executive relationship portfolio often write formal, measured prose for messages the executive would send casually. A note to a long-standing peer gets the same drafting treatment as a note to a new board member, and neither feels right.
Both mistakes come from the same source: not enough research into the executive existing correspondence before drafting begins.
Access to the sent folder is the starting point. The assistant should spend the first one to two weeks reading the last six months of outbound messages, grouping them by recipient type and noting the patterns: how messages to board members differ from messages to direct reports, how the executive opens and closes correspondence, and what their sentence rhythm looks like under different levels of stakes.
Most executives have distinct registers for different relationships. The messages to investors are different from the messages to the operations team. The assistant needs to learn each register separately and apply the right one based on the recipient.
Take notes on specific phrases the executive uses repeatedly. These act as calibration points when drafting and help the assistant reproduce the executive voice rather than approximating it.
For any draft, the assistant should resolve four questions before writing: Who is the recipient and what is the relationship context? What is the single main point? What is the appropriate formality level? Is there a deadline or constraint the message needs to acknowledge?
Those four answers narrow the draft to a small target. The assistant writes the message the executive would send if they had two minutes and no friction: direct, appropriately toned, and complete without being comprehensive.
Frame the draft for approval with a short context line at the top: the recipient, the purpose of the message, and whether the draft is ready to send or needs the executive to weigh in on a specific point. This reduces review time to under 60 seconds for most messages.
Ongoing threads are harder than one-off messages because the assistant must track context across multiple exchanges. The first reply is straightforward if the draft framework is in place. By the third or fourth exchange, the assistant may be managing a conversation they did not initiate and were not fully briefed on.
The rule for threads: draft if the next reply follows a clear pattern from earlier in the thread; escalate if the thread has moved into territory where the assistant lacks enough context to navigate. A transparent escalation note is better than a confident draft that misses the mark.
For the broader inbox system that supports this workflow, see our guide to the email triage system. For a complete view of how correspondence management fits the executive assistant role, see our piece on what executive assistants do.
The drafting scope expands over time as the assistant builds more context and confidence. In the first month, the assistant drafts only the messages they are confident about and flags anything uncertain. By month three, the scope should cover most routine correspondence. By month six, the executive should be reviewing and approving drafts more often than they are writing from scratch.
The messages that stay in the executive lane throughout are the ones that carry the highest relationship stakes: board communications, personnel matters, and any message where the executive position on an open question shapes the reply. These do not belong in the drafting workflow even when the assistant has deep familiarity with the relationship.
The best way to expand the drafting scope is to ask for feedback on every draft the executive edits significantly. A short conversation after the fact covers what was wrong with the draft and how the executive would have written it. That feedback compresses the learning curve more than practice without it.
| Message type | Draft or escalate | Notes |
|---|---|---|
| Meeting confirmations and scheduling updates | Draft | Follows a clear template the assistant can own |
| Routine stakeholder acknowledgments | Draft | Consistent tone, low risk if phrasing is slightly off |
| Follow-up notes after calls | Draft with context note | Assistant briefs on context if not present at the call |
| Board, personnel, and strategic communications | Escalate | Require executive judgment that cannot be delegated |
How do you make a ghostwritten email sound like the executive wrote it?
Research before drafting, not guessing in the moment. Read six months of the executive sent folder and identify the consistent patterns: sentence length, how they open and close messages, the vocabulary they use with different audiences, and the level of formality they apply in each relationship. The first drafts will need adjustment. The calibration happens over the first 30 days, not on day one.
Which categories of email should an EA always draft rather than the executive writing from scratch?
The best candidates are messages that follow a recognizable pattern: meeting confirmations, scheduling updates, routine stakeholder acknowledgments, and follow-up notes after calls the assistant attended or was briefed on. Messages that require executive judgment, such as board communications, personnel decisions, or sensitive client negotiations, should be flagged rather than drafted.
How does the executive signal what they want without writing the email themselves?
The most effective method is a brief verbal or written note before the draft: the key point to communicate, the tone, and any specific phrasing to include or avoid. A two-sentence briefing gives the assistant enough to write a solid first draft. Drafting without that input typically results in a draft that misses the key point and requires a full rewrite.