Writing status updates people actually read: the five-line format

Visibility · 8 min read

Most status updates fail in a specific way: they are written for the writer's need to account for the week, in the order the week happened, at the length the week felt. The reader — a manager with nine other updates open — needs something else entirely: the state of the work, the evidence, and anything required from them, findable in under a minute. Every update that gets 'any updates?' replies and follow-up meetings is an update whose reader could not find those three things.

The fix is embarrassingly mechanical. A fixed five-part shape, a status vocabulary of four words, an ask that is never buried, and a production habit that means you never write the thing from memory on Friday afternoon. This guide lays out the format, shows the before-and-after on real-feeling lines, and gives the running-note procedure that makes the whole thing take five minutes.

The five-line shape

The weekly format that survives across template guides has the same skeleton: a header (period, author), a one-to-two sentence summary, key accomplishments, progress against goals with an explicit status, priorities for next week, and challenges with support needed (s1). Compressed for a busy reader, it becomes five moves. One: the status word, first, alone — On Track, At Risk, Delayed, or Ahead of Schedule, the standard labels defined once and then reused until they are reflex (s3). Two: the summary sentence — what the status word means this week, in one line. Three: results — the completed things, each with its evidence. Four: next — the priorities the reader will see reported on next week, which quietly makes this week's update a promise next week's must keep. Five: the ask — risks, blockers, and the specific decision or help needed, with an owner and a date (s2).

Two placement rules do most of the work. The status also goes in the subject line — 'Website redesign — At Risk — Oct 16' — because readers triage by subject and a status they can see without opening is a status that gets acted on; a simple red/yellow/green convention works the same way once readers learn it (s4). And the ask never travels inside a paragraph: it gets its own labelled line, because the single most common failure of status writing is the one decision you need, buried in the middle of a long block of prose (s2).

Set the contract once, out loud: tell your readers exactly what they will get and when — 'every Friday, a short update: status, results, problems, and what I need from you' (s4). The contract feels like overhead for one week and pays for a year, because readers stop wondering whether the update is worth opening. It always contains the same things, in the same order, at the same time — and the week it says At Risk, they already know where to look.

Results, not activity: the wording difference

The canonical mistake in status writing is listing activity rather than results: 'worked on the report' instead of 'completed the draft of section three' (s2). Activity lines are unfalsifiable and uncomparable — they tell the reader you were busy, which was never in doubt, and nothing about whether the work moved. Result lines carry a verb of completion, an object, and where possible a number: finished, shipped, approved, signed, tested with twelve participants. The worked examples in template guidance show the register — 'In progress: building the checkout page, 60 percent complete. Risk: the payment provider has not issued test credentials, which could delay integration by up to a week. Action: escalated Tuesday; decision needed by Thursday on the backup provider' — every line short, each carrying an owner or a date, fact separated from request (s2).

The honesty rule pairs with it. Reporting green every week until a sudden red erodes trust faster than any delay, because it teaches readers that your green means 'not yet admitted' (s2). Flag amber early, while the problem is still cheap: an At Risk with a plan reads as competence, and it is the deposit that makes a later Delayed survivable. The status vocabulary only works if each word keeps its meaning — which is a discipline about the past as much as the present.

Length follows from the discipline. An update whose results fit in five to eight lines is an update that gets read to the end; the detail your reader might someday want belongs in the linked document, the tracker, the appendix of your working life — referenced, not pasted. If a line does not change what the reader knows, decides, or does, it is diary, and the diary has its own home in your running note.

The running note: how the update gets written in five minutes

Writers who produce crisp updates on Fridays are not recalling the week better than you. They never recall it at all. The method the guides name is the running note: keep one note open all week, drop a line into it whenever something completes, blocks, or changes, and at writing time spend the last few minutes turning the note into the clean update — which removes the blank-page struggle entirely (s1). The note is allowed to be ugly. Its job is capture, not prose.

Run the note in the update's own shape — five headings matching the five moves — and Friday's work becomes sorting, not writing. Completions land under Results as they happen ('section three draft done, sent to Priya Tue'). Risks land under Ask with their dates. Next-week intentions write themselves from whatever is left open. The five-minute edit is then mostly deletion: strike the lines that turned out not to matter, tighten the ones that did, set the status word honestly, and send. The same note, kept across weeks, also becomes the raw material for reviews, handovers, and the 'what did we do last quarter' question that otherwise costs an afternoon of inbox archaeology.

One format, every week: consistency as the trust mechanism

The last rule is about time rather than text. Send at the same time every week, use the same format every week, and be consistent about honesty; readers learn the shape, learn where the ask lives, and start trusting and reading the updates because the cost of reading them keeps falling (s4). The counterpart mistakes are the format that changes weekly — so readers cannot compare periods — and the update calibrated to its audience's mood rather than the work's state (s2).

There is a quiet compounding here. A manager who trusts your updates stops asking for interim ones. A team that sees its work reported accurately borrows the format. And your own archive becomes the most reliable record of your work that exists anywhere — more reliable than memory, kinder than the ticket system, and already written. The update is the smallest document in your working life with the longest half-life. Write it like it will be read in a year, in five lines, by someone in a hurry. It will be.

Before and after: the same week, written two ways

Writing the weekly update in five minutes

1. All week: keep the running note open with the five headings; drop a dated line in whenever something completes, blocks, changes, or is promised.
2. At the scheduled time, open the note — not a blank document. Sort the week's lines under Results, Next, and Ask; delete what no longer matters.
3. Write the one-line summary and choose the status word honestly: would last week's reader, seeing this week's evidence, agree with the colour?
4. Check the ask: does it name a specific decision or help, an owner, and a date? If any of the three is missing, the ask is not finished.
5. Put the status in the subject line, send at the usual time, and start next week's note with the promises this update just made.

What success looks like: Success looks like this: your manager replies to the ask, not with 'any updates?'; nobody requests a meeting to find out what the update was supposed to say; and writing it took five minutes because the week wrote it for you.

FAQ

How long should a status update be?

Short enough to read in a minute: a status word, a summary line, three to five results, two to three next steps, and the ask. Detail belongs in linked documents; the update is the map, not the territory (s1, s2).

What if nothing is blocked and nothing is needed?

Say so in one line — 'Asks: none this week.' A visible empty ask teaches readers that when an ask appears, it is real. And check honestly first: most weeks contain at least a small decision someone else is unknowingly sitting on.

My manager never reads them. Why bother?

Because the record compounds even when the reader skims: performance reviews, handovers, and project post-mortems all run on exactly this archive. And readership usually follows consistency — same time, same shape, early honesty — more reliably than it follows reminders (s4).

General workplace-communication information only; adapt the format to your organisation's own reporting tools and conventions where they exist.

Back to all guides →