Skip to content
Gustry

Free template · Operations

Meeting Notes Template

A meeting notes template captures the three things that matter after a meeting: what was decided, what happens next, and who owns each action by when. Discussion detail is optional; decisions and actions are not.

Updated August 2026

What to include in your Meeting Notes Template

  • Meeting title, date, attendees and apologies
  • Purpose in one line
  • Decisions made, each stated as a decision rather than a discussion
  • Actions with a single named owner and a due date
  • Open questions and who will resolve them
  • Items explicitly deferred, with when they return
  • Next meeting date and its purpose

Practical guidance

Decisions first, discussion last

Structure the page so decisions and actions sit at the top and discussion notes below. Most readers will only ever read the top third, and that is fine as long as the top third contains what they are accountable for.

One owner, one date, one verb

Every action should read like an instruction: a person, a verb, an object and a date. If an action needs two people, split it into two actions with a dependency noted.

How to use this template

  1. 1Fill the purpose line before the meeting starts; it prevents drift.
  2. 2Write decisions and actions live, not from memory afterwards.
  3. 3Read the actions aloud in the last two minutes and confirm the owners.
  4. 4Send the notes within a working day while the context is shared.
  5. 5Open the next meeting by reviewing the previous actions.

Filled-in example

Example

Filled-in example: weekly operations meeting

  • Purpose — clear last week's exceptions and confirm this week's schedule.
  • Decision — move Friday deliveries to the morning run from 1 April.
  • Decision — pause the second van hire until the July workload is confirmed.
  • Action — Sam to update the delivery SOP and reissue by 27 March.
  • Action — Priya to confirm July bookings with the two largest accounts by 29 March.
  • Open question — whether the morning run needs a second driver; Sam to check hours by 3 April.
  • Next meeting — 1 April, review the morning run's first week.

Common mistakes

  • Transcribing discussion instead of recording decisions.
  • Actions with two owners, which means no owner.
  • No due dates, so items reappear unchanged next week.
  • Sending notes days later when everyone has moved on.
  • Never reviewing prior actions, which teaches the team that actions are optional.

Frequently asked questions

Who should take the notes?
Anyone but the person leading the discussion. Rotating the role keeps the format consistent and stops one person carrying the admin.
Should I record every meeting?
Record decisions for anything recurring, client-facing or budget-related. A quick two-person catch-up rarely needs formal notes, only a confirmed action.
How do I stop actions being ignored?
Review the previous actions as the first item on every agenda. Visibility does more than any tracking tool.
Free template

SOP Template

A standard operating procedure template gives you a fixed structure for writing down a repeatable task: what the procedure covers, who owns it, what is needed before starting, the numbered steps, and how you know the work was done correctly.

Open Free template

Scope of Work Template

A scope of work document states exactly what will be delivered, what will not, who does what, when each milestone lands and how changes are handled.

Open Free template

Performance Review Template

A performance review template gives a small team a fair, repeatable structure for a review conversation: what the person is accountable for, what actually happened with evidence, what they should keep doing, what needs to improve, and the two or three commitments for the next period..

Open Guide

How to Write an SOP

To write an SOP, pick one repeatable task, perform it while recording each action, then write those actions as numbered single-verb steps with an owner, prerequisites, decision points and a definition of done.

Open