Meeting Notes for Project Managers

The project manager's information problem

You are in many meetings, and every one produces requirements, dependencies, risks, decisions and deadlines. Minutes take time. Action items from last week's meeting are forgotten until someone asks about them. Reports are written from partial memory.

Workflows

1. Requirements. Capture client requirements and open questions, and turn them into a requirements document. See the project requirements template.
2. Dependencies and risks. The notes include a section for risks and dependencies, so "we cannot start until the API is ready" is not lost.
3. Decisions. Keep confirmed decisions separate from proposals, with a link to the moment of the decision.
4. Deadlines and actions. Review the action items from each meeting and confirm the ones that become tasks with reminders. See meeting action items.
5. Progress reporting. Draft a progress report with completed, in-progress and upcoming work, risks and budget status, and export it as a branded PDF. See meeting notes to PDF.

Fit and limits

MeetMemo is not a project-management suite. It has no Gantt charts, resource planning, ticketing or team task assignment. It records the conversations those tools depend on and your own follow-ups. Minutes are drafts to be reviewed by attendees, and AI can miss an implicit decision, so check anything critical. See pricing.

Read: how to track meeting action items and the meeting minutes template.