How to Write an Async Standup Update

The async standup is supposed to replace the daily meeting, but most written updates fail to earn that trade. They are either a diary (“spent the morning in emails, then some meetings, then got into the code”) or a status so vague nobody can act on it (“making progress, still working on the thing”).

A good async update does what the standup meeting did, without the meeting: it tells the team what moved, what is stuck, and where you need help. It is scannable in ten seconds and complete in three lines.

Use The Three-Line Shape

The classic yesterday, today, blockers format works because it maps to what teammates need: what changed, what is coming, and what might slow it down. Keep each to a line.

Before:

Been heads down on the payments work, ran into some issues with the API but I think I have a handle on it now, will keep pushing today and hopefully wrap it up soon.

After:

Done: payments refund flow is built and tested. Today: wiring it into the admin panel. Blocked: need the final refund policy from Legal to finish the copy.

The second version is scannable, specific, and surfaces the blocker where someone can act on it.

Make Blockers Loud And Addressable

The blocker line is the whole reason async standups exist. Do not soften it into invisibility. Name what you need and who you need it from.

Blocked since Tuesday: waiting on staging access from Infra. This is holding the release. Marco, can you approve or point me to who can?

A blocker that names a person and an ask gets resolved. A blocker phrased as “still waiting on some things” gets scrolled past.

Report Outcomes, Not Hours

Nobody on the team needs your timesheet. They need to know what state the work is in. Replace effort with status.

Instead of “spent all day on the migration,” write “migration is 80 percent done, the last blocker is the legacy data cleanup, expect to finish tomorrow.”

Status lets teammates plan around you. Effort just tells them you were busy.

Keep It Consistent Day To Day

An update that changes shape every day is hard to scan across a team. A steady structure lets people read six updates in the time it used to take to read one rambling one.

Since you write these daily, it is worth locking the format. A Wrivio Context for standups could say:

Rewrite this as a scannable async standup update in three parts: Done, Today, and Blocked. Report concrete outcomes and states, not hours or activity. Make any blocker specific, naming what is needed and from whom. Keep it under 60 words and consistent in structure. Keep all names and dates exactly as written.

Press Ctrl+Shift+Space, paste your rough notes into the overlay, and run it. Read the result and confirm the blocker line names a clear ask, and the whole thing scans in seconds.

If your update references internal systems or unreleased work, run the rewrite in Wrivio’s Local mode so it stays on your machine.

The Scroll Test

Before you post, imagine a teammate scrolling ten updates on a busy morning. Would yours give them what they need in one glance, and would your blocker jump out to the person who can clear it? If so, you have replaced the meeting properly, which is the entire point of writing it down.

Download Wrivio for Windows to turn a rambling status into a standup update your team can act on in seconds.