A meeting summary turns discussion into a record people can use. It should separate what was discussed from what was decided, and make each next step specific enough that the owner knows what to do.
A practical workflow
- Capture the meeting purpose, date and relevant participants using minimal identifying information. Group notes by topic rather than attempting to reproduce every sentence.
- Write decisions as decisions and unresolved questions as unresolved questions. For each action, include an owner, a due date and the expected result.
- Review names, dates and commitments before sharing. Send the recap to the intended recipients and provide a clear way to correct an inaccurate record.
Worked example
Topic: website launch. Decision: use the five-page version for the initial release. Action: Alex prepares the revised copy by 12 June; Maya reviews it by 14 June. Open question: whether translations are needed at launch. This is a fictional example of a useful structure, not a record of an actual meeting.
What to check before sharing
Do not turn a tentative suggestion into an agreed commitment. Avoid full account numbers, identity documents and sensitive details that the recipients do not need.
How long should the summary be?
Long enough to record the decisions and responsibilities accurately. A one-page recap suits many short meetings, but complex matters may need supporting records or an approved formal process.