Free to read · no account needed

18 min · writing

Take email from correct to polished with Claude

Goal: keep your facts, upgrade tone and structure so the mail is sendable.

Best for: Claude chat. Ideal when the draft is already “right” but stiff, long, or slightly off-relationship.

Correct is not enough for relationship email. Claude is strong at tone polish—after your facts and offers are frozen.

Why beginners skip this

Polishing before facts are frozen shines the wrong message. Correct → clear → polite, with one ask—read aloud before send. Mid-week cost shows up as rework, not as a missing bookmark.

The three-layer ask

1. Facts freeze — what must not change 2. Relationship — who they are to you 3. Polish — length, warmth, directness

Goal: Revise this email so it is ready to send.
Relationship: [manager / peer / vendor / executive I rarely email]
Must keep: [decision, dates, ask]
Tone: clear, respectful, no flattery, no corporate sludge.
Format: subject ≤7 words; body ≤140 words; one explicit ask; optional 3-bullet next steps.
Boundaries: Do not add new commitments. Mark any assumed date with [?].

Draft:
---
[paste]
---

Variants — say no / chase / apologize

Example

Filled prompt

Goal: Revise this email so it is ready to send.
Relationship: peer PM I work with weekly
Must keep: delay Friday launch by one week; need freeze date from eng
Tone: clear, respectful, no flattery
Format: subject ≤7 words; body ≤140 words; one explicit ask
Boundaries: Do not add new commitments. Mark assumed dates with [?].

Draft:
---
Hey, so launch might slip, can you sync with eng whenever? Thanks!!!
---

What good output looks like

  • Subject names the artifact (e.g. “Launch delay — freeze date?”)
  • Body ≤140 words with exactly one clear ask
  • No invented freeze date, launch %, or new promises
  • Tone stays calm—neither stiff corporate nor over-familiar slang
  • Facts match your notes line for line with no cheerful padding

Decline

Same facts. Soften the no without leaving a loophole. Offer one alternative time window or resource. ≤100 words.

Chase

Rewrite as a polite bump. Reference the prior ask in one line. New subject that includes the artifact name. No guilt language.

Apology

Acknowledge the miss in one sentence, state the fix, give the new date. No over-apology. No blame on others.

Diff view (optional)

Example

Filled prompt

Email facts: delay 3 days, cause = warehouse backlog, offer CODE-WAIT 10% (approved).
Pass 1: correct facts only. Pass 2: polish tone. Never invent refund. Draft only.

What good output looks like

  • One-sentence miss + concrete fix + new date
  • No “so so sorry” pile-on, emoji flood, or dramatic guilt trip
  • No blaming another team or hiding the miss behind soft language
  • Ask stays singular and actionable (person + decision + timing)
  • Fits a skim on a phone screen in under twenty seconds
Return: (1) revised email (2) bullet list of what you changed and why (max 5 bullets).

You decide which edits to keep.

Correct before polish

Polish on wrong facts is expensive theater. Freeze the factual skeleton first.

Check the unknown path

What should the model do when a field is missing—null, TBD, or ask you? Write it once in Boundaries.

Subject carries the artifact

Vague subjects (“Quick question”) die in mobile inboxes. Name the thing and the decision (“Launch delay — freeze date?”). The body then only needs the ask and the frozen facts.

Example

Filled prompt

Live artifact this week for: keep your facts, upgrade tone and structure so the mail is sendable.
Name real files/people. No invented facts; label Unknowns; stop before send/delete.
Return working prompt + one pass/fail check I can mark in a minute.

What good output looks like

  • Pulls from Project/file named in the ask for “Take email from correct to polished”
  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good”
  • One-minute check: does output match claude-email-from-correct-to-polished Done?
Example

Filled prompt

Pass1: 1-day delay, backlog, CODE-WAIT approved.
Pass2 polish. Draft only. No extra coupons.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.

What good output looks like

  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good”
  • One-minute check: does output match claude-email-from-correct-to-polished Done?
  • Pulls from Project/file named in the ask for “Take email from correct to polished”

Red flag

Polishing wrong facts; mass-send without a read-aloud; politeness layer adding new promises—freeze facts first.

Save this card

Card: Correct facts first, polish second; one ask; no invented dates or blame—check it once this week, or it stays a bookmark. Keep this beside the tool; read before you start.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Open the Claude Project you will keep. Confirm standing instructions + the knowledge file for “keep your facts, upgrade tone and structure” are current. Guide: claude-email-from-correct-to-polished. If you only have a blank practice box, stop and fetch the real job first.

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week in Claude: take one correct-but-stiff email—fix pass first, polish pass second, one ask only. No invented dates. Save both versions on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed claude-email-from-correct-to-polished, put 25 minutes on the calendar and redo once.

Pitfalls

  • Letting Claude invent a meeting time → Boundaries
  • Warmth that sounds fake → specify relationship honestly
  • Endless regenerations → change one constraint per retry
  • Extra pitfall: treating the bookmark as the practice—open a live artifact, run Practice now, and date a pass/fail (Asia/Shanghai).

Common pitfalls

PitfallFix
Repasting FAQ every chat — claude-email-from-correct-to-polishedPut standing instructions + one knowledge file in Project
“Summarize the PDF” with no ledgerDecision ledger: quote or Unclear
Deep thinking on every polishSave deeper mode for real tradeoffs

Practice now

Live card: take one correct-but-stiff email; polish tone without changing facts; Blind-pass before send (Asia/Shanghai).

Today: write a delay email with subject naming the artifact, body ≤140 words, one ask, no invented freeze date. Then write a miss-acknowledge: one sentence miss + fix + new date—no apology pile-on.

Today card (copy) — claude-email-from-correct-to-polished: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Correct facts first, polish second; one ask; no invented dates or blame—check it once this week, or it stays a bookmark

  • You can point to a dated refuse-line
  • You have one artifact path from tonight
  • You can teach the red flag in one sentence

Next

Long document pass · Writing path · Claude Projects · Style guides that stick · Draft & revise

Pair with today: open the first Next link (claude-long-document-pass) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start