A meeting summary can sound complete while leaving everyone unsure what happens next. The useful result is more specific: decisions the group made, actions someone owns and questions that are still open. Keep those three things separate and the record becomes easier to use.
Start with a source you can check
Use the meeting notes or transcript as the starting point. Give the record a clear title and date, and link any documents that shaped the discussion. If the source is incomplete, say so at the top instead of asking a summary to fill in the gaps.
Transcription uses network-backed processing. Follow the recording and sharing requirements that apply to your meeting, and confirm which material you can use before starting.
Sort the outcome into three groups
A decision says what was agreed. An action says what someone will do. An open question says what has not been settled. Mixing these together can make an idea look like a commitment or make a commitment disappear into general notes.
| Type | Example | What to confirm |
|---|---|---|
| Decision | Use a phased launch | Was this agreed, or only proposed? |
| Action | Maya drafts the launch checklist | Did Maya accept it? Is there a due date? |
| Open question | Which partner needs early access? | Who will resolve it, and when? |
The names and entries above are examples. In your own record, use “owner to confirm” or “date not agreed” when the source does not establish a detail. Missing information should remain visible.
Ask for an action record, not a polished story
From these meeting notes, produce three sections: confirmed decisions, actions and open questions. For each action, include the owner and due date only if stated. Include a source reference for every decision. Flag ambiguous commitments rather than guessing.Read the suggested record beside the source. Check the passages around each reference, especially where people were comparing options or speaking conditionally. A clear sentence can still misrepresent an uncertain conversation.
Keep the next steps with the project
Add the reviewed record to the relevant project note or space. Link the source so the team can revisit the discussion without relying on memory. Avoid maintaining a second action list that silently diverges from the one people use.
- Make every action observable: describe what will exist when it is done.
- Confirm ownership before treating a name as an assignment.
- Keep unresolved questions in view until someone closes them.
At the next meeting, start with the unresolved actions and questions. Update the record when a decision changes, preserving enough context to understand why. See Turn notes into a place to work for a structure that keeps this material usable.
