How to Create a Meeting Follow-Up Email

Why send one

A follow-up email does three jobs. It proves you listened, it creates a written record of decisions, and it gives everyone a chance to correct a misunderstanding while it is cheap to fix. It also shows professionalism, which matters when you are selling or serving.

When to send it

The same day, ideally within a few hours. The longer you wait, the less accurate your memory and the less urgent the email feels.

What to include

1. A subject line that says what it is. "Recap: website kickoff, 12 Oct" works better than "Following up".
2. A thank-you in one line.
3. The key points discussed, in two to four bullets.
4. Decisions, written as full sentences.
5. Action items with an owner and a date.
6. Open questions and who will answer them.
7. A request for correction: "Reply if I have missed anything."
8. The next step or meeting date.

A worked example

Subject: Recap: website kickoff, 12 Oct

Hi Priya,

Thanks for your time today. Here is what I understood:

Decisions
- The site launches on 14 November.
- Northwind sends all copy by 24 October.

Next steps
- I will send the revised scope by Friday.
- Dev will share design options on Tuesday.

Still open
- Hosting access: could you confirm by 19 October?

If I have missed or misunderstood anything, tell me and I will correct it.

Best,
Alex

More ready-made versions are in our follow-up email templates.

Tone and length

Keep it short and neutral: one screen is enough. State agreements as facts and uncertainty as questions. Never present a suggestion as a decision, because a client may treat your email as the record.

Mistakes to avoid

• Waiting a week.
• Vague actions with no owner or date.
• Over-confirming: writing "agreed" about something that was only discussed.
• Burying actions in a long paragraph.
• Sending nothing and hoping memories match.

Using MeetMemo

MeetMemo's notes include a suggested follow-up message based on the meeting, and its action items include owners and dates only when they were stated. Treat the suggestion as a draft: read it, correct it and send it yourself. See AI meeting summaries and meeting action items. The product is in early access.

Subject lines that get opened

A good subject line says what the email is, so it can be found later.

• "Recap: [meeting title], [date]"
• "Action items from [meeting title]"
• "Confirming what we agreed on [date]"
• "Next steps for [project name]"
• "Question before I write the proposal"

Avoid vague lines like "Following up" or "Quick note", which are hard to search for and easy to ignore.

Follow-ups for different meetings

• After a sales call: thank them, restate their problem in their words, confirm what you will send and when, and propose a next step with a date.
• After a project meeting: list decisions and actions with owners and dates. Keep it short.
• After a client disagreement: stay neutral. State what each side said, what was agreed, and the next step. Avoid assigning blame in writing.
• After a first meeting with a stranger: keep it warm and brief, and include the one thing you promised to send.

When nobody replies

Silence is not agreement. If you asked for confirmation of decisions, set a date in the email: "I will treat this as confirmed on Friday unless I hear otherwise." Then, on Friday, send a one-line note to say you are proceeding on that basis. This is polite, clear and leaves a record.

What not to put in a follow-up

• Anything you would not want quoted back to you
• Confidential details about other clients
• Commitments you are not sure of
• A long recap nobody asked for

Frequently asked questions