The 90-Second Self-Editing Workflow I Use Before Sending Any Important Email

I’m Bryan Collins. I’ve been editing my own writing — business emails, newsletters, client drafts — for over seven years. I’ve made every mistake on the list below. This is the 90-second protocol I run before I send any email I’d be embarrassed to get wrong. It works the same whether English is your first language or your fifth.

TL;DR: Before you press send on an important email, run a five-step pass that takes around 90 seconds for a four-paragraph message. Read it out loud. Cut filler words. Swap passive voice to active where it tightens the sentence. Check the tone with one quick question. Paste the draft into an AI editor for a second opinion. The protocol catches the mechanical errors that make smart people sound unsure of themselves.

Why 90 Seconds, Not 90 Minutes

You are not a copywriter. You are a working professional with twelve more emails to write before lunch. Any self-editing routine that takes longer than the email itself gets skipped — and skipped routines do not protect your reputation.

The 90-second protocol fits into the gap between “draft ready” and “click send”. It catches what managers and clients notice: confusing structure, buried requests, hedged tone, passive sentences that sound evasive.

Run it on emails where the cost of a misread is high — status updates to senior leaders, replies to clients, anything you’d be embarrassed to see quoted back. Skip it on quick internal chat.

Step 1: Read It Once Out Loud (10 Seconds)

Read the whole email out loud, at normal speaking speed, before you touch anything.

Your ear catches awkward phrasing your eye glides over. Long subordinate clauses, missing words, repeated words, and sentences that loop back on themselves all sound wrong when spoken — even when they look fine on screen.

A sentence like “I wanted to reach out to follow up on the email I sent last week about the report that we discussed in the meeting” reads almost normal silently. Out loud, you hear three layers of throat-clearing before the actual point.

If you cannot read a sentence in one breath, it is too long.

Step 2: Cut Filler Words (20 Seconds)

Search your draft for these and delete them where the meaning survives:

• really, very — cut, or replace with a stronger word
• actually, basically — usually filler
• kind of, sort of — vague; cut or be specific
• in order to → to
• at this point in time → now
• due to the fact that → because

Before:

I really wanted to reach out in order to actually confirm that we are basically on track for the Friday deadline.

After:

I wanted to confirm we are on track for the Friday deadline.

Twenty-one words become twelve. Nothing of substance is lost.

Step 3: Swap Passive to Active Where It Tightens the Meaning (20 Seconds)

Passive voice puts the action before the actor. Active voice puts the actor before the action.

• Passive: “The report was reviewed by the team.”
• Active: “The team reviewed the report.”

Active sentences are shorter and tell the reader who is responsible — which is usually what business email is about.

If your first language uses passive constructions for politeness or formality (academic Romance-language English is a common pattern), this step catches the most cases. Look for “was [verbed] by”, “has been [verbed]”, “is being [verbed]”. Most flip to active without changing meaning.

Keep the passive when you genuinely do not know or do not want to name the actor: “A decision will be made next week” is fine when the decision-maker is not the point.

Step 4: Check the Tone (20 Seconds)

Ask yourself one question:

If my manager read this in five seconds, what would they think I am asking for?

If the answer is not clear in five seconds, the request is buried in hedging.

Before:

I hope this email finds you well. I was wondering if it might be possible, when you have a moment, for you to take a look at the attached draft and let me know your thoughts whenever convenient.

After:

Could you review the attached draft by Thursday? I need your sign-off before sending to the client.

The second version is not rude. It is clear. Clear is respectful — it lets the reader know exactly what you need and by when.

Step 5: Paste Into an AI Editor for a Second Pass (20 Seconds)

Two tools are worth keeping open while you write:

• Grammarly — catches grammar, punctuation, and tone drift in real time. Its tone detector tells you whether your email reads as confident, neutral, or hesitant.
• Claude or ChatGPT — catches structural issues Grammarly misses. Paste your draft with the prompt: “Read this business email and tell me, in five seconds, what I am asking for. Then suggest one structural change.” A free-tier account covers a few daily edits.

The protocol works without these tools. They add a second pair of eyes that does not get tired at 4pm.

For a deeper checklist to run after Step 5, see common email mistakes non-native speakers make.

A Full Before-and-After Example

Aditi drafts an email to her project sponsor, checking in on a delayed deliverable.

Before (the draft):

Hi Marcus,

I hope this email finds you well. I wanted to quickly reach out in order to follow up on the status of the Q2 analytics report that was discussed in our meeting last week. I am really sorry to bother you, but I was wondering if there had been any updates.

As you may be aware, the report was originally supposed to be delivered by the end of last week, and it has been mentioned that there were some delays due to the fact that the data team was waiting for inputs from the regional offices.

I would really appreciate it if you could possibly let me know when we might be able to expect the report, as it is basically needed for the steering committee presentation that is scheduled for next Tuesday.

Thank you so much for your time and patience.

Best regards, Aditi

After (90-second pass applied):

Hi Marcus,

Checking in on the Q2 analytics report. [Cut over-apology and filler opener — Step 2.]

I know the regional offices were holding up the data team last week. [Active voice, shorter — Step 3.] Do you have an updated delivery date?

I need the report by Monday morning for the steering committee on Tuesday. [Direct request with deadline — Step 4.]

Thanks, Aditi

The rewrite is 47 words, down from 134. Marcus now knows in five seconds what Aditi needs and by when. Aditi sounds calm and in control.

What This Protocol Won’t Catch

The protocol catches mechanics, not strategy.

It will not tell you whether the email should be sent at all, whether email is the right channel, or whether your manager’s manager needs to be copied. It will not catch political nuance — the unwritten rules about who gets credited, who gets challenged, and how directly you can push back on a senior person.

For those calls, you need context the protocol cannot give you: who the reader is, what they care about, and what the email is really for. Run the protocol on every important email. Run a strategy check on the ones where the stakes are highest.