How to take meeting notes that people actually read comes down to two passes: capture roughly during the meeting, then distill within the hour into decisions, action items with one owner each, and open questions. A good set of notes can be scanned in under a minute. Everything else, including the full transcript, is background that you archive rather than send.
This guide covers what to write down, which framework to use, the workflow, the phrases that signal a decision in real time, and a template you can paste into your own tools.
Why most meeting notes get ignored
Most notes get ignored because they are a transcript in disguise: a chronological account of who said what, with the useful parts buried in the middle. Readers skim the first few lines, find nothing they need, and close the document.
Meaty argues that effective notes should be scannable in under a minute and should prioritize decisions, single-owner action items and open questions over a chronological narrative. That is a useful test. If someone who missed the meeting cannot tell what was decided and what they owe in 60 seconds, the notes have failed, however accurate they are.
There are two separate documents here, and mixing them causes most of the clutter:
- The transcript is the raw record. It is long, complete and searchable. Archive it and link to it.
- The summary is the thing people read. It goes in the email body or the team chat, not in an attachment.
If you paste a transcript into a chat thread, people mute the thread. If you send a three-line summary with a link to the transcript, they read the summary and click through only when they need detail.
What to write down and what to skip
Write down only what someone will need to act on or to check later: decisions, tasks, open questions, and the context needed to understand them. Skip everything that describes how the conversation unfolded.
| Write it down | Skip it |
|---|---|
| Decisions, and the reason in one line | Who spoke first or who disagreed with whom |
| Action items with one owner and a date | Tasks assigned to "the team" |
| Open questions and who will answer them | Side conversations that went nowhere |
| Numbers, names, dates and links mentioned | Full sentences that restate the agenda |
| Risks or objections that changed the plan | Pleasantries and status updates already in a doc |
One owner, one deadline
Unfill's guidance is that every action item needs exactly one owner and an explicit deadline. Assigning a task to a team, or writing "soon", dissolves accountability. "Design review: Hnin, Friday 17:00" works. "Someone to look at the design soon" does not.
When nothing was decided
Some meetings produce no decisions and no tasks. Unfill suggests writing "Decisions: none" and "Action items: none" rather than inventing follow-ups. This is more honest, and it tells readers they can stop reading. It also shows that a "none" was a conscious result and not a gap in the notes.
How to take meeting notes: which framework fits
Pick one framework and use it every time. Consistency matters more than the choice, because your readers learn where to look.
| Framework | Layout | Best for |
|---|---|---|
| Outline | Agenda items as headers, bullets beneath | Recurring team meetings, status reviews |
| Cornell | Cues in a narrow left column, rough notes on the right, summary strip at the bottom | Long discussions, workshops, interviews |
| Quadrant | Four boxes: decisions, actions, questions, background | Decision-heavy meetings, client calls |
Cornell
Borrowed from students, the Cornell method splits the page into three zones: cues or keywords in a narrow left column, rough notes in a wide right column, and a summary strip across the bottom. The summary strip is the part that matters for meetings. Writing it forces you to distill before you close the document.
Outline
Outline is the default we would suggest. You create headers from the agenda before the meeting and type under them as people talk. It is fast, it matches how the meeting is run, and it is easy to clean up afterward.
Quadrant
A quadrant layout gives you four boxes on one page. The version we find useful uses decisions, actions, open questions and background. It is harder to use when topics jump around, but it makes the final summary almost automatic, since the top three boxes are what you send.
The three-phase workflow: prepare, capture, distill
Notes get better when you treat them as a process with three phases, not one activity during the call.
- Prepare (5 minutes before). Copy your template and add the agenda items as section headers. Monday.com suggests pre-populating a template this way, so you fill in a structure rather than face a blank page. Add the attendee list and the meeting's one-line purpose.
- Capture (during). Write fast and rough. Type keywords, names, numbers and fragments. Mark anything that sounds like a decision, a task or an unanswered question with a symbol you will search for later, such as
D:,A:andQ:. Do not format. Do not write full sentences. - Distill (within the hour). Monday.com recommends cleaning up and distilling notes within 30 to 60 minutes after the session ends, while context is fresh. Turn your marked lines into the final summary. Check that every action has one owner and a date. If you are missing either, ask in the meeting channel now, not next week.
If you are running the meeting
You cannot facilitate and take thorough notes at once. Three options, in order of preference:
- Ask someone else to take notes and rotate the role.
- Record the meeting, with everyone's agreement, and write the summary afterward from the recording.
- If neither is possible, write only the marked lines: decisions, owners and dates. Say them aloud as you write ("So Aung will send the draft by Thursday") so the group confirms them on the spot.
That last habit does double duty. It captures the item and gets it verified before anyone leaves the room.
Verbal triggers: how to spot decisions and action items
Decisions and commitments tend to arrive in predictable phrases. Listening for them lets you write less and miss less.
Decisions
- "Let's go with..."
- "We agreed..." or "So we're settled on..."
- "Okay, that's the plan."
- "We'll stop doing..." or "We're not going to..."
When you hear one, write the decision and the reason in a single line. If nobody states the reason, ask: "Is the reason cost?" It takes five seconds and saves a long argument later.
Action items
- "I'll take that."
- "Can you own this?"
- "By Friday" or "before the next call"
- "Send me..." or "Loop in..."
The common failure is a task that someone volunteers for without a date. Ask for the date before the topic changes.
Open questions and objections
- "We still don't know..."
- "Let's park that."
- "I'm not comfortable with..."
- "That depends on..."
Parked items and objections are the ones that quietly cause trouble in the next meeting. Record them with a name beside each: who will find the answer.
When people switch languages
In many teams, including bilingual teams in Myanmar, people discuss in one language and decide in another, or switch within a sentence. This makes manual capture harder, because the decision phrase might be in a different language from the rest of your notes.
Two habits help. First, capture the decision as spoken, in whatever language it came in, and translate or standardize only during the distill phase. Second, write the owner's name and the deadline the same way every time, whichever language the sentence was in, so that your summary reads cleanly. For more on why mixed-language speech is hard, see our post on Burmese-English code-switching and our multilingual transcription guide.
A copy-paste meeting notes template
This is the version to send. Keep the working notes separate and link them at the bottom.
Meeting: [Name] | Date: [YYYY-MM-DD]
Attendees: [Names]
Purpose: [One line]
SUMMARY
[Two sentences: what this meeting settled and what is still open.]
DECISIONS
1. [Decision] - [Reason in one line]
(or: Decisions: none)
ACTION ITEMS
1. [Task] - Owner: [One name] - Due: [Date]
(or: Action items: none)
OPEN QUESTIONS
1. [Question] - Who will answer: [Name] - By: [Date]
NEXT MEETING: [Date / time / main topic]
Full transcript and recording: [link]
Notes on using it:
- Fill the summary last, after the lists.
- If a section is empty, write "none" instead of deleting it.
- Keep the whole message short enough to read on a phone without scrolling much.
Distribute and follow up so notes drive action
Send the summary in the body of an email or chat message, not as an attachment, and send it while people still remember the meeting. Within an hour is the target.
A few rules that help:
- Put the actions first in the message for people who only read the top.
- Tag each owner by name so they get a notification.
- Link the transcript for anyone who needs the detail.
- Check the dates at the next meeting by opening the previous notes and reading the action items aloud. Two minutes of this changes how seriously people treat the notes.
Meeting notes versus meeting minutes
Notes are a working summary for the team. Minutes are a formal record, usually needed for boards, legal compliance or contracts, and they follow stricter conventions about attendance, motions and approvals. If you need that, see our guides to how to write meeting minutes and the Myanmar meeting minutes template. Many teams send notes within the hour and produce minutes only when a formal record is required.
Using AI without cluttering the summary
AI tools can record, transcribe and draft a summary, which removes most of the typing. The risk is sending everything the tool produces. Treat the AI output as your first pass in the workflow above: review it once, correct names and dates, check each action has one owner, and delete anything that is not a decision, a task or a question. Archive the transcript and send the short version.
How Loka Note fits
Loka Note handles the capture and first-draft stages of this workflow. It records meetings in your browser without a bot joining the call, or takes uploaded audio and video files, and then produces a transcript and a summary with a TL;DR, decisions, action items and open questions. Those are the same sections as the template above, so your distill pass becomes a review.
It is built Burmese-first and handles mixed Burmese-English speech, along with Thai, Vietnamese, Chinese, Yoruba, Hausa and English. Action items are collected into a to-do list, notes can be exported as PDF or sent by email, and Ask Loka lets you ask questions such as "What did we decide about pricing last month?" across your past meetings.
There are no plan tiers. Minute top-ups start at $1.99 for 60 minutes, and an optional Unlimited plan is $19.99 per month. You still need to read the output and confirm owners and dates, because that is the part that makes notes trustworthy.
Try it on your next meeting: create an account at app.lokanote.com/signup
Frequently asked questions
What should be included in standard meeting notes?
Include the decisions made, the action items with one owner and a deadline each, and the questions that remain open. Add the date, attendees and a one-line purpose so the notes make sense later. Leave out the play-by-play of who said what.
What is the difference between meeting minutes and meeting notes?
Minutes are a formal record, often needed for legal, board or compliance reasons. Notes are a working summary written so the team can act. Many teams keep both: the notes go out within the hour, and the minutes are produced when a formal record is required.
How do you take notes when you are also running the meeting?
Pre-fill a template with the agenda items as headers and only type decisions, owners and deadlines as they come up. Record the meeting if everyone agrees, so you can fill gaps afterward. If possible, hand the note-taker role to someone else.
What note-taking method is best for business meetings: Cornell, Outline, or Quadrant?
The outline method works for most recurring meetings because it follows the agenda. Cornell suits long discussions where you want a summary strip at the bottom. A quadrant layout suits decision-heavy meetings. Pick one and use it consistently so your team learns where to look.
How can AI tools help take meeting notes without cluttering the final summary?
Keep the full transcript as an archive and send only the short summary: decisions, action items and open questions. Review the AI output once, correct names and deadlines, and delete anything that is not a decision, task or question before sharing.
