Writing Clear Work Reports and Emails

Work writing is there to support decisions

Writing at school often follows the flow of your thinking, building up step by step from an introduction. At work, readers are usually busy and want to know first what this document asks them to decide or do. So a work document should be judged not by how hard you worked on it but by how quickly the reader can grasp the situation and act. Before you start, write one sentence on who will read it and what you want them to do afterwards; it sets the direction.

Lead with the conclusion

The basic order of a work document is conclusion, reasons, details. State the main point and your request in the first paragraph, such as "I propose we proceed this way" or "I need approval by this week", and then add the supporting evidence. That way your manager can make the big call from the first paragraph and read further only when needed. Reports that walk through events in chronological order tend to bury what matters at the end. The worse the news, the more it pays to put it up front instead of talking around it.

Structures for different reports

What goes into a report depends on its purpose. Choosing a template that fits what you are reporting means less gets left out.

• Progress report: current status, what changed since last time, next steps, blockers
• Results report: outcome against the goal, what went well and what did not, follow-up
• Incident report: what happened, how far it reaches, action taken so far, decisions needed
• Proposal: background, comparison of options, recommendation and why, resources and timeline
• Meeting notes: decisions made, actions and owners, deadlines, open issues

Work email basics

A subject line should carry the purpose and the action needed, so the email stands out in the inbox. Rather than "Request for materials", something like "[Review needed] Q3 event quotes compared, by Friday" tells the reader what to do and by when before they even open it. In the body, get to the point right after a brief greeting, and number separate requests. Put the people who need to act in the To field and those who only need to know in Cc. Keeping one topic per email makes it easier to find later and easier to reply to.

Separate facts from opinions

The most dangerous thing in a report is something unverified written as fact. Make it clear in your sentences what you confirmed yourself, what you heard from someone else and what is your own guess or view. "The client confirmed" and "it seems likely" are pieces of information the reader should weigh differently. When you give figures, include the source and the date they refer to, and use specific dates and owners instead of vague wording. "By next Wednesday" causes far fewer misunderstandings than "as soon as possible".

Make it easy to read

The same content reads faster or slower depending on its shape. Keep one idea per sentence, and break long paragraphs up with subheadings or lists. Abbreviations familiar in your team may be unknown in other departments, so spell them out the first time. Use a table when comparing several items, but do not turn simple content into a table. If your company has a set template, follow it first; simply keeping the conclusion at the top within that template already makes it much easier to read.

Replies and follow-ups

When you cannot answer an email right away, letting the sender know you have seen it and when you will reply stops them waiting anxiously. If you asked for something and heard nothing, follow up briefly in the same thread, restating what you need and by when. If a long email exchange keeps going round in circles, settle it with a short call or a face-to-face chat, then put the decision back in writing by email. Even things agreed in conversation are easily remembered differently later if there is no record.

Check before you send

A work document is hard to take back once sent, and emails travel further than you expect. Skimming it from the top just before sending, as if reading it aloud, makes missing words and awkward sentences stand out. If you wrote an email while upset, do not send it straight away; leave it for a while and read it again. If it contains sensitive personal information or internal material, send it in a way that follows your company's security rules.

• Are the recipients and Cc list right?
• Is the attachment actually attached and the latest version?
• Are dates, days, amounts and names correct?
• Are the conclusion and request in the first paragraph?
• If you need a reply, did you give a deadline?