20 Meeting-Note Templates for Dev Teams

Copy any template below into a blank markdown file. Each one uses checkboxes for action items and a clear owner plus date, so the note becomes tracked work instead of a chat message. For the reasoning behind these, read the meeting notes guide.

1. Daily standup

# Standup Notes

**Date:** 2026-08-13
**Team:** Platform

## Yesterday
-

## Today
-

## Blockers
-

## Action items
- [ ] 

2. Sprint planning

# Sprint Planning

**Sprint:** 24
**Dates:** Aug 13 - Aug 27

## Goal
-

## Committed items
- [ ] 

## Capacity notes
-

## Risks
-

3. Sprint retro

# Sprint Retro

**Sprint:** 24

## What went well
-

## What went wrong
-

## What to try next
- [ ] 

## Action items
- [ ] 

4. One-on-one

# 1:1 Notes

**Date:** 2026-08-13
**With:** 

## Check-in
-

## Wins
-

## Challenges
-

## Growth / feedback
-

## Action items
- [ ] 

5. Bug triage

# Bug Triage

**Date:** 2026-08-13

## New reports
- [ ] BUG-101: 

## Severity
- Critical:
- High:
- Low:

## Assigned
- [ ] 

## Next sync
-

6. Design review

# Design Review

**Feature:** 
**Date:** 2026-08-13

## Context
-

## Options considered
- Option A:
- Option B:

## Decision
-

## Follow-ups
- [ ] 

7. Architecture decision record (ADR)

# ADR-012: 

**Status:** Proposed
**Date:** 2026-08-13

## Context
-

## Decision
-

## Consequences
- Good:
- Bad:

## Reviewers
- [ ] 

8. Incident postmortem

# Postmortem: 

**Severity:** 
**Date:** 2026-08-13
**Owner:** 

## Impact
-

## Timeline
- 10:00:
- 10:15:

## Root cause
-

## What we fixed
- [ ] 

## What stays broken
-

9. Onboarding checklist

# Onboarding: 

**Start:** 2026-08-13
**Buddy:** 

## Day 1
- [ ] Access to repo
- [ ] Dev environment up

## Week 1
- [ ] First PR merged
- [ ] Read the ADRs

## 30-day goal
-

10. Client call summary

# Client Call: 

**Date:** 2026-08-13
**Attendees:** 

## Asked for
-

## Promised
- [ ] 

## Concerns
-

## Next step
-

11. Technical interview loop

# Interview: 

**Role:** 
**Date:** 2026-08-13
**Panel:** 

## Candidate
-

## Rounds
- [ ] Coding:
- [ ] System design:
- [ ] Behavior:

## Score (1-4) and notes
-

## Decision
-

12. All-hands update

# All-Hands: 

**Date:** 2026-08-13

## Wins
-

## Metrics
- MRR:
- Churn:

## What's next
-

## Q&A
-

13. Roadmap review

# Roadmap Review

**Quarter:** Q3
**Date:** 2026-08-13

## On track
-

## At risk
- [ ] 

## Dropped
-

## New bets
-

14. OKR check-in

# OKR Check-in

**Cycle:** Q3
**Date:** 2026-08-13

## Objective
-

## Key results
- KR1:  / target
- KR2:  / target

## Blockers
-

## Action items
- [ ] 

15. Pairing session log

# Pairing Session

**Date:** 2026-08-13
**Pair:** 

## Goal
-

## Did
-

## Learned
-

## Left for later
-

16. Code review notes

# Code Review: 

**PR:** 
**Date:** 2026-08-13
**Reviewer:** 

## Strengths
-

## Issues
- [ ] Blocker:
- [ ] Nit:

## Verdict
- Approve / Request changes

## Follow-ups
- [ ] 

17. Security review

# Security Review

**Scope:** 
**Date:** 2026-08-13

## Findings
- [ ] High:
- [ ] Medium:
- [ ] Low:

## Remediation owner
-

## Re-review date
-

18. Release planning

# Release Plan: 

**Version:** 
**Target date:** 2026-08-20

## Scope
-

## Blockers
- [ ] 

## Rollout plan
-

## Comms
-

19. Stakeholder update

# Stakeholder Update

**Date:** 2026-08-13

## Status
- On track / At risk / Delayed

## This week
-

## Asks
- [ ] 

## Decisions needed
-

20. Weekly team sync

# Weekly Sync

**Date:** 2026-08-13

## Highlights
-

## Cross-team deps
-

## Blockers
- [ ] 

## Next week
-

Use them in ForgeMD

Open ForgeMD, paste any template into a blank document, and invite the team to co-edit live. ForgeMD keeps the file as markdown on your machine and merges everyone’s edits without conflict, so the note stays searchable and portable after the meeting ends.