
A long report is easy to write. A short one that gets read takes more care.
Who is reading
Imagine your reader has four minutes between meetings. They will read the top, scan the headings, and look for numbers and a decision. If the first paragraph does not tell them why they are reading, many will stop. Reports and proposals are two of the document types in Business Writing, in the units on reporting and updating (Unit 8) and on proposing and deciding (Unit 9).
Put the answer first
A good report or proposal opens with a short summary: what happened or what you recommend, and what you need from the reader. The details come after. This is sometimes called the answer-first pattern. It feels backwards if you were taught to build up to a conclusion, but a busy reader prefers it.
An invented example opening for a proposal:
“I recommend replacing the two oldest printers with one shared machine. This would cut costs over three years and free a desk. I need your approval by 30 November to order.”
Three sentences: recommendation, benefit, and what is needed from the reader.
A simple structure
For most short reports and proposals, these parts are enough:
- Summary. Two to four sentences.
- Background. Only what the reader needs to understand the situation.
- Findings or options. The facts, in a logical order.
- Recommendation or next steps. What you propose, who does what, by when.
Your workplace may have its own template. If it does, use it and apply the same ideas inside it.
Make it easy to scan
- Use headings that say something: “Costs are lower with one printer” tells more than “Costs”.
- Keep paragraphs short, with one idea each.
- Use a list when you have steps or parallel points, and a table for numbers that must be compared.
- Bold only the few things the reader must not miss.
Cut ruthlessly
Ask of each paragraph: would the reader miss this if it were gone? If not, remove it or move it to an appendix. Watch for long introductions, repeated points and background that the reader already knows. Plain words usually beat formal ones: “use” over “utilise”, “start” over “commence”.
Describing data
When you report numbers, say what they mean. Do not just write “sales were 12,400”. Write “sales were 12,400, up from 11,100 last month”. A comparison turns a number into information. Choose the figures that support your point and put the rest in a table or appendix.
A worked example
This progress report is invented. A team lead, Ravi, is updating his manager.
Weak: “We have been working on the new filing system and there have been some delays due to various issues. Work continues.”
Better: “The new filing system is two weeks behind. The delay is caused by missing scans from Finance. Finance will deliver them on 21 November, and we will finish on 5 December. No extra cost. Decision needed: none.”
The better version states the status, the cause, the new date, the cost and what the reader must do. It also uses fewer words.
Before you send
Read only your summary. Could the reader act on it alone? Then check that the rest backs it up. For tone in a proposal, see Tone That Is Firm, Polite and Clear. To see how reports sit among the other documents, see Inside Business Writing.
Quick FAQ
How long should a report be?
As short as it can be while giving the reader what they need. Many are one or two pages.
Where do I put a recommendation?
At the top in the summary, and again with detail near the end.
Should I use a template?
Yes if your employer has one. Otherwise the four-part structure above is a safe start.
Keep going: the Business Writing course, free taster courses and free sample tests.
