Meeting documentation guide
Create meeting notes that preserve decisions and drive follow-up
Good meeting notes are a record of shared understanding, not a transcript. They identify why the meeting happened, which topics were discussed, what was decided, what remains unresolved and who will do what next. A mind map separates those information types while keeping their relationship visible. Readers can see which discussion produced a decision and which action item is required to carry it out.
Paste handwritten notes, a cleaned transcript or an agenda with annotations. Remove greetings, repeated arguments and sentences that do not affect the outcome. AI can group topics and suggest a hierarchy, but names, dates, approvals and commitments must be checked against the recording or participants. Publish the notes promptly enough for owners to correct misunderstandings before work begins.
Design the hierarchy around retrieval. A participant returning two weeks later should be able to find the decision on a topic, the reason behind it and the current action without replaying the meeting. Use consistent labels for Decision, Action, Owner, Due date and Open question. When a conclusion depends on a document or metric, link or name that evidence beside the decision instead of relying on memory.
What belongs in meeting notes?
Record meeting title, date, purpose, participants, agenda topics, concise discussion points, explicit decisions, action items, one accountable owner and a due date or review condition. Keep unresolved questions separate from agreed actions.
Minutes, transcript or action log?
A transcript preserves exact speech; minutes summarize the official record; an action log tracks work after the meeting. This template combines concise minutes with actions, while the original transcript can remain linked as supporting evidence.
