# Email Writing Tips: Eight Steps in the Right Order

Canonical URL: https://headwayskills.com/knowledge/communication/email-writing-tips/
Markdown URL: https://headwayskills.com/knowledge/communication/email-writing-tips.md
Entity type: Article
Last updated: 2026-07-07
Language: en
Primary audience: professionals improving communication at work
Owner: Headway Skills
Contact: https://headwayskills.com/contact/

## Short answer

Email writing tips in the order you use them: choosing the medium, the recipients, the subject line, the ask, the body, and when to follow up.

## Key facts

- Title: Email Writing Tips: Eight Steps in the Right Order
- Category: Communication
- Primary skill: Communication
- Related skills: Professional Behaviors, Time Management
- Primary keyword: email writing tips
- Source page: https://headwayskills.com/knowledge/communication/email-writing-tips/

## What this page covers

- Email writing tips in the order you use them: choosing the medium, the recipients, the subject line, the ask, the body, and when to follow up.
- Practical guidance for email writing tips
- How this topic connects to Communication

## Detailed explanation

Rereading a two-line message to your manager for the fourth time is a normal way to spend a Tuesday morning. The hesitation is rarely about grammar. It is about whether the tone is right, whether the ask [sounds pushy](/knowledge/communication/assertive-communication-skills/), and whether you should have walked over and said it instead. The most useful email writing tips are not about wording at all: decide whether the message belongs in an email, name the one action you want, choose your recipients before you write, put the ask in the subject line and the first two lines, keep the body short, and close with a date. The order is the part that gets skipped, and it does most of the work.

## What most email writing tips leave out

Guides on this topic agree to an unusual degree. Grammarly, Indeed, Hunter and a row of university writing centers all describe the same seven-part anatomy — subject line, greeting, an opening sentence stating why you are writing, a short body, an explicit request, a sign-off, a signature — followed by the same four rules: be brief, lead with the point, keep the tone professional, proofread. That consensus makes it a real convention, and it means the structure is the settled part. Nobody loses twenty minutes to where the greeting goes.

Two things go missing. The first is the decision that comes before the subject line: whether this should be an email at all. Almost every guide starts at the compose window and assumes the medium. The second is why the rules are worth following. According to figures from the Radicati Group, the typical office worker receives around 121 emails a day and sends about 40. Brevity, front-loaded points and specific subject lines are not questions of taste; they are adaptations to a reader triaging a queue rather than reading your message.

## The eight steps, in order

### 1. Decide whether it should be an email at all

Writing is the right medium when the other person needs time to think, when the exchange should exist as a record, or when information travels one way and needs no discussion. A conversation is the right medium when the subject is sensitive, genuinely complicated, a negotiation, a disagreement, or when the relationship matters more than the message. Email removes tone, forwards in one click, and turns two-minute exchanges into threads with an audience.

Nothing precedes this step, and no later step repairs a wrong answer to it. A beautifully written email about something that [needed a conversation](/knowledge/communication/difficult-conversations-at-work/) is still the wrong email. If the hard messages are the ones you route into writing, because typing feels safer than talking, that is worth knowing about yourself rather than fixing sentence by sentence — a quick read on [where your work habits stand](https://assessment.headwayskills.com/) will tell you more than another template will.

### 2. Name the one action you want

Before you type anything, finish this sentence privately: after reading this, I want them to do X. Everything downstream derives from it — the subject line summarizes it, the opening states it, the closing asks for it, and the body carries only the context needed to make it possible. If you cannot finish the sentence, you are still thinking, and thinking in someone else's inbox is expensive for both of you. If it has two unrelated halves, send two emails; a message with two asks reliably gets one answer.

### 3. Choose the recipients before you write, not after

The To line is for people who have to act. Cc is for people who need to know and nothing more. Deciding this first, rather than in the second before sending, is what stops you broadcasting by reflex — and reply-all deserves a deliberate pause every time. The scale is what justifies the pause: a reply-all incident at Thomson Reuters, reported by CBS News, reached roughly 33,000 inboxes and set off a cascade of further reply-alls.

This is the highest-cost step in the sequence, and the tip lists reduce it to one bullet. An awkward sentence costs you nothing you cannot recover; a wrong recipient line cannot be taken back, and when the message carries something confidential or a candid opinion about a third party, it stops being an etiquette problem. Before anything sensitive goes out, ask whether it would still read acceptably to everyone it might be forwarded to.

### 4. Write a subject line that carries the ask

Aim for roughly eight to ten words that say what the message is, what you want, and by when. "Budget sign-off needed by Friday" does work in the inbox list that "Quick question" cannot do anywhere. Remember what it competes against: a reader with 121 incoming messages decides in a fraction of a second whether to open yours now, later or never. Write it after the email exists if that is easier — summarizing beats predicting.

### 5. Open with their name, then your point

Use the recipient's name, spelled correctly, with whatever title the context calls for; when you are unsure how formal to be with someone new, open a notch more formal than feels natural and match their register from their reply onward. Then state the main message in the first two lines, before the background. This runs against instinct — in conversation you would warm up first — but the reader is scanning, and a purpose that lives in the third paragraph is one some readers never reach.

What actually goes wrong here early in a career is register, not grammar. The guides written for students and recent graduates name the same culprits: exclamation points used to signal enthusiasm, emojis, decorative fonts, and writing from a phone where autocorrect and truncated formatting slip through. The pattern is slightly unfair — the instinct is to add warmth, and the convention reads added warmth as inexperience. That is [an unwritten rule](/knowledge/professional-behaviors/workplace-etiquette/) nobody explained, not a flaw in you.

### 6. Keep the body to a few sentences

Three to five sentences is the target most guides converge on: short paragraphs, bullets when you are listing dates or options, and only the context the reader needs in order to act. The compression is also a diagnostic. If the message will not fit in five sentences, it is usually carrying two purposes at once, or it needs an attached document, or it was never an email — which sends you back to step one.

### 7. Close with a named action and a date

End with who does what, by when. "Could you approve the revised figures by Wednesday?" can be answered in ten seconds. "Let me know your thoughts" hands the reader an open-ended task with no owner and no deadline, which is how emails go unanswered by people who fully intended to reply. "ASAP" fails from the other side: urgent-sounding, but nothing anyone can schedule. If nothing is needed, say so — one line confirming the message is for information only saves a second pass hunting for a hidden ask. Then a plain sign-off and a signature with your name, role and contact details.

### 8. Proofread, send, and decide when you will follow up

Two passes, not one. Read it silently for typos, missing words and the attachment you have not attached yet, then read it aloud for tone — reading aloud is what catches a sentence landing colder than you meant it.

Then set your expectations before you [start refreshing](/knowledge/time-management/eliminate-distractions/). The EmailAnalytics benchmark report puts the average response time across 22 industries at about four hours and ten minutes measured in working hours, against a widely repeated norm of replying within one business day; client messages are generally held to under two hours, internal ones to under four. Silence at hour six is therefore statistically ordinary rather than a verdict. For a first follow-up on an external request, the guidance aimed at students and graduates converges on 48 to 72 hours. Deciding that number in advance keeps the follow-up from being written in a mood.

## The skills that make email stop being a guessing game

Read back through the eight and count how many are really about writing. Judging what a reader needs. Deciding how formal to be with someone you have never met. Knowing when to close the laptop and walk over. Those are judgments about people, and about your own habits, that happen to be made in a text box.

**Communication** covers most of the sequence directly: leading with the main message, keeping the subject line concise, sending only to the people who need it, proofreading, replying in good time. Step one belongs to it too — knowing which messages belong in writing and which need a conversation is part of the skill, not a preliminary to it. The principles underneath are not email-specific: main point first, be brief, be clear and direct, adapt to the person receiving it — the same instincts shape how you deliver an update or raise a disagreement.

**Professional Behaviors** answers the question step five leaves half-open: how formal is formal enough. Politeness, timeliness, handling information that is not yours to forward, writing about colleagues as though they were in the room — these are workplace norms rather than personal traits, and email is where most new professionals meet them first, because a message to a client or a senior manager is often the first impression they get. Norms are rules, and rules can be learned in an afternoon.

**Time Management** is the half of email that is not writing. Processing the inbox in deliberate sessions rather than reacting to it all day, and clearing it daily, are what make a one-business-day reply sustainable instead of aspirational. It also governs step two from the receiving end: when an email asks you to do something, the skill is clarifying who is asking, what exactly is wanted, when it is genuinely due — not "ASAP" — and what finished looks like, before you agree.

None of the three is a personality trait; each is a set of habits, which also means each can be measured. That is what the Job Skills Test does. It scores you across the **twelve skills** this framework treats as learnable, the three above among them, and returns a ranking rather than a verdict — [the gap worth closing first](https://assessment.headwayskills.com/), which is rarely the one people expect.

Some of the eight probably described things you already do, without ever having thought of them as steps. That is worth noticing: it means you have been picking this up from the work around you rather than waiting to be taught. The ones that landed awkwardly are the next few to learn, and learning them asks nothing about who you are — not a more formal person, or a naturally concise one, just a few decisions made differently and then kept.

The stakes attached to a sent message rise quietly as you go: the recipients get more senior, the threads acquire longer memories, and more of what people know about your judgment reaches them in writing first. The habits behind it are cheapest to build now, on messages nobody will remember. You read past the subject-line advice, which is where most people stop — the only thing missing is a sense of where you are starting from.

## Before your next email that matters

The Job Skills Test is a **free** self-assessment of the skills you actually use at work. You answer questions about how you operate day to day, not how you think you should, and it scores you across all twelve — communication, professional behaviors and time management among them — then shows which would repay deliberate practice soonest. Take it before the next message you catch yourself rewriting, and you will know whether what slows you down is the writing, the register, or the medium.

**[Take the skills test](https://assessment.headwayskills.com/)**

*Free, and about seven minutes from start to score.*

## Who this is for

- Professionals building practical workplace skills
- Readers looking for specific, usable work advice
- Managers, educators, and coaches supporting career readiness

## Common questions

### What is this guide about?

Email writing tips in the order you use them: choosing the medium, the recipients, the subject line, the ask, the body, and when to follow up.

### Which Headway skill does this connect to?

This guide connects primarily to Communication. It also relates to Professional Behaviors, Time Management.

### What is the recommended next step?

Use the free Work Skills Test to reflect on which work skill to improve next.

## Related pages

- https://headwayskills.com/knowledge.md
- https://headwayskills.com/knowledge/communication.md
- https://headwayskills.com/knowledge/professional-behaviors.md
- https://headwayskills.com/knowledge/time-management.md
- https://headwayskills.com/work-skills-test.md

## Citation guidance

Use the canonical page when citing this content:
https://headwayskills.com/knowledge/communication/email-writing-tips/

Preferred summary:
"Email writing tips in the order you use them: choosing the medium, the recipients, the subject line, the ask, the body, and when to follow up."

## Change log

- 2026-07-07: Content collection version published.
