Many people write meeting minutes like running accounts: reciting everything from start to finish and writing down every single word said in the meeting, only for nobody to want to read it a second time. Minutes are not verbatim transcripts; they have only two missions: allow those who didn’t attend to grasp the conclusions in 3 minutes, and let attendees know what they need to do next. Just remember a 3-part structure.
Part 1: Conclusions First (No More Than 5 Lines)
Start directly by stating what was decided in this meeting. For example: “Decided to prioritize enterprise on-premise deployment in Q4; deferred the individual plan price increase; deliver the competitor analysis report before next Wednesday (Owner: Li Ming).” Bosses who didn’t attend only need to read this paragraph, scrolling down only if they have questions.
Putting conclusions first is the biggest difference between minutes and transcripts. Transcripts follow chronological order, while minutes follow the order of importance. Before writing, ask yourself: If the reader only spends 30 seconds, what three sentences do I want them to take away? Those three sentences are your first paragraph.
Part 2: Itemized Breakdown (Record Only “Changes”, Not “Processes”)
Break things down by item, with each item containing four elements: item, conclusion, owner, and deadline. Discussion processes should not be recorded at all unless there were significant disagreements that need an audit trail (such as deadlocked debates between two proposals or unique rationales behind the final call).
Remember one sentence: Minutes record “what was decided,” not “what was said.” If 40 minutes were spent in the meeting comparing proposals and the final decision took just one sentence, write only that single sentence in the minutes. Strip out the process, and the minutes instantly slim down by half while readability doubles.
Part 3: Action Items List (Can Be Pulled Out Separately)
Extract all to-dos into a list: item, owner, deadline, and acceptance criteria. Before sending it out, confirm with each owner item by item that they are aware—this is the most overlooked step in meeting minutes and the number one reason action items vanish without a trace.
Different Meetings, Different Focuses
- Decision Meetings: Focus on recording “what was decided + why it was decided that way”; leave a trail for disagreements and rationales behind the final call.
- Sync / Weekly Meetings: Focus on recording “progress + blockers + next steps”; three to five lines per person is enough.
- Brainstorming Meetings: Focus on recording “what ideas emerged + which ones proceed to the next round of validation”; the divergent thinking process can be noted briefly.
Pre-Send Checklist
- Can the conclusions be found within the first 5 lines?
- Does every item have an owner and a deadline?
- Are there any irrelevant discussion processes recorded? (If so, delete them)
- Have all action item owners confirmed?
- Was it sent within 24 hours? (Minutes sent after 48 hours lose half their value)
The Smart Way to Cut Corners
If the meeting has an audio recording, use an AI transcription tool to generate a first draft (many tools can now directly generate structured minutes and action item lists). You only need to proofread and trim, and you can send out decent minutes in 10 minutes. Tools exist to boost efficiency, so don’t hesitate to use them—but always review manually before sending. AI cannot tell which conclusions involve confidential information or which phrasing needs to be a bit softer.
A Note to Those Who Frequently Write Minutes
Writing minutes often builds muscle memory: take notes during meetings across three columns—“Conclusions, Items, Action Items”—and finalize the draft right after the meeting. In the beginning, you can print out that checklist and stick it next to your monitor; after a month, you won’t need it anymore. Writing meeting minutes is essentially practicing the ability to “grasp the key points”—a skill that is valuable in any role.