When to send a meeting follow-up
Send a recap when the meeting produced a decision, an action with an owner, or a deferred question the next conversation depends on. Skip it when the meeting was informational. Empty recaps teach people to skim the useful ones.
The recap's job is to lock the decision before memory diverges. In a PLOS One study of 189 outpatient visits, patients recalled fewer than half of the decisions and recommendations from a single conversation a week later without prompting. Meetings aren't clinics, but recall fades the same way, so the written recap becomes the record people trust over what they remember.
Recap what was settled, not every topic discussed. If a sentence wouldn't change what someone does next, it doesn't belong in the recap. For sales-specific calls, use the sales call follow-up templates. For project updates, use the project status update templates.
Five ways meeting recaps fail
In HBR's meeting follow-through guidance, Paul Axtell argues that follow-up needs to capture what was decided, who is accountable, when implementation happens, and how it will be communicated. The failure modes below all track to one of those missing pieces.
- Discussion masquerading as decision: The draft says what people talked about, such as "we discussed pricing options," but never names what was settled. Replace discussion bullets with the actual decision, the open question, or nothing.
- Shared ownership: Two names beside one action usually means no owner. Bain's RAPID decision framework uses one decider to prevent shared accountability from becoming no accountability. Use the same logic for actions: pick one owner and list watchers separately.
- Window dates: "Next week," "end of month," and "soon" aren't calendar-ready. Use a day or date, then say what happens if the date slips.
- Paraphrased decision: The recap rewrites the decision-maker's words into your own phrasing. That creates room for "that's not quite what I meant." Use their wording when the decision matters.
- Wrong recipient list: The whole attendee list gets copied by default, so owners read the thread like FYI traffic. Put owners on the To line, visibility-only readers on Cc, and leave everyone else out.
Which template to send
Pick by what the recap has to carry, not by the meeting type.
- One or two decisions, same day: Use the same-day decision recap.
- Several actions across different people: Use the owners and dates email.
- Someone who missed the meeting needs the short version: Use the forwardable summary.
- The first recap went silent: Use the re-anchor on silence.
- Timing, owner, or scope changed after the meeting: Use the plan changed follow-up.
Same-day decision recap
Send this within the meeting day when one or two decisions came out of it. Keep this email about decisions. Actions belong in the owners email below.
Decisions from [topic] today
Hi [Name],
Three things came out of today's call:
1. We're going with [decision, in the decision-maker's own words].
2. Still open: [the one question this decision depends on]. I'll come back with [my answer or recommendation] by [day, e.g. Wednesday].
3. Next touch: [meeting or send] on [day].
I'll pick up [next deliverable] after [day].
Thanks,
[Your Name]
Use the decision-maker's exact phrasing on line 1. If you wrote shorthand in your notes, expand it back to their words.
Avoid burying the decision under context. The first line after the greeting should be the decision sentence, not the agenda, attendees, or discussion.
Owners and dates email
Use this when the meeting created three or more actions across different people. The body's job is to bind one name and one calendar date to each action.
Action owners from [meeting]
Hi [Name],
One name and one date on each item from today.
- [First name]: [action stated as a verb] by Mon [date].
- [First name]: [action stated as a verb] by Wed [date].
- [First name]: [action stated as a verb] by Fri [date].
One item we didn't assign: [item]. I'll take it unless [Name] wants it by [day].
Thanks,
[Your Name]
Name a single owner per line, even if two people worked on it together. If you can't pick one, the action isn't ready to assign.
Avoid "team" as an owner. "Engineering will take a look" sounds assigned, but it leaves no accountable person.
Forwardable summary for someone who missed it
Use this when your contact has to forward the recap to a decision-maker who was not in the room. Write the email for that person, not for the attendee.
Summary for [absent person] on [topic]
Hi [Name],
Pasting a version of today's recap you can forward without editing.
- We decided to [decision in one sentence].
- The driver was [constraint or tradeoff].
- Next: [action] by [date], owned by [name].
- We considered [alternative] and ruled it out because [reason].
Happy to jump on a call if [absent person] wants the longer version.
Thanks,
[Your Name]
Include the ruled-out alternative. The forwarded reader's first question is often why the group skipped another path.
Avoid names without role context. The reader of the forward did not hear the conversation, so "Camille's number" may mean nothing to them.
Re-anchor when the recap went silent
Use this when the original recap got no reply and the action it carried still has to happen. Anchor to the specific item that's stuck.
Re: recap, is [specific item] still good for [day]?
Hi [Name],
Following up on [specific action from the recap], which was sitting at [day] on your side.
If [day] still works, I'll send [next deliverable] right after. If it slipped, I have [day at 10:30] or [day at 3] open for a quick call to reset the timing.
Thanks,
[Your Name]
Anchor to the specific item, not the meeting. "Following up on the vendor decision" gives them the action without forcing them to scroll.
Avoid "checking in." It signals the unfinished action is vague on your side too.
Plan changed follow-up
Use this when timing, owner, or scope shifted between the meeting and now. Lead with what changed.
Update on [item]: [what changed]
Hi [Name],
One change from what we agreed on [day].
[Action] is moving from [original owner or date] to [new owner or date]. Reason: [the concrete thing that drove the change].
Everything else from the recap still stands. New next checkpoint: [date].
If that changes anything else on your side, I'll adjust the handoff.
Thanks,
[Your Name]
Name the reason in one clause. People accept a moved date faster when they understand what drove it.
Avoid rewriting the whole recap. If only the date moved, only the date should change in the email.
Who goes on the To line
When you copy every attendee by default, the owners read the recap like FYI traffic and no one replies. Split the list by what each reader owes the thread.
- To: People who own an action in this recap. They need to reply, push back, or act.
- Cc: People whose work depends on the decision, but who don't owe this thread a response.
- Off the thread: People who attended but neither own anything nor depend on it. Brief them later only if they need the outcome.
Pre-send check
Read the draft as the decision-maker
- 1The decision line uses words the decision-maker actually said. If you can't remember them, the recap isn't ready.
- 2No action has two names. Two names means no owner, so pick one or move the item to the unassigned line.
- 3Every date is a calendar date, not a window. "By next week" gets reread as a suggestion.
- 4No bullet recaps what was discussed without recording what was decided. If a line wouldn't change what someone does next, cut it.
- 5The To line is people who must act. People who only need to know are on Cc or off the thread.
- 6Nothing in the recap relies on context only attendees have. A forwarded version would still make sense.
- 7Deferred decisions are labeled deferred. They aren't buried inside action items that pretend the decision is closed.
How dreamif.ai helps with meeting follow-ups
Paste your meeting notes, including decisions, owners, dates, and unresolved questions, and dreamif.ai drafts a recap that keeps those pieces visible. It can use connected Gmail, connected Calendar, approved Drive folders, saved contact notes, and user-supplied instructions when those sources are allowed. You review the draft before it sends.
If you want recaps shaped a specific way, set that in your drafting style: decisions first, owners and dates only, or forwardable to a non-attendee. The style is a user-set control, and you can change it whenever you want.