Meeting minutes
How to Write Meeting Minutes People Will Actually Read
Create a concise record of the purpose, decisions, important context and next steps — without turning the minutes into a word-for-word transcript.
Minutes and transcripts serve different purposes
A transcript preserves what was said. Meeting minutes help a future reader understand what the group considered, decided and agreed to do next. Copying the entire conversation makes the important information harder to find.
The level of detail depends on the meeting. A routine project sync can be concise, while a formal board, governance or regulated meeting may have specific legal and procedural requirements.
Capture the facts before summarising
Record the date, purpose, attendees and agenda. During the discussion, mark decisions, motions, objections, commitments and questions that remain open. A recording or transcript provides a reference when wording is disputed later.
Do not assume the loudest or longest part of the conversation is the most important. A short final decision may matter more than twenty minutes of exploration that came before it.
- 01
Capture the meeting
Record the agenda, participants and conversation so the final record can be checked against the source.
- 02
Extract the essentials
Identify decisions, material context, action items, owners, deadlines and unresolved questions.
- 03
Draft for scanning
Organise by agenda topic and use consistent labels instead of reproducing the conversation.
- 04
Verify and distribute
Review important details, follow the approval process and share the correct version with the intended audience.
Use a structure readers can scan
Organise minutes by agenda topic. For each topic, summarise the relevant context, state the decision clearly and list resulting action items. Keep opinions attributed only when attribution is required or important to understanding the record.
Use consistent labels for decision, action item, owner and deadline. Link to supporting documents instead of copying them into the minutes, and include the next meeting date when known.
Review, approve and distribute
Compare the draft with the transcript for names, numbers, decisions and commitments. Ask the chair or designated reviewer to resolve ambiguity. Formal meetings may require approval at a later meeting, so mark drafts and approved versions clearly.
Distribute the minutes promptly to the intended audience and store them in a consistent location. Apply the organisation's access, retention and confidentiality rules, especially when sensitive matters were discussed.
A practical meeting-minutes structure
Meeting details
Date, time, purpose, chair, note taker, attendees, absences and the agenda or related documents.
Discussion summary
Only the context and alternatives needed to understand the outcome, organised by agenda topic.
Decisions
A direct statement of what was approved, rejected, postponed or escalated, including votes when required.
Actions and follow-up
Each task with one owner, expected result, deadline and any unresolved question for the next meeting.
Meeting-minutes checklist
- The date, purpose and participant list are correct.
- Every final decision is easy to identify.
- Action items include an owner and deadline.
- The summary is neutral and contains enough context to understand outcomes.
- The draft, approval status, access and retention rules are clear.
Common questions
How detailed should meeting minutes be?
Include enough context to understand decisions and obligations, but omit conversational detail that does not affect the record. Formal requirements may demand more detail.
Are meeting minutes a transcript?
No. A transcript records speech in sequence; minutes organise the essential facts, decisions and follow-up for readers.
Who should approve meeting minutes?
The process depends on the organisation and meeting type. It may be the chair, participants, a board or approval at the next formal meeting.