The one-line status update: what every project update should say

Status updates have a way of growing. A weekly update becomes a page, a page becomes a deck, and the reader still cannot tell whether the project is fine. Most readers want the answer to three questions, and all three fit on one line.

The three questions

1. Is it on track? Yes, at risk, or blocked.
2. What happens next? The single most important next action.
3. Who has the ball? The person who owes that next action.

The format

`[Project]: [On track / At risk / Blocked]. Next: [action]. Ball: [person].`

For example:

• Website refresh: On track. Next: final copy review. Ball: Priya.
• Supplier contract: Blocked. Next: legal comments on clause 7. Ball: their legal team, chased Monday.
• Q1 hiring: At risk. Next: approve budget for second role. Ball: me.

A reader can scan ten of these in thirty seconds.

Why "who has the ball" matters most

"Blocked" on its own is not useful. "Blocked, waiting on their legal team since Monday" tells the reader exactly where help could unblock things. It also stops updates from hiding the fact that the next move is the author's own. See the who-has-the-ball framework.

Add detail only when asked

If someone needs more, they will ask, or you can link to the detail. The one line is the summary; it should not try to be the whole story. This keeps updates honest and short, which is the opposite of the trend we describe in AI-generated status reports.

Let the board write it

On a 2D board, the one-line update almost writes itself. Each project row shows whether actions are stuck in Other, what is in Mine, and who owns each one. Reading across a row gives you the status, the next action and the ball in seconds. For replacing status meetings entirely, see clear ownership without status meetings.