ASYNC STATUS UPDATE TEMPLATE

Replace the status meeting without losing the signal.

A useful async update separates progress from decisions. Readers should be able to scan what changed, who owns the next action, and what actually needs a live conversation.

Weekly async update

Outcome we are moving: [one sentence]

Changed since last update: [facts, shipped work, or decisions]

Next action and owner: [name + action + date]

Blocked by: [specific dependency + person needed]

Decision requested: [choice + decision owner + deadline]

Live discussion needed only if: [tradeoff, disagreement, or risk that cannot be resolved in writing]

Three rules that keep it useful

Write for scanning.Lead with what changed. Link to detail instead of pasting a full project history.
Separate blockers from decisions.A blocker needs help; a decision needs a bounded choice and a named owner.
Use a live-time trigger.Call a meeting when disagreement, ambiguity, or coordination genuinely benefits from real-time discussion.

A two-week replacement test

Replace two occurrences of one status-only meeting with this update. Track delayed decisions, unclear ownership, missed dependencies, and the amount of follow-up chat. Restore a live meeting only around the work that actually needs the room.

Do not turn async into silent overload.

Set a deadline for reading and responding, keep one stable update location, and summarize the final decision where everyone can find it.

PAIR IT WITH AN AUDIT

Use the free Meeting Reset Starter.

Decide whether to keep, shorten, shrink, or replace the meeting, then review the result after two cycles.

Download free PDF

MEASURE THE BASELINE

See how many team-hours the current meeting consumes.

Open the free calculator