Meeting Note Templates for Decisions, Actions and Clear Follow-Up

The best meeting note template makes four things easy to find: what was decided, why it matters, who owns the next action and when it is due. It should preserve enough context to prevent confusion without becoming a transcript.

Below are copy-ready templates for common meeting types, followed by a workflow for consent, review and distribution.

Use this universal meeting note template

Meeting:
Date and time:
Purpose:
Participants:
Note-taker:

Agenda
1.
2.

Key context
-

Decisions
- Decision — approver — date

Open questions
- Question — owner — review date

Actions
- Owner — action — due date — status

Next meeting or checkpoint:
Draft reviewed by:

Keep “decisions,” “open questions” and “actions” separate. A proposal is not a decision, and a discussion topic is not an action. The meeting notes vs minutes comparison explains when a working note needs formal approval.

Before the meeting, duplicate the template and assign one note owner. Fill in the purpose and decision questions in advance so the document guides attention instead of merely storing a retrospective account. During discussion, use short factual lines and mark uncertainty explicitly. Do not polish language so aggressively that conditions, disagreement or missing evidence disappear.

Weekly team meeting template

Use a rolling document so the previous action list is visible before new discussion begins.

Week of:
Outcome needed today:

Previous actions
- Owner — action — status — blocker

Updates by exception
- What changed since last week?

Decisions needed
- Decision — options — deadline

Risks and blockers
- Risk — impact — owner — response

New actions
- Owner — action — due date

Avoid round-robin status narration when nothing changed. Ask people to update routine status asynchronously and reserve meeting time for decisions, dependencies and blocked work.

Close each action aloud: name the owner, restate the deliverable and agree the due date. “Marketing to follow up” is not sufficiently specific. “Rina sends the approved landing-page copy to Alex by Tuesday 16:00” can be checked. If no person accepts ownership, keep the item under open questions rather than pretending it is assigned.

One-to-one meeting template

One-to-one notes may contain sensitive employment information. Limit access and separate developmental notes from formal performance records.

Date:
Employee topics:
Manager topics:

Progress and wins
-

Obstacles and support requested
-

Feedback discussed
- Observation — context — agreed next behavior

Development
- Goal — practice — support — check-in date

Commitments
- Owner — action — due date

Do not use inferred sentiment or an AI score as a fact about the employee. Record observable behavior, context and the person’s response.

Give both participants access to the shared working note unless a documented process requires otherwise. Invite corrections, especially where feedback or commitments are summarized. A private manager scratchpad should not silently become the employee’s formal record. Keep access narrow and apply the organization’s retention rules.

Client meeting template

Client notes should distinguish the customer’s words from your interpretation.

Client and meeting purpose:
Participants and roles:

Customer goals
- Stated goal — source/context

Constraints and concerns
- Confirmed fact / hypothesis to verify

Options discussed
- Option — condition — unresolved question

Agreed decisions
- Decision — participants confirming

Next steps
- Owner — deliverable — date

Customer-facing recap reviewed by:

Use the meeting follow-up guide to turn the reviewed note into a concise external recap without exposing irrelevant internal commentary.

Capture consented in-person context before filling the template. Kuno is a physical AI voice recorder designed and developed in Munich, with EU-hosted processing and storage; current core features are marketed without a subscription. Explore Kuno

Decision meeting template

This format prevents a decision from being separated from its assumptions.

Decision required:
Decision owner:
Deadline:

Options considered
- Option — benefits — costs — risks

Evidence used
- Source — date — limitation

Decision
- Selected option:
- Rationale:
- Conditions:

Dissent or unresolved risk
-

Implementation actions
- Owner — action — due date

Review trigger
- Date or condition that reopens the decision

Do not manufacture consensus. If someone disagrees or evidence remains uncertain, capture it proportionately. A review trigger makes it possible to revisit the choice when assumptions change.

Record the evidence available at decision time, including its limitations. This protects against hindsight bias and helps a later reviewer understand why a reasonable decision changed. Link to the source rather than pasting large confidential extracts into a broadly shared note.

Project kickoff template

Project and sponsor:
Problem to solve:
Success measure:
In scope / out of scope:

Roles
- Decision owner:
- Delivery owner:
- Contributors:

Milestones
- Milestone — owner — date

Dependencies and risks
- Item — owner — response

Communication rhythm
- Channel — audience — frequency

Immediate actions
- Owner — action — due date

Keep the kickoff note linked to the living project plan. The notes explain the conversation; the plan should remain the operational source of truth for current status.

Make templates accessible and scannable

Use real headings, descriptive links, short tables and plain language. Do not encode status by color alone. Keep dates unambiguous and write the owner’s name rather than “team.”

The University of Michigan-Flint’s official accessible meeting-minutes templates recommend consistent heading structure and provide basic and detailed variants. Carnegie Mellon’s meeting minutes guidance includes attendees, agenda, notes, decisions and specific action items.

Those sources inform structure; your governance determines whether the result is informal notes or official minutes. For formal preparation, also see meeting minutes format.

Record only with explicit agreement

If audio capture supports the note process, inform every participant before recording. Explain purpose, access and retention, obtain explicit agreement and offer a fully equal no-recording/manual-notes alternative. Refusal must not reduce participation, service or influence.

Never record covertly or bypass conferencing controls. Apply the relevant laws and organizational policies. Under GDPR Article 5, transparency, purpose limitation, minimisation and accuracy are core principles.

Verify AI-filled templates

AI can map a transcript into headings, but it can misidentify speakers, omit conditions or convert a suggestion into a decision. Every AI output is a draft requiring human verification before CRM, minutes, coaching, forecasting or external use, including generated transcripts, meeting notes, CRM entries and forecasts.

The reviewer should confirm names, decisions, dates, owners, quotations and sensitive details against the authorized source. Mark unresolved items rather than guessing. For action structure, see what action items are in a meeting.

Move from source to reviewed action list. Use Kuno for overt, agreed in-person capture, then keep the generated note in draft until a responsible human approves it. See Kuno

Share, approve and retain notes

Share operational notes while context is fresh and identify the review deadline. Give participants a clear correction route. For formal minutes, follow the organization’s approval procedure rather than treating silence as approval unless that procedure explicitly says so.

Restrict sensitive notes to people with a legitimate need. Apply a retention period to raw audio, drafts and approved records separately. Delete duplicates and exports when their purpose ends.

Recommended default

Start with the universal template and remove fields that do not support a decision or action. Use specialized templates only when they improve the meeting’s purpose. Keep one named note owner, one review step and one authoritative final location. A good template reduces ambiguity; disciplined review makes it trustworthy.