How to Write Better Emails: Subject Lines, Length, and Formatting That Gets Read

Most people write dozens of emails a week without ever stopping to ask whether those emails are actually working. The recipient opened it but did not reply. Or replied but missed the main question. Or skipped it entirely because the subject line looked like noise. Email is so routine that its problems stay invisible until something goes wrong: a missed deadline, a confused colleague, a client who never got back to you. The fix is almost never about writing talent. It is about structure, length, and the first seven words your reader sees.

Why Most Emails Fail Before They Are Opened

Your email lives or dies in the preview pane. Most email clients show the sender name, the subject line, and a short snippet of the first sentence - typically 60 to 100 characters of body text. That is all the reader sees before deciding whether to open, skip, or delete. If your subject line is vague, your email is competing with dozens of others that are equally vague. It loses.

The most common subject line mistakes are easy to name: they are too long, too generic, or bury the point. "Following up" tells the reader nothing. "Question" tells them slightly more but still nothing actionable. "Hi!" is actively harmful. Compare those to "Invoice 204 - due Friday" or "3 questions before Thursday's call" or "Updated project timeline - please review." The difference is specificity. A good subject line tells the reader exactly what the email is about and, where relevant, what they need to do with it.

The Right Length for a Subject Line

Most email clients truncate subject lines between 50 and 70 characters on desktop, and around 30 to 40 characters on mobile. That means your most important words should appear first. Front-loading the topic - not a greeting, not "RE: RE: RE:" chains, not your company name - puts the relevant information where the reader's eye lands.

A useful test: read just your subject line and ask whether a stranger could understand the purpose of the email. If the answer is no, rewrite it. Aim for under 50 characters when you can. Brevity signals respect for the reader's attention.

When to Use RE: and FWD:

Reply threads accumulate prefixes until a subject line reads "RE: RE: FWD: RE: Meeting notes." This is mostly harmless in a tight conversation between two people, but it becomes a problem when the thread changes topic or needs to be forwarded to someone new. When the subject drifts from the original, start a new thread with a new subject line. Clarity matters more than keeping the reply chain intact.

Getting Email Length Right

There is no universal correct length for an email, but there is a useful rule: an email should be as long as the task requires and no longer. The problem is that most emails are longer than necessary. People pad them with context the recipient already has, hedge every statement, repeat the subject in the opening line, and close with three paragraphs of pleasantries before getting to the point.

A rough benchmark for everyday professional email: if the email takes more than 60 seconds to read, it is probably too long, or it is covering more than one topic and should be split. Emails that need a scroll to reach the action item are emails that get deferred or forgotten.

Word count is a rough proxy, but sentence count can also reveal a lot. A five-sentence email that uses 40-word sentences is harder to read than a ten-sentence email with tight, direct clauses. If you want to check the sentence structure of an email before sending, a sentence counter can show you exactly how many sentences your draft contains and flag any that run unusually long.

How to Match Length to Purpose

A quick question or confirmation deserves a short reply - sometimes one sentence. An email that opens a project, explains a complex decision, or introduces someone to a new situation can be longer, but it should still follow structure: one paragraph of context, the key information, and a clear ask or next step. Informational emails with no action item are often better sent as documents or shared notes with a one-line email linking to them.

If you find yourself writing long emails often, the problem is usually one of three things: you are including information the reader does not need, you are uncertain what you want from them, or the email format is the wrong tool for the job. A five-minute call handles what ten emails cannot.

Formatting for Clarity and Fast Reading

Most professional emails are read in a split-second scan before the reader decides whether to engage fully. Good formatting supports that scan. Poor formatting forces the reader to hunt for what matters.

The most useful formatting habit is visual separation. Short paragraphs - two to four sentences - with a line break between them are easier to skim than one dense block of text. Each paragraph should carry one idea. If you find a paragraph covering two distinct points, split it.

When to Use Bullet Points

Bullet points work well for lists: action items, options being presented, or steps in a process. They break parallel information out of prose so the reader can compare or reference each item individually. Where bullet points fail is when writers use them to replace reasoning. A bullet that says "Consider timeline" without explanation is less useful than a sentence that says "The current timeline gives us three working days to review, which may not be enough."

A practical rule: use bullet points for items that genuinely belong in a list. Use prose for reasoning, context, and explanation. Mixing the two - a long preamble followed by a list of bullets followed by more prose - is fine, but overloading an email with bullets fragments it and makes it look like a checklist rather than a communication.

Bold Text and Emphasis

Bold is useful for highlighting the most important information in an email - a deadline, a decision point, a specific number. Used sparingly, it draws the eye exactly where you need it. Used constantly, it loses meaning and makes the email visually noisy. As a rule, bold no more than one or two phrases per email, and only when the reader genuinely needs that emphasis to act correctly.

Greetings and Sign-Offs

How you open and close an email carries more social weight than the content, even though it takes the least time to write. "Hi [Name]," is almost universally appropriate for professional email. "Dear Sir or Madam" signals a form letter. "Hey," is fine internally with colleagues you know well; less so with clients or external contacts you have never met.

Sign-offs follow a similar pattern. "Best," "Thanks," and "Kind regards" are all safe choices that neither pull focus nor read as overly formal. What to avoid: lengthy closing paragraphs that repeat the ask you already made, or email signatures that are longer than the email itself. A signature with your name, title, and one contact link is all most people need.

Cleaning Up Text Before You Send

One underappreciated source of email quality problems is copy-pasted text. When you draft in a word processor or notes app and paste into your email client, hidden formatting often comes with it: smart quotes that render as question marks on older systems, curly apostrophes that paste as garbled characters, line break characters that interrupt your paragraphs mid-sentence, or bold and italic styles that clash with the email client's default font.

The simplest fix is to paste into a plain text intermediary first - a basic text editor - and then copy from there into your email. This strips most hidden formatting automatically. If you write in rich text and find that pasted content keeps picking up unwanted styles, a dedicated tool for removing text formatting can help you strip styles cleanly without losing your content.

Removing Line Break Problems

A related issue is broken line breaks. If you draft an email in a plain text editor and paste it into a rich-text email client, the hard line breaks at the end of each line often become forced line breaks in the email body. The paragraph flows normally in your editor but arrives with a new line after every 80 characters, making it look like a typewriter output. If you run into this pattern, a line break remover can strip those extra breaks so the text wraps naturally in the email client instead.

Editing with Find and Replace

If you send templated or recurring emails - outreach, status updates, invoices, announcements - find and replace is one of the most underused tools in your workflow. You can replace every instance of a placeholder like [CLIENT NAME] or [DATE] in one pass rather than searching manually. You can also use it to catch and fix specific phrases you overuse, like "just checking in" or "as per our last conversation," by searching for them across a draft and replacing them with something more direct.

Use the Find and Replace Tool to make those edits in bulk before pasting the final text into your email client.

Putting It Together: A Pre-Send Checklist

Before you send any important email, it helps to run through a short checklist. The subject line should be specific enough that the reader knows what the email is about before opening it. The first sentence should get directly to the point. The body should cover one topic, or clearly separate multiple topics if more than one is necessary. The action item - what you need the reader to do - should be unambiguous and easy to find. And the text should be free of pasted formatting issues, broken line breaks, or AI-generated phrasing that reads as generic and flat.

This checklist takes under a minute to run through. Most email problems either do not exist or get caught in that minute.

When Email Is the Wrong Tool

One more thing worth saying: email is often the wrong tool for what people are trying to do with it. If a decision requires back-and-forth, a call or a shared document with comment threads is faster. If you are documenting something for future reference, a shared folder or wiki page is more findable than an email thread. If you are coordinating tasks across a team, a project tool handles it better than CC lists.

This does not mean avoiding email. It means recognizing when you are reaching for email out of habit rather than because it is the right fit. The emails you send when you have thought about format tend to be shorter, clearer, and more likely to get a useful response.

Summary

Better emails start with better subject lines - specific, front-loaded, and short enough to read in a mobile preview. They are only as long as the message requires, which is usually shorter than a first draft suggests. They use visual separation and selective formatting to support scanning rather than forcing the reader to dig for the point. And before they go out, they are clean: free of broken formatting, repeated phrases, and buried action items.

None of these habits require talent. They require a moment of intentional editing before you hit send. Over time, that moment becomes automatic, and the quality of your communication - and the responses you get - improves accordingly.