Template

Staff meeting minutes template

Staff minutes should be action-first: blockers, decisions, owners, due dates.

Generate staff minutes from a form
Template
Copy → paste → ship
# Staff Meeting Minutes

**Team:** {Team}
**Date/Time:** {YYYY-MM-DD}, {Start–End}
**Attendees:** {Names}

---
## Wins (fast)
- {Win}

## Metrics / Scoreboard (optional)
Metric | Goal | Actual | Notes
---|---:|---:|---
{Metric} | {Goal} | {Actual} | {Notes}

---
## Updates (short bullets)
- {Function/Person}: {Update}

---
## Blockers & Asks
- {Owner}: {Blocker/Ask}

---
## Decisions
- {Decision} — {Owner/Group}

---
## Action Items
Owner | Task | Due | Priority | Status
---|---|---|---|---
{Owner} | {Task} | {Due} | {H/M/L} | {Status}

---
## Next Meeting
- Date/time:
- Prep required:
How to use
  • Keep updates short; push deep dives into follow-ups.
  • Use one action table so nothing gets lost.
  • Send the recap the same day while context is fresh.
Common mistakes
  • Writing minutes as a summary instead of a work plan.
  • No owners/due dates for action items.
  • Letting blockers stay vague (“someone should”).
AI note‑taker fit
  • Overlap is common in team meetings — validate diarization.
  • Names are critical for ownership; numbers for timelines and commitments.
  • Export/copy helps you paste into tickets and task tools.
See pricing table • Take Tool Finder • See lab receipts
Want the cheapest tool that can populate this template?
Use Tool Finder, then validate the failure mode that matters.
Take Tool Finder See pricing table See lab receipts