All posts

How to Use Markdown for Meeting Notes: Template and Best Practices

Master meeting notes with markdown. Template, structure, task lists, searchability, and portability. Better than Word or Google Docs for professional note-taking.

If you've been taking meeting notes in Word, Google Docs, or email, switching to markdown will change how you organize, find, and act on meeting information. Markdown meeting notes are searchable, portable, version-controllable, and easier to share than traditional formats.

Here's how to structure meeting notes in markdown, along with a template you can use immediately.


Why Markdown for Meeting Notes

Better than Word: No formatting distractions. You focus on capturing information, not clicking buttons.

More portable than Docs: Google Docs requires internet access and is locked into Google's ecosystem. Markdown is plain text — open it on any device, in any editor, sync it to any cloud service.

Searchable: All your notes in plain text markdown are easily searchable with command-line tools or even your operating system's file search. Find every mention of "Q3 budget" across all your meetings instantly.

Version-controllable: If you use Git for your notes (many professionals do), markdown works perfectly with it. You can see who suggested what and when, and collaborate without conflicting edits.

Linkable: Use markdown links to connect related meetings, decisions, and projects. Build a personal knowledge base of meeting outcomes.

Task-trackable: Use markdown task lists to track action items directly in your notes.


Meeting Notes Template

Use this template for every meeting. Copy it, fill it in, and save the file with a meaningful name like 2026-02-21-product-planning.md.

---
title: "Meeting Title"
date: 2026-02-21
attendees: [Name1, Name2, Name3]
duration: "1 hour"
next_meeting: "2026-02-28"
---

# Product Planning Meeting

**Date:** Feb 21, 2026
**Time:** 2:00 - 3:00 PM
**Location:** Zoom / Conference Room A

## Attendees

- John (Product Manager)
- Sarah (Engineering Lead)
- Mike (Design)
- You (Note-taker)

---

## Agenda

1. Q1 roadmap review
2. User feedback on new feature
3. Engineering capacity for Q2

---

## Discussion

### Q1 Roadmap Review

John opened with goals for Q1:
- Launch dark mode by Feb 28
- Improve search performance
- Start design work for new dashboard

**Key points:**
- Dark mode is on track, 85% complete
- Search performance improvement could impact other features
- Dashboard design not starting until mid-March due to availability

**Decision:** Prioritize search performance over dashboard work in early Q2.

### User Feedback on New Feature

Sarah shared feedback from beta users on the new export function:
- Users love the speed improvement
- Some confusion about file format options
- Request for bulk export functionality

**Feedback summary:**
- Positive: 4.8/5 rating from beta testers
- Pain point: File format selection needs better UX
- Feature request: Bulk operations

### Engineering Capacity for Q2

Mike discussed bandwidth for Q2:
- Current team: 4 engineers
- Expected: 3 engineers (one on sabbatical)
- Hiring: 1 new engineer joining in March

**Capacity impact:**
- Reduced capacity March-April while new engineer ramps up
- Recommend deferring lower-priority work to Q3

---

## Decisions Made

- [x] Prioritize search performance for Q2
- [x] Improve export UX before next release
- [x] Defer dashboard redesign to Q2

---

## Action Items

- [ ] John: Update roadmap docs with Q2 priorities by Feb 23
- [ ] Sarah: Create UX spec for export dialog by Feb 25
- [ ] Mike: Schedule onboarding plan for new engineer by Feb 22
- [ ] You: Send feedback summary to beta testers by Feb 24

---

## Next Meeting

**Date:** Feb 28, 2026
**Time:** 2:00 PM
**Topic:** Progress update on export UX, new engineer onboarding check-in

---

## Links and References

- [Previous meeting notes](2026-02-14-product-planning.md)
- [Q2 Roadmap](https://wiki.company.com/q2-roadmap)
- [Beta user feedback spreadsheet](https://docs.google.com/spreadsheets/...)

Key Markdown Features for Meetings

Task Lists

Track action items with checkboxes:

- [x] Completed task
- [ ] Pending task
- [ ] Assigned to someone else

Renders as clickable boxes. OpenMark and most markdown editors let you click to toggle completion.

Bold for Names and Decisions

**Sarah:** "We should prioritize this in Q2."

**Decision:** Launch by March 15.

Makes it easy to scan who said what and what was decided.

Nested Lists for Structure

## Budget Discussion

- Q1 spending: $45K
  - Engineering: $28K
  - Marketing: $12K
  - Operations: $5K
- Q2 forecast: $52K
  - Hiring impact: +$8K
  - Tool upgrades: +$3K

Links for Context

Reference related notes and documents:

[Previous sprint planning notes](2026-02-14-sprint-planning.md)
[Project wiki](https://wiki.company.com/project)
[Customer feedback](https://canny.io/board/product-feedback)

Blockquotes for Quotes

Capture exact quotes:

> "We need to ship this by end of quarter." — CEO

Structuring Large Meetings

For longer meetings with multiple topics:

# All-Hands Meeting — February 2026

## Opening Remarks

[Summary of CEO's key message]

## Departmental Updates

### Engineering

[Engineering team updates]

### Sales

[Sales team updates]

### Marketing

[Marketing team updates]

## Company Financials

[Financial update]

## Q&A

- **Question:** What's the hiring timeline?
- **Answer:** We're opening 3 positions in March.

---

[Next all-hands: March 15]

Searchability: The Hidden Power

Once you have 50+ meeting notes in markdown:

# Find all mentions of "budget" across meetings
grep -r "budget" ~/notes/meetings/

# Find all action items assigned to you
grep -r "assigned to \[Your Name\]" ~/notes/meetings/

# Find all decisions from a specific month
grep -r "Decision:" ~/notes/meetings/2026-02/

When your notes are plain text markdown, they're instantly searchable in ways that Google Docs or Word documents aren't.


Storage and Sync

Keep your markdown notes in a folder structure:

notes/
├── meetings/
│   ├── 2026-02/
│   │   ├── 2026-02-07-sprint-planning.md
│   │   ├── 2026-02-14-product-planning.md
│   │   └── 2026-02-21-executive-meeting.md
│   ├── 2026-03/
│   └── 2026-04/
├── projects/
└── reference/

Sync this folder to iCloud, Dropbox, or OneDrive, and your notes are accessible on any device. Or use Git to version-control them and collaborate with your team.


Viewing and Editing

  • Write: Any text editor (TextEdit, VS Code, Sublime Text)
  • View: OpenMark (native Mac app with beautiful formatting)
  • Preview: Built-in preview in VS Code, Obsidian, or other markdown editors

For a native macOS experience, OpenMark opens your markdown meeting notes with proper formatting, making them easy to read and review.


Converting and Sharing

Need to share notes with non-markdown users? Convert instantly:

# Convert to Word
pandoc meeting-notes.md -o meeting-notes.docx

# Convert to PDF
pandoc meeting-notes.md -o meeting-notes.pdf

# Convert to HTML
pandoc meeting-notes.md -o meeting-notes.html

Your meeting notes stay in markdown (portable, searchable, lightweight) but you can export them to any format when you need to share with stakeholders.


Pro Tips for Meeting Notes

  1. Record the time: Include the meeting date/time and duration at the top for context later.

  2. Name the note-taker: If this goes into a shared repo, others need to know who captured what.

  3. Link to previous meetings: Use relative links to build context. [Previous planning](2026-02-14-sprint-planning.md)

  4. Use two spaces at the end of a line for hard breaks if you want to separate related points without a new paragraph.

  5. Archive old notes: Move notes older than 6 months to an archive folder to keep your active notes clean.

  6. Use headings consistently: Always use ## for sections, ### for subsections. This helps tools parse and organize your notes.

  7. Separate discussion from decisions: A clear "Decisions Made" section lets people quickly see what was actually decided.


The Workflow

  1. Before the meeting: Create a markdown file with the template, add the agenda
  2. During the meeting: Take notes in markdown, use task lists for action items
  3. After the meeting: Polish the notes, link to related documents, add decisions
  4. View: Open in OpenMark to see beautifully formatted notes
  5. Share: Export to PDF or Word if needed, or link to the markdown file if sharing with team

For a guide to markdown syntax basics, see How to Write Markdown: A Beginner's Guide.

For a complete reference including task lists and other features, see Markdown Quick Reference.


Download OpenMark → — $9.99, one-time, native macOS. Open your markdown meeting notes and read them beautifully formatted. Support for task lists, tables, and all markdown syntax. Perfect for professionals who take notes in markdown.