Asynchronous meetings: how to replace status meetings without losing the plot

Teams don't have too many meetings because they like meetings. They have them because a meeting is the only reliable way they know to get updates, collect opinions and make sure someone actually makes a call. Take the meeting away and the work scatters across chat threads, email and documents nobody can find.

An asynchronous meeting fixes that. It keeps what a meeting gives you (a clear purpose, the right people, a deadline and a record of what was decided) and drops the part where everyone has to be in the same place at the same time. This guide covers when to go async, the practices that make it work, and how to convert one recurring status meeting this week.

What is an asynchronous meeting?

An asynchronous meeting is a structured exchange that people take part in on their own schedule, within a set window. Instead of a 30-minute call, you share the context and the questions up front. Each person adds their input before a due date. Then someone closes it with a conclusion everyone can see.

That last part is what separates an async meeting from "just send a message." A good async meeting has:

• A goal. One sentence on what this exchange needs to produce.
• Specific prompts. Questions people answer, not a document they are vaguely asked to "look at."
• Named participants. Only the people whose input you need.
• A window. A start and a due date, so it doesn't drift for weeks.
• A conclusion. A written outcome: the decision, the next steps, the owner.

Synchronous vs asynchronous meetings

A synchronous meeting happens in real time: everyone joins the same call or room at the same moment. An asynchronous meeting happens over a window of hours or days, and each person takes part when it suits them. Neither is better in general. They are good at different things.

Most teams need both. The goal is to stop using live time for things that don't need it, so the meetings you keep are shorter and about decisions.

When to go async and when to meet live

Async isn't the goal. Good decisions and steady progress are. Some conversations really are better live, and pushing them async just creates long, tangled threads. Use the purpose of the meeting to decide.

A simple rule of thumb: if one person talks and everyone else listens, it can be async. If the group needs to react to each other in real time, meet. And if you do meet, do the prep async so the live time goes to the decision.

Asynchronous meeting best practices

Async meetings fail in predictable ways: nobody responds, people respond with "looks good," or everyone responds and nobody decides. These asynchronous meeting best practices prevent each of those.

1. Start with a one-line goal. Write down what the exchange must produce before you invite anyone. "Agree on the launch date" is a goal. "Discuss the launch" isn't.
2. Ask precise questions. "Please review this proposal" gets you silence or polite approval. Ask what you actually need: "Which of these two options would you pick, and why?" "What's the biggest risk you see in this plan?" "Is anything missing that would block your team?"
3. Invite fewer people. Every extra participant adds more to read and makes it easier for each person to assume someone else will answer. Invite the people whose input changes the outcome. Share the conclusion with everyone else.
4. Give context up front. Put the background, the relevant files and any constraints at the top, so nobody has to go hunting or ask before they can answer. A short screen recording often explains a draft faster than a page of text.
5. Set a due date and stick to it. Flexibility is the point of async, but open-ended means never. A clear window, like "input by Wednesday at noon," lets people plan their week and tells everyone when the decision happens.
6. Make it visible who has responded. Accountability in async work comes from transparency, not chasing. When everyone can see who has added their input, most people add theirs.
7. Always close with a conclusion. Summarize what was decided, what happens next and who owns it. An async meeting without a conclusion is just a thread, and threads get reopened.
8. Keep the record in one place. Decisions scattered across email, chat and documents are how teams end up re-deciding the same thing. Keep the conclusion with the work it belongs to, so the next person can find it.
9. Reuse a template. A weekly update or a design review follows the same pattern every time. Save the structure once and stop rebuilding it.

A simple async meeting template

Every async meeting needs the same six parts. Copy this structure into your tool of choice and fill in each line before you invite anyone.

How to replace one recurring status meeting

Don't try to move your whole calendar async at once. Pick one recurring meeting, ideally a weekly status or update meeting where people mostly report and listen, and convert just that one. Here is how.

1. Check what the meeting really does. Look at the last few instances. Write down what actually came out of them: updates shared, blockers raised, decisions made. Usually most of it is updates, and a small part is the one or two things that needed a real discussion.
2. Turn the agenda into prompts. Each recurring agenda item becomes a question. A typical set: "What did you finish this week?", "What are you working on next?", "What's blocking you?" and "Is there anything you need a decision on?"
3. Set the window. Pick a start and a due date that fit the old rhythm. For example, the update opens Monday morning and is due Wednesday at noon, so the leader can read it and act before the end of the week.
4. Tell the team what changes. Explain that the meeting slot is gone, where to add updates, and when. Be clear that blockers still get attention, they just get raised in writing first.
5. Read, respond and conclude. When the window closes, read every update, reply where needed and write a short conclusion: decisions made, blockers and who is handling them, anything that needs a live conversation.
6. Escalate only what needs it. If one blocker needs a real discussion, book a short call with just the two or three people involved. That replaces a full-team meeting with a smaller, focused one.
7. Review after a month. Ask the team what's working and what's missing. Adjust the prompts or the window. If people miss the social side, add a short live check-in less often, rather than bringing back the full status meeting.

What an async update looks like in Nova

In Nova, a meeting is a session. A session can be a live meeting, a workshop or async work that people complete in their own time. Each session has goals and instructions, a start and due date, and a list of steps. Each step asks for one kind of input, such as an individual note, comments, a vote or an approval.

A few details make this work without anyone chasing:

• Owners and due dates per step. You can assign specific people to a step and give it its own due date. Assigned sessions and steps show up on each person's Tasks, Sessions and Calendar pages, and can sync to Google Calendar or Outlook.
• Private answers when you need them. Set a step to Collaborator responses private so each person sees only their own notes, which is useful for honest feedback.
• Completion you can see. People select Mark complete for me when they are done, so you can tell who has added their input and who hasn't.
• Conclusions, written or drafted. Write the conclusion yourself, or select Generate AI Conclusions to have Nova AI draft one from the notes, then edit it.
• A weekly rhythm. With Nova Pro, use Make recurring to repeat the session every week. The project's Rituals tab lists every recurring session.

To start with a ready-made structure, open the asynchronous meeting template or the daily stand-up template in the process library. For the full list of step types and settings, see Sessions and steps.

Run reviews and approvals in order

Feedback and approvals are where async saves the most time, because they usually happen in a sequence: someone shares a draft, reviewers comment, one person approves. In a Nova session, a step can wait for the one before it. Turn on Notify assigned when previous step is complete and the next owner gets an email when it's their turn, instead of waiting for the next meeting.

You can also invite people outside your team, such as clients or partners, as collaborators on a single session. They see only that session and nothing else in your workspace. The async design review template gives you this structure ready to use.

How to make decisions asynchronously

Async decision making works when everyone knows what is being decided, by whom and by when. Without that, a written discussion goes around in circles. Use these five steps:

1. Name the decision, the owner and the deadline. "Maria decides by Friday which vendor we sign with." One person makes the call, even if many give input.
2. Lay out the options and trade-offs. Two or three options, with the cost, risk and benefit of each. People can't weigh in on a decision they have to reconstruct first.
3. Collect positions, not comments. Ask each person to pick an option and give one reason. A vote or an approve/decline step gets clearer input than an open thread.
4. Decide and write it down. The owner posts the decision, the reason and what happens next, in the place the team will look for it later.
5. Escalate only if stuck. If positions are split and the trade-offs are unclear, book a short live call with the people involved. The written input means the call can start from the options, not from the beginning.

What to look for in tools for asynchronous decisions

Chat and email can carry a discussion, but they are poor at closing one. A tool for async decisions should give you:

• Structured prompts, so people answer the question you asked.
• Votes and approvals, so input is a clear position.
• Due dates and visible completion, so you can see who has responded.
• A written conclusion stored with the work, so the decision is findable months later.
• Notifications when it's someone's turn, so nobody waits for the next meeting.

In Nova, these are step types and settings in a session: Multiple choice for votes, Approve / decline for sign-offs, due dates per step, Mark complete for me for visible completion, and conclusions that go to the project's decision log.

Keep a decision log instead of meeting notes

The real cost of moving away from meetings isn't the updates, it's losing track of what was decided. Meeting notes rarely help, because nobody goes back to them. A decision log does, because it holds only the outcomes.

In Nova, every project has a Decision log. Session conclusions appear in it automatically, and you can add entries with Log an update. Each entry has a type, such as a decision, a win, a blocker or a date change, and a severity.

When sessions are connected on the project board, conclusions can also flow forward. The next session shows them under Previous conclusions and decisions, so this week's update starts from last week's outcomes. See Track progress and report for the full set of project views.

Asynchronous work best practices beyond meetings

Async meetings are easier when the rest of the team's work is async-friendly too. These habits make the difference:

• Agree on response times. For example: chat within a few hours, async meeting prompts by the due date, urgent issues by phone. People stop checking messages constantly when they know what's expected.
• Write for the reader who wasn't there. Lead with the point, then the context. A message that needs a follow-up question costs a day in async work.
• Keep status visible instead of reported. When tasks, owners and due dates are where everyone can see them, nobody needs a meeting to ask where things stand.
• Protect a few overlap hours. Async doesn't mean never together. Teams across time zones often keep two or three shared hours for quick calls.
• Keep one place per topic. A discussion that starts in chat and continues in email and a document is impossible to follow. Pick where each kind of work lives.
• Protect focus time. The point of async is longer stretches without interruptions. Batch notifications and turn them off during deep work.
• Make ownership explicit. Every task, decision and open question needs one named owner. "The team" never answers.

Common mistakes to avoid

• Async in name only. A long document with "thoughts?" at the bottom isn't an async meeting. Without prompts, a due date and a conclusion, it's a thread.
• Replacing every meeting. Teams that cancel everything lose connection and end up with more chat, not less. Keep the live time that builds trust.
• Leaders who don't close the loop. If people add input and never hear what happened, they stop adding it. The conclusion is your half of the deal.

Frequently asked questions

What is the difference between synchronous and asynchronous meetings?

A synchronous meeting is live: everyone takes part at the same time, on a call or in a room. An asynchronous meeting runs over a window of hours or days, and people add their input when it suits them, before a due date.

What are the best practices for asynchronous meetings?

Give each async meeting a one-line goal, specific questions, only the participants you need, a clear due date and a written conclusion. Make it visible who has responded, and keep the outcome in one place with the work.

What's the difference between an async meeting and a status email?

A status email goes one way. An async meeting has a goal, specific questions, named participants, a due date and a conclusion. Everyone adds input in the same place, and the outcome is recorded where the team can find it later.

How do I get people to actually respond?

Ask fewer, more specific questions, invite only the people whose input you need, and set a clear due date. Then close every exchange with a conclusion, so people see that their input led somewhere. When completion is visible to the group, most people respond without reminders.

How long should the response window be?

Long enough for everyone to fit it into a normal working day, and short enough that the decision doesn't stall. For a weekly update, a day or two is common. If your team spans many time zones, make sure the window includes a full working day for everyone.

Do async meetings work for remote and hybrid teams?

Yes, they work especially well. Async meetings don't depend on overlapping hours, so people in different time zones take part on equal terms. For a hybrid team, they also mean the people in the office don't make decisions in a hallway that remote colleagues never hear about.

Can I try this without changing my whole calendar?

Yes. Start with one recurring meeting, follow the steps above, and review after a month. If you want a structured push, the Friday back challenge walks your team through cutting meeting time, and Meetings that actually work shows how Nova handles both live and async sessions.