Capture the source
The browser records audio that reaches the selected microphone and displays a running transcript when browser speech recognition is available.
A meeting minutes template built for decisions and follow-up.
Useful minutes tell a reader what changed, why it changed, who owns the next step, and when it is due. Copy the template below for any meeting, or use Notes Recorder to draft the same structure from a live transcript.
What good meeting minutes answer
What was discussed? What was decided? What remains uncertain? Who will do what by when? A transcript preserves the conversation; meeting minutes make the outcome usable.
Copyable meeting minutes template
Delete sections that do not apply. Do not invent an owner, decision, or due date when the meeting did not establish one—write “Unassigned,” “Not decided,” or “Due date not set” instead.
# Meeting title
**Date:** YYYY-MM-DD
**Time:** Start–end and time zone
**Location or call:**
**Facilitator:**
**Note owner:**
**Attendees:**
**Absent / optional:**
## Purpose
One sentence explaining why the meeting occurred.
## Executive summary
- Most important outcome
- Material change or decision
- Highest-priority follow-up
## Decisions
1. **Decision:** What was approved or selected
- **Owner / approver:**
- **Reason:**
- **Effective date:**
## Discussion by topic
### Topic 1
- Key context
- Evidence or constraint
- Open question
## Risks and blockers
| Risk or blocker | Impact | Owner | Mitigation / next review |
| --- | --- | --- | --- |
| | | | |
## Action items
| Action | Owner | Due date | Status |
| --- | --- | --- | --- |
| | Unassigned | Not set | Open |
## Parking lot
- Item intentionally deferred
## Next meeting
- Date / trigger:
- Proposed agenda:How to write minutes that people will act on
- Start with the meeting outcome. Write the executive summary for someone who will not read the rest.
- Separate discussion from decisions. A proposal is not a decision. Use explicit language such as “The group approved…” only when the transcript supports it.
- Preserve uncertainty. Record unresolved questions and dissent rather than smoothing them into false agreement.
- Make actions atomic. Each action should contain one concrete task, one accountable owner, and one due date when a date was actually agreed.
- Keep risks near their context. State the potential impact and the planned mitigation or next review point.
- Verify names, numbers, and dates. Check material details against the transcript or the speaker before distributing the recap.
- Send while context is fresh. Share the reviewed minutes promptly and provide a correction path.
What AI should draft—and what a human should verify
| Minutes element | Useful AI role | Human review |
|---|---|---|
| Summary | Condense repeated discussion into a short overview. | Confirm that the emphasis matches the meeting’s actual outcome. |
| Topics | Group related statements into readable sections. | Check that important context was not merged or omitted. |
| Decisions | Identify language that sounds like approval or selection. | Distinguish a final decision from a recommendation, assumption, or idea. |
| Action items | Extract tasks, owners, and dates mentioned in the conversation. | Verify exact ownership and avoid inventing a due date. |
| Risks | Surface blockers, dependencies, and uncertainty. | Validate severity and add any context that was implicit rather than spoken. |
| Transcript | Create a searchable source record and speaker-separated draft. | Correct recognition errors; AI transcripts are not certified records. |
How Notes Recorder applies this workflow
Organize the outcome
AI turns the conversation into an overview, topic sections, decisions, risks, and action items that stay separate from the source transcript for review.
Review and correct
Use the visible transcript to check names, owners, dates, and context. Correct transcript details and refresh the note when needed.
Save, copy, or export
Save private meeting history, copy notes and transcript independently, or export the notes as Text, CSV, Word-compatible, or print-ready PDF output.
Notes Recorder is a microphone-based web app. It works best for in-person meetings and speakerphone calls; online meetings played through speakers may work after a short test. It does not directly capture system audio and is not a fit for calls heard only through headphones. See the capture compatibility matrix.
Templates by meeting type
Project status
Add milestones, schedule variance, dependencies, decisions required, and a RAID-style section for risks, assumptions, issues, and dependencies.
Customer conversation
Add customer goals, current pain, evidence, objections, commitments, unanswered questions, and the next agreed interaction.
One-on-one
Add wins, concerns, feedback, support requested, development topics, and commitments from each participant. Limit distribution appropriately.
Decision review
Add options considered, evaluation criteria, evidence, dissent, final decision, approver, effective date, and conditions for revisiting it.
Recording and privacy reminder
Tell participants when a conversation is being recorded and obtain any consent required by law, contract, workplace policy, or meeting rules. Do not put confidential or regulated content into a tool your organization has not approved.
Turn an authorized conversation into reviewable minutes
Choose a plan based on monthly recording minutes, confirm that your meeting setup matches the microphone capture method, and keep a human in the review loop before sharing the result.