Meeting Minutes

Standard meeting minutes — attendees, decisions, action items, next steps.

Customise

Live preview

MEETING MINUTES

WEEKLY PRODUCT REVIEW

Date:     May 4, 2026
Time:     10:00 AM – 11:00 AM PT
Location: Conference Room B / Zoom

──────────────────────────────────────────────────────────────────────

ATTENDEES:
Jane Doe (CEO)
John Smith (CTO)
Maria Garcia (Head of Product)
Alex Lee (Engineering Lead)

ABSENT / REGRETS:
Sam Chen (Designer) — vacation

──────────────────────────────────────────────────────────────────────

AGENDA:
1. Q3 launch readiness review
2. Customer feedback from beta cohort
3. Engineering capacity for Q4
4. Open discussion

──────────────────────────────────────────────────────────────────────

DISCUSSIONS AND DECISIONS:

1. Q3 LAUNCH READINESS
   - Maria reported all features feature-complete; QA in progress.
   - John flagged risk: third-party API dependency may not stabilise by launch date.
   - DECISION: Soft-launch to top 50 customers on planned date; full launch delayed by 2 weeks pending API stability.

2. CUSTOMER FEEDBACK
   - 78% of beta users completed full onboarding (target was 70%).
   - Top complaint: lack of integration with Slack.
   - DECISION: Slack integration moved to top of Q4 backlog.

3. ENGINEERING CAPACITY
   - Alex confirmed team can absorb Slack work without delaying Q4 roadmap items.

──────────────────────────────────────────────────────────────────────

ACTION ITEMS:

John | Confirm soft-launch date with marketing | 2026-05-10
Maria | Draft Slack integration spec | 2026-05-15
Alex | Spike on Slack OAuth flow | 2026-05-20
Jane | Send launch update to investors | 2026-05-12

──────────────────────────────────────────────────────────────────────

NEXT MEETING:
2026-05-13, 10:00 AM PT, same Zoom

──────────────────────────────────────────────────────────────────────

Minutes prepared by: __________________________

Approved by:         __________________________     Date: ____________

About this template

Meeting minutes are the institutional memory of an organisation — the written record of what was decided, by whom, and what comes next. Most teams skip them or write paragraph-style narratives that no one re-reads. Effective minutes are STRUCTURED: who was there, what was decided (not what was discussed), what action items came out, and who owns each. The action-items table with owner + due-date is the single most valuable element — it converts a meeting into a tracking artifact that can be reviewed at the next meeting. For corporate boards, properly-formatted minutes are LEGALLY REQUIRED in most US states and provide protection in disputes. For team meetings, well-written minutes save time at the next meeting (no "wait, what did we decide last time?") and prevent half the action items from being forgotten.

When to use it

  • Board meetings (legally required in most US states).
  • Recurring team meetings where decisions need to be tracked.
  • Cross-functional meetings with multiple attendees.
  • Client meetings where deliverables or commitments are agreed.

What to include

  • Meeting title, date, time, location.
  • Attendees + absent.
  • Agenda items.
  • Key discussions and explicit decisions.
  • Action items with owner + due date.
  • Next meeting date/time.
  • Approval signature line.

Frequently asked

Document decisions, not discussions. "We discussed pricing for an hour" is useless; "Pricing decision: $99/user/month for Pro tier, effective Q3" is the gold. If a discussion was particularly important, summarise the reasoning in 1-2 sentences.
⚠ Legal disclaimer. This template is provided for informational purposes only and is not a substitute for legal advice from a qualified attorney. Always consult a licensed professional before using this document for any binding agreement.

Related templates