Career development

Clear Workplace Communication: Emails, Meetings and Updates

A good deal of friction at work comes from messages that were vague, late or sent to the wrong people. This guide gives practical patterns for five everyday situations: writing an email, running or attending a meeting, giving a status update, raising a problem and disagreeing with someone, each with model wording.

Key points

  • Put the point or the request in the first two lines of any message.
  • Say who needs to do what, and by which date.
  • Call a meeting only when people need to decide or discuss something together, and end it with written actions.
  • Report status as done, next and blocked, with dates and figures.
  • Raise a problem early, with the facts, the effect and a proposed next step.

Clear communication at work is mostly a matter of order: the main thing first, then the detail, then what you need. People read messages between other tasks, on phones, and often only the opening lines. If the request sits in the fourth paragraph, it may never be seen.

The patterns below are simple enough to use tomorrow. None of them depends on a particular personality or a talent for writing.

Write emails that can be answered quickly

Before writing, finish this sentence in your head: "After reading this, I want the reader to..." If you cannot, you are not ready to write. Then build the message in this order.

  1. Subject line that states the topic and any action or deadline, such as "Approval needed by Thursday: supervisors' course".
  2. Opening lines containing the request or the main point.
  3. Supporting detail in short paragraphs or a list, and only as much as the reader needs in order to act.
  4. Close with the next step and the date.

Weaker

Subject: Quick question

Hi Daniel, hope you're well. So I've been looking at the training plans for next quarter and talking to a few people about what they need, and there are a few options but I think the supervisors' course would be good. It's quite expensive though and I wasn't sure about the budget situation. Let me know your thoughts when you get a chance. Thanks!

Stronger

Subject: Approval needed by Thursday 15 October: supervisors' course, 2,400

Hi Daniel,

Could you approve 2,400 from the training budget for six supervisors to attend the two-day coaching course on 9 and 10 November?

- Why: all six asked for it in their reviews.
- Cost: 400 each. The budget has 3,100 left this quarter.
- Deadline: the provider holds the places until Thursday 15 October.

A yes or no by Thursday is all I need. The course outline is attached.

Thanks,
Amara

Why: The first email hides the request, gives no figure or deadline and asks for "thoughts", which invites delay. The second can be answered with one word, because the amount, the reason, the remaining budget and the date are all in view.

A few habits help further. Keep one email to one subject. Put people who must act in "To" and people who only need to know in "Cc". If a draft runs long, the word counter shows its length and most repeated words. The same order of point, detail and next step suits job applications too, as the guide to sending a resume and cover letter by email explains.

Run meetings that end with decisions

A meeting is expensive: an hour with eight people is a working day. Call one when people need to decide, discuss or solve something together. If you only need to pass on information, write it down and send it.

  • Before: send the purpose and agenda at least a day ahead, with anything people need to read. State the decision you want to reach, and invite only those needed for it.
  • During: start on time, restate the purpose and note decisions as they are made. If a topic needs longer, schedule it separately and move on. Ask quieter attendees for their view by name.
  • After: send the actions within a day. Each action has one owner and a date.
Model action notes sent after a meeting

Subject: Actions from rota planning meeting, 6 October

Decided:
- The Christmas rota will be published on 2 November, two weeks earlier than last year.
- Leave requests for 21 December to 3 January close on 23 October.

Actions:
- Hye-jin: email all staff about the leave deadline, by 8 October.
- Rafael: draft the rota from the requests received, by 28 October.
- Olu: confirm agency cover for the night shifts, by 28 October.

Next meeting: 29 October, 10:00, to approve the draft.

When you are attending

Read the agenda and decide beforehand what you want to say or ask. Make your point once, briefly, and tie it to the decision on the table. If it is unclear at the end who is doing what, ask: "Can we confirm the actions before we finish?" Everyone in the room benefits.

Give status updates people can use

A status update answers three questions: what is finished, what happens next and what is in the way. Use the same structure every time, so that readers know where to look.

Weaker

Things are going well with the website. Been really busy this week, lots of progress. A few issues but nothing major. Should be on track.

Stronger

Website relaunch, week ending 9 October. Status: one week behind.
Done: product pages migrated (212 of 212); checkout tested on desktop.
Next: mobile checkout testing, due 14 October.
Blocked: the payment provider has not issued the live API key, requested on 28 September. Without it by 13 October, launch moves from 19 to 26 October.
Needed: Lucia, could you raise it with their account manager?

Why: The first update offers impressions and no facts, so the reader cannot tell whether to worry. The second gives the status at the start, measurable progress, a dated risk with its consequence, and a specific request to a named person.

Report bad news in the update where it first becomes likely, not the one where it becomes certain. Keep your updates, too: they become the record of results you will need for reviews and for quantifying achievements on a resume.

Raise a problem early and usefully

A problem is easier to deal with while there are still options. Bring four things: what has happened (facts, not blame), what the effect is, what you have already tried, and what you suggest or need.

Model wording for raising a problem with your manager

"I need to flag a problem with the October invoice run. The export from the new system dropped the tax code on 38 of 410 invoices. None has been sent. I've checked, and it only affects customers set up since August. I can correct the 38 by hand today, which takes about two hours, but the cause needs fixing before November's run. Could you ask the systems team to look at the export, or shall I raise it with them directly?"

If the problem is a person's behaviour and not a process, speak to them first where that is safe and reasonable, in private, describing what you saw and its effect. For serious matters such as harassment, safety or dishonesty, follow your employer's formal procedure and keep a written note of dates and facts.

Disagree without making it personal

Disagreement is useful when it is about the idea and comes with a reason and an alternative. Ask a question first to check that you have understood. Then give your concern, the evidence for it and what you would do instead.

Weaker

"That won't work. We tried something like that before and it was a disaster."

Stronger

"Can I check I've understood: the plan is to move all support to chat from January? My concern is the older customers. About a third of last month's calls came from people who told us they don't use the app. Could we keep the phone line for the first quarter and compare the numbers before deciding?"

Why: The first reply rejects the idea and leaves the other person nothing to do but defend it. The second confirms the proposal, raises a specific risk with a figure and offers a smaller step that can be accepted without loss of face.

Once a decision is made, say so if you still disagree, then support it in practice. Before sending anything drafted while annoyed, wait an hour and remove "always", "never" and "as I said before". Conversations about your own role need the same preparation; see how to ask for a promotion.

Choose the right channel

SituationBetter channelWhy
A decision or request that needs a recordEmailIt can be found later and forwarded
A quick factual questionChat messageFast, and easy to answer between tasks
Sensitive feedback or bad newsIn person or a callTone is heard and questions are answered at once
A thread that has gone back and forth several timesA short call, then a written note of the outcomeTalking ends the loop and the note keeps the record
Information many people needA written update or shared documentPeople can read it when it suits them

Common mistakes

  • Burying the request at the bottom of a long email means it is often missed; put it in the first two lines.
  • Using a vague subject line such as "Quick question" or "Update" makes a message hard to prioritise and to find later; name the topic and the deadline.
  • Calling a meeting to share information that could have been written wastes the time of everyone invited; send a note and meet only for decisions.
  • Ending a meeting without named owners and dates means the same discussion is repeated next time; send the actions within a day.
  • Holding back bad news until it is certain removes the options that existed earlier; flag a risk as soon as it becomes likely.
  • Replying in anger, or copying in senior people to apply pressure, damages working relationships; wait, then speak to the person directly.

Questions and answers

How long should a work email be?

As short as it can be while still letting the reader act without a follow-up question. For most requests that is well under 150 words. If you need more, put the request and deadline at the top and the background underneath or in an attachment.

How do I speak up in meetings when I am junior or shy?

Prepare one point or question beforehand and make it early, before the discussion moves on. Asking a clarifying question is a legitimate contribution. If speaking in the room is hard, send your point to the chair in advance or follow up in writing straight afterwards.

What should I do when someone does not reply?

Wait a reasonable time, then follow up once on the same thread with a shorter message that restates the request and the date. If it is urgent, call or message them directly. Assume they are busy, not ignoring you; a neutral tone gets a quicker answer than a reproachful one.

Is it better to use chat or email?

Use chat for quick questions and coordination, and email for requests, decisions and anything that needs a record or will be read by people outside your team. If your workplace has its own conventions, follow those, and move long chat threads to a call or a document.