# How to Write Meeting Minutes That Actually Get Used URL: https://aisummary.link/journal/how-to-write-meeting-minutes Type: blog Locale: en Published: 2026-09-13 Updated: 2026-09-14 --- > Meeting minutes only work if people read them. Here is how to write them fast, keep them short, and make them useful months later. To write meeting minutes well, capture three things before you leave the room: the decisions made, the action items assigned with names and deadlines, and the brief context that explains why those decisions were reached. Everything else is optional. This guide on how to write meeting minutes covers the full process, from the template you prepare before the meeting starts to the document you distribute within an hour of ending, including where AI recording tools now change the work and where human judgment still carries the load. ## What meeting minutes are actually for Most meeting minutes exist for one reason: someone who was not in the room needs to know what happened. That could be a colleague who was traveling, a manager reviewing decisions made without them, or your future self trying to reconstruct why a particular direction was chosen three months ago. The word "minutes" comes from the Latin *minutia*, meaning small details. The name is accurate. Minutes are not a transcript. They are not a narrative summary of what was discussed. They are a structured record of the small but consequential things that happened: who agreed to do what, by when, and on what basis. When minutes are done well, they collapse a 60-minute discussion into a 200-word document that contains everything actionable. When they are not done at all, the meeting leaves no trace, and the same decisions get relitigated at the next gathering. Research into knowledge worker schedules consistently puts executive meeting time at 20 hours a week or more. Most of that time produces no lasting record. ## The five things worth capturing There is a useful simplification here. Good meeting minutes contain exactly five types of information: - Date, time, location or platform, and the names of attendees. - The agenda items as actually discussed, not necessarily as originally planned. - The decisions reached on each item, stated plainly. - The action items that follow, each assigned to a named person with a concrete deadline. - The date of the next meeting, if one was scheduled. That is the complete list. Not full discussion summaries unless a discussion produced genuine ambiguity. Not who said what unless attribution matters for accountability. Not the back-and-forth of a debate unless the team specifically uses minutes to track evolving positions over time. The cleaner the minutes, the more likely people will actually read them. A document that takes longer to read than the meeting it summarizes is not minutes -- it is a transcript, and most people will stop reading it after the second paragraph. ![Notebook with structured handwritten notes and bullet points](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/aisummary/2026-09/cd28af-inline1.webp) ## How to prepare before the meeting starts The single most useful thing you can do before a meeting is open an empty document and paste in the agenda. That becomes your template. Label each agenda item. Under each label, write three subheadings: *Decision*, *Action items*, *Notes*. Leave the notes section blank and plan not to fill it unless something unusual comes up. The structure does the work of reminding you what you are actually looking for while you listen. If the meeting is recurring -- a weekly sync, a sprint review, a monthly board check-in -- keep the same document for the series. A shared file where each session is a dated section means the full history is one search away. Team members who missed several weeks can scroll back without asking anyone. No one needs to reconstruct "what did we decide about the pricing model in February." For one-off meetings, a clean document for each session works just as well. The key is that the template exists before the conversation starts, not assembled on the fly while people are already talking. ## Taking notes in the room without losing the thread The hardest part of writing meeting minutes is staying present in the conversation while also writing it down. These two tasks pull against each other. People who try to capture everything miss what is happening. People who listen without writing miss what was decided. One approach that works: write only in the *Decision* and *Action items* fields as the meeting unfolds. Do not try to capture the discussion in real time. Let the conversation happen. When a decision is announced or an action is assigned, write it down. That is all. If you miss something, do not stop the meeting to reconstruct it. Flag the gap with a question mark and ask at the end of the meeting, during a two-minute wrap, whether the item landed the way you understood it. That two-minute review before the meeting closes is worth building in as a standing habit. Read the action items back aloud. Each person named should confirm what they are taking on and by when. This takes two minutes and removes a whole category of follow-ups that begin with "I did not realize I was supposed to handle that." ![Laptop screen showing a clean structured meeting notes document](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/aisummary/2026-09/204cd3-inline2.webp) ## Writing up after the meeting Write up the minutes within an hour of the meeting ending, while the context is still present. Not the next day. Not later in the week. Within the hour. This is not about discipline or good habits. It is about information decay. Decisions that seemed clear in the room become ambiguous four hours later. The action item that seemed obvious in the moment turns out to need a clarifying note. The person you were going to ask before writing something down is still reachable right after the meeting. The writing itself should take fifteen minutes or less. You are not composing prose. You are filling in the fields you set up before the meeting. Clean the rough notes, remove the question marks, confirm the deadlines, and send. Distribute the minutes by sharing a link rather than an attachment. An attachment goes into an inbox and stays there. A shared document link goes into a workspace and becomes the record that persists, searchable, six months from now. ## The rotating responsibility problem One of the more persistent myths about meeting minutes is that they require a dedicated note-taker -- a role that tends to fall, by default, to the most junior person in the room. This arrangement reliably produces thin minutes. The person assigned to note-taking participates less. They have less context for the decisions being made because they were writing when the reasoning was given. They leave sections blank because they did not follow what was being discussed. A more practical approach: the person who scheduled the meeting takes the minutes. They understand the agenda, they know why each item is on it, and they have a direct interest in capturing what was decided accurately. Across a team, this distributes the documentation work evenly without requiring an explicit policy. For recurring meetings, rotating the responsibility works well. Each week someone different writes up the session. A shared template keeps the output consistent regardless of who is holding the pen. ## Where AI recording tools fit, and where they do not There is now a category of tools that join your calls and produce a transcript, a summary, and a list of auto-extracted action items. They work. They reduce the effort of capturing the raw material considerably. They also produce output you should not publish directly as meeting minutes without a review pass. The AI-generated transcript is accurate but long -- often 10 to 20 times longer than the minutes it is supposed to inform. The auto-summary misses the context that explains why a decision was reached the way it was. The extracted action items sometimes include things said conditionally -- "we could consider reaching out to..." -- as though they were firm assignments. There is also a subtler problem. When an AI recorder is running, participants sometimes assume the documentation is handled. The note-taker stops taking notes. The two-minute closing review gets skipped. The clean template that would have structured the discussion goes unused. The recorder captures everything, but nobody does the editorial work of deciding what matters. ![Sticky notes and index cards arranged by topic on a wooden desk](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/aisummary/2026-09/d891cd-inline3.webp) The useful approach is to run an AI recorder in parallel with your notes template, not instead of it. After the meeting, use the transcript to fill gaps and confirm details you flagged with question marks. Use the AI summary as a starting point for the write-up. Then edit the human document into the clean record you would have written anyway. This takes slightly longer than trusting the AI output directly. It produces minutes that are significantly more useful, because a person who understood what the meeting was trying to accomplish made the judgment calls about what goes in and what stays out. If you skip that editorial pass, you end up with a long auto-generated document that no one reads -- which is not the goal. ## What good minutes feel like when you read them later Good minutes feel like they were written by someone who understood what the meeting was trying to accomplish. They are short enough to read in two minutes. They contain every decision, every action item, and just enough context to know why a direction was chosen. Bad minutes feel like a log. They contain the full arc of the discussion, with attribution and debate captured in paraphrase. They take ten minutes to read. They are more useful as a record of disagreement than as a guide for what to do next. The test is simple: if a person who was not in the meeting can read your minutes and understand what was decided and what to do next, your minutes are good. If they need the transcript as well to understand the context, your minutes are missing something. If they give up halfway through, your minutes are too long. Write for the person who was not there. Keep it short. Send it fast. The meeting ends when the minutes land in the shared workspace, not when people leave the room. ## FAQ ### What should be included in meeting minutes? Meeting minutes should include the date, time, location, attendees, the agenda items as discussed, the decisions reached on each item, action items with named owners and deadlines, and the date of the next meeting if scheduled. ### How long should meeting minutes be? A 60-minute meeting should produce roughly half a page of minutes -- typically 150 to 300 words. Anything longer is usually a transcript rather than minutes, and most people will not read it. ### How soon after a meeting should minutes be distributed? Within an hour of the meeting ending. Context decays quickly, and the person taking notes can still fill gaps and confirm details while the conversation is fresh. Distributing the next day is acceptable. Next week is not. ### Who should take meeting minutes? The person who scheduled the meeting is the most natural choice -- they know the agenda and have context for each item. Rotating the responsibility across a team works well for recurring meetings. ### Can AI tools write meeting minutes automatically? AI recorders can transcribe, summarize, and extract action items reliably. They produce useful raw material, but the output needs a human editorial pass before it becomes the official record. Auto-generated summaries often miss context and include conditional statements as though they were decisions. ### What is the difference between meeting minutes and meeting notes? Meeting notes are informal and personal -- a record for the note-taker. Meeting minutes are the official shared record of what was decided and assigned. Minutes are distributed; notes are kept privately or used to write the minutes. ### How do you write action items in meeting minutes? Each action item should include three elements: the specific task, the person responsible by name, and a concrete deadline. 'Follow up on vendor contract -- Ana, by September 20' is an action item. 'Follow up on contracts' is not.