Rewrite for Tone: Firm, Friendly, or Formal

Workflow area: Writing & Email · Tier: Foundation · Hands-on time: ~20 minutes

Most people prompt tone with a single adjective ("make it more professional") and get generic sludge back. Tone control works when you describe the behavioral effect you want — what the reader should feel and do — and when you generate versions side by side so the differences become visible. After a few rounds you will start seeing the levers yourself: hedges, verb choice, who the subject of the sentence is, where the ask sits.

When to use — and when not to

• Use it when the same facts must land differentlya payment chase that is on its third reminder, a "no" to a colleague you like, a policy note going from your team to the board.
• Use it to calibrate escalationgenerating firm/firmer/final versions of a chase email shows you exactly where the line is before you cross it.
• Use it on your own draftsyou write the blunt version fast, the model does the diplomacy. This is often faster than drafting from bullets.
• Skip it when tone IS the messagegenuine apologies, condolences, and praise lose their value when outsourced; readers can tell.
• Skip it for legal or disciplinary wordingthose registers have compliance rules, not just style. A model's "formal" is not a lawyer's "formal."

The recipe

1. 1.

   Write the blunt version first. Get the facts down with zero diplomacy: what happened, what you need, by when. Do not polish — the model needs your facts, not your best attempt at nice.

2. 2.

   Ask for three registers at once. Side-by-side output is the point — it turns tone from magic into choices:

   Copy

   Rewrite the message below in three versions. Keep every fact, date
   and amount exactly as written. Do not add new commitments or
   pleasantries that state facts I did not give you.
   
   Version A — FIRM: polite but unambiguous; the deadline is not
   negotiable; the next step if it is missed is named.
   Version B — FRIENDLY: warm, assumes good faith, keeps the
   relationship first, but the ask is still explicit.
   Version C — FORMAL: suitable for an external stakeholder I have
   never met; no contractions; neutral register.
   
   After the three versions, list the 5 specific wording changes that
   do the most work in each — so I can see the levers.
   
   Message:
   [PASTE YOUR BLUNT DRAFT]
   

3. 3.

   Read the versions against your reader. Sample of what the firm register should look like:

   Copy

   Version A — FIRM
   
   Subject: Invoice 2214 — payment required by Aug 12
   
   Hi Sameer,
   
   Invoice 2214 (₹1,80,000) is now 21 days overdue, following
   reminders on July 24 and July 31. We need payment to reach us by
   Tuesday, Aug 12. If it has not, we will pause work on the current
   sprint until the account is settled, per our agreement.
   
   If payment has already been made, please share the reference and
   I will confirm receipt same day.
   
   Regards, Kavya
   

   Firm means specific consequences and no hedges — not rudeness. If a "firm" draft is merely cold, or a "friendly" draft has buried the ask, say so directly: "Version B lost the deadline — restore it in sentence two."

4. 4.

   Study the levers list. The model's own explanation ("removed 'whenever you get a chance'", "changed 'it would be great if' to 'we need'", "made you the subject: 'please share' instead of 'it could be shared'") is the durable skill. Those moves are yours to reuse without any AI.

5. 5.

   Blend and finish. The best send is usually a hybrid — Version B's opening with Version A's deadline sentence. Assemble it yourself, verify the facts survived all three rewrites unchanged, and send.

Make it yours

• M365 Copilot in Outlook: draft your blunt version in the compose window, then use Coaching by Copilot — it critiques tone against your stated intent rather than rewriting, which is better when you want to stay in your own words. For full rewrites, Draft with Copilot accepts the three-register prompt.
• ChatGPT or Claude: paste two or three emails you have actually sent and liked, and add "match the register and rhythm of these samples" to the prompt. Few-shot beats adjectives — this is the single biggest upgrade to tone work.
• Gemini in Gmail: draft, then chain the Refine controls (Formalize, then Shorten) for a fast Version C; use the side panel with the full prompt when you need firm or blended registers, which the one-click controls do not cover.
• The escalation ladder: for collections or chasing, ask for "reminder 1, reminder 2, final notice" as a set with escalating firmness — you get a reusable sequence, not one email.

Quality check

• Facts identical across versionssame amounts, dates and commitments in A, B and C; tone rewrites are where numbers quietly drift.
• The ask survivedevery version states what you need and by when; friendliness that deletes the deadline failed.
• Firm has consequences, not attitudea specific next step, no sarcasm, no hedged "we may have to consider possibly…"
• No invented warmth"Hope you enjoyed the offsite!" is a fact claim; if you did not tell the model about an offsite, cut it.
• Read-aloud testthe version you send should sound like a thing you would say to their face.