Practical Markdown workflow

Markdown Meeting Notes Template

By KenRich ยท Last updated: August 20, 2026

A meeting note is easier to use when the decision, the owner, and the next action are easy to find. This Markdown template gives you a small structure that works for project meetings, one-to-ones, and follow-up notes.

Why use a meeting note template?

Meeting notes often fail after the meeting, not during it. The notes contain plenty of discussion, but nobody can quickly tell what was decided or who needs to do what.

A small template gives every note the same shape. That makes it easier to scan later, search across a folder, and hand the work to someone who was not in the room.

Start with the shape
Markdown input 
# Project check-in

**Date:** 2026-08-20
**People:** Alex, Sam, Priya

## Decision

Choose the smaller release scope for this week.

## Next actions

- Alex: update the release checklist by Friday
- Sam: test the Windows installer

## Open questions

- Do we need a separate Linux package note?
Rendered preview

Project check-in

Date: 2026-08-20 People: Alex, Sam, Priya

Decision

Choose the smaller release scope for this week.

Next actions

  • Alex: update the release checklist by Friday
  • Sam: test the Windows installer

Open questions

  • Do we need a separate Linux package note?

NoteThe headings make the important parts easy to find before you add more detail.

The basic template

Keep the top of the file factual: date, people, project, and purpose. Then separate decisions from discussion and actions. You can add a short context section when the note will be read by someone who missed the meeting.

The template does not need to be long. Its job is to make the next useful fact easy to locate.

Reusable meeting notes
Markdown input 
# Meeting title

**Date:** YYYY-MM-DD
**People:**
**Project:**

## Context

Why did we meet?

## Discussion

- Point worth keeping
- Constraint or risk

## Decisions

- Decision and the reason for it

## Next actions

- Person: action, due date

## Open questions

- Question that still needs an answer
Rendered preview

Meeting title

Date: YYYY-MM-DD People: Project:

Context

Why did we meet?

Discussion

  • Point worth keeping
  • Constraint or risk

Decisions

  • Decision and the reason for it

Next actions

  • Person: action, due date

Open questions

  • Question that still needs an answer

NoteCopy this structure for the next meeting, then remove sections that do not help.

Keep decisions separate from discussion

Discussion records what people considered. A decision records what the group chose. Mixing the two makes old notes hard to trust because readers have to reconstruct the outcome from the conversation.

Put the decision near the top when it affects the rest of the note. Keep the reason short, and link to a longer specification or issue when the details belong elsewhere.

Decision with context
Markdown input 
## Decision

Use local Markdown files as the source of truth for the preview workflow.

**Reason:** The team needs files that can be backed up and opened outside one service.

**Related:** [Local-first Markdown editing](/docs/local-first-markdown)
Rendered preview

Decision

Use local Markdown files as the source of truth for the preview workflow.

Reason: The team needs files that can be backed up and opened outside one service.

Related: Local-first Markdown editing

NoteA short reason helps a future reader understand why the decision was made.

Write action items someone can act on

An action item needs an owner and a concrete verb. Write "Priya: check the PDF output on Windows" instead of "PDF testing". Add a due date when the timing matters.

Keep open questions separate from actions. An unanswered question may need research before anyone can take responsibility for it.

Action items and questions
Markdown input 
## Next actions

- Jordan: add the missing screenshot to the guide by 2026-08-22
- Mei: review the table layout in the exported PDF

## Open questions

- Should the next release keep the current PDF watermark?
Rendered preview

Next actions

  • Jordan: add the missing screenshot to the guide by 2026-08-22
  • Mei: review the table layout in the exported PDF

Open questions

  • Should the next release keep the current PDF watermark?

NoteThe owner and verb tell the reader what happens next.

Review the note before sharing it

Read the note once from top to bottom. Remove repeated discussion, check names and dates, and make sure each decision has enough context to stand on its own.

Then preview the rendered document. Tables, links, code blocks, and long headings can look different from the source. Download the Markdown file before you close the browser, or save the document locally when it needs to be kept.

A short review checklist
Markdown input 
## Before sharing

- [ ] The title and date are correct
- [ ] Decisions are separate from discussion
- [ ] Each action has an owner
- [ ] Open questions are still open
- [ ] Links and tables render correctly
- [ ] The Markdown source is saved
Rendered preview

Before sharing

  • [ ] The title and date are correct
  • [ ] Decisions are separate from discussion
  • [ ] Each action has an owner
  • [ ] Open questions are still open
  • [ ] Links and tables render correctly
  • [ ] The Markdown source is saved

NoteA short checklist catches the mistakes that are easiest to miss after a busy meeting.

Use the template in VeloWrite

Open the web editor when you need a quick note during or after a meeting. The split view lets you check the source beside the rendered result, and the Markdown download keeps a copy you can move into your project folder.

Use the desktop app when the notes belong with local project files or need offline access. Local history gives you a few recovery points while you clean up the note after the meeting.

Continue with VeloWrite

Open Web Editor

Read Developer Guide