A meeting notes template people actually read

Most meeting notes go wrong in the same place. They record what was discussed and leave out what was decided. In Microsoft’s 2023 Work Trend Index survey of 31,000 workers in 31 countries, 55% said the next steps at the end of a meeting are unclear, and 56% said it is hard to summarize what happened (Microsoft WorkLab). Good notes fix both problems, and they take less writing.

What notes are for

Notes record decisions, so nobody has to decide the same thing again next week. They assign actions, each with one owner and a date. They keep open questions in view until someone answers them. And they give people who were not there enough context to understand the decisions, and no more.

Everything else is optional, including who said what. If a meeting produced no decisions, no actions and no open questions, the notes can say so in one line, and that line tells the reader something useful about the meeting.

The template

Copy this into your document tool. It is written in Markdown, so most editors accept it as it is.

# [Meeting name] · [date]

**Attendees:** names (and who was invited but absent)
**Purpose:** the one outcome this meeting is for

## Decisions
- [Decision, written as a statement in the past tense]

## Action items
- [ ] [Action] · Owner: [one name] · Due: [date]

## Open questions
- [Question] · Who will find out: [name]

## Notes
### [Agenda item 1]
- Only what someone who missed it needs to understand the decisions above

## Links
- Documents, tickets, recordings

The order is deliberate. A reader who stops after the first screen already has the decisions and the actions, which is all most readers need.

Filling it in during the meeting

Open the document before the meeting starts, with the purpose and the agenda in it, and attach it to the invitation. GitLab’s handbook, written for a company that runs almost everything remotely, is firm about this. Every meeting gets a single live agenda document, and a meeting without an agenda should not happen (GitLab Handbook).

Write each decision down the moment it is made, as a statement someone could act on. A line saying the team will launch on 3 November behind a feature flag is a decision. A line saying that launch timing was discussed records only that people talked, and the same discussion is likely to start again next week. Give every action a single owner, too. A team cannot report back, so when two people share a task, name the one who will.

In the last two minutes, read the actions back to the room. It is the cheapest check there is, because people correct owners and dates while they are still present. And keep one source of truth. When two people take notes in two documents, merge them before sending. GitLab’s own rule is to stop the meeting and settle on one agenda as soon as a second one appears.

Variants for common meetings

A one-to-one works best as a single running document for the whole working relationship, with the newest meeting at the top and a section for topics either person wants to raise next time.

For a project status meeting, put a short line per workstream above the decisions, saying whether it is on track, at risk or blocked and why. Words are easier to scan than colours, and they read correctly for everyone.

Notes from a client or sales call gain two sections, the client’s goals and their concerns, in their own words where possible. A third section lists the follow-up you promised, and it becomes your email.

In an interview debrief, rate each competency on its own, with the evidence you heard, before anyone discusses the overall decision. Writing evidence before opinions keeps one loud view from setting everyone else’s rating.

A recurring team meeting should carry open actions forward at the top until they are done or dropped, so nothing quietly disappears.

After the meeting

Send the notes the same day, while people still remember the discussion. Put the decisions and actions in the body of the message and link to the full document, because most people will never open the link. If an action belongs in a task tracker, create the task there and link it from the notes, so the tracker and the notes cannot disagree.

Meetings are expensive. Harvard Business Review reported that executives spend nearly 23 hours a week in meetings, up from under 10 in the 1960s (Perlow, Hadley and Eun, 2017). Notes are how that time turns into something that lasts beyond the call.

Transcripts, AI summaries and notes

Recording and transcription tools make it easy to capture everything, which makes notes more important, because someone still has to say what mattered. Treat the transcript as the record you check the notes against, and keep the notes short. If you use an AI summary, read it before sending. Summaries handle topics well and are weaker on exactly who agreed to what.

Everyone in the meeting should know it is being recorded or transcribed, and in some places the law requires their agreement, which our article on recording consent explains. Transcripts are also personal data, so keep them only as long as they are useful.

Prepped, the app this site is about, writes meeting notes from a meeting’s transcript and material, in sections you can set for each kind of meeting, so the sections of the template above can become its sections. The meeting exports as plain text, ready to paste into an AI tool or a chat, or as a Word document.