The 5-line update people actually read.

01 / Lead with what changed.

An update earns attention when it tells the reader something new. Start with the meaningful change since the last review: a direction has been approved, a deliverable is ready, or a dependency has shifted. Avoid opening with a list of meetings attended. Activity can explain progress, but it cannot stand in for it.

02 / Make the consequence clear.

Explain why the change matters to the project. A revised headline may require another design pass. An approved page may release the next stage of development. Connecting a change to its consequence gives the reader context for the decision you are about to ask them to make.

03 / Name the next action.

Use a verb, an owner, and an output. “Design to review” leaves too much room for interpretation. “Project lead to consolidate homepage comments into the review document” is easier to act on. Add a date only when it has been agreed, and distinguish a proposed deadline from a committed one.

04 / Surface the decision or risk.

If progress depends on a missing input, say so directly. Describe the dependency and the choice needed to resolve it. Keep the tone calm and factual. A useful update gives the team time to respond; it does not wait until the deadline is missed to explain what was blocking the work.

05 / Link the source of truth.

Finish with the current file or task. Link to the exact place a reader needs to review, rather than a folder full of versions. The update can stay short because the supporting detail has a clear home. Before sending, ask whether someone can act without asking you where the work is.