Three meeting notes templates you can copy today

Notes or minutes? Decide in one line

Meeting notes are for the people who were in the room. Minutes are for the record. That is the whole difference.

Minutes are formal. They follow a fixed order, they name who proposed and who seconded, and somebody approves them at the next meeting. Boards, committees and anything with legal weight need that. If that is your situation, use the meeting minutes template instead of this page.

Notes are looser. Nobody signs them off. They exist so four people remember the same thing next week, and so the person who missed the meeting can catch up in two minutes. That means you can drop any field below that does not help you. Minutes do not give you that freedom.

Template 1: agenda, decisions, actions

This is the default. Use it for team meetings, project check-ins, client calls, kickoffs, anything with more than two people and a real outcome. If you are not sure which of the three formats you want, take this one.

Copy everything from here down. Square brackets are placeholders. Start with the header, which you fill in before anyone speaks.

Meeting: [what this meeting is called]

Date and time: [14 May 2026, 09:30 to 10:05]

Place or link: [room name, or the call link]

Note taker: [your name]

Purpose, one line: [why this meeting is happening at all]

Attendees:

The part you fill in while people are talking

Same template, second half. Write the discussion as it happens and the decisions as they land, not afterwards from memory.

Agenda item 1: [What was actually said. Two to four lines. Positions, numbers, objections. Not every sentence.]

Agenda item 2: [Same again.]

Agenda item 3: [Same again.]

Decisions: [One line per decision. What was decided, who decided it, and the reason. The reason matters more than it looks.]

Action items: [One row per action in the table below.]

• Open questions: [Things nobody could answer today, and who will find out.]
• Parked: [Topics you agreed not to discuss now, and where they go instead.]
• Next meeting: [Date, time, and the first thing it has to cover.]

Filled example: product sync, Thursday 14 May

Here is the same template with a real-shaped meeting in it, so you can see how much detail is enough.

Meeting: Product sync, week 20. Date and time: Thursday 14 May 2026, 09:30 to 10:05. Place: Meeting room 2, with Google Meet for Priya. Note taker: Dana Okafor. Purpose: decide whether the May release still ships on the 22nd.

Attendees: Dana Okafor (product, there), Marc Lindqvist (iOS, there), Priya Raman (design, remote), Tom Beale (support, there), Sofia Ricci (backend, absent, sent comments by email).

1. Release date. Marc said the receipt email bug is not fixed. Two of the three failing tests now pass, the third fails only on iOS 17. He needs three more working days and does not want to ship with the bug visible to paying customers. Sofia's email agreed.

2. Support load. Tom has 14 open tickets about missing receipts since 2 May. He is answering each one by hand, roughly 20 minutes each. He asked for two things: a canned reply he can paste, and an in-app banner. Dana pointed out that a banner needs a release, and there is no release until the bug is fixed.

3. Onboarding step 3. Priya showed the redesigned screen. Drop-off at step 3 was 41 percent in April. The new version removes the address field. Marc said the address is needed for tax. Priya asked whether that is true for personal accounts. Marc checked, and it is only required for business accounts, so it can move later in the flow.

Decision 1. The release moves to Thursday 29 May. Dana decided, after Marc said the receipt bug needs three more working days. Shipping on the 22nd would mean shipping the bug.

Decision 2. Support gets a canned reply today, not a banner. Dana and Tom agreed. A banner needs a release, and the next release is the 29th.

Decision 3. The address field moves to business signup only. Dana decided, Priya and Marc agreed. Tax only needs it for business accounts.

• Open questions: does the German tax rule require an address at signup? Sofia to confirm before Monday.
• Parked: the pricing page redesign, moved to the June planning meeting.
• Next meeting: Thursday 21 May, 09:30. First item is whether the 29th still holds.

What each field is for, and what people get wrong

Every field above earns its place. Here is what goes in it, and the mistake that shows up most often.

• Date and time. Write the end time too, not just the start. After a month you can see that a 30-minute slot really runs an hour every week. That is the evidence you need to shorten it.
• Attendees. Record who was absent, not only who came. Absent people are the ones who later say they never agreed to it. One line saying Sofia was absent and sent comments by email settles that before it starts.
• Purpose, one line. Most people skip this. Write it before the meeting, from the agenda. If you cannot put the purpose in one sentence, the meeting probably did not need to happen.
• Discussion. Write what was said, not what you thought about it. The common mistake is trying to capture everything, which turns you into a typist and takes you out of the conversation. Two to four lines per item is enough for a reader to follow the argument.
• Decisions. Give every decision a reason. The reason is the field people drop, and the one they badly want three months later. A decision with no recorded reason gets re-argued by the next person who joins the team.
• Actions. The owner is a person, never a team. "Marketing will look into it" is not an action item, it is a wish. The due date is a date, not "next week", because next week moves and 19 May does not. If you want a standalone list to work from afterwards, see the action items list template.
• Open questions. This field lets you write down that nobody knew. Notes that hide uncertainty look tidy and cause trouble.
• Parked. A polite way to end a tangent in the room. Saying "I am parking that, it is in the notes" stops the detour without cutting anyone off.

Template 2: the Cornell split page

Use this when you are mostly listening. Training sessions, lectures, product demos, a long walkthrough from a client, discovery calls where the other person talks for 40 minutes. Anything you will need to revise later rather than act on immediately.

The layout is old and it works. Draw a vertical line about a third of the way across the page and leave five blank lines at the bottom. On a laptop, a two-column table does the same job.

1. 1During the session, write only in the wide right column. Short lines, abbreviations. If you miss something, type ?? and keep going.
2. 2Straight after, read your own notes once and fill the narrow left column. One cue per block: a keyword, a name, a number, or a question you still have.
3. 3Star anything in the cue column that you personally have to do. Those stars become your task list.
4. 4Write the bottom strip in your own words, five lines maximum. If you cannot summarise it, you did not understand it, which is better to find out now than next month.
5. 5To revise later, cover the wide column and answer your own cues from memory. This is the study trick the format was built for, and it works on a client discovery call as well as it does on a lecture. If you are doing this for coursework, see the students and lectures page.
6. 6Know where it fails: fast back-and-forth decision meetings. Four people interrupting each other will outrun a split page every time. Use Template 1 for those.

Template 3: since last time, what I owe, what I am waiting on

This is the personal note. It is not a record of the meeting, it is a record of your position in an ongoing thing. Use it for one-on-ones, standups, weekly project check-ins and recurring client calls, where the same people meet again in seven days and nothing needs minuting.

Filled in, it reads like this. Since last time: the API contract is agreed, staging is still not up. Decided today: we ship the read-only version first. What I owe: the migration plan to Dana by Friday, a cost estimate to Tom by the 20th. What I am waiting on: staging access from IT, asked on 6 May, nine days now. What I still do not understand: who signs off on the data retention period.

The waiting line is the one that pays. Most projects do not stall on work, they stall on somebody waiting for somebody else, and nobody writes that down because it does not feel like progress. Once it is a field on the page, it gets said out loud in the meeting. Put four weeks of these side by side and you can see whether a project is moving or whether the same waiting line has been sitting there since April.

The trade-off is honest: this format keeps almost no detail and it is written from your point of view. Anyone who missed the meeting needs Template 1 instead. For the manager's half of the same conversation, the one-on-one meeting template covers what to ask.

Five lines, and that is the whole template.

• Since last time: [what actually moved, and what did not. Two or three lines.]
• Decided today: [the one or two things that are now settled]
• What I owe: [my tasks, each with a date and the person expecting it]
• What I am waiting on: [who I need something from, what it is, and since when]
• What I still do not understand: [the honest list, to bring to the next one]

Which of the three fits your meeting

One rule of thumb before the table. If a decision in the meeting could cost money or move a deadline, use Template 1 even when the meeting is small. Five minutes of extra structure is cheap next to one argument about what was agreed.

Habits that make any of these templates work

The format matters less than what you do around it. These six habits do most of the work.

• Fill the header before the meeting starts. Name, date, attendees, purpose. It takes 40 seconds and it stops you starting from a blank page while people are already talking.
• Say decisions out loud as you write them. "So we are moving the release to the 29th, Marc owns the fix, due Tuesday." That one sentence catches half of all later disagreements, in the room, for free.
• Mark what you missed with ??. Do not stop to catch up, keep typing and come back. If you recorded the meeting, timestamps solve this properly: in an app like Noter AI you tap the line in the transcript and hear that exact moment again.
• Give yourself five minutes at the end. Notes tidied while the meeting is still in your head are worth twice as much as notes tidied the next morning.
• Send them within the hour. Fast and rough beats polished and Thursday. Paste the decisions and the action table into an email and stop there, or use the meeting recap email template.
• If the meeting runs in two languages, pick one for the notes. Switching mid-page produces something nobody can read back. Write in the language the actions will be carried out in, and keep the original wording only for quotes you may need to prove. Recordings behave differently here: a tool that locks to one language before you press record writes the second language out phonetically, so word-level detection is the thing to check. That is covered in the best app for transcribing multilingual meetings.

If you would rather not type any of it

The three templates above are yours. Copy them, change them, put your own logo on them. This last section is the part of the page that pays for the rest, so it is one section and then you are done.

Noter AI records the meeting from your phone and writes the notes for you. The output style called Key bullet points returns almost exactly the shape of Template 1: what was covered, what was decided, and who owes what by when, with the action items pulled out separately and owners attached. Switch the style and the same recording comes back as Minutes of meeting for the formal version, a To-do list if you only want the tasks, an Email, a Formal report, or a Custom instruction where you describe in your own words exactly how you want it written.

You also get speaker labels so you know who said what, timestamps on every line, synced playback so tapping a line replays that second of audio, and an editable transcript. Fix a misheard name or a product term, re-run the summary, and the correction carries through. There is AI chat over one note or across every note you own, plus folders, note search, and export to PDF, Word or plain text.

It covers both halves of a normal week. In-person meetings record from the phone microphone, and recording keeps running with the screen locked, so the phone can sit face down on the table. For online meetings a bot joins Zoom, Google Meet, Microsoft Teams and Webex, and it can take the schedule from Google Calendar or Outlook. Audio you already have can be imported from the Files app or shared in from Voice Memos, WhatsApp voice notes and other recorders.

Language is where it is strongest. Transcription covers 60+ languages with automatic detection, so you never choose a language before recording, and language is tagged word by word, so a sentence mixing Arabic and English, or Hindi and English, is written down as it was actually spoken. Finished notes translate into 18 languages, which means you can run the meeting in one language and send the key bullet points in another.

Price is $9.99 a month or $49.99 a year, flat, not per seat. Put the alternatives on the same basis and the shape is clear: Otter.ai Pro is $16.99 a month per user, Notta Pro $13.99, tl;dv Pro $18, Granola $14 on Business, Fireflies $10 to $19 per seat. Those all scale with head count. This one does not, because everyone records from their own phone rather than occupying a licence in a shared workspace. What you give up for that is the shared workspace itself: no admin console, no single invoice, no company-wide search across everyone's notes. There is a free trial, so test it on one real meeting before you decide.

The limits, plainly. Transcription happens in the cloud, not on the device. There are no live captions while the meeting runs, the summary arrives after. It takes audio files only, not video files or links. Data is encrypted in transit and at rest, and you can delete it whenever you want. It runs on iPhone and iPad and on Android.