Meeting follow-up email template and example

Edit or download the email template

Replace the brackets with details from your meeting and copy the finished email into your mail app. The Word and TXT links download the blank template, which you can also edit separately.

Decide what the recipient needs to do

Start with the outcome the reader needs: review a draft, send feedback, approve a choice or clarify a question. Keep the subject specific enough to find later, such as “Website review: copy options and next steps”, and put the confirmed outcome before the background.

A follow-up email is a message people can act on. If you also need a complete record of the discussion, use the meeting minutes template and keep the email focused on the decisions and actions relevant to its recipients.

Example: a client meeting about a website

This fictional example shows how to report progress without implying that every proposal has been approved. The team agreed to review two introductions; the launch date still needs a decision.

The message gives each task an owner and a date, while keeping the unresolved approval separate. Replace those details with what your participants actually confirmed; remove a deadline if it was only suggested.

Prepare the draft from your recording in Whynote

On Mac, record your microphone and the call audio in Whynote, or import a recording you already have. Agree on recording with the participants and check the audio setup before the call. On iPhone, use a saved audio file or a voice note of your own to prepare the recap.

Open the transcript and find the passages where a decision, owner or date was confirmed. With the appropriate Pro access, use a meeting summary as a draft for the follow-up, then check it against those passages. Summary generation uses an internet connection even when speech recognition ran locally.

The recording-to-summary guide explains that workflow. Copy the checked decisions into the email template, adjust the greeting and send it through your usual mail app.

Adjust the message for a client or your team

For a client, include the agreed scope, anything that needs approval and the next deliverable. Leave internal discussion and unconfirmed estimates out of the message. A sentence such as “The delivery date is still to be confirmed” keeps an open question visible.

For your team, put the work in a form people can pick up: a named person, a concrete result and an agreed date. If there are several tasks, keep the detailed action list beside the short email instead of making everyone search through a long recap.

Check commitments before you send

Read the email once as its recipient: is it clear what you need from them and what you will do next? Check names, figures and dates against the conversation, and keep a proposal separate from an accepted decision.

Remove the unused template fields and replace every bracketed instruction. If a detail is missing, mark it as open and ask the relevant person to confirm it. Keep the recording and the checked note in Whynote so you can return to the context when a reply arrives.

More in this topic