Back to Blog
Best Practice•2026-11-16•12 min read

Meeting Notes Template + 5 Formats That Work

Meeting Notes Template + 5 Formats That Work
TL
Team Laxis
Laxis Team @ Laxis

Somewhere around minute eleven you realize you've been typing steadily and absorbing nothing. The notes are a bad transcript. You missed the one sentence that changed the plan. And on Thursday, when someone asks what was agreed, the doc you produced is unreadable even to you.

That's a structure problem, not a discipline problem. A meeting notes template fixes it by deciding, before anyone starts talking, what you're listening for — so your attention goes to judgment instead of stenography. Below is one master template that works for almost any meeting, plus five formats shaped to specific situations: one-on-ones, team syncs, client and discovery calls, interviews and user research, and a personal capture format for people who run a second-brain system.

Take whichever one fits, drop it in a doc, and use the worked example underneath it to calibrate how much detail is actually enough. Blank fields never tell you that.

Notes, minutes, and transcripts are three different things

People use these words interchangeably and then wonder why the document disappoints someone. They're three separate artifacts with three separate jobs, and reaching for the wrong one is the usual reason note-taking feels like wasted effort.

Notes are informal and working. You write them for yourself and your team, in your own shorthand, during the meeting. Nobody approves them. They can contain your opinion — "Devi sounded unconvinced" is a legitimate note and would never belong in an official record.

Minutes are the formal record of a governing body. Board, committee, HOA, council. Fixed structure, neutral voice, motions and votes recorded verbatim, approved at the following meeting, and in many jurisdictions legally required. If that's the document you need, use the free meeting minutes template instead — it has the quorum, motion, and signature blocks this page deliberately leaves out, and the guide to writing meeting minutes covers the neutrality rules that go with them.

Transcripts are raw. Every word, every filler, every tangent, usually machine-generated. A transcript is source material, not a document — it's what you search when someone disputes a detail, and it's a terrible thing to send to a busy person.

Meeting notesMeeting minutesTranscript
Written forYou and your teamThe organization and its recordSearch and reference
Written whenDuring, tidied afterDuring, formalized afterAutomatically, in real time
VoiceYours — shorthand and judgment allowedNeutral third person, no interpretationVerbatim, no voice at all
Formal statusNoneOfficial; may carry legal weightNone
Who approves itNobodyThe body, at the next meetingNobody
Typical lengthA screen or two1–3 pagesThousands of words
Use it forAlmost every meeting you attendBoards, committees, anything governedDisputes, quotes, training material

One more distinction worth naming before we get to the templates: an agenda is what you plan to discuss, written before the meeting. Notes are what actually happened, written during and after. They're two halves of the same loop, and if you want the front half, there's a full meeting agenda template with examples covering the same range of meeting types.

The master meeting notes template

Start here. Five blocks, and the first one is the one people skip: a single line naming what you need out of this meeting. Write it before you join. It changes what you hear.

Template — master meeting notes

[MEETING NAME]. — [Date] · [Time] · [Who's there]

What I need out of this: [One line. A decision? A number? Clarity on who owns something?]

Notes

  • [Topic] — [what was said that I couldn't reconstruct on my own]
  • [Topic] — [numbers, names, exact phrasing worth keeping]
  • [Anything that surprised me or contradicted what I assumed]

Decisions

  • [What was settled — in a full sentence, not a fragment]

Actions

  • [Owner] → [Specific task] → [Due date]
  • [Owner] → [Next task] → [Date]

Open questions

  • [Question that didn't get answered] — ask [Name] by [Date]

Next: [When we meet again, and what has to be true by then]

Here it is filled in, from a 40-minute cross-team meeting where the real outcome wasn't on the agenda at all:

Filled example — master format

PRICING PAGE REDESIGN — KICKOFF SYNC. — Tue Aug 4 · 2:00–2:40 pm · Nadia Farouk, Theo Brennan, Wren Sato, me

What I need out of this: a launch date I can commit to in the board deck.

Notes

  • Wren: pricing page gets 38% of site sessions but converts at 2.1%. Biggest drop-off is the plan comparison table on mobile.
  • Theo: the billing migration lands Sept 14 and freezes all pricing copy for two weeks either side. Nobody had flagged this before today.
  • Nadia, on shipping before the migration: "we'd be redesigning a page that's about to change underneath us."
  • Surprise: legal reviews any plan-name change. Adds ~5 business days we hadn't budgeted.

Decisions

  • Ship the mobile comparison table fix on its own in August. Hold the full redesign until after the billing migration completes.
  • Plan names stay as they are, which removes legal review from the critical path.

Actions

  • Wren → mobile comparison table mockups, two options → Fri Aug 7
  • Theo → confirm the migration freeze window in writing → Thu Aug 6
  • Me → move the redesign date in the board deck to Oct 6 → Wed Aug 5

Open questions

  • Does the freeze cover the FAQ block at the bottom of the page, or just plan cards? — ask Theo by Thu Aug 6

Next: Aug 18, same time. By then: mobile fix in staging, migration window confirmed.

Tip: write the "what I need out of this" line before you join. It takes eight seconds and it does more work than anything else on the page. It turns you from a passive recorder into someone with a question, and questions are what make notes selective.

It also has an uncomfortable side effect, which is the point: some meetings you'll find you can't fill that line in at all. That's useful information about the meeting.

What to write down, and what to skip

The most common failure in note-taking isn't missing things. It's capturing too much — a wall of text where the two sentences that mattered are buried in forty that didn't.

A simple filter: write what you couldn't reconstruct on your own tomorrow. Numbers, names, dates, exact phrasing that will be argued about later, and anything that contradicted what you walked in believing. Skip anything already documented elsewhere, anything you'd remember anyway, and the entire narrative of how the group arrived at a conclusion.

Concretely, capture these:

  • Decisions, in full sentences. "Hold the redesign until after migration" survives three weeks. "redesign → after migration?" does not.
  • Commitments with a name attached. The moment someone says "I'll handle that," write their name. Volunteering is the least durable form of memory in any organization.
  • Numbers and their source. "2.1% conversion (Wren, from the July analytics export)" beats "conversion is low."
  • Exact words when the wording matters. A client's phrasing of their own problem, an objection, a caveat attached to an approval. Quote it.
  • What surprised you. The gap between what you expected and what you heard is usually the most valuable thing in your notes and the first thing you'll forget.
  • Questions that died unanswered. These are next week's agenda, sitting there for free.

And skip these: the play-by-play of the discussion, anything on a slide you'll still have access to, restating the agenda back to yourself, and — this one is hard — your own points. You'll remember what you said. Write down what other people said.

Format 1: one-on-one notes

One-on-ones need a different shape because the value is longitudinal. Any single 1:1 might be unremarkable; the pattern across six of them is where you notice someone's been quietly blocked on the same thing since April. So this format carries forward, and it separates what your report needs from what you owe them.

Template — one-on-one notes

1:1 — [Name]. · [Date] · Last time: [Date]

Carried over from last time

  • [Item] — [status: done / still open / dropped and why]

Their agenda

  • [What they brought — in their words, not my paraphrase]

My agenda

  • [Feedback, context, or the thing I needed to tell them]

Blockers and asks

  • [What's in their way] → [what I said I'd do about it]

Growth thread

[The longer-running career or skill conversation — one or two lines, updated each time]

Actions

  • [Me / Them] → [Task] → [By when]

Watch for next time

[Something I noticed but didn't raise — mood, hesitation, a pattern forming]

Filled example — one-on-one

1:1 — Callum Reid. · Aug 4 · Last time: Jul 21

Carried over

  • Intro to the data team for the attribution question — done, met Jul 28, unblocked him.
  • Conference talk proposal — still open, deadline moved to Sept 1.

His agenda

  • Is the onboarding project still a Q4 priority? He's heard "it's on the list" three times and read that as a soft no.
  • Frustrated with review turnaround. Two PRs sat five days each last sprint.

My agenda

  • Told him onboarding is funded and his to run — I'd assumed he knew, which was my mistake.
  • Praised how he ran the Jul 30 incident call: stated impact before cause, which kept the room calm.

Blockers and asks

  • PR review latency → I'll propose a rotating reviewer-of-the-day at Monday's team meeting.

Growth thread

Moving toward tech lead. Gap is written communication to non-engineers, not technical depth. Onboarding is a good forcing function — he'll write the rollout plan for support and sales.

Actions

  • Me → confirm onboarding scope and budget in writing → Wed Aug 5
  • Me → propose reviewer rotation at team meeting → Mon Aug 10
  • Callum → draft the talk proposal, send me a look before Sept 1 → Aug 22

Watch for next time

He said "it's fine" twice about the review delays before actually saying it wasn't. Ask directly next time rather than waiting.

If you want the conversation structure that goes with these notes — question banks, cadence, what to do when someone brings nothing — that's covered in the one-on-one meeting template. This is just the capture layer.

Format 2: team or status meeting

Team meetings generate a lot of talk and a small number of things worth keeping. This format is built to be filled in during the meeting and readable by someone who missed it, in that order. Everything gets sorted into changed, stuck, or decided.

Template — team / status meeting notes

[TEAM] — [Meeting name]. · [Date] · Present: [Names] · Missing: [Names]

What changed since last time

  • [Area] — [what moved, with a number if there is one]

What's stuck

  • [Thing] — blocked by [what/who] — [days open] — needs [what, from whom]

Decided

  • [Decision] — [who made the call]

Discussed, not decided

  • [Topic] — [where it landed] — [when we'll close it]

Actions

  • [Owner] → [Task] → [Due]

For anyone who missed this

[Two sentences. The only part some people will read.]

Filled example — team meeting

GROWTH — Weekly sync. · Mon Aug 3 · Present: Ines Moreau, Gabriel Santos, Hana Kobayashi, me · Missing: Bram Visser (PTO)

What changed

  • Lifecycle email — reactivation series went to 14,000 dormant accounts Friday. 9.4% open, 1.1% clicked, 62 reactivations so far.
  • Paid search — cost per trial up to $84 from $61 in three weeks. Gabriel suspects a competitor bidding on our brand terms; not confirmed.
  • Referral program spec done, in review with legal.

What's stuck

  • Attribution dashboard — blocked on the data team's warehouse migration — 16 days open — needs a date, not more nudging.
  • Landing page tests — blocked on design capacity — 9 days — Hana to ask for a standing half-day.

Decided

  • Pause the two worst paid search ad groups now rather than waiting for the full analysis — Ines called it.
  • Reactivation series becomes evergreen, triggered at 60 days dormant.

Discussed, not decided

  • Q4 partnership push. Everyone's for it, nobody has capacity. Revisit Sept 1 with a headcount answer.

Actions

  • Gabriel → pause the two ad groups, pull brand-term search data → Tue Aug 4
  • Hana → standing design request, half-day weekly → Wed Aug 5
  • Ines → get a committed date from the data team lead → Fri Aug 7
  • Me → write up the reactivation results for the wider team → Thu Aug 6

For anyone who missed this

Reactivation emails worked and are becoming an always-on trigger. Paid search costs are climbing and we've paused two ad groups while Gabriel investigates. Partnership push is deferred to September pending headcount.

Format 3: client or discovery call

External calls have a second audience: your CRM, your colleagues, and future-you six weeks from now trying to remember what this account actually cared about. The rule that matters here is to preserve the client's own language. When you paraphrase "our onboarding takes three months and we lose people in month two" into "onboarding friction," you've thrown away the sentence you'd have quoted back to them in the proposal. If client calls fill most of your week, our client meeting notes template goes further on that one format.

Template — client / discovery call notes

[COMPANY]. · [Date] · Call [#] · [Stage] Them: [Name, title] · Us: [Name, role]

Situation

[How things work for them today — one short paragraph]

Problem, in their words

  • "[Direct quote]" — [who said it]

Impact / what it costs them

  • [Number, time, headcount, revenue — whatever they quantified]

Who else is involved

  • [Name, title] — [role in the decision] — [met / not met]

Objections and hesitations

  • [What they raised] — [how it was answered, or that it wasn't]

Timing and process

[Driving event, budget cycle, procurement steps they named]

Next step

[What, who schedules it, by when — agreed on the call, not assumed]

My read

[Internal only. Confidence, risk, what I'd bet on. Never goes in the follow-up email.]

Filled example — discovery call

FERNWOOD LABS. · Aug 4 · Call 2 · Discovery Them: Zoe Achebe (Head of Clinical Ops), Felix Nowak (IT Manager) · Us: me

Situation

Eleven-site diagnostics network. Coordinators log study visits in a homegrown Access database, then re-key everything into the sponsor's portal.

Problem, in their words

  • "We're not slow because the science is slow. We're slow because the same data gets typed three times." — Zoe
  • "Every audit finding in the last two years has been a transcription error, not a protocol error." — Zoe
  • "I can't put another system on that Access box. It's held together with hope." — Felix

Impact

  • ~40 hours/week of coordinator time on duplicate entry, across two people.
  • Six audit findings in 24 months, all transcription. One triggered a corrective action plan.
  • Sponsor data delivery averaging 9 days against a 5-day contractual target.

Who else is involved

  • Zoe — economic buyer, owns the budget line — met.
  • Felix — technical veto, cares about the migration path — met.
  • VP of Quality, unnamed — signs off on anything touching audit trail — not met. Zoe: "she'll want to see it."

Objections

  • Migration risk off the Access database — Felix wants a rollback plan, not a slide.
  • Validation burden in a regulated environment — Zoe raised it, unresolved on the call.

Timing and process

Budget cycle closes Oct 31 or it slips a year. Procurement requires two references in the same regulatory category. The corrective action plan is why this is moving now.

Next step

Technical session with Felix and the VP of Quality, 60 min, week of Aug 18. Zoe gets the VP on the invite; I send three time options by Aug 6.

My read

Real pain with a named driving event, which is rare. The risk isn't interest, it's the unmet VP of Quality. Push to meet her at the technical session even if it means a shorter demo.

Keep the "my read" block out of anything you send. Split your client notes into two layers from the start — a shared summary of what was discussed and agreed, and a private assessment layer. The number of forwarded-by-accident internal reads in the wild is higher than anyone admits, and the damage is instant.

Format 4: interview and user research notes

Research notes have an unusual requirement: you have to keep observation separate from interpretation, because you'll analyze them later and your in-the-moment theories will contaminate the data if they're mixed in. Same applies to hiring interviews, where the whole point of structured notes is to make candidates comparable rather than memorable.

Template — interview / research notes

[Participant or candidate]. · [Date] · [Segment / role] · [Session #] Interviewer: [Name] · Recorded: [Y/N + consent noted]

Context on this person

[Who they are, what they do, why they're in the sample]

Observed — what they said and did

  • [Q asked] → "[verbatim or near-verbatim answer]"
  • [Behavior: hesitated, backtracked, opened a different tool, laughed]

Quotes worth keeping

  • "[Exact words]" — [context: what prompted it]

Interpreted — my reading (kept separate on purpose)

  • [Theory, pattern, or hypothesis — flagged as mine, not theirs]

Contradicts / confirms

  • [Which earlier session or assumption this supports or breaks]

Follow-ups

  • [Question to add to the guide for the next session]

Filled example — user research session

P07 — ops manager, 40-person logistics firm. · Aug 1 · Session 7 of 12 Interviewer: me · Recorded: yes, verbal consent at 0:00, confirmed she can stop at any point

Context

Runs dispatch for a regional freight firm. Daily user of our scheduling module, five years tenure, chose the tool originally.

Observed

  • "Walk me through this morning" → opened the dashboard, then immediately exported to a spreadsheet. "I always do that first."
  • Why the export → "because I can see the whole week at once and here I can't."
  • Behavior: three browser tabs of our product open, one per depot. Didn't mention it, didn't seem to consider it a workaround.
  • On the new filter panel: paused four seconds, then "I've seen it, I haven't used it."

Quotes worth keeping

  • "It's not that the numbers are wrong, it's that they're in the wrong shape." — on the daily export
  • "I've seen it, I haven't used it." — on the filter panel we shipped in May

Interpreted (mine)

  • The export isn't a reporting need, it's a layout need. She wants a week view we don't have.
  • The multi-tab workaround suggests our mental model is one depot at a time and hers is all depots at once. Bigger gap than any single feature.

Contradicts / confirms

  • Confirms P02 and P05, both of whom exported within two minutes. Three of seven now.
  • Contradicts our assumption that the filter panel addressed this. Nobody has used it unprompted.

Follow-ups

  • Add to the guide: "show me the spreadsheet you export to." The artifact says more than the description.
  • Ask about multi-depot views directly in sessions 8–12.

Tip: label your interpretations while you write them. A single word — "mine" — in front of a theory keeps your analysis honest three weeks later, when everything in the doc has flattened into "what the research said."

This is the one habit that separates notes you can synthesize from notes you have to re-listen to. It costs nothing and it survives being read by someone who wasn't there.

Format 5: the second-brain capture

If you keep a personal knowledge system — Obsidian, Notion, a plain folder of markdown files — meeting notes need to be findable months later by someone who has forgotten the meeting entirely. That person is you. The format is short, aggressively tagged, and linked to the things it touches.

Template — second-brain capture

title: [YYYY-MM-DD] [Topic] — [who] tags: #meeting #[project] #[person] #[theme] links: [[Project note]] · [[Person note]] · [[Earlier meeting]]

Why I was in this

[One line — future-you will have no idea otherwise]

Signal

  • [The two or three things worth keeping. Nothing else.]

Changed my mind about

[Anything that updated a belief — this is the highest-value line in the note]

Threads to pull

  • [Idea, question, or person to follow up with — no due date, this isn't a task list]

Actions → [task system]

  • [Task] — [moved to wherever your tasks actually live]

Filled example — second-brain capture

title: 2026-08-04 Pricing page redesign — Nadia, Theo, Wren tags: #meeting #pricing-redesign #billing-migration #conversion links: [[Pricing redesign]] · [[Theo Brennan]] · [[2026-07-14 Billing migration plan]]

Why I was in this

I own the board-deck timeline and needed a date I could defend.

Signal

  • Pricing page = 38% of sessions, 2.1% conversion. The mobile comparison table is the drop-off point.
  • Billing migration (Sept 14) freezes pricing copy ±2 weeks. This constraint isn't written down anywhere. It should be.
  • Legal reviews plan-name changes. ~5 business days. Nobody knew.

Changed my mind about

I'd been treating the redesign as a design problem. It's a sequencing problem — the design was never the constraint.

Threads to pull

  • Is there a list anywhere of things that freeze during a migration? If not, that's worth 20 minutes to write.
  • Wren's industry benchmark — where did that number come from? Want the source before it ends up in a deck.

Actions → Todoist

  • Update board deck timeline to Oct 6 — Wed
  • Ask Theo about the FAQ block scope — Thu

Three note-taking methods worth stealing

Templates give you a container. Methods give you a way of writing inside it. Three are worth knowing for meetings specifically; the full set, including mapping, charting and the Zettelkasten, is in our comparison of seven note-taking methods.

Cornell, adapted for meetings

Walter Pauk developed the Cornell layout at Cornell University in the 1950s for students, and it maps onto meetings almost unchanged. Split the page into a wide right-hand notes column, a narrow left-hand cue column, and a summary strip across the bottom. Notes go on the right as the meeting runs. The left column gets filled in after — but with action items and open questions instead of study prompts. Then you write two or three sentences in the summary strip.

Best for: meetings where you need a defensible record of reasoning — architecture reviews, client meetings, anything you'll be asked to explain later. Worst for: fast-moving standups, where the ceremony costs more than it returns.

Outline, with one strict rule

The default for most people: topics at the top level, points indented under them. It's fast and everyone already knows how to do it. The rule that makes it work in a meeting is that indentation must mean something — a sub-point is evidence or detail for the point above it, never just the next thing that got said. The moment indentation becomes chronological, an outline turns into a transcript with whitespace.

Best for: agenda-driven meetings, where the outline's top level is just the agenda items. Worst for: unstructured conversations that jump around, where you'll spend the meeting re-nesting things.

The quadrant

Divide the page into four boxes: questions in the top left, general notes in the top right, your own to-dos in the bottom left, and tasks assigned to other people in the bottom right. Everything you write goes into one of the four as you write it, so sorting happens live rather than afterward.

Best for: meetings where you're accountable for follow-through and there are a lot of moving commitments — project reviews, cross-team coordination. Worst for: listening-heavy sessions like research interviews, where the four-way sort interrupts the flow of attention.

If you're recording the meeting anyway, the calculus changes. When a tool is capturing the full transcript and pulling out commitments, the point of taking notes by hand shifts from capture to thinking — you're writing down your reactions and judgments rather than racing to get the facts. That's a better use of a human in the room, and it's the honest case for an AI meeting note-taker in 2026: it doesn't make you a better note-taker, it frees you to stop being one.

The ten minutes that turn notes into action

Notes decay fast. The context that makes a fragment meaningful is gone within a day, and by the following week you're reading your own handwriting like a stranger's. So the work isn't taking the notes. It's the ten minutes immediately after.

Four passes, in this order:

  1. Extract every commitment into a real task. Anything of the form "someone will do something" leaves the notes and goes into the system where work actually lives — your tracker, your task app, the ticket queue. Notes are a terrible task manager because nobody reads them twice.
  2. Give every action an owner and a date. No exceptions. "We should look into that" is not an action item; it's a feeling. If you can't name who and when, either resolve it now with one message or move it to open questions where it belongs. There's a whole method to phrasing these well in how to write action items that get done.
  3. Rewrite the decisions as full sentences. Fragments that made sense in the room won't survive. "Hold redesign → post-migration" becomes "We're holding the full pricing redesign until after the billing migration completes on September 14."
  4. Send the short version. Decisions, actions, and one line of context, to whoever needs it, the same day. Not the raw notes. Raw notes are for you.

That last step is where most of the value is and where most people stop. A meeting where three people leave with different memories of what was agreed didn't fail during the meeting — it failed in the two hours after it, when nobody wrote down which version was right.

Tip: send the recap before you switch tasks. Not end of day, not "when I get a minute." The gap between the meeting ending and the recap going out is the window where corrections are cheap — people still remember well enough to say "that's not quite what I agreed to."

Twenty-four hours later, nobody remembers precisely enough to correct you, so your version quietly becomes the truth whether it's accurate or not.

The practical obstacle is that the ten minutes after a meeting are usually the ten minutes before the next one. That's the gap a meeting assistant fills. In the Laxis desktop app you type your own notes, in whichever format above suits the meeting, while Laxis records the call; nothing joins the meeting unless you choose to invite its visible meeting bot. About every five minutes it adds a short AI note under its own heading without touching your text, and when you stop it tidies the page against the full transcript, writes a summary and turns the action items into tasks. It transcribes 60+ languages, the free Basic plan covers 300 minutes a month, and the Business plan can send the results to HubSpot or Salesforce.

Three limits worth stating plainly. The AI draft still needs a person to decide what mattered and what to cut, and the template is where that judgment goes. In the standard apps, processing happens in the cloud. And recording is your call to announce: tell people at the start and get their consent where the law requires it. Our state-by-state and country-by-country rundown of consent rules is a sensible starting point, not legal advice.

Already recorded the meeting? Upload the audio to Laxis (a free account works) and you get a summary, the decisions and the action items back, which covers most of the four passes above.

14-day Premium trial, no credit card. Try Laxis free

Keep the template. Hand off the typing. Laxis records your Zoom, Google Meet and Teams meetings on the desktop, adds AI notes beside the ones you type and turns the action items into tasks, so the judgment stays with you. 14-day Premium trial, no credit card. Download Laxis

The bottom line

Every one of these formats is really a set of questions the page refuses to let you skip. The master template asks what you needed from the meeting. The 1:1 format asks what you noticed but didn't say. The discovery format asks what the client's own words were. The research format asks which part is observation and which part is your theory.

Pick the one that matches the meeting, keep the fields in the same order every time so your eye knows where to go, and spend the ten minutes afterward. If you only take one thing from this page, take the habit of writing a purpose line before you join — the notes get better because the listening does.

Frequently asked questions

What should a meeting notes template include?

Five things: a one-line purpose so you know what you are listening for, a short context block with the date and who was there, a running notes area for what was actually said, a separate decisions list, and an action list with an owner and a date on every line. Questions you did not get to answer deserve their own spot too, because they are the seed of the next conversation.

What is the difference between meeting notes and meeting minutes?

Meeting notes are an informal working document written for you and your team, and nobody has to approve them. Minutes are the official record of a body such as a board or committee, they follow a fixed structure, and they get formally approved at a later meeting. Notes can carry your opinions and shorthand. Minutes cannot, because they can carry legal weight.

How do you take good meeting notes without missing anything?

Stop trying to capture everything. Decide before the meeting what three things you need from it, write only decisions, commitments, numbers, and phrasings you could not reconstruct later, and leave the discussion narrative alone. If you genuinely need the full detail, record the meeting so your hands are free to think instead of typing.

Should meeting notes be shared with everyone?

Share the decisions and actions, keep the rest private unless you wrote it to be read. Most people keep two layers: a personal scratch layer with half-formed reactions and reminders, and a clean summary that goes into the shared channel within a few hours. Sending raw notes creates as much confusion as sending nothing at all.

Is the Cornell method good for meeting notes?

Yes, with one change. The Cornell layout, developed by Walter Pauk at Cornell University in the 1950s, splits a page into a wide notes column, a narrow left cue column, and a summary strip at the bottom. For meetings, use the cue column for action items and open questions rather than study prompts, and write the summary in the first two minutes after the call ends.

Can AI take meeting notes for you?

It can produce a solid first draft and catch commitments you missed, but it cannot decide what mattered. Laxis, for one, records Zoom, Google Meet and Teams calls from your desktop, adds AI notes next to the ones you type, and turns action items into tasks. The editing pass is still yours: cutting tangents, fixing a loosely worded decision, and choosing what the team needs to read.

Related Product

Laxis Meeting Assistant

Automate your notes today.

  • Bot-free notes for Zoom, Google Meet, Teams and in-person meetings
  • AI summaries, action items and follow-ups in 60+ languages
  • Mac, Windows, iPhone and Android, with a free plan

Start for free, no credit card required.

Learn More ▷