How long should minutes be?

Inverse to meeting length, paradoxically. A 30-minute meeting produces about 100-200 words of minutes. A 90-minute meeting still only needs 300-500 words because the goal is OUTCOMES, not transcript. If your minutes are running 1,000+ words for a one-hour meeting, you’re writing too much — focus on decisions and action items, summarize discussions in 1-2 sentences each.

What's the difference between minutes and notes?

Minutes are the formal organizational record — typically reviewed and approved at the next meeting, used as institutional memory. Notes are personal/team artifacts — looser, can include context and color, don’t require formal approval. Many teams blur the line; the key is to know which you’re producing. For board meetings and decision-bearing meetings, you want formal minutes. For weekly team syncs, notes are usually sufficient.

Should I record the meeting AND take minutes?

Often yes. Recording covers the audit trail; minutes give the readable summary. But: recording laws vary by jurisdiction (single-party vs all-party consent), some companies have policies forbidding recording without explicit notice, and recordings of confidential discussions create legal discoverability. Default to minutes-only unless there’s a specific reason to record (training material, regulatory compliance).

What should action items always include?

Three things: WHO is responsible (one person, never “the team”), WHAT specifically (action verbs, not “think about” — “send proposal”, “review draft”), and WHEN by (specific date, not “next week” — “by EOD Friday Oct 24”). Without all three, the item won’t get done. Include status field (pending / in-progress / done) for tracking across meetings.

Who should take minutes?

Either a designated note-taker (rotates among attendees in some teams), an admin/EA (for executive meetings), or the meeting organizer. The role should be explicit — assigning at start of meeting prevents the “I thought you were taking notes” problem. Note-takers should NOT also be the primary discussion driver — splitting attention degrades both roles.

How fast should minutes go out?

Same day if possible, definitely within 24 hours. Memory degrades fast — by 48 hours later, you’ve forgotten 30%+ of nuances. Send draft, let attendees flag corrections within a 24-48 hour window, then mark final. Absent attendees should have minutes in their inbox before the next meeting so they’re not surprised by what was decided.

Productivity · Free tool

Meeting Minutes Template

Fill in attendees, agenda, decisions, and action items, then export clean Markdown or plain text. An instant, free online template with no signup needed.

Updated June 2026

Title

DateTime

Attendees (one per line)Agenda (one per line)DiscussionDecisions (one per line)

Action items

Preview

# Weekly product sync

**Date:** 2026-06-01 · **Time:** 10:00

**Attendees:** Jay, Alex, Priya

## Agenda
- Review last week's ship list
- Triage bug backlog
- Plan next sprint

## Discussion
Team walked through the new onboarding flow and agreed it needs a progress bar.

## Decisions
- Move launch to next Thursday
- Drop pricing experiment

## Action items
| Owner | Task | Due |
|---|---|---|
| Jay | Draft launch post | 2026-05-01 |
| Alex | Fix checkout bug | 2026-04-28 |

Found this useful?Email Buy Me a Coffee

What it does

Meeting minutes are the institutional memory of any organization — what was discussed, what was decided, who agreed to do what by when. Done well, they take a 60-minute conversation and convert it into a 200-word artifact anyone who couldn't attend can read in 90 seconds and immediately know what they need to act on. Done badly, they become the verbose stenographic transcripts that never get read, leading to dropped action items, repeated discussions, and an organization that loses the same arguments three times because nobody can find what was decided last time.

The classic minutes structure has six core sections: meeting metadata (date, time, location/link, attendees, absent), agenda items covered, key discussion points (1-2 sentences per topic, NOT a transcript), decisions made (formal record of what changed), action items (assignee + task + deadline format — without all three, the item won't happen), and date/time of next meeting. The discipline is in ruthlessly summarizing — minutes capture OUTCOMES, not WORDS. A 60-minute meeting should produce roughly 200-400 words of minutes; if you're writing 1,000+ words, you're transcribing instead of summarizing.

The tool fills each section with structured text fields and outputs Markdown-formatted minutes that paste cleanly into Slack, Notion, Google Docs, email, GitHub Discussions, and Linear/Jira. Action items are formatted as standardized rows (assignee · task · deadline · status) so they extract easily into trackers. For recurring meetings (weekly team sync, monthly board), reuse the same attendee list and agenda template as a starting point. Best practice: send minutes within 24 hours of the meeting while details are fresh; let attendees flag corrections within a defined window (24-48 hours), then mark the minutes as final.

Embed this tool on your siteShow snippet

Paste this snippet into any page. Loads on-demand (lazy), no tracking scripts, and sized to most dashboards. Replace the height to fit your layout.

<iframe src="https://freetoolarena.com/embed/meeting-minutes-template" width="100%" height="720" frameborder="0" loading="lazy" title="Meeting Minutes Template" style="border:1px solid #e2e8f0;border-radius:12px;max-width:720px;"></iframe>

Embed docs →

How to use it

Fill meeting metadata: date, time, attendees, absent (so people know who decided what).
List agenda items covered — short bullets, not paragraphs.
Capture key decisions made — explicit record of what changed.
Add action items: who · what · when. Without all three fields, items get dropped.
Set the next meeting date/time before everyone leaves the call.
Click Generate — get clean Markdown ready to paste into your tool of choice.

When to use this tool

Recurring team meetings (weekly sync, sprint planning, retrospectives).
Board meetings, executive committees, or any meeting with formal decision-making power.
Project kickoffs and milestone reviews.
Cross-team coordination meetings where stakeholders need a shared record.
Client meetings where decisions need to be documented for billing or scope clarity.

When not to use it

Brainstorming sessions — minutes constrain creative flow; use a separate notes-doc instead.
1:1 meetings — too informal for full minutes; a shared running doc with action items works better.
Standups — use the standup-notes-template instead (different format).
Confidential strategy meetings (M&A, layoffs) — minutes create a written record that may have legal exposure; consult counsel before formalizing.

Common use cases

Onboarding a colleague who needs the same calculation/conversion
Verifying a number or output before passing it on
Quick use during a typical workday
Pre-decision sanity-check on inputs and outputs

Frequently asked questions

How long should minutes be?: Inverse to meeting length, paradoxically. A 30-minute meeting produces about 100-200 words of minutes. A 90-minute meeting still only needs 300-500 words because the goal is OUTCOMES, not transcript. If your minutes are running 1,000+ words for a one-hour meeting, you’re writing too much — focus on decisions and action items, summarize discussions in 1-2 sentences each.
What's the difference between minutes and notes?: Minutes are the formal organizational record — typically reviewed and approved at the next meeting, used as institutional memory. Notes are personal/team artifacts — looser, can include context and color, don’t require formal approval. Many teams blur the line; the key is to know which you’re producing. For board meetings and decision-bearing meetings, you want formal minutes. For weekly team syncs, notes are usually sufficient.
Should I record the meeting AND take minutes?: Often yes. Recording covers the audit trail; minutes give the readable summary. But: recording laws vary by jurisdiction (single-party vs all-party consent), some companies have policies forbidding recording without explicit notice, and recordings of confidential discussions create legal discoverability. Default to minutes-only unless there’s a specific reason to record (training material, regulatory compliance).
What should action items always include?: Three things: WHO is responsible (one person, never “the team”), WHAT specifically (action verbs, not “think about” — “send proposal”, “review draft”), and WHEN by (specific date, not “next week” — “by EOD Friday Oct 24”). Without all three, the item won’t get done. Include status field (pending / in-progress / done) for tracking across meetings.
Who should take minutes?: Either a designated note-taker (rotates among attendees in some teams), an admin/EA (for executive meetings), or the meeting organizer. The role should be explicit — assigning at start of meeting prevents the “I thought you were taking notes” problem. Note-takers should NOT also be the primary discussion driver — splitting attention degrades both roles.
How fast should minutes go out?: Same day if possible, definitely within 24 hours. Memory degrades fast — by 48 hours later, you’ve forgotten 30%+ of nuances. Send draft, let attendees flag corrections within a 24-48 hour window, then mark final. Absent attendees should have minutes in their inbox before the next meeting so they’re not surprised by what was decided.

Learn more

Explore more productivity tools

100% in-browserNo downloadsNo sign-upMalware-freeHow we keep this safe →