Reports and briefs

A report is writing with a job: someone reads it and then decides, approves, or acts. That job changes how you draft it — and it's why report work belongs at the careful desk, where long instructions get honored and the input documents stay anchored. This lesson is the report workflow end to end: from "I owe them a write-up" to a document that survives its reader's questions.

Start from the reader's decision. Before any drafting: "who reads this, what do they decide after reading, what do they already believe?" Put those three answers at the top of the ask. A report aimed at a decision writes itself tight; one aimed at "covering the topic" bloats by design. This is the outline-first rhythm from the writing course, with the outline's first question sharpened.

Feed it the evidence, not the vibe. Reports run on material: the data file, last quarter's version, the meeting notes, the source documents. Attach them and bind the draft to them — "use only the attached material; mark [gap] where evidence is missing." The gaps that surface are your to-do list, and they surface before the reader finds them, which is the whole difference between a draft and an embarrassment.

Structure: conclusion first, always. Busy readers read the first paragraph and skim the rest. Ask for that shape explicitly: "one-paragraph summary a reader could act on alone; then findings, each with its evidence and source; then recommendations with their trade-offs; appendix for everything else." If the summary can't stand alone, the report isn't done — that's the test, and it's checkable in ten seconds.

The hostile read before it ships. Reports meet skeptics, so rehearse: "read this as the most critical person in the room: what would they challenge, what number would they ask the source for, what alternative explanation fits the same evidence?" You know this switch from the idea sessions; on reports it's the difference between defending your work in the meeting and discovering its holes there.

Recurring reports become templates-plus-rooms. The monthly status, the quarterly review — freeze the structure as a template, run it inside the project room that holds the standing context, and let each run diff against the last: "what changed since the previous report, and what stayed stubbornly the same?" The stubborn list is often the real report.

Briefs are reports with the appendix amputated. The one-page version — for the busy stakeholder, the pre-meeting read — isn't a shrunken report but a different ask: "from this full report, a one-page brief: the decision needed, three facts that drive it, the recommendation, and what happens if we do nothing." Write the full version first, brief second; a brief written from evidence you've already structured stays honest, while a brief written from memory smuggles in whatever you wish were true.

One mistake to skip: writing the report to demonstrate effort. Length signals work; readers reward clarity. If the honest content is four paragraphs, four paragraphs plus an appendix beats twelve pages of upholstery — and the ask should say so: "as short as the evidence allows." The courage to be brief is a human contribution; the machine will pad happily forever if you let it.