What to Include in Meeting Minutes (and What to Leave Out)
Taking notes for yourself during a meeting is easy. It's writing minutes that everyone else can read and actually use afterward that's hard. You want to capture everything that matters, but writing every word will stop you from participating and the meeting will pass you by. So the real skill of taking valuable minutes is knowing what makes the cut and what doesn't.
TL;DR: Good meeting minutes aren't a transcript. Start by gauging how formal the meeting is, then record in order of importance: decisions made, action items (the single most important thing to capture), information that will shape future decisions, and finally general remarks worth revisiting. Leave out the word-for-word discussion, personal commentary, and side chatter. The goal is a record someone who wasn't there could read and understand quickly and without much effort.
There's a good reason to get this right. People forget a striking amount of what they hear: one widely cited estimate from work on the forgetting curve suggests we lose roughly half of new information within a few weeks, sometimes far more. Your minutes are the team's defense against that. If they're vague, bloated, or missing the parts that matter, the meeting may as well not have happened since recovering that information later will be very challenging.
Minutes for everyone vs. notes for yourself
Before deciding what to record, it helps to be clear about who you're recording for, because "minutes" and "notes" are not the same thing, even though people might use the words interchangeably.
Notes are for you. They're informal, personal, and unstructured. You jot down what you found noteworthy, scribble a reminder, capture an idea, maybe add your own opinion in the margin. Nobody else has to understand them, so you can use shorthand, abbreviations, or your own private system and record them anywhere you like. As Indeed notes in its breakdown of the two, notes can leave out whatever you choose because they exist purely to jog your own memory.
Minutes are for everyone. They're the shared, often official record of what happened, written so that someone who wasn't in the room, an absent teammate, a manager, a new hire, or in formal settings an auditor, can read them and understand what was decided and what happens next. That means no private shorthand, no personal commentary, and a consistent structure. Minutes speak for the group, not for the note-taker.
This distinction is the lens for everything that follows. When you're writing for yourself, anything goes as long as it's helpful for you. When you're writing minutes, every line has to earn its place by being useful to someone who relies on you to capture it. The rest of this article is about minutes, the harder of the two, and the hierarchy of what to include.
Start by knowing how formal the meeting needs to be
Not all minutes are created equal, and the first thing to calibrate is how thorough yours need to be. There's a world of difference between the minutes for a board meeting and the minutes for an agile refinement, and writing the wrong amount for the occasion wastes your effort or leaves you exposed.
At the formal end, think board meetings, committee meetings, anything with legal or financial weight. Here, minutes are often an official record and may be required by law or governance rules. They demand a defined structure and a factual, objective tone, and they sometimes need detail you'd never bother with elsewhere. For instance, guidance for nonprofit boards advises that you generally record decisions without attributing them to individuals. Furthermore, these minutes will often undergo an approval process once they are completed, before distribution, to ensure completeness and accuracy. That's the kind of thoroughness a formal meeting can require. For these more formal meetings, the preferred minutes format is often laid out in advance, and should be followed over the course of the meeting.
At the informal end, a team standup or a refinement session, minutes are lightweight. You're capturing decisions and tasks so the team stays aligned. You aren't building up a legal document, so a few clear lines are often enough.
So before the meeting starts, ask yourself: if someone challenged what happened here in six months, how much detail would I need on record? Would I be able to get enough information from these minutes to respond? Your answer sets the thoroughness dial for everything else, and it's worth matching your minute-taking style to the meeting type rather than using one approach for all of them.
The hierarchy of what makes the cut
Once you know how formal to be, the question becomes what to actually write down, and in what order of priority. If you only had time to capture a few things, here's the order to capture them in, from most important to least.
1. Decisions that were made
Every meeting that matters produces decisions, and these are the first thing to record. A decision is the resolution of a question the team was sitting with:
- which vendor to go with
- whether to ship on Friday
- what the budget will be
Months later, the most common reason a team stalls mid-meeting is that someone asks "wait, what did we decide last time?" and nobody can remember. Clear records of decisions (that you can easily access!) prevent that.
Write the decision plainly and completely enough to stand on its own. Depending on the meeting, it may also make sense to record who made the decision. In a casual team setting that's usually unnecessary, but in a formal one it can matter a great deal, and the governance rules for that meeting will often tell you how much attribution is expected. Use your formality dial to decide how much attribution is warranted.
2. Action items: the single most important output
If decisions are what the meeting concluded, action items are what the meeting produces, and they are the most important thing you will write down. A meeting without action items often means nothing actually moved forward. As we've argued before, action items are the most important thing to come out of any meeting, so above all else, record them clearly.
The reason action items fail isn't usually that they go unrecorded, it's that they're recorded vaguely. "Follow up with the client" is not an action item; it's a wish. A real action item answers three questions, sometimes framed as the who, what, and when:
- Who is responsible. One named person, not "the marketing team." When a task belongs to everyone, it belongs to no one, a trap sometimes called the diffusion of responsibility. Even for a collaborative task, name a single accountable owner who answers for it.
- What the deliverable is, described with a clear verb and object. "Draft the Q2 messaging brief," not "messaging." Make sure that the deliverable has a clear "definition of done" so that there is no ambiguity that the action item was completed.
- When it's due. A firm date, not "soon" or "next week." For distributed teams, an absolute calendar date is crucial, and it's worth adding a time zone so a deadline means the same thing in London and San Francisco especially if the task is time-sensitive.
Here's an example: A weak action item reads: "code new features discussed." A strong one reads: "Priya to add a Sign Up button to the home page by March 15." The second is specific, owned, and dated, and nobody reading it later has to guess what it meant. The next steps are clear and following up is easy.
One practical caution: defining an action item well should take under a minute during the meeting. If pinning down the who, what, and when starts eating five minutes of discussion, that's a sign the task needs its own conversation offline with just the people involved, rather than holding up the whole room. Capture that it needs follow-up, and move on. You might consider holding something like a refinement meeting to iron out the non-specific tasks.
3. Information that will inform future decisions
Below decisions and action items sits a tier that's easy to overlook but still useful: information shared in the meeting that the team will want when making future decisions. This is the context that explains why, not just what.
Think of the report someone referenced, the budget figure that came up, the constraint a client mentioned, the reason a particular path was ruled out. You don't need to transcribe the discussion, but a line capturing the key fact, and ideally a link to any document or report that was referenced, saves the next reader from hunting it down. When a future meeting asks "why did we decide to go this way?", this tier holds the answer.
This can go a long way but does take some extra doing. Often, if you can attach the relevant documents to the agenda before the meeting, you can save yourself (and everyone else!) a lot of time down the line.
4. General remarks worth revisiting
At the bottom of the hierarchy are the general remarks: comments, observations, or open questions that aren't decisions or tasks but might be worth a look later. An idea someone floated for next quarter. A concern raised but not resolved. A question that got asked and answered, so it doesn't have to be asked again.
These make the cut only after the tiers above are solid, and only when they're actually likely to be useful. This is the first place to trim when you're short on time or attention.
What doesn't make the cut
Knowing what to leave out is just as important as knowing what to keep, because over-recording is its own failure mode for minutes. Bloated minutes can be nearly as useless as no minutes, so take care to note the following.
- The word-for-word discussion. Minutes are a summary, not a transcript. If you've ever stared at a raw transcript of a long meeting, you know it's an impenetrable wall of text that's about as useful as no notes at all. Capture the outcome, not every turn of the conversation that led there.
- Personal commentary and opinion. Your private reaction to a decision belongs in your own notes, not the group's record. Formal minutes in particular stay factual and objective.
- Side conversations and tangents. The chatter that didn't lead anywhere doesn't need preserving. If a tangent produced a decision or a task, record that outcome and drop the rest.
A simple test: if a line wouldn't help someone who missed the meeting understand what was decided or what to do next, it probably doesn't belong in the minutes.
Capturing all this without missing the meeting
There's a practical tension running underneath all of this. The more carefully you record, the less you're actually participating, and if you're a contributor as well as the note-taker, that presents a problem. A few things help. If you're capturing in priority order (decisions and action items first) then a moment of distraction costs you a general remark instead of a critical task. Use shorthand in the moment and clean it up immediately afterward, while the meeting is still fresh, since minutes are most useful when they're distributed within 24 to 48 hours of the meeting. And if minute-taking consistently pulls you out of meetings you need to contribute to, that's a strong argument for sharing the role, rotating it, or using a collaborative tool so the record is being built by more than one person at once.
This is also where a purpose-built tool earns its keep. A platform like Knowtworthy lets your whole team collaborate on a single live set of minutes, assign action items with owners and due dates as they come up, and share the record with a link the moment the meeting ends, so capturing the important things doesn't have to come at the cost of being in the room.
The bottom line
Taking valuable minutes is a career skill that is worth perfecting. Decide how formal the meeting needs to be, then work down the hierarchy: record the decisions, nail the action items above all else, capture the information that will inform what comes next, and add the general remarks worth keeping. Leave the transcript, the commentary, and the tangents out. Do that consistently and your minutes become what they're supposed to be, a record the whole team can rely on long after everyone's forgotten the details.
For more on running meetings worth documenting, take a look at the rest of the Knowtworthy blog, where we cover agendas, action items, and the habits that make meetings actually productive.