Most meeting notes get written and never read again. Here's a structure that people actually open afterward, because it tells them exactly what they're supposed to do next.
The short version: write down what was decided, what needs to happen next, who's doing it, and by when. Skip the rest. Send it within an hour, to everyone who was in the room, in a format short enough that people actually read it.
A meeting produces a lot of talk and very little of it needs to survive in your notes. If you try to capture everything, you end up typing instead of listening, and the note is too long for anyone to read later. Aim for four categories:
Everything else, the side conversations, the jokes, the three ways someone explained the same idea, can be left out. If it becomes important later, someone will bring it up again.
You don't need a system with a name. Three approaches cover almost every meeting:
Pick one before the meeting starts. Switching methods mid-meeting is how notes turn into a mess.
This is the format to start from. Paste it into a blank document before your next meeting and fill in the blanks as you go.
| Meeting: [name] Date: [date] Attendees: [names] Summary (1-2 sentences) Decisions - Action items - [task] | owner: [name] | due: [date] - [task] | owner: [name] | due: [date] Open questions / follow-up needed - |
The summary line matters more than it looks. A single sentence at the top ("Agreed to push the launch two weeks and split QA between Sam and Priya") lets someone who missed the meeting understand the outcome without reading the rest.
Notes taken during a meeting are usually rough, half-sentences, abbreviations, things only you would understand. The habit that separates useful notes from a pile of scribbles is a short cleanup pass right after:
Everything above works with nothing but a blank document. If you're in back-to-back meetings and the ten-minute cleanup keeps not happening, an app can do the typing and cleanup part for you.
Amlin is a Mac app that listens to a meeting the same way you do, by picking up the sound your computer is already playing (so nothing joins the call as a visible participant) along with your own microphone. You can still jot a word or two if something matters, but you don't have to write full sentences while you're trying to listen. When the meeting ends, Amlin turns the conversation and your rough notes into a structured summary: decisions, action items with owners, all in about the format above, ready in seconds. It also keeps one running list of action items across every meeting you take, instead of one per note, so a task from three weeks ago doesn't get lost in an old document. The meeting audio itself is never saved; it's used to write the note and then discarded.
Amlin runs on macOS 13 or later on Apple silicon, and has a free plan that covers about 5 or 6 meetings a month.
Four things: decisions that were made, tasks someone now owns, who owns each task, and any date attached to it. Most of what's said in a meeting is discussion that leads up to a decision. Write down where the discussion landed and skip the path it took to get there.
Whichever one you'll actually finish and send afterward. Handwriting is often more memorable and less distracting on a video call, but typed notes are faster to turn into a follow-up message. If you type, keep your notes app separate from anything with notifications, so you're not half in the meeting and half in email.
Short enough that someone reads all of it. A meeting note with a two-line summary, a short decisions list, and an action item table usually beats a page of prose, because the reader can scan it in fifteen seconds and find what applies to them.
No. A blank document and the structure on this page is enough. Software helps if you'd rather not type while you're trying to listen, since an app can capture the conversation and hand you a draft to edit instead of a blank page.
If the ten-minute cleanup is the part that keeps slipping, Amlin does that part for you.
Download for MacFree to start · macOS 13+ · Sign in with Google