AI Prompt to Rewrite Emails for Clarity

What it does

Takes a draft email and rewrites it following executive communication principles: lead with the ask, front-load context, make action items explicit. Three modes let you choose between a fast rewrite, teaching feedback on what to fix, or both — so a one-time email also becomes a coaching session. Especially useful for upward communication (to managers, executives, clients).

The Prompt

Rewrite the following email to be clearer and more actionable.

Context (fill in what you know):
- Who is the reader? [e.g., my manager / a client / cross-functional team / direct report]
- What's the relationship? [e.g., formal, friendly, first contact, long-standing]
- What stakes? [e.g., routine update / time-sensitive decision / difficult conversation]

Mode:
- Rewrite — give me the improved email, ready to send
- Teach — explain what's wrong and how to fix it, but don't rewrite
- Both — rewrite first, then explain what you changed and why
[CHOOSE ONE MODE OR DEFAULT TO "BOTH"]

Rules:
1. First sentence: what you need from the reader (decision, approval, FYI, or response to a question)
2. Second sentence: the key context they need to act — no more, no less
3. Bullet points for any action items, with owners and deadlines
4. Remove hedging language ("just wanted to," "I was wondering if," "sorry to bother you") — unless the tone genuinely calls for softening
5. Keep it under 150 words unless the complexity demands more. If the original is under 150, make it shorter, not longer
6. Preserve the original tone — formal stays formal, warm stays warm. Tighten, don't transform

Anti-instructions:
- Do NOT make it sound like a different person wrote it. Match the sender's natural voice, just sharper
- If the original email is already clear and actionable, say so and explain what makes it work. Do not rewrite for the sake of rewriting
- Do NOT strip personality, humor, or warmth in the name of "clarity." Personality is not the enemy of professional communication
- Do NOT add corporate jargon ("per our discussion," "circle back," "align on") that wasn't in the original

In "Both" or "Teach" mode, structure your explanation as:
1. Diagnosis — what's the core problem with this email? (buried ask, unclear audience, too long, wrong tone, etc.) — one or two sentences
2. Key changes — 2-4 specific things you fixed or would fix, with before/after snippets from the actual email. Keep this section under 80 words total
3. Pattern to watch — one habit the writer should notice in their future emails, stated in a single sentence

Email to rewrite:
[PASTE YOUR EMAIL HERE]

Usage Notes

• Works with any AI model. The rules are explicit enough that smaller models follow them well.
• Default to “Both” mode the first few times — the Pattern-to-watch line compounds across emails, so the rewrite gets better the more you use it.
• Use “Teach” mode when you want to learn rather than ship. Good for sensitive emails you want to write yourself.
• Fill the Context block honestly. “Direct report going through a hard time” produces very different advice than “VP asking for a status update.” The prompt calibrates to what you tell it.
• For very long emails (500+ words), consider splitting into “TL;DR + Full Context” format instead.
• If the original email has no clear ask, the AI will surface that gap — which is the real problem to fix.