This Meeting Minutes example shows how Alex Morgan, PMP, documented the decisions, action items, and issues raised during the Weekly Status Review on May 7, 2025 — part of Project Phoenix, a $72,250 website launch managed using the PMBOK Guide 8th Edition. Meeting minutes are the institutional memory of a project: without them, decisions evaporate, accountabilities blur, and teams find themselves re-litigating the same issues week after week.

What Are Meeting Minutes?

Meeting Minutes are a formal written record of what was discussed, decided, and assigned during a project meeting. They capture who attended, what was said on each agenda item, what decisions were made and by whom, and what actions were assigned with due dates and owners. In PMBOK 8, meeting minutes are referenced within the Stakeholder and Communications Performance Domains as key project documents that support stakeholder engagement and provide an auditable record of project governance. Well-written meeting minutes are distributed within 24 hours of the meeting and confirmed by participants before being filed in the project document repository.

What's Inside This Meeting Minutes Example

This Meeting Minutes example for Project Phoenix includes:

• Meeting details: Weekly Status Review — May 7, 2025, 9:00–9:45 AM, Zoom; attended by Alex Morgan, Sam Lee, John Tran, Maya Chen, Tom Nguyen, Riley Park (partial — first 20 minutes)
• Key discussion item: ISS-005 — the hosting migration had been delayed 11 days due to a conflicting IT infrastructure upgrade window, creating schedule pressure on the critical path
• Five action items with specific owners and due dates: Alex Morgan to escalate ISS-005 to IT Director (due May 8), Sam Lee to resequence development tasks to work around infrastructure dependency (due May 9), Maya Chen to brief content team on revised delivery timeline (due May 9), Tom Nguyen to update QA test plan for revised schedule (due May 12), Alex Morgan to send updated status report to Riley Park (due May 8)
• Three formal decisions documented with rationale: buffer reallocation approved (3-day schedule buffer from non-critical activities transferred to hosting migration path), vendor escalation authorized (Alex to contact BrightFrame about any hosting-related advisory), scope adjustment deferred (decision to not compress QA phase even if hosting delay extends further)
• Risk raised: Maya Chen flagged that CRM Mautic integration complexity might require 1–2 additional developer days; logged as Risk R-012 for monitoring
• Next meeting: May 14 — hosting migration go/no-go review with IT Director

How Alex Morgan Used These Meeting Minutes

Alex Morgan distributed the May 7 meeting minutes within 4 hours of the meeting ending — by 1:30 PM that same day. She sent them to all attendees and copied Riley Park, asking for confirmation or corrections by end of business May 8. By May 8, all five attendees had confirmed the minutes with no corrections. This rapid distribution and confirmation loop served two purposes: it validated the accuracy of the record while memories were fresh, and it created immediate accountability for action items — no one could later claim they "didn't know" they had been assigned a task, because they had confirmed the minutes in writing.

Download and Customize

This Meeting Minutes example is available as a free download. Use it as a reference to build your own meeting minutes, or start with the blank template and fill it in for your project.

• Download the Meeting Minutes Template — PMBOK 8 (blank, ready to use)
• Read the article: Meeting Minutes in PMBOK 8 — Guide and Best Practices

Meeting Minutes Example: Key Takeaways

The standout lesson from this Meeting Minutes example is that the format matters less than the discipline. Alex Morgan did not use an elaborate template — her minutes followed a simple structure (attendees, discussion, decisions, actions, next meeting) that took about 20 minutes to write and 5 minutes to review. What made them powerful was the consistency: every meeting produced minutes within 24 hours, every action item had a named owner and a due date, and every decision included the rationale. Over 13 weeks, this produced a comprehensive, searchable project record that Riley Park referenced twice during post-project audits — and that formed the foundation of the lessons learned document.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.