Meeting Recap Email: Record Decisions and Next Steps

A recap should let someone who attended the meeting check what was agreed. It should also give an absent colleague enough context to understand the next steps without reading a transcript.

Separate decisions from proposals. If the group discussed an option but did not approve it, don’t record it as agreed.

Summarize an agreed plan

Subject: Onboarding review: decisions and next steps

Hi team,

We agreed to keep the setup guide and shorten the background section. The revised guide will include separate instructions for administrators and regular users.

Maya will revise the copy by 13 October. Jordan will review the account-connection steps by 15 October. I’ll prepare the final version once those comments are resolved.

The draft and notes are linked below. Please reply if I’ve recorded a decision or owner incorrectly.

Thanks, Alex

Names and dates make action items usable. If an owner has not accepted the task, mark it as awaiting confirmation rather than assigning it through the recap.

When a decision remains open

Subject: Workshop planning recap: venue decision outstanding

Hello everyone,

We confirmed the workshop agenda and the speaker list today. The venue remains open because we need the final accessibility information from the two shortlisted locations.

Casey will collect that information by Thursday. We’ll then choose the venue by email; no further meeting is planned unless there is an unresolved concern.

Best, Lee

The recap tells people both what is settled and what is not. That prevents work from starting on assumptions.

Keep notes proportionate

You rarely need to record every comment in the email. Link to detailed notes when useful and focus the message on outcomes that affect the work.

For sensitive conversations, consider who should receive the recap. An action summary can often be shared more widely than the discussion that led to it.

Send the recap while you can still verify what happened. If someone corrects it, update the shared record so readers don’t have to reconstruct the final agreement from several replies.

Use a meeting request to set a clear purpose before the conversation, and a project status update to report progress afterward.