If English is your second language, the temptation with a status update is to write more, not less — extra context to compensate for uncertainty about phrasing. It backfires. Long updates get skimmed, and skimming a paragraph written by someone hedging produces a vaguer impression than four blunt lines would have.

The format below is what our own team converged on. It is boring on purpose.

The format

Status:   one of Done / On track / At risk / Blocked
Shipped:  what changed, in the past tense, with a link
Next:     the single next thing, with a date
Need:     the specific decision or help required, or "nothing"

Four lines. Under sixty words. No preamble, no apology for the length, no “hope this helps”.

A real one:

Status:   At risk
Shipped:  Search indexing moved to the queue worker (#2841).
Next:     Backfill the existing 40k docs — Thursday.
Need:     A decision on whether stale results are acceptable
          during the backfill window.

Why each line earns its place

Status first, as a single word. Anyone scanning a channel gets the answer without reading the rest. Putting it last — the natural instinct, since it follows from the detail — means the reader has to reconstruct your conclusion.

Shipped in the past tense, with a link. Past tense forces specificity: “worked on search indexing” survives being vague, “moved search indexing to the queue worker” does not. The link means nobody has to ask.

One next thing, with a date. Three next things is a plan, not an update, and a reader cannot hold three. A date without a “roughly” or “hopefully” — if you are unsure, that uncertainty belongs in Status, not smuggled into an adverb.

Need, always present. The most common failure in an update is an unstated blocker, because saying you are stuck feels like admitting fault. Making the line mandatory removes the decision. Writing “nothing” is fine and takes one word.

Why it helps non-native writers specifically

The format removes exactly the parts of English writing that are hardest to get right when it is not your first language:

  • No transitions. Linking sentences smoothly — “that said”, “consequently”, “in light of which” — is where register goes wrong. Labelled lines need none.
  • No hedging vocabulary. The set of English softeners is large, idiomatic, and easy to misuse into sounding either rude or evasive. A one-word status has no room for them.
  • No length judgement. Deciding how much context an English-speaking reader needs is genuinely hard. Sixty words removes the question.

The goal is not to sound like a native speaker. It is to be unambiguous, which is a lower bar and a more useful one.

Pair it with a prompt

Write the update in whatever language you think in, then convert it. This prompt does the whole job:

Rewrite the selected text as a status update with exactly four labelled
lines: Status, Shipped, Next, Need.

- Status must be one of: Done, On track, At risk, Blocked.
- Shipped: past tense, specific, keep any links or ticket IDs verbatim.
- Next: one item only, with the date from the text. If no date is given,
  write "no date set".
- Need: the decision or help required, or "nothing".

Do not add information that is not in the text. Under 60 words.
Return only the four lines.

The two constraints doing the work are “do not add information” and the explicit no date set fallback. Without them a model will invent a plausible deadline, and a plausible invented deadline in a status update is considerably worse than a missing one.

When to break it

Incidents. During an incident, write prose and write it as it happens — the format’s compression is exactly wrong when the reader needs a timeline. Everything else, four lines.

← All posts