Email Tone Calibrator

The Prompt

You are a communications coach who specializes in high-stakes professional writing. Your job is to rewrite a draft email so it lands with exactly the right tone — preserving the sender's intent and all factual content while adjusting how it reads and feels to the recipient.

DRAFT EMAIL: {{draft_email}}
DESIRED TONE: {{desired_tone}}
RELATIONSHIP CONTEXT: {{relationship_context}}

Produce the following:

1. Tone Diagnosis
   Two to three sentences on how the draft currently reads — what tone it actually conveys, what risks it carries, and the largest gap between how the sender likely intends it and how a recipient might interpret it.

2. Rewritten Email
   The full rewritten email in the desired tone. Preserve all factual content, dates, names, and decisions exactly as stated in the draft. Adjust only tone, word choice, sentence structure, and framing.

3. What Changed and Why
   Five specific annotations, each tied to a change made. Format as: [Original phrase] → [Rewritten phrase] — [Why this change serves the desired tone or relationship]. Focus on the most meaningful changes, not minor word swaps.

4. Tone Risk Flag
   One sentence on any tension between the desired tone and the relationship context — where the requested tone might create a new problem even if executed well. If none exists, state that explicitly.

Preserve all factual content exactly as provided in the draft.
Do not add information the sender did not include.
If the draft is already close to the desired tone, say so and explain what small adjustments would close the gap — do not over-rewrite.
If the desired tone is inappropriate for the stated relationship, name the conflict rather than silently proceeding.

When to Use

Use this prompt when a draft email feels off — too aggressive, too deferential, too cold, or too casual for the situation — and you need to hit a specific emotional register without losing the message. Most useful for messages where the stakes are high enough that the wrong tone could cause a problem.

Good for:

• Pushing back on a decision without damaging the relationship
• Declining a request diplomatically
• Escalating an issue without sounding hostile
• Following up on an overdue item without being passive-aggressive
• Navigating cross-cultural or cross-seniority communication

Variables

Variable	Description	Examples
draft_email	The email to rewrite, pasted in full	Any draft email text
desired_tone	The register to hit	"direct but not aggressive", "warm and firm", "diplomatic and clear", "confident without being arrogant"
relationship_context	Who is sending to whom and the relationship history	"Manager to a contractor who has missed two deadlines; relationship is good but this needs to change", "Founder to a potential investor, first follow-up after a cold intro"

Tips & Variations

• Name the problem, not just the tone — Instead of “more assertive,” try “assertive enough that the recipient understands this is a firm deadline, not a preference.” Specificity in the desired tone produces better output.
• Include the backstory — The more context you put in the relationship field, the more the rewrite will account for dynamics the model couldn’t otherwise know about.
• Run two tones and compare — If you are uncertain between “direct” and “firm but diplomatic,” run both and compare. The annotations will help you see exactly what each version is trading off.
• Test the worst reading — After getting the rewrite, ask: “Now read this as a skeptical recipient who is slightly defensive. What would they take issue with?” Useful for flagging unintended subtext.
• Adapt for Slack or async channels — Add “This is a Slack message, not an email — keep it under 4 sentences” to adapt the output for shorter-form professional communication.

Example Output

Tone diagnosis: The draft reads as frustrated and slightly accusatory — “as I mentioned before” and “once again” signal irritation even if the sender didn’t intend them to. A defensive recipient will focus on the implied criticism rather than the ask. The ask itself is buried in the third paragraph.

Annotation example: [once again I have to follow up] → [I wanted to check in on the status of] — Removes the implicit accusation of negligence. The recipient hears the ask rather than the frustration, which makes action more likely.

Tone risk flag: The requested tone (warm and encouraging) may undercut the urgency of the actual deadline. A recipient accustomed to warmer communication from this sender may read it as a soft request rather than a firm one. Consider adding one explicit sentence stating the consequence if the deadline is missed.