Meeting minutes should be as short as they can be while still capturing every decision, action item and owner. For most meetings that is half a page to one page; for a typical one-hour meeting, one page, rarely more than two. Length should follow the meeting's purpose: a 30-minute status call needs a few bullet points, a board meeting needs a fuller record. If you are writing more than a page for a routine team sync, you are probably writing a transcript, not minutes.
Below: the right length by meeting type, what makes minutes run long, and when longer is genuinely better.
The rule: minutes record decisions, not conversation
The biggest reason minutes run long is that people try to capture what was said instead of what was decided. A 45-minute discussion about a marketing budget might produce three sentences of actual outcome: the budget was approved as proposed, the campaign launches next Tuesday, and Priya owns the vendor follow-up. Everything else (the back-and-forth, the tangents, the "on the other hand") is conversation, and does not belong in the minutes.
Keep that filter in mind while writing and length mostly takes care of itself.
Length by meeting type
| Meeting | Typical length | What goes in |
|---|---|---|
| Daily or weekly team sync | 3–5 bullets, half a page or less | Decisions (if any), action items with owners and dates |
| Project or client meeting | Half a page to one page | Attendees, agenda items covered, decisions, action items, open questions |
| Board or committee meeting | 1–3 pages | Attendance (including absentees), motions, how votes went, resolutions |
| All-hands or large update | Half a page | Announcements, decisions, any action items that came out of it |
Team syncs. Most standups do not need a discussion section at all. Who was there, what was decided, who does what by when.
Project and client meetings. This is what most people mean by "minutes of meeting format". The full structure is in our MoM format guide.
Board meetings. Boards and formal committees often have legal or governance reasons to keep a fuller record, and your company's rules or local law may say what must be in it. This is the one meeting type where more detail is expected, not optional.
All-hands. These usually have few real decisions. A short summary of what was announced plus any action items is enough.
What makes minutes too long
- Near-verbatim notes instead of a summary. If a sentence starts with "Rahul said that…" and runs on for two more sentences about what Rahul said, you are transcribing. Compress it to the outcome: "Agreed to delay the launch by one week."
- Every agenda item, even the ones with no outcome. If an item was discussed but nothing was decided and nothing assigned, one line is enough: "Discussed Q3 hiring plan; revisit next meeting."
- Copying the full agenda. The agenda and the minutes are different documents. The minutes only need the items that led to a decision or an action.
- No structure. Long paragraphs feel longer than they are and are harder to scan. Short bullets under clear headings (Decisions, Action items, Next steps) shrink both the real and the felt length.
A structure that keeps minutes short by default
- Header: meeting name, date, attendees (and who was absent, if it matters).
- Decisions: one line per decision.
- Action items: task, owner, due date. Nothing else. See how to write action items that get done.
- Open items: anything unresolved that comes back next time.
If a section has nothing in it, leave it out rather than writing "No decisions were made in this meeting". A ready-to-copy version is in the meeting minutes template.
When longer is better
There are a few good reasons to write longer minutes:
- Compliance or audit requirements, such as board meetings or safety committees, where a fuller record protects the organisation.
- Complex technical discussions, where the reasoning behind a decision matters as much as the decision, and a reader months later needs that context.
- Disagreement, where recording that a decision was contested, and by whom, matters for accountability.
Outside these cases, treat every extra paragraph as something to justify, not the default.
Short minutes, full record
The fear behind long minutes is usually "what if we need the detail later?". The answer is to keep the detail somewhere else. If you record the meeting (with everyone's consent), the minutes can stay to one page because the full record exists.
That is how MeetNotes works: record an in-person meeting on your phone, or a Zoom, Google Meet or Teams call, and you get two things. A transcript with each speaker labelled and timestamped, which is the full record. And minutes: a summary, key takeaways, decisions, and action items with an owner and a due date when one was said. If someone later asks what exactly was said, you can ask a question about the meeting and get the answer with the exact line it came from. Every account starts with 100 free minutes.
FAQ
Should meeting minutes include a full transcript of the discussion?
No. Minutes summarise outcomes: decisions, action items and owners. A transcript is a different document. If you need one, record the meeting and keep the transcript alongside the minutes rather than inside them.
How long should minutes be for a one-hour meeting?
For most one-hour work meetings, half a page to one page. If the minutes for a one-hour meeting run to two or three pages, check whether you are recording decisions or recording conversation.
Is it okay to send very short minutes, like just a list of action items?
Yes, for routine internal meetings this is often the most useful format, because it is what people actually read and act on. Keep the fuller format (attendees, decisions, context) for meetings where a formal record matters, such as board or client meetings.
How detailed should board meeting minutes be?
More detailed than ordinary minutes: who attended and who was absent, each motion, how the vote went and the resolutions passed. They still record outcomes, not the full debate. Check what your company's rules or local law require.
