Markdown Meeting Minutes Template: Decisions and Action Items

Copy a practical Markdown meeting-minutes template, record decisions and owners clearly, and export professional minutes as PDF.

Minutes should preserve outcomes, not every sentence

Meeting minutes are most useful when readers can quickly answer four questions: what was decided, what remains open, who owns each action, and when it is due. Markdown is a good format for this job because headings, lists, checkboxes, and tables create a repeatable structure. The source remains searchable and easy to review in Git, a wiki, chat, Word, or PDF.

A template can also become too complicated to use during a live meeting. Start with five blocks: meeting information, decisions, action items, discussion highlights, and the next meeting. Add specialist sections only when the meeting genuinely requires them.

Copyable Markdown meeting-minutes template

# [Meeting name] — Minutes

## Meeting information

| Field | Value |
|---|---|
| Date and time | YYYY-MM-DD HH:MM–HH:MM |
| Location | Room / online |
| Attendees | Names |
| Apologies | Names |
| Note taker | Name |
| Objective | One sentence describing what must be decided |

## Decisions

- [Decision and effective date]
- [Selected option]

## Action items

| Status | Action | Owner | Due date |
|---|---|---|---|
| Not started | [Specific action] | [One owner] | YYYY-MM-DD |

## Topic 1: [Topic]

### Conclusion

[Conclusion for this topic]

### Important discussion points

- [Fact that influenced the decision]
- [Options considered and rationale]
- [Remaining concern]

## Open questions

- [ ] [Question] — Owner: [name], due: YYYY-MM-DD

## Next meeting

- Date: [date and time]
- Main topic: [decision required]
- Preparation: [documents or research]

Put decisions before the discussion

Most readers want the result, not a replay of the conversation. Place decisions near the beginning and write them as concrete statements. “Review the proposal” is not a decision; “Adopt option A from September 1” is. Include the scope and effective date when they matter.

Do not mix unresolved ideas into the decision list. Move them to Open Questions and assign an owner and a deadline for obtaining the missing information. This distinction reduces the common disagreement in which one participant believes an item was approved while another believes it was only discussed.

Give every action one owner and a real date

An action without an owner is unlikely to happen. Record the task, one primary owner, and a calendar date in the same row. If several people will help, list the accountable owner in the table and describe collaborators in the detail section. A date such as 2026-08-14 remains clear when somebody reads the minutes weeks later; “by Friday” does not.

Keep status values simple: Not started, In progress, Done, and Blocked are normally enough. If action items are copied into a project-management system, link to the resulting ticket and let that system remain the source of truth.

Summarize rationale instead of transcribing speakers

Chronological notes such as “Alex said this, then Morgan disagreed” become long and difficult to scan. Summarize the alternatives, facts, constraints, risks, and rationale that led to the outcome. Record speaker names only where attribution is required for legal, audit, or governance reasons.

Preserve facts that future readers will need to understand the decision: prices, dates, contract conditions, incident evidence, and dependencies. Clearly label assumptions and unverified claims. A short but ambiguous record is not better than a long one.

Prompt for organizing raw notes with ChatGPT or Claude

Organize the notes below as professional Markdown meeting minutes.

Requirements:
- Summarize conclusions and rationale; do not produce a transcript
- Put only explicitly approved items under Decisions
- Write “To confirm” when an owner, date, or fact is missing
- Use the order Decisions, Action Items, Topic summaries, Open Questions, Next Meeting
- Use one H1, H2 for main sections, and H3 for supporting sections
- Format actions as a table with Action, Owner, and Due Date
- Return Markdown only

Raw notes:
[paste notes here]

Human review is mandatory. Check decisions, names, monetary values, dates, and customer information against the recording or original notes. Before sending confidential material to an AI service, follow your organization's data-handling policy.

Turn the minutes into a professional PDF

For formal distribution or archiving, apply a consistent print stylesheet for meeting notes. A one- or two-page weekly meeting usually does not need a cover or table of contents. Longer steering meetings may benefit from a cover and an H2-based TOC.

Avoid splitting the decision list or action table across an awkward boundary. If a heading is stranded at the bottom of a page, move the page break in the preview. Page numbering in 1/n form makes missing printed sheets easier to identify. Reopen the saved file and inspect the first page, final page, action table, and page count. To apply the same workflow to specs, resumes, and other business documents, see Markdown for Business Documents: Minutes, Specs, Resumes & PDFs.

Pre-distribution checklist

Meeting name, date, attendees, and note taker are correct
Decisions and open questions are clearly separated
Every action has one owner and a calendar due date
Names, figures, and dates have been checked against primary notes
Unnecessary personal data and conversational remarks are removed
The document uses one H1, H2 chapters, and optional H3 subsections
Tables fit within the PDF page
The entire last page appears in the exported file
The filename contains the meeting name and date

FAQ

Must every field be completed?

No. Keep Decisions, Actions, and Next Meeting, then remove sections that do not apply. A smaller template that people consistently complete is better than an exhaustive form they avoid.

Do meeting minutes need a table of contents?

Usually not for one or two pages. Add one when a document combines several meetings or contains many independent topics.

Can Markdown checkboxes replace task management?

They work for a small team and short-lived actions. If owners need reminders, move the actions to a task system and link the tickets from the minutes.

What if recipients need to edit the minutes?

Use Pandoc or another compatible converter to create a docx for an editable handoff. PDF is preferable when the approved record should retain its layout.

Summary

Effective minutes are measured by clarity, not length. Separate decisions from open questions, assign every action to one person, and use precise dates. Markdown keeps the record portable; a cover, TOC, controlled page breaks, and page numbering can be added only when a formal PDF is needed.

Create a PDF from Markdown meeting minutes