A Plain-Text Meeting Notes Template You'll Actually Reuse

Introduction

A good meeting notes template is the one you don't have to rebuild every time. A date and attendee line, a one-sentence summary, headings for what got discussed, a checklist for what happens next — that's the whole shape. Plain text and Markdown make it portable: the same file opens the same way in any editor, on any device, years later. If you already keep a plain-text note-taking system for capture, this is that same idea applied to meetings. Write it once, reuse it every time.

Why Plain Text Wins for Meeting Notes

Markdown's whole design goal is that a marked-up file stays readable as raw plain text, without a renderer. No app has to open correctly for you to read back what you wrote. That matters most mid-meeting, when you're typing and rereading in the same breath, often switching between a laptop and a phone — the file has to make sense either way.

It also means the notes outlast whatever app you took them in. A .md file doesn't lock you into a subscription or an export format. It's just text, so it stays searchable and yours for as long as you keep the file.

The Reusable Header Block

Every meeting note should open with a small block of identifying context: date, attendees, and a one-line summary. Research on group notetaking backs this up — notes need enough identifying information that anyone revisiting the file later knows who to ask if something's unclear, instead of reconstructing context from memory.

The one-line summary matters too. It's the same idea MDN's writing guidelines formalize as a page summary: the first line after the header should let you skim a folder of past notes and get the gist without opening every file.

# Weekly Sync — 2026-07-07
Attendees: Dana, Priya, Marcus
Summary: Shipped the export fix; blocked on API rate limits for next release.

Structuring the Template with Headings

Use ## and ### — plain ATX-style headers — for each agenda item and its sub-points. They're faster to write live than the older underline style, since there's nothing to go back and add once you've typed the line. Keep headings navigable the same way you would in any long document: one heading per topic, sub-bullets for detail underneath.

## API Rate Limits
- Current limit is hit ~3x/week during peak traffic
- Two options on the table: request a limit increase, or add client-side caching

Write one point per bullet, not a paragraph bundling three ideas together. That's not just a style preference. It's what makes notes scannable and sortable after the fact — the difference between notes you skim in ten seconds and notes you end up reading twice.

Action Items You'll Actually Check Off

This is the section that makes a notes template worth reusing. Markdown's task-list syntax — - [ ] for open, - [x] for done — turns the same line that records what was discussed into a checklist you can actually work from afterward.

## Action Items
- [ ] **Marcus** — file a ticket for the rate-limit increase
- [x] **Dana** — draft the caching proposal
- [ ] **Priya** — follow up with the API vendor by Friday

Bold the owner's name at the start of each line. It's a small habit, but it means you can scan a long action-item list and see who owns what right away, without reading every word.

Flagging Decisions and Risks

Not everything in a meeting is an action item. Sometimes you need to flag a decision or a risk without breaking up the flow of the notes. Markdown's blockquote-based callouts handle that:

> [!NOTE]
> Decided to postpone the redesign until after the rate-limit fix ships.

And when an option gets discussed and ruled out, strike it through instead of deleting it. ~~text~~ keeps the record of what was considered without cluttering the final decision:

- ~~Option: switch providers~~ — too costly this quarter
- Option: add client-side caching — moving forward with this

That way the file still answers "why didn't we just do X" months later, without anyone having to remember the conversation.

Doing This with Carets

Carets is a fast, native notes and code editor for iPhone, iPad, and Mac, and this template is exactly the kind of file it's built around: plain-text Markdown, organized into files, projects, and tags. Open a new note in the right project before the meeting starts, type the header block and headings as the conversation moves, and the file's done the moment the meeting ends. No export, no formatting pass.

Two features matter most here. Syntax highlighting means action-item checkboxes and code snippets pasted mid-discussion render clearly as you type, not just after saving. And because everything stays organized into files, projects, and tags, a recurring meeting's notes live together and stay searchable — you're never hunting across apps for that decision from three weeks ago.

Carets is available on the App Store for iPhone, iPad, and Mac.

Frequently Asked Questions

What's the minimum a meeting notes template needs?

A date/attendee header line, a one-sentence summary, a discussion section broken into headings per agenda item, and an action-items section using task-list checkboxes. Everything else — decisions log, callouts — is optional polish on top of that core.

Should I use numbered headers or checkboxes for action items?

Checkboxes. Markdown's task-list syntax ([ ] / [x]) lets a single line double as both the record of what was discussed and a live to-do list you can check off after the meeting, which a numbered list can't do.

Do I need a different template for every recurring meeting?

No — the value of a plain-text template is that one skeleton (header, summary, agenda-by-heading, action items) reuses across any recurring meeting; only the heading labels under Discussion change week to week.

Conclusion

The whole point of a template is that you stop rebuilding it. Header block, headed discussion, task-list action items, and the occasional callout for a decision worth flagging — that's the full skeleton, and it's the same four pieces whether the meeting is a weekly sync or a one-off planning session. Write it once as a starting file. Every future meeting is just filling in the blanks.