flownote / Templates
Short answer
A useful meeting recap email leads with the outcome, lists confirmed decisions, gives every action one owner and a deadline when agreed, names open questions, and links to fuller notes. Send it while the context is fresh, but review facts before pressing send.
Editorial note: This guide was prepared with AI-assisted research, reviewed against the cited public documentation, and uses no customer recordings or private meeting data. Examples are explicitly fictional.
The copy-and-edit template
Copy and edit
Subject: Recap — [meeting/topic] — [date]
Hi [names],
Thanks for the conversation. Here is the short recap.
Outcome — [One sentence describing what the meeting accomplished.]
Decisions — [Decision 1] | [Decision 2]
Actions — [Owner] will [specific task] by [date].
Actions — [Owner] will [specific task] by [date].
Open question — [Question], with [owner] driving the answer by [date].
Full notes — [Link, if recipients are authorized to view them.]
Please reply with corrections by [time/date].
Thanks, [name]
Delete empty sections. A recap should reflect the meeting that happened, not make every conversation look equally complicated.
A fictitious client recap
Copy and edit
Subject: Recap — Atlas onboarding — Aug. 15
Hi Sam and Lee,
Thanks for today. We aligned on a September 8 pilot for the fictional Atlas support team.
Decisions — Start with 12 pilot seats; use the weekly client-update format.
Action — Riley will send the security questionnaire by Aug. 18.
Action — Sam will confirm pilot participants by Aug. 20.
Open question — Final training time; Lee will propose two slots.
The full notes are linked here: [authorized link]. Please send corrections by Monday.
Best, Riley
Note — Atlas, the people, and every detail above are fictional.
Write action items people can execute
| Weak wording | Better wording | Why |
|---|---|---|
| Look into training | Lee will propose two training times by Aug. 19 | Adds one owner, a deliverable, and a date |
| We should update the page | Riley will publish the revised FAQ by Friday | Turns a suggestion into a confirmed commitment |
| Team to follow up | Sam will email the participant list to Riley | Names a person instead of a group |
Do not invent a due date or owner to make the recap look complete. If the group did not decide, put the item under open questions and ask for confirmation.
The review checklist
- Does the opening sentence state the outcome rather than retell the agenda?
- Is every listed decision final, or did the group only discuss it?
- Did each person actually accept the action attributed to them?
- Are dates, prices, quantities, names, and links correct?
- Are sensitive details necessary for every recipient?
- Does the notes link have the intended access settings?
- Is there a clear way and reasonable window to correct the recap?
Use AI for the draft, not the final judgment
A meeting note taker can extract decisions and candidate actions while the conversation is still fresh. In Flownote, review the structured note, ask follow-up questions with Ask AI, correct the output, and share or export the approved recap.
Frequently asked questions
How soon should I send a meeting recap?
Send it while the context is fresh, after verifying the important facts. For a routine meeting that may be the same day; a sensitive or formal recap may need additional review.
Should every recap include the full transcript?
No. Link the transcript only when it is useful and recipients are authorized. The email itself should contain the decisions and actions needed for follow-through.
What if no deadline was agreed?
Do not invent one. Say that the date is unconfirmed and identify who will set or confirm it.
Related guides