A report, an email, a set of minutes and a proposal all do the same job for the reader: they let someone who was not in the room, or who has ten seconds before the next meeting, find out what happened and what is being asked of them. The forms differ in shape, but the reader-first principle behind them does not change. Put the thing the reader needs first. Everything else, however true, comes after.

The summary that stands alone

A report's summary has to work as a document in its own right, because for most readers it is the only part they will read. It states the finding, the recommendation and the reason, in that order, before the report goes on to show the working. A summary that opens with background and saves the recommendation for the last line is asking a busy reader to do the report's job for it.

An email that gets read

An email earns its reply in the first line or loses it there. The subject line and opening sentence should carry the request or the decision needed. A reader working through an inbox decides in seconds whether an email needs action now, later, or not at all, and that decision is made from the first line whether the writer intended it or not.

Minutes that record a decision

Minutes exist to settle, later, what was agreed and who is doing it, so a decision recorded without an owner and a date is not yet a decision, only a note that a conversation happened. The discussion that led to the decision matters less than the decision itself. Minutes that transcribe the discussion in full and bury the outcome in the middle of a paragraph are minutes nobody will check when the argument about what was agreed starts three weeks later.

A proposal that answers the question first

A proposal is read by someone deciding whether to say yes, and that person wants the answer, the cost and the timescale before the argument for why it is the right answer. Justification belongs after the answer. A proposal that spends its first page building a case and only states what it is actually asking for on page two has the structure backwards for the reader holding the budget.

What to leave out

Reader-first writing is as much about omission as ordering. Detail that would only matter if something went wrong, background the reader already has, and the process by which a conclusion was reached are all worth a line or an appendix. The guide to structure for longer pieces covers how to decide what earns a place in the main text and what belongs further back, and the plain English guide covers the sentence-level version of the same instinct: saying only what the reader needs and no more.

Reading four pieces of workplace writing that work tells you more than a list of rules ever will, because the difference between the version that gets acted on and the version that gets skimmed and forgotten is usually one thing done differently near the top.

A report summary that stands alone

A summary that opens with background, then more background, then finally the finding on the third line, forces the reader to do the sorting that the summary was meant to do for them. A summary that opens with the finding, for example "Three of the five regional offices are running below capacity, and the shortfall is concentrated in recruitment rather than retention," lets a reader who never reaches page four still walk away knowing the one thing that matters. The context, the method and the caveats follow underneath; none of that is lost, it is simply no longer standing between the reader and the point.

An email that gets read

An email titled "Update" with the actual request buried in the fourth paragraph competes for attention against everything else sitting in that inbox, and loses. An email titled "Need your sign-off on the Thursday deadline" with the request in the first line gives the reader everything they need before they have decided whether to keep reading. The GOV.UK style guide makes a similar point about digital writing generally: put the thing the reader needs to do or know first, because most readers scan before they commit to reading in full.

Minutes that record a decision

Minutes that record the conversation, "there was a discussion about the budget, several views were expressed," are a record of the meeting having happened. Minutes that record the decision, who owns the action and the date it is due, "the budget for Q3 is approved as circulated; Priya to confirm supplier costs by the 14th," give the next reader something they can act on without having sat in the room. The test is simple: could someone who missed the meeting read the minutes and know what happens next.

A proposal that answers the question before justifying the answer

A proposal that opens with the background to the problem, the options considered and the criteria used, arriving at the recommendation only on the final page, asks a busy reader to trust that the destination will be worth the journey. A proposal that opens with the recommendation, "this report recommends moving the helpdesk to a single shared platform," and then sets out why, lets the reader judge the reasoning against a conclusion they already know, which is a faster and fairer way to read an argument than being led to it blind.

Each of these forms, along with what its reader needs first and what can be safely left until later, is covered in more detail on the reports, emails, minutes and proposals section of this guide. The Plain English Without Dumbing Down guide covers the sentence-level habits that make any of these four easier to read once the structure is right.