How to Write Meeting Minutes: Steps, Template and Example

To write good meeting minutes, you record what the group decided and what it assigned, not everything it said. You prepare a template from the agenda before the meeting, you capture decisions and action items while people talk, and you write the record up the same day, while the discussion is still fresh. Anyone who reads the finished minutes should be able to answer three questions in under a minute: what did we decide, who owns each next step, and when is it due.

That sounds simple, and the failures are simple too. Minutes go wrong when they turn into a transcript of who argued what, or when an action item leaves the room with no owner and no date attached. This guide walks through the whole job: what minutes are, what belongs in them, the three phases of the work, a complete worked example, the difference between board minutes and team minutes, and the mistakes that make minutes useless.

What meeting minutes are, and what they are not

Meeting minutes are a short, formal record of a meeting. The rule that governs them comes from Robert’s Rules of Order, the standard rulebook for formal meetings in the United States. Its principle fits in one line: minutes record what was done at a meeting, not what was said by the people in it. SHRM, the Society for Human Resource Management, states the same principle in its quick reference on effective meeting minutes: minutes are the official record of actions taken, not a record of the discussion. Everything in this guide on how to write meeting minutes follows from that one rule.

So a debate that ran for twenty minutes may earn two lines in the minutes, while a decision that took ten seconds earns a full, exact line of its own. Minutes exist so that people who missed the meeting can act on it, and so the group can prove later what it agreed. They are not a story of the meeting, and they are never a place for the minute taker’s own opinion.

Your personal notes are a different tool. Notes are a memory aid you keep for yourself, in any shape that helps you: half sentences, stars, arrows. A transcript is the opposite extreme, a word for word record of everything said, usually made from a recording. Minutes sit in the middle, shorter than both in the ways that matter: checked by others, shared with the whole team, and built to be acted on.

What belongs in meeting minutes

Every set of minutes, from a five person team check-in to a company board, rests on the same set of parts. Leave one out and readers start guessing.

Action items deserve the most care of any line on the page. An action with no owner is a wish, and an action with no date drifts. Teams often lift the action list straight out of the minutes and into their project planning templates, so the work gets tracked where the rest of the project lives instead of sitting forgotten in a document.

Before the meeting: set yourself up to succeed

Learning how to write meeting minutes starts before the meeting does. Ask for the agenda as soon as it exists, and build your template straight from it: one heading per agenda item, with space under each heading for the discussion, the decision and the actions. Walking in with that skeleton means you spend the meeting listening instead of formatting.

Read the papers that come with the agenda, so the topics and the names of projects are familiar before anyone says them out loud. Learn the names of everyone attending and how to spell them, including guests, because the minutes will name the people who own actions. Confirm who chairs the meeting and who takes the minutes. Where the team can manage it, the person leading the discussion should not also write the record: leading and recording split your attention, and the record suffers first.

Agree on one format with your team and reuse it every time. A fixed format means regular readers always know where to look for decisions and where to look for their own actions, and it means a new minute taker can pick the job up without inventing a style.

During the meeting: capture decisions, not speeches

Your job in the room is to listen for outcomes. Decisions often arrive in plain words: let us go with the second design, approved, we will wait until January, that budget is agreed. Mark each one the moment it lands, because the group will move on within seconds and the exact wording will blur.

For each decision, write the outcome first, then add the shortest reason a reader who missed the meeting would need. For each action, check three things: who, what, and by when. If one of the three is missing when the topic closes, ask out loud in the room. A ten second question during the meeting saves days of guessing afterward, and most chairs will welcome it, because it means the action was real.

Most teams now meet inside software, and modern team collaboration tools will record the call and gather the shared documents in one place. Use the recording as a safety net for checking a decision or a deadline later. Do not let it replace the minutes: nobody will listen to an hour of audio to find one date, and a recording captures talk, while minutes capture commitments.

Write in short, neutral lines as you go, and favor action verbs: approved, agreed, assigned, postponed. Neutral matters. The minutes report that the group cut the budget; they do not report that the cut was wise, reckless or overdue. The rewrites below show the habit in practice.

After the meeting: write it up, share it, get it approved

Write the minutes up the same day, or within 24 hours at the latest. Memory for detail fades fast, and a decision you were sure of on Tuesday afternoon turns fuzzy by Friday. Work from your template, turn rough notes into clean lines, and cut every sentence that reports talk instead of an outcome.

Read the draft once with a stranger’s eyes. Would someone who missed the meeting know what was decided, what they personally owe, and when it is due? Fix names, dates and numbers at this pass, because an error in minutes gets quoted for months. Then share the draft with everyone who attended and invite corrections while the meeting is still fresh in their minds.

In formal settings the group approves the minutes at its next meeting, sometimes with corrections, and only then do they become the official record. File the approved version where the whole team can find it months later, in the same knowledge base software that holds your other shared records, not in one person’s inbox, where it vanishes the day that person changes jobs.

A worked example: one short meeting, written up properly

Here is how to write meeting minutes for one short team meeting, from the first line to the last. The company, the people and the dates are fictional. The shape is the point.

Notice what the example leaves out. Nobody’s arguments appear, nobody’s tone is graded, and no opinion is dressed up as a fact. A reader who missed the meeting still learns every decision, every owner and every date in about a minute, and the whole record fits on one page.

Board minutes and team minutes: same job, higher stakes

A board meeting follows the same logic with extra weight on the record. Board minutes can serve as legal evidence that directors did their jobs properly, so formal bodies add structure a team meeting does not need. The guidance published by the City of Madison attorney’s office on taking committee minutes lists what Robert’s Rules expects: the kind of meeting, the name of the body, the date, time and place, whether the chair and secretary were present, whether the previous minutes were read and approved, and the final wording and outcome of every main motion. Points of order and rulings join the record when they affect a result, and the closing line states the time the meeting adjourned. The official Robert’s Rules of Order website explains the same framework for groups that adopt the rulebook.

For a team meeting, you keep the discipline and drop the ceremony: no motions, no movers, no vote counts, just decisions and owned actions. For a board, a union, a school council or any body whose rules name Robert’s Rules or a similar authority, keep the formal parts intact and get advice that fits your organization, because this section describes common practice, not legal advice. In both worlds, minutes sit in the same family as a team’s other written records: like good technical documentation, they only help if they stay short, current and easy to search.

Mistakes that make minutes useless

Even people who know how to write meeting minutes slip into the same five traps. Each one quietly destroys the record’s value.

• Transcribing the argument. Pages of who said what bury the two lines that matter. Summarize the topic, record the outcome.
• Opinions dressed as facts. “Most people seemed unhappy with the vendor” tells a reader nothing they can check. Record what the group decided about the vendor instead.
• Actions with no owner or date. “Someone will check the figures” assigns the work to nobody. Every action leaves the room with a name and a deadline.
• Writing up days later. Late minutes carry wrong dates, softened decisions and missing actions. Same day write ups stay accurate.
• A new format every meeting. When the layout keeps changing, readers hunt instead of reading. One template, used every time, makes minutes skimmable.

Conclusion

How to write meeting minutes comes down to one habit: record outcomes, not talk. Prepare from the agenda, capture decisions and owned actions in the room, write the record up the same day, and let the group check and approve it. Do that for every meeting, and your minutes become the page everyone trusts when memories disagree.