Email tone checker: catching the line that reads wrong

Re-reading an email five times catches typos. It does almost nothing for tone.

Tone and spelling are different problems. Proofreading your own writing for meaning is unreliable, because you already know what you meant to say.

The email tone checker exists for the gap re-reading leaves behind. It's a second pair of eyes that doesn't get tired after the third pass.

The fifth re-read never catches tone

Proofreading your own work is unreliable for a specific reason. You read what you intended to write, not always what's actually on the page.

That's true for spelling. It's also true for tone, which is easy to misjudge when you already know what you meant.

A phrase like "just following up" can read as a gentle nudge. Or it can read as mild criticism, depending entirely on the reader.

You can't always predict which one lands, especially with someone new or senior to you.

If you've ever sent an email and worried about it all day, that worry usually isn't about spelling. It's tone, and re-reading alone won't settle it.

What the checker actually flags

Paste your draft in, and the tool checks for four things. Curt phrases, like "as per my last email" or "please advise." Passive constructions that hide who's responsible, like "it has been decided."

It also checks for long sentences over 28 words. And it checks for workplace jargon, like "circle back" or "touch base."

Each flagged phrase is highlighted in your text. You get a plain-English note on why it might land badly, and a suggested alternative.

Nothing is stored or sent to a server. It's safe to paste a real draft, including the awkward one you've been sitting on all afternoon.

A worked example

Take this short draft: "Just following up on the report. As I mentioned on the call, please advise on next steps. Obviously this needs to be resolved before Friday."

Four sentences. Four flags.

The tool marks this "Worth reviewing" because two flagged phrases are high severity. "As I mentioned" implies the reader wasn't paying attention. "Obviously" implies they should already know.

Both are easy to write without noticing. Both are easy to soften once flagged.

None of these phrases are dramatic alone. Stacked together in one short email, they shift the whole tone toward impatient.

The three scores explained

Clarity measures long sentences, passive voice, and jargon. A high score means your point is easy to find.

Warmth measures a rough balance of warm words, like "thanks" and "appreciate", against cold ones, like "obviously" and "should have."

Reading age is a rough Flesch-Kincaid estimate. It shows whether your draft matches how you'd want it read.

Use the scores as a quick check before sending, not a target to chase. Your real voice matters more than a perfect score.

The fixes that come up most

Two changes fix most flagged emails. First, cut softeners like "just" and "kindly" — they often read as apologetic rather than polite.

Second, name who's doing what. Swap "it has been decided" for "I've decided" or "we've agreed." That single change removes most passive-voice flags at once.

Fix the two or three flagged lines that matter most, then send. You don't need a perfect score to hit send with confidence.

What this means for you

If your usual pattern is reading an email five or six times before sending, try the tool after the second read instead. It catches a different kind of problem than re-reading does.

If tone anxiety costs you real time most weeks, the masking cost calculator can put a number on it.

The reasonable adjustments email builder can also help. Use it if the real fix is support at work, not just a better tool.

Use the second pair of eyes before you send. That beats worrying about the email for an hour after it's already gone.