A clear email is one the reader can act on straight away: after the first lines they know what you’re asking, by when and what happens next. Unclear emails cost time in follow-up questions, extra meetings and decisions that stall. The good news: most unclear writing comes from a handful of recurring patterns. Here are seven, each with an alternative.
How do you adapt a business email to purpose and reader?
A business email becomes more concrete when you first decide what the reader needs to do and which information they need for that. Be-Inc helps you recognise phrasing patterns; you supply the facts and check that the context is right. The method is: purpose → shared knowledge → action.
- 1Purpose: do you need a decision, information or an appointment? Put that request first.
- 2Shared knowledge: a colleague who was there needs less background than someone who has just joined. Explain unfamiliar terms.
- 3Action: say who replies, about what and by which confirmed date. Do not invent a deadline to make a sentence concrete.
Original
Can you send the QBR input quickly?

Why
The new colleague may not know the abbreviation yet. The request also does not say which input is needed. You want input for the quarterly business review; you must fill in the section and date yourself.
Alternative
Could you send your input about [section] for the quarterly business review (QBR) by [date]? Let me know if you need an explanation.
For a colleague who already knows the agreement, you can leave out the explanation of QBR. The request and deadline stay the same. You adapt the information, not the substance or an assumed personal profile. Be-Inc does not predict whether the recipient understands. See also the context matrix for brand voice and tone in work emails.
For formal layout, such as subject line, salutation and closing, see Taaladvies.net’s business email guide (Dutch). The patterns below cover phrasing within that layout.
1. Vague timing
Words like ‘shortly’, ‘ASAP’ and ‘later this week’ feel concrete to the writer but mean something different to every reader. The result: nobody schedules it.
Original
Let’s discuss Project Titan shortly.

Why
‘Shortly’ is a vague timeline. The reader can’t put it in a calendar.
Alternative
Let’s discuss Project Titan on [date] at [time].
2. The ask is buried
Many emails open with context and end with the request. Anyone reading on a phone or skimming misses it. Put the ask at the top and the context below.
Original
As you know, we started with the new supplier last month. There were some delays at first, but things are running better now. […] Could you approve the invoice?

Why
The ask is in the last sentence. Skimmers won’t see that action is needed.
Alternative
Could you approve the new supplier’s invoice by [date]? Background below.
3. Passive voice
The passive voice hides who has to act. ‘It is expected that’ and ‘this should be done’ sound formal, but leave open whose move it is.
Original
It is expected that the report will be submitted on Friday.

Why
It’s unclear who submits the report. Everyone assumes someone else will.
Alternative
Could you submit the report on Friday?
4. Jargon and abbreviations
Jargon is efficient inside a team and a barrier outside it. New colleagues, clients and people reading in their second language drop out, often without saying so.
Original
Please share your input for the QBR re the KPIs from the OKR cycle.

Why
Three abbreviations in one sentence. Not every reader knows them, and nobody likes to ask.
Alternative
Could you share your input for the quarterly business review (QBR) by [date]? It’s about the KPIs from our goals for [period].
5. Long sentences
A sentence with three sub-clauses asks the reader to hold everything at once. Split long sentences: one thought per sentence.
Original
Because the schedule, which we discussed last week and whose details aren’t all fixed yet, may shift, I’d like to propose that we move the launch, if everyone agrees, back by a week.

Why
One sentence, three interruptions. The point, moving the launch, only arrives at the end.
Alternative
I propose moving the launch back by a week. The schedule may shift. Do you agree?
6. Hedging
‘Just’, ‘maybe’, ‘if you have time’: meant politely, but it makes your request easy to ignore. This is about the tone of your message. Direct is not the same as unfriendly.
Original
I just wanted to quickly check if you might have a moment to look at the budget.

Why
‘Quickly… might… a moment’ sounds hesitant and is easy to ignore.
Alternative
Do you have [number] minutes on [date] to look at the budget?
7. No next step
‘Let me know’ ends an email without an agreement. The reader doesn’t know what you expect or when. Close with a concrete next step.
Original
Let me know what you think.

Why
No question, no deadline. The email sinks to the bottom of the pile.
Alternative
Could you let me know by [date] at [time] whether you agree?
A checklist for every email
- Is the ask in the first two sentences?
- Is it clear who needs to do what, and by when?
- Could someone outside your team follow every abbreviation?
- Does each sentence carry one thought?
- Does the email end with a concrete next step?
Clear emails aren’t a matter of talent. They’re patterns you can learn to recognise. Want to know what clarity is worth to your organisation? Take the communication scan, or book a demo.



