Office English in Email and Chat: The First Three Lines Decide the Tone

Introduction: it is not a length problem

Sometimes you reread an English email you have just written and something is off, but you cannot tell where. The grammar is right. The words are not wrong. Yet it reads stiff, or the opposite, like you are pleading.

Many people treat this as a length problem. Write it shorter and it should get better. But you write it shorter and the awkwardness stays exactly where it was.

Here is why. What sets the tone in an English work email is not the total length but the first three lines. The reader decides inside three lines how to read this message, and everything after that is read under that judgement. However politely you write further down, you will not overturn the tone the first three lines set.

The three lines each do a different job.

Line one sets the distance. A single greeting declares how close the two of you are.

Line two sets the kind. Whether this is a request, a demand for a decision, or just a notification is what the reader works out here.

Line three sets the urgency. By when, and what gets blocked if it does not happen.

This arrangement has a name. It is BLUF — bottom line up front — which came out of US military documents and spread into corporate writing. And there is a practical reason for it beyond style. Most people now see only the first two or three lines of a message in a phone notification and decide from that whether to open it now. If the request is not inside three lines, that email gets read later or not at all.

The default order of a Korean work email is more or less the reverse. Lay down the background, explain the situation, and place the request at the end. It is a courteous arrangement and it works well in Korean. Carried straight into English, it reads as one of two things. Either an FYI, or a person working up to a request they are uncomfortable making.

Line one: greetings by relational distance

If you pick one, pick Hi Sarah,. It is unremarkable in the US, the UK, Europe, internally and externally, and it is almost never so formal that it jars or so casual that it offends.

Where Dear sits varies a great deal by region. In internal mail at an American tech company, Dear Sarah, reads oddly formal, or makes you sound like an outsider. In formal business correspondence in a number of European countries and in the UK, it is still close to standard. Following how the other person wrote to you is the safest rule.

Dear Sir or Madam, looks lazy when the name was available. Spend thirty seconds on LinkedIn or the company's about page and use the name.

A word on the pleasantry line as well. Hope you're well, is a harmless formula and common in external mail. I hope this email finds you well, means the same thing, but plenty of people read it as fairly old-fashioned. And in internal mail, leaving the pleasantry out entirely is not rude. If anything it reads as efficient.

Lines two and three: the business goes to the front

No action needed on your side is a small courtesy that lands large. What tires people most in work email is not the content but not knowing whether they have to do something. Say explicitly that they do not, and that weight disappears.

Heads-up means giving advance notice, and it is used constantly in English-speaking workplaces. You use it to pre-announce bad news, to lay context before a meeting, and when a schedule changes. If you are memorising one, this one is powerful too.

The subject line is part of the opening as well.

What the good subjects share is a verb and a date. If someone can read the subject alone and know what they have to do, that subject has done its whole job.

Some companies use square-bracket tags like [Action needed], [FYI] or [Decision needed]. They are convenient, but the conventions differ from company to company, so in a new organisation watch what everyone else does first.

Chasing without nagging: four steps

The situation where no reply comes will arrive sooner or later. There is an order to this, and jumping straight to the last step damages the relationship.

Step 1, a light lift.

Step 2, name the cost.

Step 3, set a default.

Step 3 is the most effective one in practice. And it is also the most honest form. It is a sentence that gives information rather than applying pressure, and it lets the other person agree by doing nothing. Most non-responses are not being ignored, they are being outranked, so setting a default makes life easier for both sides.

Step 4, add people.

There is one thing I want to say strongly here. Copying in someone's manager reads as a pressure tactic in almost every organisation. Do it only when you genuinely need that person's judgement, and say in one line why you are doing it. Adding them quietly with no reason given is the worst version.

And there is one chasing phrase to avoid absolutely. As per my last email. The literal meaning is neutral, but in English-speaking workplaces it is widely known as the flagship phrase of passive aggression. Per my previous message, As previously mentioned and Just to reiterate are all in the same family. If you have to point back at earlier content, do not point — just paste it. Copying the relevant bit here so it's in one place: is enough.

Vague dates and times will cause an incident, guaranteed

The most frequent accident in written work is not a grammar mistake, it is a time notation. And this has almost nothing to do with your English, because native speakers get it wrong in exactly the same way.

next Friday is a particularly famous trap. When today is Wednesday, whether that means two days away or nine days away is read differently by different people, and English speakers check with each other about it every single time. Writing the weekday and the date together makes the entire problem disappear.

Time zones need one more level of care. 3pm my time is not information. On a team spread across countries, giving at least two is the convention.

That last sentence comes up often in practice. Asking to move a time because of the time difference is not rude in the slightest. Saying nothing and joining at 1am is what causes a problem later.

Expressions of clock time carry regional differences too. In Britain half five is 5:30, and in America quarter of five is 4:45. If you are unsure of either, just write the numbers.

Email and Slack are different languages

The most important difference is the last row. Decisions and commitments have to be left as a record. When a conclusion lands in Slack, summarise it in one line and nail it into the thread or a document. Summarising so it's findable: we're going with option A, Sujin owns it, target is the 12th. That one line removes a meeting two months from now.

A few Slack conventions worth writing down as well.

Using an emoji reaction instead of a reply is completely normal at most tech companies. That said, this depends heavily on company culture, so on a new team watch how other people use them and follow. You will sometimes hear that a bare thumbs-up feels dismissive to some people, but in most workplaces it simply reads as an acknowledgement. If you are unsure, attach one short word.

There is one thing not to do in Slack: send a greeting and then wait for the other person to answer. Send only Hi! and the other person is left waiting without knowing what this is about, and the habit is known as one that English-speaking tech workplaces explicitly dislike. Put the question in the first message. Hi! Quick one — do you know who owns the billing cron now? One line like that lets them answer in a gap between things.

How to read a short reply

This part is the closest thing to the real world in this article. Losing a day because you did not know what a native-speaker colleague's three-word reply meant happens often.

Do not use this table as a decoder. The same words are used differently by different people in different situations. Interesting. really does often mean interesting.

So what you actually need is not a table but one sentence.

Just to make sure I'm reading this right — are you saying we should hold until the audit's done?

This sentence is not rude. If anything it gently hands back the responsibility for having written ambiguously, while making you the person who works precisely. In English-speaking workplaces a confirming question reads as a professional habit, not a weakness.

British understatement and American overstatement

Knowing both directions of distortion cuts your misreadings a great deal.

British workplace English leans towards saying it weaker. a bit of a problem can be a considerable problem, and I'm not entirely convinced can be strong disagreement. quite good is especially confusing: in the British reading it is closer to "acceptable" and in the American one to "pretty good". The same two words point in opposite directions.

American corporate English leans the other way, towards saying it stronger. Because awesome, amazing and love it are used routinely, an American's great can be close to a British person's fine.

There is a caveat that has to be attached here. The tables circulating online headed "what the British say and what they really mean" were made for fun and are considerably exaggerated. Individual variation is bigger than national variation. Trust that table as a decoder and you will misread people who meant exactly what they said. Keep the direction in mind, and on anything that matters, use the confirming sentence.

Sign-offs

One simple rule. If you asked for something, Thanks,; otherwise Best,. Those two cover most internal mail.

Things better left undone

As per my last email. As above: the byword for passive aggression.

Placing the request after five paragraphs of context. The point of this whole article. A request below the scroll line might as well not exist.

Please advise. It is widely used and not incorrect, but to some people it reads as dry as a government form. Let me know what you think or Which would you prefer? is warmer, and more importantly it is clear what the other person is supposed to answer.

Exclamation marks and capitals. One exclamation mark is friendliness and three is panic. All caps reads as shouting.

Please revert and Kindly do the needful. These are entirely standard in Indian English business writing. But to American and British readers revert means "return to a previous state", which causes confusion. If your recipients span several countries, Please let me know and Could you please ... travel further.

Mixing three requests into one email. One gets handled and two get forgotten. If there are several, number them or split the email.

Thanks in advance. Very common and mostly harmless, but its structure thanks someone who has not agreed yet, so some people feel it as pressure. If it bothers you, Thanks for taking a look does the job.

Sending at 2am and expecting an immediate answer. Most mail clients have scheduled send. Especially on a team spread across time zones.

A worked example: one email and the chase behind it

Subject: Payments spec — need your review by Thu

Hi Sarah,

Quick ask: could you review the payments spec by Thursday?
It's blocking the QA kickoff on Friday.

The doc is here [link]. It's about ten minutes — I've marked the
three sections that actually changed, you can skip the rest.

If Thursday's bad, tell me and I'll ask Jae instead.

Thanks,
Youngju

If there is no reply by Thursday, it continues in Slack like this.

Me:    Hi Sarah — quick one. Any update on the payments spec review?
       QA kickoff is tomorrow morning.

(if there is still no reply half a day later)

Me:    No pressure on the detail — if I don't hear back by 4,
       I'll kick QA off against the current version and we can
       fold your comments in next week. Shout if that's wrong.

Sarah: Sounds good, sorry — swamped today. Skimmed it, one comment
       in section 3.

Me:    Got it, thanks. Just to make sure I'm reading this right —
       you're okay with the retry logic as written?

Sarah: Yes, fine as written.

Me:    Perfect. Summarising in the channel so it's findable:
       spec approved, one comment on section 3, QA starts 9am tomorrow.

Everything above is in there. The request sits in the first two lines, an escape hatch is left open, the chase names the cost and then closes with a default, the ambiguous reply is resolved with the confirming sentence, and the conclusion is left as a record. There is not a hard piece of English anywhere in it.

Try this today

1. Request to the front: put the business and the deadline in the first two lines of your next email.
2. One escape hatch line: If Thursday's bad, tell me and I'll ask someone else.
3. Step 3 of the chase: If I don't hear back by Thursday, I'll go ahead with option A.
4. Unpick the vague reply: Just to make sure I'm reading this right — are you saying ...?

Writing good English email does not mean writing ornate sentences; it means the reader knows within three seconds what they have to do.

Read next

• Asking and saying no in office English — the previous article. The same requests and refusals, done out loud.
• Reporting status and delivering bad news in English — the next article. Where the first-three-lines principle does the most work.
• Writing Practice — practice turning the sentence frames above into your own sentences.
• Browser AI Lab — you can run an ambiguous reply through sentiment analysis and Korean-English translation for a second look. It will not make the judgement for you, but it is useful for reducing misreadings.