How to Write Great Async Status Updates

A weekly async update is the smallest, highest-leverage habit on a remote team. It saves meetings, surfaces blockers, and forces clarity on what is actually happening.

1. Why async updates matter

Async updates:

replace status meetings
align distributed teams across time zones
help leadership trust your work
create a paper trail of decisions

Strong remote workers send strong updates.

2. The five-section template

Use this every week.

Sections:

this week: what shipped
next week: what is planned
blockers: what is stuck
key decisions: what was decided
one win or learning: a personal note

Five short sections. 200 to 400 words.

3. Lead with the most important thing

Most updates bury the lead.

Open with:

the biggest accomplishment
the most critical blocker
the most strategic decision

Skim-friendly leads keep readers engaged.

4. Use bullet points

Walls of text get skipped.

Use:

bullets for lists
short paragraphs for context
bold for key points
TL;DR at the top of long updates

Format for skimmers.

5. Be specific

Vague updates do not help anyone.

Bad:

"Worked on the new feature."

Better:

"Shipped phase 1 of onboarding redesign. Activation lifted from 41 percent to 49 percent so far."

Specifics build trust.

6. Include numbers when possible

Numbers anchor your work.

Examples:

"Closed 4 deals worth $48k ARR."
"Cut bug backlog from 24 to 9."
"Published 3 articles, 2 on first page within a week."

Numbers signal real impact.

7. Mark blockers clearly

Blockers should be obvious.

Use:

"BLOCKER:" prefix
explicit owner of the blocker
proposed resolution

Hidden blockers are the worst kind.

8. Include decisions

Decisions are the most underused part of updates.

Format:

decision made
alternatives considered
person who decided
implications

Documenting decisions saves rework.

9. End with a personal note

A short personal note humanizes the update.

Examples:

"Heads up: out Thursday afternoon for a kid's school event."
"Win: finally automated the QA report."
"Learning: discovered that two clients had the same hidden need."

Personal notes build remote relationships.

10. Set a consistent cadence

Pick a day and stick with it.

Common cadences:

Friday afternoon (weekly recap)
Monday morning (week-ahead plan)
Wednesday midweek (current status)

Consistency builds trust faster than perfection.

11. Keep updates skimmable

Aim for 200 to 400 words.

Tactics:

short bullets
one bold line per section
subheadings for each section
minimal jargon

Long updates get archived.

12. Use Loom when text fails

Some updates are clearer with voice.

Use Loom for:

complex decisions
design walkthroughs
post-incident reviews
nuanced demos

A 3-minute Loom often replaces a 30-minute meeting.

13. Make updates discoverable

Place updates somewhere everyone can find.

Options:

a shared Notion or Coda page
a dedicated Slack channel
a recurring email thread
a project tracker (Linear, Asana)

Searchable updates compound knowledge.

14. Make it easy on yourself

Use a template.

Template:

This week:

shipped X

made Y decision

moved Z forward

Next week:

finishing X

starting Y

kicking off Z

Blockers:

none

Wins / learnings:

one note

Templates reduce friction.

15. Update upward and outward

Update both:

your team (peers and reports)
your manager or stakeholders

Different audiences need slightly different framing, but the structure is the same.

16. Use updates in 1-on-1s

Strong 1-on-1s start with the latest update.

Structure:

read the update before the call
skip routine status questions
spend the time on coaching, ambiguity, and growth

Updates upgrade 1-on-1s.

17. Common update mistakes

writing too long
skipping blockers
vague language
inconsistent cadence
writing only when asked

Each weakens trust.

A final thought

A great async update is short, specific, and consistent. Five sections, 200 to 400 words, every week. Done well, your updates make you the most trusted person on the team.