Much of the email that wastes our time is not what we receive but what we write badly: messages that trigger requests for clarification, replies that never come, threads that drag on for days. Writing clear emails is a form of digital organization in its own right, because it reduces the number of messages needed to reach a result. Here is a simple method that works for most work communication.
The subject: say it all in one line
The subject is what the recipient sees in the message list, and also what they will use to find your email again in a month. A good subject contains:
- the specific topic, not a generic one;
- the type of action requested, when there is one;
- a deadline, if one exists.
Compare:
| Weak subject | Effective subject |
|---|---|
| Question | Brochure printing quote: need quantity confirmed by Thursday |
| Meeting | Project Alpha meeting moved to Tuesday 10:00 |
| Update | Association website: new events page live, please check |
| Urgent!!! | Invoice 42 rejected by the portal: must be reissued today |
Some groups use agreed prefixes such as «[Decision]», «[Info]» or «[Action]». They work if everyone knows them and uses them the same way.
The request up front
Many emails follow the order of the writer's thoughts: context, background, reasoning and, at the end, the request. Readers, especially on a phone, often stop at the first lines. It is therefore better to reverse the order: the request first, then the necessary context.
An example:
Hi Laura, I need your approval on the attached quote by Thursday, so I can confirm the order with the printer.
Compared with the previous version only the paper changes, a heavier stock, adding 40 euros. The other items are unchanged.
The recipient knows immediately what to do, by when and why.
One message, one topic
Putting three different issues in the same email looks efficient, but in practice it produces partial answers: the recipient replies to the first question and forgets the others, or the thread branches out and becomes impossible to follow. If the topics are independent, write separate messages with specific subjects. They will also be easier to find later.
Visual structure
For messages longer than a few lines, a few tricks help a lot:
- short paragraphs separated by a blank line;
- bullet lists for options, steps or questions;
- numbered questions, so the reply can say «1: yes, 2: no, 3: Monday»;
- bold used sparingly, only for deadlines or decisions.
If the email runs past twenty or thirty lines, ask yourself whether an attached document or a short phone call followed by a written summary would be better.
Recipients: «To», «Cc» and «Bcc»
Using the recipient fields correctly avoids confusion about who needs to act:
- To: the people you are asking for something. If there are several, state in the text who has to do what.
- Cc: people who should be informed but do not need to act.
- Bcc: recipients hidden from the others. Useful for mailings to many people who do not know each other, so as not to spread everyone's address.
Before using «Reply all», ask whether everyone really needs your reply. A «thanks» sent to thirty people produces thirty useless notifications.
Deadlines and next steps
A request without a deadline is often postponed indefinitely. Giving a concrete date («by Thursday the 12th») is more effective than «when you can» or «no rush». Likewise, at the end of an exchange that led to a decision, a short summary («To recap: we confirm 500 copies, delivery on the 20th, I pay the difference») prevents different interpretations.
Attachments and links
Give attachments understandable names and mention them in the text, so readers know they are there and what they are for. For heavy files or files that will keep changing, a link to a shared folder is often preferable: everyone sees the current version and inboxes do not fill up with copies.
Reread before sending
Thirty seconds of rereading are enough to check three things: the request is clear, the recipients are right, the attachments are there. Many clients also let you delay sending by a few seconds, giving you a chance to cancel: a setting that saves you from quite a few small embarrassments.
In short
- Write specific subjects with topic, action and deadline.
- Put the request in the first lines and the context afterwards.
- Cover one topic per message and use lists and short paragraphs.
- Use To, Cc and Bcc according to who must act and who just needs to know.
- Give concrete deadlines and close decisions with a summary.
