How to write meeting notes people actually use (a template for the junior note-taker)

Nobody reads meeting notes for the conversation. They read them to find out what got decided, what they owe, and by when.

That’s the job when you’re the junior learning how to write meeting notes. Someone says “can you take notes?”, and you have two bad options on autopilot: type a transcript and send a wall of text two days later, or jot fragments and never send anything. Both are forgivable. Neither gets read.

Here’s a picture you’ve probably seen. A new analyst sends 900 words on Thursday for a Tuesday meeting (“Then Dana said she thinks maybe…”). By then someone has already asked in Slack, “wait, who’s doing the vendor deck?” The answer is in paragraph six. Nobody got to paragraph six.

If you’re worried about getting stuck as the permanent note-taker, that’s a different post. This one is about writing notes that make you look like you ran the meeting, not like you typed it up.

What good meeting notes actually do

Good notes answer three questions for someone who wasn’t there: what did we decide, who owes what by when, and what’s still open. Everything else is optional.

Cubicle To Corner Office treats note-taker as a real meeting role, and it says the recap should carry “a summary of key decisions and action items.” That’s the spine. The book’s line on written work applies too: “Your reader shouldn’t need a decoder ring to decipher your message.”

Put a two-sentence recap at the top

Busy people read the first two lines and stop. So the first two lines should be the answer.

We decided [X]. Next: [Owner] [does Y] by [date]; open question on [Z] goes to [person].

That’s the two-sentence recap habit, sitting on top of the notes. It also works as a standalone Slack message when the full notes live in a doc.

The copy-paste meeting notes template

Yes, “Not decided” feels like admitting the meeting failed. Write it anyway. An honest “we didn’t land this” saves a week of people acting on a decision that never happened.

How to write each line so nobody misreads it

Write decisions as decisions. “Discussed launch timing” is how half the team walks out thinking the date moved and half thinks it didn’t. “Decided: launch moves to Oct 15; Sam confirms with Sales by Fri” ends the argument.

Name the option you rejected. “Going with X, not Y” keeps somebody from reopening Y in two weeks.

One person, one date. Never “team,” “marketing,” “next week,” or “ASAP.” An action with no owner and no date is a wish. If nobody claimed it, write “Owner TBD” and ask your manager to assign it. Don’t guess.

Start actions with a verb. “Sam — send revised timeline to Sales — by Fri Oct 2.” Readers scan for their own name, then the verb.

Cut the play-by-play. Who said what, in what order, is a transcript. AI transcripts are raw material, not notes.

The fastest way to get owners right is in the room, before people leave: “Before we drop, let me read back the action items so I get owners right.” It feels slightly bossy the first time. It’s the most senior sentence a junior person can say in a meeting.

Send it within the hour

The notes are worth the most while people still remember the meeting. Clean them up and send within the hour, same day at the latest.

Take 60 seconds to proofread names, dates, and owners. The book is blunt about it: “A polished report is a professional report.” A misspelled name in the Actions list is the one typo everyone notices.

Subject line: “Notes + next steps: [Meeting] ([Date]).” If the notes go to Slack, link the doc and pin the message so it doesn’t scroll away.

Running the meeting yourself? These meeting rules cover the one-sentence outcome, naming the decider, and ending on action items.

The book path

Meeting Logistics in Cubicle To Corner Office covers the full meeting, from assigning roles like note-taker to action items with clear deadlines to the recap email. The paperback goes deeper: Cubicle To Corner Office.

---

Notes aren’t a transcript of what people said. They’re a record of what people agreed to do. Write that down, send it fast, and the meeting keeps working after everyone leaves.