Meeting notes template: decisions, owners and next steps
By Juste Tools · Published
The most useful meeting notes make it possible to answer three questions later: what was decided, who will do the next task and when it is due. A transcript is not required for every meeting. Start with a short structure that separates the conversation from its outcomes, then confirm the parts that need agreement.
A copyable meeting-notes template
Paste these headings into your preferred document before the meeting. Leave space under each rather than trying to design a complicated layout while people are talking. The structure is intended for ordinary working notes; formal minutes may need your organisation’s own approved format.
- Meeting: title, date and the purpose of the discussion.
- People: attendees and any relevant role for this meeting.
- Discussion: the short points needed to understand the decision.
- Decisions: what was agreed, including important conditions.
- Actions: one task per line, with a named owner and a due date or agreed checkpoint.
- Open questions: unresolved items and who will clarify them.
- Next review: when the group will check progress.
A filled example
Here is an invented example for a small website project. Meeting: homepage review, 12 October. Purpose: choose the next draft. People: Alex, Sam and Jo. Discussion: the mobile heading was difficult to read over the image. Decision: use the second image crop and a shorter heading for the next draft.
Actions: Sam adjusts the image framing by 14 October. Jo checks the page heading on a phone by 15 October. Alex confirms the final wording after that check. Open question: which translated heading needs the most space? Next review: a short check on 16 October.
The example is useful because the decision and tasks can be found without rereading the whole conversation. “Discussed the homepage” would record the topic but leave the next person unsure what to do.
Write an action someone can complete
Start with a verb and name the output. “Review accessibility” is broad; “check keyboard navigation on the new menu and report any blocked controls” is something a person can finish. Agree on the owner and timing rather than assigning them silently in the notes afterwards.
If there is no decision yet, put the item under open questions. Do not turn a suggestion into an agreement. Mark uncertain dates or names for confirmation and ask before the meeting ends when possible. A short accurate note is more useful than a confident record of something nobody approved.
Use a document or a built-in template
You can use this structure in an ordinary document or notes app. Google Docs also offers a meeting-notes building block: type “@” in a document, choose meeting notes and select a Calendar event. Google’s help explains how the event details are inserted and how sharing or attaching the document works.
Check sharing before adding material that should stay within a smaller group. An event’s guest list and a document’s permissions are related choices, but you should verify the actual document access rather than assuming a title or link keeps the notes private.
Clean up and follow through
After the meeting, move repeated points into one clear entry and remove notes that no longer affect understanding. Keep a decision’s conditions: “approved for the test” is different from “approved for release”. Send the agreed note through your team’s normal channel and ask people to correct factual mistakes.
At the next review, mark each action completed, still open or changed by a later decision. If you dictate your own summary afterwards, review it against the notes you took. Dictating a personal recap is a different workflow from recording and automatically transcribing a meeting.