A useful meeting follow-up says what was decided, who will do what, and when it is due. Send it where the people doing the work can find it, and give them a chance to correct anything you misunderstood.
The meeting is over. Everyone remembers agreeing to something. This is an excellent moment to write down what that something was, before it becomes four different somethings.
Copy this follow-up
Keep the note short enough to scan, with a link to detailed notes for anyone who needs the context. The example below is fictional.
Subject: Onboarding pilot: decision and next steps Decision: Launch the pilot on May 19, provided reporting access is ready. Priya made the call after reviewing the support and engineering risks. Actions: - Morgan: confirm reporting access by May 12. - Alex: publish the support guide by May 15. Still open: If access is delayed, Priya will choose a fallback by May 13. Morgan will flag the issue directly to Priya as soon as it is known. Full notes: [link] Please flag corrections in the document by May 8.
The correction deadline applies to the record, not to urgent blockers. Name a separate escalation route when waiting for a reply would slow the work.
Record decisions and unresolved questions separately
Write the choice and enough context to explain it to someone who missed the call. If the group did not decide, say so. Record the missing information, who will find it, and who will make the eventual call.
For each action, name one accountable owner and an agreed due date. If several people will help, list them alongside the owner. If nobody accepted an action or date in the meeting, ask before recording it as a commitment.
Further reading: Asana: Meeting notes and action items
Choose who needs the note
Send the summary to participants and people affected by the decision. Use a shared project space when that is where the team already tracks its work. For a confidential conversation, share only with the people authorized to receive it; a private one-on-one does not need a team-wide recap.
If the update produces a disagreement that written replies cannot resolve, bring the people involved together for the specific trade-off. Afterward, update the same record so the next reader sees the outcome.
For the next written update, adapt the async update template.

