Meeting Notes Template in Markdown: 3 Copy-Paste Kits

A meeting notes template in markdown is a plain-text layout you duplicate before every meeting: a header for date and attendees, sections for notes and decisions, and an action items list written as checkboxes. The four templates below cover a general meeting, a 1:1, a standup, and a client call. Copy the first one now; steal the variants as you need them.

# Project sync - 2026-08-19

Attendees: Ege, Maya, Tom
Facilitator: Ege

## Agenda
- Status on the pricing page
- Demo video slot
- Offline queue edge case

## Notes
- Pricing copy is one revision from done
- Demo needs the new onboarding flow, which ships behind a flag Thursday

## Decisions
- Keep the paper texture in illustrations
- Launch post moves to 2026-08-26

## Action items
- [ ] Ege: revise pricing page copy, due 2026-08-21
- [ ] Maya: send flag config to ops, due 2026-08-20
- [ ] Tom: book demo video slot, due 2026-08-22

That file does everything a meeting template needs to do, and it renders anywhere GitHub Flavored Markdown does: Obsidian, VS Code, Typora, Bear, or a GitHub issue. If you want the daily and weekly files this one plugs into, they live in the markdown todo list template pack.

Why do meeting action items die after the meeting?

Meeting action items die in the transfer, not the meeting. The note was taken, the file was saved, and then the follow-up lived only inside a document nobody reopens. Research on meeting follow-through is thin, but the pattern is familiar to anyone who has audited old notes: unchecked boxes from three weeks ago, owner unknown, context gone.

Three failure modes account for most of it:

• Topic-style items. "Pricing discussion" is not an action item; it is a memory aid. Without a verb and an owner, nothing can be checked off, so nothing gets done.
• Notes that never merge into the task system. The meeting file and the todo list are different places, and nobody performs the copy step.
• No retrieval path. If you cannot answer "what do I owe people?" in one search, follow-ups surface only when the other person asks, which is the expensive way.

The templates on this page attack all three with one convention: every action item is a checkbox line starting with an owner. It looks almost too simple. It is the whole trick.

What do the four markdown meeting notes variants look like?

The general template at the top of this page handles a standard team meeting. The three variants below adjust the middle sections for meetings with different shapes: a 1:1, a standup, and a client call. All four end with the same checkbox action items section.

The 1:1 template

# 1:1 Ege + Maya - 2026-08-19

## Their topics
- Worried about the Q4 scope
- Wants feedback on the ops runbook

## My topics
- Review coverage during launch week
- Growth plan check-in

## Notes
- Runbook feedback: tighten the escalation section
- Scope worry is really about the contractor handoff

## Action items
- [ ] Maya: draft handoff plan, due 2026-08-26
- [ ] Ege: book coverage review with Tom, due 2026-08-22

A 1:1 file is one running file per person, newest meeting on top. Keeping the history in one place turns "how long has this been a concern?" into a scroll, and pattern-spotting across eight weeks of notes is where 1:1s actually earn their hour.

The standup template

# Standup - week of 2026-08-17

## 2026-08-19
### Ege
- Done: [x] pricing revision sent
- Doing: [ ] changelog for 2.4
- Blocked: waiting on legal terms

### Maya
- Done: [x] flag config to ops
- Doing: [ ] onboarding flow QA
- Blocked: none

Standup notes are a rolling weekly file, newest day at the top. Yesterday's "doing" becomes today's "done" by flipping [ ] to [x], which means updating the file takes under two minutes and the empty-square view at the top of the file is everyone's open work.

The client call template

# Call - Acme Corp - 2026-08-19

Attendees: Ege; Dana (Acme)
Goal: agree on pilot scope

## Notes
- Pilot covers two teams, not the whole org
- Security review needed before data flows

## Their asks
- Pricing for 25 seats
- SOC 2 summary document

## Action items
- [ ] Ege: send seat pricing, due 2026-08-20
- [ ] Ege: send SOC 2 summary, due 2026-08-21
- [ ] Dana: confirm pilot teams, due 2026-08-26

The client variant adds a goal line at the top and a "their asks" section, because the most valuable part of a sales or success call is usually the list of things you owe afterward. Items with the client's name as owner stay in the same searchable format, which makes the gentle follow-up email a grep away.

How do action items survive the meeting?

Action items survive the meeting when they leave the notes file within the hour and land in the place where work actually gets tracked. The markdown convention buys you the retrieval path, but the transfer step still has to happen, and doing it by hand at 6pm is exactly the kind of task that gets skipped twice and then forgotten entirely.

The lowest-friction version of the transfer: say the follow-up out loud the moment it is assigned. Speak "Maya sends the flag config to ops by Wednesday" into quik.md, and the AI organize step files it as a task with the next step already written. Everything stays exportable as markdown, so the meeting file and the task list never disagree about who owns the data. The full capture flow is described on the meeting notes to action items page, and the same voice-first habit that rescues action items also covers spontaneous work outside meetings, as in the project idea capture walkthrough.

quik is a PWA, the free plan covers a daily AI-organize cap with browser speech recognition, and Pro is $14.99 monthly or $69.99 yearly with a 7-day trial, or $99.99 once for lifetime. If you are weighing where a capture layer sits relative to the rest of your stack, the pillar on AI task managers maps the category.

Pricing shown reflects plans at the time of writing. Check quik.md/pricing for current rates.

FAQ

What should a meeting notes template include?

A meeting notes template needs five things: a header with the date and attendees, an agenda or topics section, space for notes, a decisions list, and an action items section with an owner and a due date on every item. Everything else, from attendees' roles to parking-lot topics, is optional friction you can add later if a meeting type demands it.

How do you write action items in markdown meeting notes?

Write each action item as a checkbox line with an owner prefix and a due date: - [ ] Maya: send the revised proposal, due 2026-08-28. The checkbox marks it as open work, the owner prefix makes it searchable across every meeting file, and the date makes it followable. Topic-style items like "discuss pricing" are notes, not action items.

What is the best format for standup notes?

The best standup format is three headings per person: done, doing, blocked, each with checkbox lines underneath. Keep the file running (one file per week, newest day on top) so yesterday's "doing" rolls into today's "done" by flipping a checkbox. A standup file should take under two minutes to fill in.

How do I find my action items from old meetings?

Search across your meeting notes folder for - [ ] YourName: with the trailing space after the bracket. In VS Code this is one find-in-files search; in Obsidian the same pattern powers Tasks plugin queries. The owner-prefix convention is what makes this work, which is why every template on this page includes it.

Can AI take meeting notes instead of a template?

AI transcription tools can draft raw notes from a recording, as of 2026 most of them do that reasonably well. The template still matters because the output that survives is structured: decisions and owner-tagged action items. Tools like quik.md work from the other direction, capturing spoken follow-ups as they happen and filing them as markdown tasks.

What should you read next?

• Markdown todo list templates, the daily, GTD, weekly, and kanban files this one pairs with.
• Meeting notes to action items, the voice-first capture flow for follow-ups.
• Project idea capture, the same habit applied to ideas between meetings.
• AI task manager, where AI routing fits with markdown-first note workflows.

References

• GitHub Flavored Markdown spec, GitHub.
• Obsidian Tasks plugin, Clare Macrae.
• Markdown Guide: extended syntax, Matt Cone.
• Harvard Business Review: meetings, Harvard Business Review.