Tone is not mainly about politeness. It is about a handful of measurable patterns that undercut the sentence they appear in. Four categories account for most of it.
Hedges reduce your own claim before the reader can evaluate it:
| Hedge | Effect | Replacement |
|---|---|---|
| I just wanted to ask… | Frames your request as an intrusion | Could you… |
| I think maybe we should… | Two hedges on one idea | We should… |
| Sorry to bother you, but… | Apologises for doing your job | Quick question on… |
| Does that make sense? | Implies you explained badly | Happy to expand on any part. |
| I could be wrong, but… | Pre-discounts your point | Based on the data… |
| Hopefully I can get it done by Friday | Commits to nothing | I will send it Friday. |
Unearned apologies. Sorry belongs with an actual error. Applied to asking a question, following up, or having a boundary, it trains the reader to see your requests as impositions. Following up on a legitimate deadline is not something to apologise for.
Intensifiers — very, really, extremely, absolutely, super — dilute rather than strengthen. Very urgent is weaker than a deadline and a consequence. The same applies to exclamation marks: one can warm a message, four read as anxious.
Passive voice where accountability matters. Mistakes were made says nobody made them. It is genuinely useful when the actor is unknown or irrelevant, but in an email about who does what by when, it is where clarity goes to die.
Before, at 62 words:
Hi, sorry to bother you again! I just wanted to quickly follow up on the report I think I sent over last week — I know you are super busy. If you have any thoughts at all it would be really helpful, but no rush at all obviously. Sorry again for the extra email. Does that make sense? Thanks so much!!
After, at 31 words:
Hi Sam — following up on the report I sent on Tuesday. Could you send comments by Thursday so I can finalise it before the board pack closes? Thanks.
The second version is shorter, easier to answer, and gives the reader a date and a reason. Nothing was lost except the anxiety. Note also what was added: a specific day, a specific deadline, and why the deadline exists. Vagueness is the real problem in most weak emails, and hedging is its symptom.
Stripping every softener produces something that reads as cold or aggressive, which is a different failure with worse consequences. Warmth is not weakness, and there is a real asymmetry — a colleague reads a blunt email in the least generous available tone, because text carries none of the cues that would prevent that.
The distinction worth keeping: relational softeners are good, epistemic hedges are not. Thanks for turning this round quickly, or I hope the week is going well, costs you nothing. I think maybe we could possibly consider undermines your point. Keep the first, cut the second.
Any tool that scores tone is pattern-matching on words, and words are not meaning:
Use a checker as a prompt to reread, not as a verdict. The most reliable test is still to read it aloud and ask whether you would say it that way to the person face to face.
No. It is right when the actor is unknown, when the object is the real subject, or when you deliberately want to avoid assigning blame. It is wrong when it hides who is responsible for the next step.
Be specific and neutral. Name the thing, the date, and the consequence, and leave out adjectives about the situation or the person. Specificity reads as confidence; emotional language reads as escalation.
Lead with the ask or the news. Readers on phones see two lines in preview. Three sentences of pleasantries before the point means the point may never be read.
No. The text you paste is analysed in your browser and nothing is transmitted or logged.
Every tool comes with a written guide, and every category is one click away.