How to take meeting notes: a simple template and filled example

A meeting ends and everyone goes back to work. Two days later, someone asks what was agreed. You remember the discussion, but not whether the delivery date was confirmed or merely suggested.

Useful meeting notes make that difference clear. They do not need to capture every sentence. They need to preserve enough context to explain a decision, who will act on it and what remains unresolved. Here is a simple structure you can use on your phone or Mac, with a fictional example.

What belongs in meeting notes?

Start with the meeting topic, date and participants. Then separate three kinds of information: decisions, next steps and open questions. Add a short explanation where the reasoning matters.

A proposal is not a decision. “Could move delivery to Thursday” and “Agreed: delivery moves to Thursday” describe different outcomes. If agreement is unclear, keep it under open questions until someone confirms it.

For everyday working notes, this can be brief. If your organization requires formal minutes or approval, use its process alongside your personal notes.

Prepare a small template before the meeting

Copy these fields into a new note. Leave space beneath each heading rather than trying to predict the discussion.

• Meeting and date:
• Participants:
• Purpose:
• Decisions and brief reasons:
• Next steps: action, owner, due date.
• Open questions and who will clarify them:
• Next review or meeting:

The owner and due date matter as much as the task. “Send photos” leaves room for confusion. “Sam sends the entrance photos by Thursday, 1 October” is much easier to follow up. If no deadline was agreed, write “due date to confirm”.

During the meeting, keep entries short

Capture a useful phrase when something changes. On a phone, short notes such as “Blue sample approved”, “Sam sends photos Thu” and “Delivery date still open” are enough to hold the essential detail.

Do not spend the whole conversation formatting the record. When you have a moment, expand anything that your future self would struggle to interpret. Keep an uncertain statement visibly uncertain rather than polishing it into a fact.

Filled example: a small project check-in

This example is fictional. It shows a simple meeting record for a workspace refresh, not a real client project.

• Meeting: Atlas check-in, 30 September 2026, 10:00.
• Participants: Alex and Sam.
• Purpose: Confirm the material choice and information needed before ordering.
• Decision: Use the blue sample. The team preferred it beside the existing furniture.
• Action: Sam sends photos of the entrance by Thursday, 1 October.
• Action: Alex asks the supplier for a delivery date by Friday, 2 October.
• Open question: Delivery timing is not confirmed. Alex will report the supplier’s answer.
• Next review: Friday, 2 October, after the supplier reply.

The record separates the agreed material choice from the unresolved delivery question. It also makes each next step concrete enough to check later.

Finish with a two-minute recap

Before leaving the meeting, or immediately afterwards, read the decisions and actions back. Check names, dates and any ambiguous wording. A quick confirmation can catch a misunderstanding while the conversation is still fresh.

When writing the recap later, distinguish the meeting date from the time you recorded it. Lognote’s timestamp belongs to the note; it is not a replacement for explicitly naming the meeting or an agreed deadline.

A person’s name written in a note does not assign work or notify them. If somebody needs the recap, share it through the channel your team uses. Check the content before sending it.

Keep the record easy to find in Lognote

A Meetings group gives your records a consistent home. Add a project tag such as #atlas when related notes also appear in a work log. The hashtag guide explains how to find notes across groups within the active workspace.

On Mac, keep the meeting group beside your work log while writing the recap. Our guide to tabs and side-by-side notes shows that setup. You can retain the detailed discussion in its original group while adding a short outcome to your daily log.

Review actions without losing context

At the next review, return to the original note and check the actions. Add an update such as “Photos received, 1 Oct” or “Supplier reply still pending”. Keep the outcome connected to the original question.

If you use #followup, remember that it is a label, not an automatic reminder or completed-task status. Decide when to remove it so old resolved items do not keep returning to your review.

Start with one meeting, one short template and a two-minute recap. The test is simple: can you read the note next week and tell what was decided, who owns the next step and what still needs an answer?