Meeting Minutes Template: A Practical Copy-and-Paste Format

Good meeting minutes are not a transcript. They are a concise record of what the group discussed, decided and agreed to do next. The best format makes those facts easy to scan during the next meeting and difficult to misunderstand afterwards.

Below is a reusable meeting minutes template, followed by a filled example and variations for board, project and one-to-one meetings. Copy it into your document system and remove any fields your team does not need.

Important: This is a practical working template, not legal advice. Formal board, shareholder, public-sector or regulated meetings may have specific requirements in your jurisdiction or organization. Check those rules before relying on any general template.

Free meeting minutes template

MEETING MINUTES

Meeting:
Date and time:
Location or video link:
Chair:
Minute taker:

ATTENDEES
Present:
Absent:
Guests:

PURPOSE
What this meeting needs to accomplish:

AGENDA AND DISCUSSION
1. Topic:
   Key points:
   Decision:

2. Topic:
   Key points:
   Decision:

DECISIONS
- [Decision] — approved by [group/person] on [date]

ACTION ITEMS
- [Task] — Owner: [name] — Due: [date] — Status: [not started]

OPEN QUESTIONS AND RISKS
- [Question or risk] — Owner: [name] — Review by: [date]

NEXT MEETING
Date and time:
Proposed agenda items:

APPROVAL OR DISTRIBUTION
Prepared by:
Reviewed or approved by:
Shared with:

The template separates decisions from action items deliberately. “We should update the onboarding flow” is a discussion point. “The team approved the new onboarding flow” is a decision. “Maya will publish the updated flow by 30 September” is an action item. Keeping these separate prevents vague notes from becoming vague work.

Filled meeting minutes example

Here is the same structure used for a fictional product meeting:

MEETING MINUTES

Meeting: Weekly product review
Date and time: 17 September 2026, 10:00–10:45
Chair: Maya Chen
Minute taker: Alex Morgan

ATTENDEES
Present: Maya Chen, Alex Morgan, Sam Lee, Noor Ali
Absent: None

PURPOSE
Select the onboarding experiment for the October release and resolve
the remaining analytics dependency.

AGENDA AND DISCUSSION
1. Onboarding experiment
   Key points: The shorter flow tested better in moderated sessions.
   The team still needs a clear route for invited workspace members.
   Decision: Ship the shorter flow to 20% of new workspaces.

2. Measurement
   Key points: Activation will be measured when the first recording is
   processed, not when a user creates an account.
   Decision: Use first processed recording as the primary activation event.

DECISIONS
- Release the shorter onboarding flow to 20% of new workspaces on 1 October.
- Use first processed recording as the experiment's activation event.

ACTION ITEMS
- Add the invited-member route — Owner: Sam — Due: 24 September
- Validate the activation event — Owner: Noor — Due: 22 September
- Write the release checklist — Owner: Alex — Due: 26 September

OPEN QUESTIONS AND RISKS
- Does the invited-member route need separate copy? — Owner: Maya —
  Review by: 22 September

NEXT MEETING
24 September 2026, 10:00
Agenda: readiness review and experiment QA

APPROVAL OR DISTRIBUTION
Prepared by: Alex Morgan
Shared with: Product and engineering teams

Notice what is missing: a sentence-by-sentence account of the conversation. Anyone who needs the exact wording should consult the recording or transcript. The minutes preserve the operational record.

What to include in meeting minutes

Most useful minutes answer seven questions:

1. Which meeting was this? Give it a stable name, date, time and location.
2. Who took part? List attendees, absences and guests where that matters.
3. Why did the group meet? One sentence prevents the notes from losing context.
4. What was discussed? Summarize the points that explain a decision or next step.
5. What was decided? State decisions in direct language, including votes or approvals when required.
6. Who owns each next step? Every action needs one clear owner and a realistic deadline.
7. What remains unresolved? Keep open questions and risks visible instead of burying them in prose.

Avoid recording personal commentary, side conversations or an interpretation of someone’s motives. Write neutrally and distinguish facts from proposals. If a disputed detail matters, verify it against the source recording before distributing the minutes.

A five-minute workflow for better minutes

Before the meeting

• Copy the agenda into the template.
• Add the date, participants and purpose.
• Put likely decision points under their agenda topics.
• Agree who is responsible for the record.

During the meeting

• Capture the outcome of each topic, not every sentence.
• Write decisions as complete statements.
• Give each action one owner, even when several people will contribute.
• Repeat the action and deadline aloud if either is ambiguous.

Immediately afterwards

• Compare the decisions and actions with the recording or transcript.
• Resolve unclear owners and dates while the conversation is fresh.
• Send the minutes through the team’s normal system, not a private notebook.
• Start the next meeting by reviewing outstanding actions.

If typing notes makes it harder to participate, an AI note taker can capture the conversation and draft the structure. You should still review names, decisions, owners and deadlines before sharing. For a deeper look at capture and verification features, see the guide to meeting transcription software.

Meeting minutes formats by meeting type

Project meeting minutes

Prioritize milestones, blockers, dependencies and changed scope. Add a short status field to every action item. If a decision changes the plan, link it to the relevant project document.

Board meeting minutes

Record the formal meeting details, attendance, resolutions, votes, conflicts and approval process required by the organization. Do not assume a general-purpose template satisfies local corporate or governance rules. Have the format reviewed by the person responsible for governance.

One-to-one meeting notes

Use a lighter structure: topics, commitments from each person, support needed and what to revisit next time. These notes may contain sensitive personal information, so restrict access and follow the organization’s retention policy.

Client meeting minutes

Include the client’s objective, commitments made by each side, delivery dates and dependencies. Send a concise version promptly so the client can correct misunderstandings.

Retrospective minutes

Organize the record around what worked, what did not, experiments to try and an owner for each experiment. Preserve the outcome without attributing anonymous feedback to individuals.

Meeting minutes, notes and transcripts are different

• A transcript is the detailed record of what was said. It is best for exact wording, quotations and verification.
• Meeting notes are usually personal or informal observations. They help the writer remember but may not represent the whole group.
• Meeting minutes are the shared record of proceedings, decisions and assigned work.

The three can work together. Transcribe the meeting to preserve the source, generate a first draft of the meeting minutes, then have a responsible person verify the parts the team will act on.

Final quality checklist

Before distributing the minutes, confirm that:

• the title, date and participants are correct;
• each decision is stated clearly;
• every action has one owner and a due date;
• open questions are not presented as decisions;
• sensitive information is included only when necessary;
• names, figures and deadlines have been checked against the source;
• access and retention follow your organization’s policy; and
• the next meeting can start from this record without reconstructing the conversation.

For meetings with sensitive material, review where recordings and transcripts are processed and stored. Klang’s security overview explains its European processing, access controls and deployment options.