And how many of those read will be understood the first time?
Most work emails meet the same fate: opened in a hurry, skimmed, archived or left pending. Not because the content is irrelevant, but because the way it's written makes it hard to understand.
Knowing how to write emails isn't a matter of style. It's an operational skill: people who write clear emails get faster replies, fewer misunderstandings and less chasing. People who write confusing emails generate requests for clarification, endless threads and meetings that could have been avoided.
This article starts from the rules of writing — subject line, structure, readability — and arrives at the point that matters most in a company: an email isn't a style exercise, it's a piece of the communication process. And like any process, it can be improved with a method.
The mistakes that make an email unreadable
Before the rules, it's worth recognizing the most common mistakes.
The first is the wall of text: a single dense block of lines, with no spacing, no paragraphs, no hierarchy. The reader's eye finds nothing to hold on to, and the instinctive reaction is to put off reading it — often forever.
The second is the email with no stated purpose. The reader gets to the end and still doesn't know what to do: reply? Approve? Take note? If the request isn't explicit, each recipient will decide on their own, and they will usually decide to do nothing.
The third is the multiple message: three different topics in the same email. The recipient answers the first point, ignores the other two, and a thread of clarifications is born that multiplies the work for everyone.
The rule that prevents most of these mistakes is a single one: one email, one message. One topic, one request, one recipient responsible for replying. Everything else — structure, subject line, tone — follows from that.
The subject line: the most important part of the email
The subject line is the first thing the recipient reads and, often, the only one.
In an inbox that receives dozens of messages a day, the subject line decides whether the email will be opened right away, put off or ignored. Yet it's usually the part that gets the least attention: it's written last, in a hurry, and ends up being generic ("Update," "Info," "Re: Re: Re: meeting").
An effective subject line has three characteristics:
- it's specific: it says what the email is about, not the category it belongs to. "Supplier X quote: approval needed by Friday" works; "Quote" doesn't
- it anticipates the action requested: from the subject line, the reader must understand whether they need to decide, reply or just take note
- it's understandable on its own: weeks later, when searching for that email in the archive, the subject line must let you find it and understand it without opening it
A principle born in email marketing also applies to work emails: the subject line should contain the benefit or the result, not the generic topic. In marketing it serves to get the email opened; in a company it serves to make clear right away why that email deserves attention over the other twenty in the queue.
A practical tip: write the subject line last, once the content is clear, and ask yourself, "If the recipient read only this line, would they know what to do?"
The structure that gets the email read (and understood)
An effective work email is read in two ways: in full and skimmed. It has to work in both cases.
The structure that makes this possible is simple:
- first line: the point. The request or main piece of information goes at the beginning, not at the end. The reader must understand right away why they received that email
- body: the essential context. Only the information needed to decide or act, in short paragraphs (two or three lines at most), separated by white space
- closing: action, owner, deadline. What is needed, from whom, by when. If the expected answer is a yes or a no, say so explicitly
Bullet points help when there are several items of the same kind (options, data, steps); bold is for highlighting the action requested or the deadline, not for decoration. If everything is in bold, nothing stands out.
For language, the principle of maximum simplicity applies: short sentences, active verbs, zero unnecessary jargon. An effective test is to ask yourself whether someone outside the project would understand the message on first reading. If implicit knowledge is needed to decode it, the risk of misunderstanding is high.
One last, often overlooked point: the recipients. The "To" field should include only the people from whom you expect an action or a reply; "Cc" is for those who only need to be informed. When everyone is in "To," nobody feels responsible for replying — and the email gets no follow-up.
Why badly written emails are a process problem, not a style problem
So far, the rules of writing. But there's a deeper level, and it's the one that makes the difference in a company.
A badly written email isn't just an ugly email: it's a defect in a communication process. And process defects have costs that spread.
The mechanism is always the same. An ambiguous email generates a request for clarification; the clarification generates another reply; more people get added in copy to the thread; after days of back-and-forth someone suggests "let's do a call to get aligned." A meeting created to fix an email that, written well, would have settled everything in one message.
Multiply this pattern by the dozens of emails that circulate every day in a company and the picture changes: we're not talking about style, we're talking about work time absorbed by communication rework. Misunderstandings about deliverables, duplicated activities because two people understood different things, decisions postponed because "it wasn't clear who was supposed to decide."
The point is that these costs remain invisible. No management system measures the time lost deciphering confusing emails or attending clarification meetings. That's why the problem is rarely tackled: it's treated as an unavoidable feature of work, not as a faulty process to be corrected.
Treating it as a process, on the other hand, changes everything: it means it can be analyzed, standardized and improved. It's the same approach that applies to internal company communication as a whole, of which email is just one channel.
Defining shared rules: from good intentions to a standard
If email is a process, the rules of writing can't remain an individual initiative.
A single person writing perfect emails in an organization that writes confusing ones gets a marginal benefit. The leap happens when the rules become a team convention: few, explicit, valid for everyone.
A team can start from a minimum set:
- subject line conventions: an agreed prefix that states the nature of the message, for example "[ACTION]" when a reply is needed, "[INFO]" when reading is enough, "[DECISION]" when approval is requested. Whoever opens the inbox sorts it in a few seconds
- a single owner per reply: every email that requires an action explicitly states who must act. The recipients in copy know they don't need to reply
- expected, stated response times: if the organization agrees that email isn't an urgent channel — for example, with a reply expected within the working day — nobody is left stuck waiting, and urgent matters go through more suitable channels
- rules on threads: when an exchange goes beyond a few rounds of back-and-forth without reaching a conclusion, you change channel. The endless thread is the signal that email is no longer the right tool for that conversation
These conventions apply to internal emails and, with the necessary adjustments, also improve external ones: a customer or supplier who receives clear emails, with explicit requests and defined deadlines, responds better and faster. Clarity is also a calling card.
What matters is that the rules are written, shared and few. A list of thirty rules will never be applied; four conventions followed by everyone transform the inbox of an entire organization.
When not to use email
Knowing how to write emails includes a skill that seems paradoxical: knowing when not to write them.
Email is an asynchronous, documentary tool. It works well when the message isn't urgent, when you need to leave a written record, when the recipient needs to be able to read and reply in their own time. Outside this scope, it becomes the wrong tool:
- for urgent matters: if you need a reply within minutes, email is the worst channel. A phone call or a direct message is better
- for discussions: when it takes more than two or three exchanges to reach a decision, a short conversation — in person or on a call — settles in a few minutes what would take days by email
- for sensitive topics: critical feedback, tensions, personal matters. Writing amplifies misunderstandings and freezes the tone; a conversation lets you adjust course in real time
- for content that needs to last: procedures, reference decisions, operating instructions. Buried in an inbox they become impossible to find; their place is a shared document or an operations manual
Choosing the channel before writing is a process decision, not a matter of etiquette. Every message sent through the wrong channel creates friction: the urgent email nobody reads in time, the strategic discussion fragmented into twenty replies, the important procedure lost in the archive.
Reducing the load: email as an activity, not an interruption
Finally, there's the other side of the coin: emails aren't only written, they're also received.
And the way they're handled on the receiving end affects productivity as much as the way they're written. An inbox that's always open, with notifications on, turns every incoming message into an interruption that fragments work and stretches the time every activity takes.
Research on office work confirms the scale of the phenomenon. An observational study conducted by Gloria Mark and colleagues at the University of California, Irvine, found that office workers' work is highly fragmented: 57% of ongoing activities were interrupted before being completed [1]. And email is among the main drivers of this fragmentation: in a study conducted at a British company with about 500 employees, workers reacted to new messages almost as quickly as they answered the phone, with an average time of 64 seconds to recover their concentration after each interruption [2].
The alternative is to treat email as an activity with its own time slots: defined moments of the day devoted to reading and replying, notifications off the rest of the time. An experiment with 124 adults showed that limiting email checking to three times a day significantly reduces daily stress compared with unlimited checking, with positive effects on overall well-being [3]. People doing deep work on an activity aren't pulled away by every new email; people writing know that the reply will come within the agreed time, not instantly.
The two sides of the topic feed each other. Better-written emails mean fewer threads, fewer clarifications, fewer messages going around: the overall load drops for everyone. And shared rules on response times make handling email in blocks sustainable, because they remove the anxiety of having to keep watch over the inbox.
That's why it pays to tackle the topic at the level of the organization and not the individual: the quality of the emails each person receives depends on the rules everyone follows.
Where to start
Writing emails that get read and understood takes a few rules applied consistently: one message per email, a specific subject line, the point in the first line, the action requested made explicit with an owner and a deadline.
But the real leap in quality comes when these rules stop being good individual habits and become conventions of the organization: subject line prefixes, one owner per reply, stated expected response times, clear criteria on when to use email and when to change channel.
A good first step, concrete and at no cost: at the next team meeting, agree on three rules for email — no more — and write them where everyone can see them. After a few weeks, the number of endless threads and clarification meetings will tell you whether they're working.
Email is one of the most used and least designed processes in any company. Designing it, even just a little, gives you back time every single day.
FAQ
How do you write an effective subject line for a work email?
An effective subject line is specific, anticipates the action requested and is understandable on its own even weeks later. "Supplier X quote: approval needed by Friday" works; "Quote" doesn't. A practical tip: write it last, once the content is clear, and ask yourself whether the recipient, reading only that line, would already know what to do.
What is the ideal structure for a work email?
Three blocks: the request or main piece of information in the first line, the essential context in short paragraphs separated by white space, and at the close the expected action with an owner and a deadline. Then the rule "one email, one message" applies: one topic, one request, one recipient responsible for replying. Everything else follows from that.
When is it better not to use email?
Email works for non-urgent communications that need to leave a written record. It's the wrong channel for urgent matters (a phone call is better), for discussions that require many exchanges (a short conversation is better), for sensitive topics (writing amplifies misunderstandings) and for content that needs to last, whose place is a shared document or an operations manual.
Does checking email constantly reduce productivity?
The available studies suggest it does: office work is already highly fragmented by interruptions [1], email is checked with the same responsiveness as a phone call [2], and limiting checking to a few defined moments of the day reduces daily stress [3]. Treating email as a planned activity, and not as a constant interruption, benefits both those who write and those who receive.
Sources and references
- Mark, G., González, V. M., & Harris, J. (2005). No task left behind? Examining the nature of fragmented work. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '05), ACM, 321-330. https://doi.org/10.1145/1054972.1055017 — Foundational reference.
- Jackson, T., Dawson, R., & Wilson, D. (2003). Understanding email interaction increases organizational productivity. Communications of the ACM, 46(8), 80-84. https://doi.org/10.1145/859670.859673 — Foundational reference.
- Kushlev, K., & Dunn, E. W. (2015). Checking email less frequently reduces stress. Computers in Human Behavior, 43, 220-228. https://doi.org/10.1016/j.chb.2014.11.005