Email Polish
When to use
Use this when you have a rough, blunt, terse, or frustrated email draft and want it to read as friendly but professional - warm, clear, respectful - without changing what it actually says.
Not for: writing an email from scratch when there is no draft or intent to work from (you would have to invent the content); translating between languages; or softening a message whose whole point is to be firm and formal, such as a legal notice or final warning - there, over-warming the tone defeats the purpose. Do not use it to add commitments, dates, or promises the owner did not make.
Method
- Read the draft and extract three things: the core ask, the key facts (names, dates, numbers, links), and the emotional register.
- Calibrate formality from the recipient. Decision point: unknown / senior / external -> "Hi Dr. Lee," and no slang; known colleague -> "Hey Sam," relaxed close; recipient unknown -> default to a safe friendly-professional register.
- Rewrite paragraph by paragraph, keeping the original structure unless it is genuinely unclear. Warm opening (one friendly line, not gushing), direct middle, courteous close.
- Preserve every fact verbatim. Names, dates, numbers, links, requests carry over unchanged. Decision point: if a needed detail is missing (a meeting time), insert a clear placeholder like
[time] rather than guessing.
- Fix grammar, spelling, and awkward phrasing. Cut corporate filler ("per my last email", "circling back"). Never let the tone turn passive-aggressive; keep a frustrated draft firm but not sharp.
- Ensure a subject line exists; propose one if absent. Match length to the original - a two-liner stays short.
Example
Input (raw): hey need the report by friday its late again. send it.
Output:
Subject: Report - Friday deadline
Hi [name],
Hope you're doing well. Quick note - could you get the report over to
me by Friday? It's slipped a couple of times now, so I want to make
sure we stay on track this week.
Thanks a lot,
[Your name]
Pitfalls
- Scope creep. Adding a promise, apology, or deadline the owner never wrote turns a polish into a fabrication.
- Padding. Inflating a two-line note into five paragraphs of pleasantries wastes the reader's time.
- Guessing missing facts. Inventing a time or name instead of leaving a marked placeholder.
- Buried point. So much warmth up front that the actual ask disappears; keep the middle direct.
Output format
Subject: <line>
<polished email body: warm open, direct middle, courteous close>
Notes: <only if placeholders were inserted or a judgment call was
made; omit this line entirely otherwise>
1---2name: email-polish3description: Rewrite a blunt or rough email draft into a warm, friendly-but-professional version - tone and clarity improved, intent, facts, names, dates, and requests preserved exactly.4---56# Email Polish78## When to use9Use this when you have a rough, blunt, terse, or frustrated email draft and want it to read as friendly but professional - warm, clear, respectful - without changing what it actually says.1011**Not for:** writing an email from scratch when there is no draft or intent to work from (you would have to invent the content); translating between languages; or softening a message whose whole point is to be firm and formal, such as a legal notice or final warning - there, over-warming the tone defeats the purpose. Do not use it to add commitments, dates, or promises the owner did not make.1213## Method141. **Read the draft and extract three things:** the core ask, the key facts (names, dates, numbers, links), and the emotional register.152. **Calibrate formality from the recipient.** *Decision point:* unknown / senior / external -> "Hi Dr. Lee," and no slang; known colleague -> "Hey Sam," relaxed close; recipient unknown -> default to a safe friendly-professional register.163. **Rewrite paragraph by paragraph,** keeping the original structure unless it is genuinely unclear. Warm opening (one friendly line, not gushing), direct middle, courteous close.174. **Preserve every fact verbatim.** Names, dates, numbers, links, requests carry over unchanged. *Decision point:* if a needed detail is missing (a meeting time), insert a clear placeholder like `[time]` rather than guessing.185. **Fix grammar, spelling, and awkward phrasing.** Cut corporate filler ("per my last email", "circling back"). Never let the tone turn passive-aggressive; keep a frustrated draft firm but not sharp.196. **Ensure a subject line exists;** propose one if absent. Match length to the original - a two-liner stays short.2021## Example22**Input (raw):** hey need the report by friday its late again. send it.2324**Output:**25```26Subject: Report - Friday deadline2728Hi [name],2930Hope you're doing well. Quick note - could you get the report over to31me by Friday? It's slipped a couple of times now, so I want to make32sure we stay on track this week.3334Thanks a lot,35[Your name]36```3738## Pitfalls39- **Scope creep.** Adding a promise, apology, or deadline the owner never wrote turns a polish into a fabrication.40- **Padding.** Inflating a two-line note into five paragraphs of pleasantries wastes the reader's time.41- **Guessing missing facts.** Inventing a time or name instead of leaving a marked placeholder.42- **Buried point.** So much warmth up front that the actual ask disappears; keep the middle direct.4344## Output format45```46Subject: <line>4748<polished email body: warm open, direct middle, courteous close>4950Notes: <only if placeholders were inserted or a judgment call was51made; omit this line entirely otherwise>52```