How to write meeting notes people actually read

Most meeting notes are written for compliance rather than for readers. They record that a meeting happened, and they make it structurally impossible to find out what was decided. Here is a structure that fixes that, and why each part earns its place.

Write the decisions first

Put the decisions at the top, before anything else. This is counter to instinct, because decisions are what you write last, while you are in the meeting. But a reader arriving at a page of notes has one question, and it is “what did we agree”. Answer it in the first three lines and everything after it is supporting detail that a reader can skip.

If you are capturing live, a tickable checklist at the top of the page is the fastest way to do this. Decisions are naturally checkboxes: done or not done.

A structure that holds up

1. Decisions. One line each, in plain language. If a line needs a paragraph, it was not a decision.
2. Actions. Who does what, by when. A decision without an owner is a wish, and a decision without a date is a someday.
3. Open questions. The things the meeting did not settle, so the next meeting does not re-litigate them by accident.
4. Notes. Context, only if it changes how someone reads the decisions above.

Tables, when the content is genuinely tabular

Action lists are the one place a table reliably beats a list, because a table makes a missing owner or a missing date impossible to miss. The gap in the owner column is visible in a way that an absent word in a bullet list is not. Use a table for actions. Do not use it for narrative, which is what tables are usually misused for.

LiveNote’s editor supports tables and tickable checklists inside a note, so the structure above is a couple of clicks rather than a formatting project.

Make the latecomer problem disappear

The reason people skip meeting notes is not laziness. It is that catching up costs more than the value of knowing, and by the time anyone bothers, the information has decayed. Anything that removes the catch-up cost wins.

• Share a link, not an export. A link opens to the current version, so a latecomer is never reading a stale copy.
• Let the people in the room contribute. Notes typed by four people are better than notes typed by one person who was also trying to run the meeting.
• Keep it on one page. If the notes sprawl, they stop being read. A page of decisions and actions is worth more than three pages of everything that was said.

LiveNote is built for exactly this shape: one page, several people, edits landing while everyone is still in the meeting, and a link that is current whenever anyone opens it later.

The two-minute version

Decisions at the top. Actions in a table with owners and dates. Open questions listed so they are not rediscovered. Then share the link and close the meeting. The notes improve while the meeting is still fresh, which is the only time anyone will pay the cost of writing them properly.