Blog · How-to

Follow-up email after a meeting: a template and example

By the Echo team · Published 26 October 2026 · 7 min read

In short: Send a follow-up email within 24 hours of the meeting, and keep it short. Include a subject line with the meeting name and date, the decisions, one owner and one due date for each action item, open questions and the next meeting. Send it to everyone who attended and to anyone who owns a task but missed the meeting.

What is a follow-up email after a meeting?

A follow-up email after a meeting is a short message that sends the outcome of the meeting to everyone who needs it. It says what was decided, who will do each task and by when, and what happens next. It is the fastest way to turn a discussion into work that people actually do.

It is not the same as the full record. Formal meeting minutes cover the whole meeting for the file. A follow-up email is the working summary that gets people moving this week. Many teams send one, and keep minutes only for boards, committees or clients who ask for them.

When should you send it?

Send it within 24 hours, while the discussion is still fresh. Granola, a company that makes meeting notes software, advises sending a recap within 24 hours and the same day for high-stakes meetings. An Arabic guide from ClickUp, a work-management software company, gives the same 24-hour window. Both are vendor guides, so treat the window as good practice rather than a rule.

Boston University’s communications team sets a looser limit for written meeting recaps: within two business days. Aim for the shorter window, and use the longer one as the deadline you must not miss.

Set a reminder for the end of the meeting. A follow-up email written from memory after three days is usually vague, and vague emails create the arguments you were trying to avoid.

Who should receive it?

Send it to everyone who attended. Then add anyone who was not in the room but needs the result: a manager who was waiting for the decision, a colleague who owns one of the tasks, or a client contact who was copied in. Boston University’s guidance makes the same point: recaps go to all attendees, and also to team members who missed the meeting but need to stay informed about the discussion and decisions.

Check the list before you send. Missing one owner is the most common reason an action item quietly stalls.

What should a follow-up email include?

Most good follow-up emails have five parts, in this order.

Subject line: the meeting name and the date, such as “Recap: Q4 pricing review, 26 October”. Someone searching their inbox in a month should find it in seconds.
Opening line: thank people for their time, and state the purpose of the meeting in one sentence.
Decisions: each decision written as a finished outcome. “The launch moves to 9 December” is useful. “We discussed the launch date” is not.
Action items: one task, one owner and one due date for each. The guide to writing action items explains how to make each one specific enough to finish.
Open questions and next step: what is still unresolved, who will bring it back, and the date of the next meeting or check-in.

Leave out the rest. Long background, quotes from the discussion and opinions about who argued well do not help the reader act.

Follow-up email template you can copy

Subject: Recap: [meeting name], [date]

Hi [names],

Thank you for your time today. The meeting was about [one sentence on the purpose].

Decisions

[Decision 1]
[Decision 2]

Action items

[Task]: [owner], by [date]
[Task]: [owner], by [date]

Open questions

[Question]: [who will follow up], by [date]

Next meeting: [date, time and link]. If I have missed or misunderstood anything, please reply by [date] and I will correct it.

Best regards,
[Your name]

Our free follow-up email template has the same structure with a filled-in example you can adapt in a few minutes.

What does a filled-in example look like?

Here is the same template after a short meeting about a website launch. The names are invented for the example.

Subject: Recap: website launch planning, 26 October

Hi all,

Thank you for your time today. The meeting was about the timing and owners for the website launch.

Decisions

The launch moves to 9 December, after the legal review.
The team will use the new photo set on the home page.

Action items

Draft the revised launch plan: Layla, by Thursday 29 October
Book the legal review: Omar, by Monday 2 November
Send the final photo set to the design team: Sara, by Friday 6 November

Open questions

Whether the Arabic pages need a separate review: Omar, will confirm by 2 November

Next meeting: Tuesday 3 November, 10:00, same link. If I have missed or misunderstood anything, please reply by Friday and I will correct it.

Best regards,
Yousef

Notice what the example does not do. It does not repeat the whole discussion. Each task has one name and one date, and the one open question has an owner and a day to come back.

How do you write it quickly and correctly?

Write the email from your notes, not from memory. Work through the notes in this order:

Decisions first. Find every sentence that starts with “so we agree”, “we will” or “the decision is”. Those are your decisions.
Tasks second. For each commitment, write the task, then ask: who said they would do it, and when?
Open questions last. Anything raised and parked goes here, with the person who will bring it back.
Check the facts. Read every name, date and number against the calendar invite and your notes before you press send.

If a due date was not set in the meeting, do not invent one. Write “date to be confirmed” and name the person who will propose it. A made-up date is worse than an honest gap, because it looks settled when it is not.

Common mistakes in follow-up emails

Vague tasks: “Follow up on the proposal” cannot be finished. Name the person and the deliverable.
Two owners: a task with two names often belongs to neither. Pick one owner and name the other as support.
Pasting the transcript: nobody reads a page of “he said, she said”. Summarise.
Waiting for a better moment: an email sent on Friday about a Monday meeting is rarely read in time.
Forgetting people who were absent: the person who owns the next task is the one who most needs the email.

Writing follow-up emails for mixed-language meetings

Many meetings in the Gulf switch between Arabic and English in the same sentence. Decide before you write which language the email will use. Most teams send in the language the majority of the group works in, and keep product names, job titles and file names in English so they can be searched later. If the meeting was in Arabic and some attendees read English only, a two-line summary in each language is better than a long email in one.

For a deeper look at this, read our guide to taking meeting notes in Arabic.

Where Echo fits

Echo is an AI notetaker that works in Arabic and English. On iPhone and Mac it records the meeting, transcribes it, and writes a summary with the key points and decisions, plus a to-do list. Use those as the starting point for your follow-up email: check each decision and task against what you remember, then send. Echo does not send the email for you.

Echo is free for 30 minutes of recording a month, with up to 15 minutes per recording. Echo Pro gives unlimited minutes and recordings of up to 4 hours. See pricing for the current plans. Before you record anyone, tell them and ask first. The law on recording differs from country to country, so check the official rules where you are.

Frequently asked questions

How long should a follow-up email after a meeting be?

Short enough to read in under a minute. Most follow-up emails need a subject line, a two-sentence opening, the decisions, one line per action item with an owner and a date, the open questions, and the next meeting. For a short meeting that is often under 200 words. If it is getting longer, move detail into a linked document.

Should I send meeting minutes or a follow-up email?

For most meetings, send a follow-up email. It is quicker to read and it gets people working. Send formal minutes when a board, committee, client or policy requires them, or when you need a record of votes and motions. Many teams do both: the email the same day, and the minutes later.

What if I forgot an action item or made a mistake?

Send a short correction as soon as you notice, with the item, the owner and the corrected date. Say what changed. Do not wait for the next meeting. A quick correction is better than a silent mistake that someone acts on.

Should the follow-up email be in Arabic or English?

Use the language most of the people who will read it use day to day. In a mixed meeting, keep product names, job titles and file names in English so they are easy to search, and write the decisions and tasks in the language your readers will act on.

Sources

Checked on 26 October 2026.

Try Echo on your next meeting. Free for 30 minutes a month.

Try Echo free