A Meeting Notes Template That Actually Gets Used

Most meeting notes fail because they capture every word or nothing useful. We only need a record of what changed and who does what next.

Use three sections: Agreed, Disagreed, and Follow up. This works in Notion, Obsidian, Apple Notes, or a shared document. It is short enough to use during a real meeting and clear enough to help people later.

Copy this template

• Meeting: [name]
• Date and people: [date, names]
• Agreed: [decisions and settled facts]
• Disagreed: [open questions and different views]
• Follow up: [owner, action, date if real]

Write in short lines. A meeting about a launch might say: Agreed, launch on May 12. Disagreed, whether to offer a free trial. Follow up, Priya will bring cost estimates by Thursday. That is more useful than three paragraphs of discussion.

Notes are not a transcript. They are a promise about what people can rely on after the call.

Three real examples

Project kickoff

Agreed: the first release includes login and billing. Disagreed: whether to support teams at launch. Follow up: Marco writes the first scope by Wednesday.

One to one

Agreed: the next month will focus on customer calls. Disagreed: none. Follow up: we will choose five customers and book the calls by Friday.

Decision meeting

Agreed: move the launch by one week. Disagreed: the size of the email list segment. Follow up: Ana owns the new calendar and sends it today.

Run the follow up ritual

Reserve the final two minutes of the meeting to read the Follow up section out loud. Confirm the owner and the next action. Then send the note while the meeting is still fresh. In Notion, link the note from the project page. In Obsidian or Apple Notes, put the project name in the title so search finds it later.

• Use an owner’s name, not “team.”
• Write an action, not “discuss.”
• Add a date only when there is a real due date.
• Move follow ups to the task tool before the next meeting.

Keep notes fair

A good meeting note should show a real disagreement without making someone sound foolish. Write the open question, not a verdict on the person who raised it. Let people correct a factual mistake soon after the meeting.

If a meeting repeats every week, open the prior note first. Start by checking old follow ups. This turns notes into a working record instead of a pile of pages nobody reads.

• Keep the next step small enough to test this week.
• Change one rule at a time, so we know what helped.
• Keep what makes the work easier and drop the rest.

Bottom line

Use the three sections in your next meeting. If the note helps one person know what to do, it did its job.