An async update is a structured, non-real-time communication, typically a written message, a brief recording, or a shared document, that replaces a synchronous meeting when the purpose is to share information rather than to make a decision.
The key distinction is intent: if the goal is for people to receive information, async is almost always more efficient; if the goal is to reach a decision together, synchronous is usually necessary.
Key takeaways
- Status updates, progress reports, and informational briefings are almost always better delivered async: they respect the recipient's time and create a searchable record.
- An effective async update answers three questions: what happened, what is next, and what, if anything, needs a response.
- Async does not mean slow. A well-structured async update often produces a faster decision than scheduling and running a meeting to discuss the same content.
- The habit of writing updates also improves meeting quality: managers who write clearly tend to run meetings more crisply because the thinking was done before the room filled.
Why it matters
Status meetings are the most common category of unnecessary synchronous time. When the purpose of a meeting is for multiple people to report what they have been doing, the meeting is serving the reporter, not the decision. A written update serves the reader, who can read it when relevant and skip the parts that are not.
Async updates also create a record that meetings do not. A weekly written update is searchable six months later. A status meeting is not. For teams that need to trace decisions, track progress, or onboard new members, the written record compounds in value over time.
For managers with high meeting load, converting status meetings to async is the fastest route to recovered focus time. One 30-minute status meeting per week per team becomes a five-minute read. At three teams, that is 90 minutes of synchronous time converted to fifteen minutes of async reading. The math is compelling even before accounting for the cognitive cost of context-switching between meetings.
How it works in practice
Writing an async update that actually replaces the meeting
-
State the purpose at the top
Open with one line: 'This update covers progress on X for the week of Y.' Readers should know in the first sentence whether this update is relevant to them and what it covers.
-
Use a consistent three-part structure
What happened (completed work, key events), what is next (planned work for the next period), and what needs input or attention (blockers, decisions needed, risks). Consistency means readers know where to find the parts they care about.
-
Keep it to five minutes of reading time or less
Async updates that require 15 minutes to read create their own meeting demand. Bullet points, short sentences, and links to detail are the right structure. The update is the summary; the linked document is the depth.
-
Be explicit about what response you need
End each update with a clear call to action: 'No response needed unless you see a problem' or 'Please confirm by Thursday whether the vendor timeline works for you.' Ambiguous async updates generate clarifying meetings.
-
Send on a consistent schedule
Weekly async updates sent on the same day at the same time get read more reliably than ad-hoc updates. Predictability trains the audience to expect and act on the information.
Common mistakes
Writing updates without a structure
Unstructured updates require the reader to do the work of finding the relevant information. A reader who has to search for the decision request will often give up and schedule a meeting instead.
Using async for decisions that need discussion
Not everything belongs in an update. A decision that requires debate, alignment, or negotiation needs synchronous time. Using async for those cases creates delays and miscommunication, not efficiency.
Making the update too long
A five-paragraph status narrative sends the signal that the writer did not edit. Long updates do not get read. If the update requires more than five minutes to read, restructure or split it.
Not following up on async questions
An async question that receives no response by a reasonable deadline needs a nudge, not a meeting. A single direct message asking for the input is usually sufficient.
What it sounds like
A manager has been running a weekly 45-minute status sync with three teams and is trying to reduce meeting load.
“I want to cancel the weekly status sync and replace it with written updates. Each team sends a three-bullet update by Monday morning,” said Guy.
“What if I have a blocker that needs input from another team?” asked Daniel.
“Flag it in the update and tag the team. If it is not resolved async by Wednesday, we do a 15-minute targeted call with just the relevant people,” said Guy.
Questions managers actually ask
How do I get my team to actually write async updates?
Provide a template with the three-part structure (what happened, what is next, what needs input) and commit to reading and responding to every update. If you engage consistently, the habit takes hold within two to three weeks.
What kinds of meetings should not be converted to async?
Decisions requiring debate, difficult conversations, performance feedback, and relationship-building should remain synchronous. The test: if real-time back-and-forth is likely to be necessary, keep the meeting.
What is the best format for an async update, written or video?
Written updates are searchable, skimmable, and faster to produce and consume for most content. Short videos under five minutes are better for demos, walkthroughs, or when tone matters. Default to written and use video selectively.
How do I handle a stakeholder who does not read async updates and keeps scheduling meetings?
Ask them directly what format works for them. Some stakeholders prefer a structured conversation over a written summary. The goal is to eliminate the status-only meeting, not to enforce a specific medium.
How is an async update different from a status report?
An async update is designed to replace a recurring meeting: it is shorter, more frequent, and explicitly identifies what needs a response. A status report is typically a formal artifact for leadership consumption, often weekly or monthly, with a different audience and level of detail.
Can AI help with async updates?
Yes. AI meeting assistants can generate a draft async update from a meeting transcript, converting a discussion into a structured summary. The manager reviews and sends it rather than writing from scratch.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.