Action itemsMeeting notesHow-to

How to take notes while leading a meeting: a worked example

Take notes while leading a meeting: an agenda frame, shorthand marks, a read-back that names owners, and one sample meeting traced from jots to notes.

By The MeetNotely team · · · 9 min read

The task a chair loses is often said between agenda items. You've closed one topic and you're already thinking about the next, and that's when someone takes on a task in passing. In the sample meeting below, Omar says "Nice. I'll tell the pilot group." the moment Sara closes the Arabic launch. Her recap, two minutes later, leaves it out.

This page is for the person running the call: what to put on the page before it starts, what to write while you talk, what to say at the end, and the ten minutes after. Each owner line you end with uses the four parts of an action item, which we don't repeat here.

Should the person leading the meeting take notes?

The person leading the meeting shouldn't keep the full record, but should keep a short list of their own. Atlassian, a vendor (11 January 2023, read 16 November 2026), puts it plainly: "If you're the one leading the meeting, you shouldn't be responsible for taking the notes."

We agree about the record. But even with a note taker in the room, the chair has to ask "who's doing that?", and you can't ask about a task you didn't notice. So split the job:

The leader's listThe record
What's in itDecisions, owners, open questions, the time of eachWhat was decided and done, in full sentences
Who keeps itYou, the chairA note taker, the secretary, or a recording
When it's finishedAt the read-back, before people leaveAfter the meeting

If nobody else writes and nothing records the call, your list is the record too: add exact numbers and the words of each decision.

Turn the agenda into your note frame

Before the call, copy the agenda into your notes and give each item three empty slots: D: for decisions, @ for owners, ? for open questions. Add a last block, "Close", for the read-back. An empty @ slot under a finished item is a question you still have to ask.

This is the frame for our sample meeting as it stands ten seconds in. The items come from Sara's opening line at 0:00: "Three things today: the Arabic launch, the pricing deck for Gulf Logistics, and Drive export."

Weekly product sync                Omar: hard stop 10:30 (0:10)

1 Arabic launch
  D:
  @
  ?
2 Pricing (Gulf Logistics)
  D:
  @
  ?
3 Drive export
  D:
  @
  ?
Close: read-back, by owner

Omar's hard stop (0:10) goes at the top: a note for the chair, not the minutes. The read-back has to happen before he leaves.

What to write while you lead: decisions, owners, open questions

While you lead, write the time first, then a few words: a decision, an owner with their task, or an open question. Never the discussion. If the call is recorded, take the time from the recorder's clock so it matches the recording; if not, the wall clock is enough. The time points you back to the exact words, so the note can stay short.

MarkMeansExample
1:11Time on the recorder's clock1:11 D: notifs follow acct lang
D:Decision1:41 D: ship Thu am, Riyadh time
@NameOwner and task2:49 @Omar deck to GL, Thu
date?Owner, but no date said1:46 @Omar tell pilot group, date?
@?Task, but nobody took it3:30 tell GL about long files, @?
?Open question or parked item2:54 ? discount on renewals, parked
→Instruction, not a decision2:31 → client's Drive as standard option

Listen for the commitment words. "I'll", "I can", "Will do", "It'll be in…" and "I'm switching to…" are where tasks start. In the sample, four of the eight tasks are taken with "I'll" or "I can", and one is accepted with just "Will do". Lina takes on resumable uploads (3:11) with "I'm switching to", which sounds like a status update.

Treat "let's" as a flag. "Let's be upfront with them" says what to do and names nobody. Write @? at once.

Each date? and @? is a question you'll ask at the read-back.

A facilitator notes example: one sample meeting, from agenda to notes

The sample is a 4:06 weekly product sync that we scripted and voiced with text-to-speech. Sara (product lead) chairs, with Omar (sales), Lina (engineering) and Yousef (design). The names, the client (Gulf Logistics), the product being launched, the pricing talk and the Google Drive work are invented, and none of it is MeetNotely's pricing, storage or roadmap. Everything below was written by hand from the script; it isn't product output. Times are when each line starts.

These are the jots a chair could write in Sara's place, on the frame above:

1 Arabic launch
  1:11 D: notifs follow acct lang      @Lina tmrw build (1:19)
  1:30 @Yousef AR email tmpl to Lina, today   ("Will do" 1:36)
  1:41 D: ship Thu am, Riyadh time
  1:46 @Omar tell pilot group, date?
2 Pricing (Gulf Logistics)
  2:14 proposal: 500 h block, 10% off, 12 mo   (Omar's, not decided)
  2:31 → client's own Drive in deck, standard option
  2:38 @Yousef 1-page data diagram, date?   ("Do it" 2:45)
  2:49 @Omar deck to GL, Thu
  2:54 ? discount on renewals, parked
3 Drive export
  3:11 @Lina resumable uploads, ~next sprint (3:23, hedged)
  3:30 tell GL long files land next sprint, @?
  3:42 @Lina folder name + link in settings, date?
Close 3:46 read-back

It holds all eight tasks and leaves out what the recording keeps anyway: why notifications should follow the account (1:05), the twelve mirrored screens (0:31). Three things it does that memory doesn't:

  • The 1:46 line is there, the one from the top of this page.
  • 2:14 says "not decided", so a number doesn't turn into a decision later.
  • Three date? flags and one @? are four questions ready for the read-back.

The jots also catch the five traps that action-item lists fall into in this same meeting, including the 2:45 double ask.

Read back by name before people leave

The read-back is the last minute of the meeting: say each owner's name with their tasks and dates, and ask every date? and @? question out loud. Go by owner, not by agenda item, so each person hears their name once and answers for all their tasks.

Sara's actual recap at 3:46: "Okay, quick recap. Arabic onboarding ships Thursday, notifications follow the account language, the Gulf Logistics deck goes out Thursday, and resumable Drive uploads land next sprint."

It's accurate, and it names nobody. It mentions two of the eight tasks, and a third (Lina's notification change) only as a decision. The other five are missing, and nobody is asked for a date.

Here is the read-back her jots would give her. It's our rewrite, not in the audio.

Before you go, by name. Lina: notifications in tomorrow's build, resumable uploads expected next sprint, and the folder name in settings, by when? Yousef: the Arabic email template to Lina today, and the data diagram, by when? Omar: the deck to Gulf Logistics on Thursday, and the pilot group, by when? And who tells Gulf Logistics that long recordings land next sprint?

It takes about half a minute. The last question is the chair's to settle: name someone and wait for a yes. Until then, the task is "owner not agreed".

Hand off the record: a note taker or a recorder

Hand the record to someone else when the meeting needs minutes, or when you'll be presenting or negotiating and can't look down. Keep your list anyway.

A note taker. Give them your frame before the call, so their notes follow the same items. If the meeting needs formal minutes, they follow the before, during and after steps for writing minutes.

A recorder. Tell people before you record. MeetNotely records the meeting from your browser tab in Chrome or Edge (the tab's audio plus your microphone) and gives you a transcript with speakers and notes where every line links to its moment. You lead; it keeps the words. See what the notes, action items and Ask do, feature by feature, and how a recording becomes cited notes.

What it doesn't do:

  • There's no button to mark a moment while you record. Jot the time from the recorder's running clock, then jump to that moment in the notes after the call.
  • Owners are speaker names from the transcript: "Speaker 2" until you rename them, and only someone who spoke can be one.
  • Due dates stay as said ("Thursday", "next sprint").
  • Nothing is emailed for you.

A recorder doesn't ask "who's doing that?" before people leave. The read-back is still yours.

The ten minutes after: from jots to clean notes

Right after the call, take ten minutes (our practice) and turn each jot into a full line, in this order:

  1. Fill in every answer from the read-back. A date? someone answered becomes a date; one nobody answered becomes "date to confirm".
  2. Rewrite each @ line as an action item: verb, owner, date, and the time it was agreed.
  3. Play anything with a number before you copy it. In MeetNotely, the cited notes and action items play the moment they came from; your jotted time says where to look.
  4. Move each ? to Parked, with when it comes back.
  5. Send it as a recap email with each owner and date, the same day.

The sample's jots as clean notes follow. In the audio, Sara never asked the read-back questions, so they keep every "date to confirm": we don't fill in answers nobody gave.

Weekly product sync, notes

Decisions
- Push notifications follow the account language (1:11)
- Arabic onboarding ships Thursday morning, Riyadh time (1:41)

Actions
- Lina: make push notifications follow the account language, in tomorrow's build (1:19)
- Yousef: send the Arabic email template to Lina, today (1:36)
- Omar: tell the pilot group about the launch, date to confirm (1:46)
- Yousef: make a one-page diagram of where the data goes, date to confirm (2:38)
- Omar: send the deck to Gulf Logistics, Thursday (2:49)
- Lina: switch large uploads to resumable uploads, expected next sprint (3:11)
- Lina: show the folder name, with a link, on the settings page, date to confirm (3:42)

Needs an owner
- Tell Gulf Logistics long recordings land next sprint (3:30). Sara to assign

Parked
- Discount on renewals: back once we see their usage (2:54)

To check against the recording
- Omar's proposal: 500 hours, 10% off, 12 months (2:14). Not decided

Compare the 1:46 jot with its clean line: four words and a flag were enough. Two calls stay out of Decisions: Sara's "put it in the deck as a standard option" (2:31) is an instruction about Omar's deck, and "Let's be upfront with them" (3:30) is the task nobody took, under Needs an owner.

With AI notes too, your jots make a quick check: compare each AI owner and date with the moment it was said. A speaker mix-up shows as a name that doesn't match your @.

Questions people ask

Does the facilitator take notes?

Yes, but only a short list: decisions, owners, open questions and the time of each. The full record goes to a note taker or a recording.

Who should take notes in a meeting?

Anyone not leading or presenting; for minutes, the secretary. Agree who before it starts.

Should I share my screen while I take notes?

Not while you jot. Share the list at the read-back, so people can correct it on the spot (our practice).

What if I miss something?

Write the time and a question mark, and carry on. Ask at the read-back, or play that moment afterwards if the call was recorded.

Notes you can check.In the language you spoke.

MeetNotely records your meeting from the browser tab or with its notetaker, and links every note to the moment it was said.