Meeting follow-up: what to send, when, and a template

· 4 min read

A good meeting follow-up is sent within a few hours, lists decisions and action items with owner and deadline, and links to anything people need to start. Keep it short enough to read on a phone. The reminders that come afterwards matter more than the email itself.

What to include

  • Decisions made, one line each.
  • Action items as a list: task, owner, due date.
  • Open questions that still need an answer, and who will answer them.
  • Date of the next meeting, or when this topic will be reviewed.

When to send it

Send it the same day, ideally within two hours. Memory fades quickly and the first day is when people are most willing to commit. If you cannot send it that fast, send only the action items.

Template

Subject: Follow-up: [meeting name], decisions and next steps

Hi all, thanks for the discussion. Here is what we agreed.

Decisions: 1) [decision]. 2) [decision].

Action items: [Owner]: [task], due [date]. [Owner]: [task], due [date].

Open questions: [question], [who] to answer by [date].

Reply if I got anything wrong. Next check-in: [date].

Beyond the email

The email is a record, not a nudge. People act on reminders sent where they work: a direct message the day before the deadline, another on the day, and a nudge when it is overdue. Add an escalation to the organizer if something is two days late.

Automating follow-up

Notemaker sends the summary to Slack, Teams, Discord, Google Chat, Telegram or email, messages each owner their own tasks with Done, Snooze, Reassign and Need-help buttons, and escalates overdue items, respecting working hours and time zones.

Frequently asked questions

How soon after a meeting should I send a follow-up?

Within two hours is ideal and the same day at the latest. Early follow-up gets higher completion because commitments are fresh.

Should the follow-up include the full notes?

No. Send decisions, action items and open questions. Link to the full notes or transcript for people who want detail.