When people are moving between tasks, they may read only the first lines of an email before deciding what needs attention. A message can contain all the right information and still be hard to act on if its purpose is buried, its request is vague, or its deadline is easy to miss. A scan-friendly email does not need special formatting or a dramatic subject line. It needs a clear order: say why you are writing, state what the reader should do, and then provide the details needed to do it.
The useful bits
- Put the purpose and requested action in the opening lines.
- Give each separate detail its own short paragraph.
- Write deadlines as a specific date, time, and time zone when applicable.
Lead with the reason and the request
Start with the point of the message, not the history behind it. In the first sentence, name the topic or decision. In the next, say what you need from the reader. This lets someone scanning the preview understand whether the email calls for action, a decision, or simply awareness.
Use a specific verb such as review, approve, send, or choose. If you need more than one action, say so plainly rather than making the reader infer it from a description of the situation. Keep background information, explanations, and context for later paragraphs.
Subject: Review the revised event schedule Hi [Name], Please review the revised event schedule and tell me whether the [session time] works for your team. I’ve noted the change and the response deadline below.
Make the action easy to locate
A request can be brief and still be unclear. Identify the item the reader should act on, the kind of response you need, and who should provide it. For example, “Please review the attached draft and send any corrections” is more actionable than “Thoughts?”
If the reader has a choice to make, list the available options in a sentence or separate lines. If you need a particular format, mention it: a yes-or-no reply, corrected text, or a selected option. Avoid placing the actual request after several paragraphs of explanation.
Give each detail room to register
Use short paragraphs to separate different jobs the email is doing. One paragraph can state the request; another can explain what changed; a third can tell the reader where to find the relevant file or information. A paragraph should carry one main idea, so a reader can pause and resume without losing the thread.
When a message has several distinct details, label them with a few descriptive words or use a compact list. Keep labels useful rather than decorative. A reader should be able to skim the first words of each paragraph and still understand the sequence.
- What changed: [brief description].
- What to review: [document or section].
- What to send back: [specific response].
Put background after the action
Context matters, but it should support the request rather than hide it. After stating what you need, explain only the background that helps the reader respond. If there is a longer history, summarize the relevant point and identify any material the reader can consult separately.
Check that each detail answers a likely question: What is different? Why does it matter? Where is the item? If a sentence does not help the reader understand or complete the request, consider removing it or moving it to a separate message.
Make the deadline unmistakable
Do not rely on phrases such as “soon,” “by end of day,” or “when you get a chance” when timing matters. State the date and, if useful, the time and time zone. “Please reply by [date] at [time] [time zone]” is easier to interpret than a relative phrase, especially when people are in different locations or read the email later.
If the timing is flexible, say that too. For instance, give the preferred date and explain whether a later response is workable. Keep the deadline close to the requested action so it is not lost among background details.
Please send your approval by [Tuesday, April 14] at [3:00 p.m. Eastern Time]. If that timing is not workable, tell me when you can respond.
Do a scan test before sending
Read only the subject line and the first two sentences. Can you tell why you are writing and what the recipient should do? Then skim the rest without reading every word. The action, key details, and deadline should still be easy to spot.
A useful final check is to compare the request with the closing: does the message name a clear next step, and is the deadline explicit where one is needed? If the recipient could reasonably ask what to do, which item to use, or when to reply, revise that part. After sending, confirm the draft contains the intended recipient, request, and timing; do not treat a sent message as proof that the reader has acted.
- Purpose appears in the opening lines.
- The requested action names the item and response needed.
- Separate details are grouped into short paragraphs.
- Any deadline includes a clear date and relevant time zone.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction