The meeting follow-up email: a template, and what to leave out

A meeting ends with everyone agreeing on what happens next. Two days later, three people remember three different versions. The follow-up email is how you stop that from happening: a short written record, sent while the meeting is still fresh, of what was decided and who’s doing what.

It’s also one of the easiest ways to look organised. Most people mean to send one and don’t. Here’s a template that takes five minutes, and what to leave out so people actually read it.

The template

Subject: [Meeting name], next steps

Hi all,

Thanks for the time today. A quick summary so we're on the same page.

Decided
- [Decision 1]
- [Decision 2]

Next steps
- [Owner]: [what], by [when]
- [Owner]: [what], by [when]

Open
- [Question nobody owns yet]

Next meeting: [date], or [what will trigger the next one].

[Your name]

That’s the whole thing. Most follow-ups should fit on one screen without scrolling.

Why each part is there

The subject line says what it is. “Product weekly, next steps” is easy to find later. “Follow-up” or “Notes” isn’t, because every follow-up is called that.

Decisions come before tasks. Decisions are what’s now settled: “The beta opens on 14 November.” Putting them first answers the question people actually have, which is “so what did we agree?” It also gives anyone who disagrees a clear moment to say so.

Every task has an owner and a date. “Ayşe: send the two pricing options, by Thursday.” A task without a name is a wish; a task without a date drifts. If you write only one part of the email carefully, make it this one. There’s more on getting these right in our post on turning a meeting into a task list.

Open questions get their own heading. Things that were raised but not settled belong here, not disguised as decisions. It’s honest, and it stops them from disappearing.

The next meeting closes the loop. A date, or a condition like “once the quote is signed”. It tells everyone when the next checkpoint is.

Example: an internal meeting

Subject: Product weekly, next steps

Hi all,

Thanks for today. Quick summary:

Decided
- The beta opens on 14 November.
- Pricing stays as it is until January.

Next steps
- Ayşe: two pricing options to the team, by Thursday.
- Me: beta release notes, by Friday.
- Mikko: book the Wednesday call with support, today.

Open
- Who reviews the release notes?

Next meeting: Monday at 10:00.

Example: a client call

With clients, add a line of thanks and keep your own commitments prominent. They’ll judge you on whether you do what you said.

Subject: Nordia onboarding call, next steps

Hi Sanna,

Thanks for walking us through your setup today. Here's what we agreed.

Decided
- We'll start with the two Helsinki teams; the rest follow in January.

From our side
- Revised quote, by Friday.
- Onboarding checklist, by Wednesday.

From your side
- List of team admins, when convenient.

Let me know if I've missed anything. Talk on the 12th.

Alex

Splitting “from our side” and “from your side” makes the client’s tasks feel like a shared plan rather than a demand.

What to leave out

The discussion. “We talked about whether the beta should slip and looked at several options” tells the reader nothing they can act on. Write the outcome: “Decided: the beta opens on 14 November.”

A full transcript or long notes. If people need the detail, link to the notes. The email is the short version.

Everyone’s every word. You don’t need to attribute who said what, unless a decision depends on it.

Hedging. “I think we sort of agreed that maybe…” invites the meeting to happen again over email. If something wasn’t decided, put it under Open.

Lateness. Send it within the hour, or the same day at worst. A follow-up that arrives two days later competes with everyone’s own memory of the meeting, and loses.

When you don’t need one

A five-minute check-in with one person rarely needs a follow-up email; a chat message with the one task is enough. Send the full version when there were decisions, when more than two people have tasks, or when someone outside your team was in the meeting.

Letting an app draft it

Writing the email is quick. Remembering the decisions and tasks accurately is the hard part, especially if you were also running the meeting.

Gistsmith, the Mac app we make, writes a note when the meeting ends, with your tasks first, then decisions and a summary. From that note, the Follow-up email recipe drafts this exact email: a subject line, thanks, the decisions, who does what by when, and the next step, written in the language the meeting was held in. You read it, fix anything that’s off, and send it from your own email.

It listens on your Mac with no bot in the call, and runs on Macs with Apple silicon and macOS 15 or later. The first 3 meetings or 7 days are free without a card; after that it’s $5.99 a month or $49 a year.

Whatever writes the first draft, read it before you send it. The follow-up is a promise to the people who were there, and it should say what they agreed, not what a tool guessed.

The short version

• Subject: meeting name and “next steps”.
• Decided, then Next steps (owner, what, when), then Open.
• Name the next meeting or checkpoint.
• No discussion, no transcript, no hedging.
• Send it within the hour.