Meeting Log
A single-meeting record covering date, type and purpose, attendees, key points, outcomes and follow-up actions.
About Meeting Log
A meeting log is a single-page record of one meeting: when it took place, what type of meeting it was, why it was held, who attended, what was discussed, what was decided and what happens next.
A consistent format means the important information is captured every time and can be found again later. It turns the discussion into a record that people who were not there can understand and that attendees can be held to.
At a glance
- Category
- Delivery
How it is structured
The log has three parts. The header records the date, meeting type and purpose. Alongside it is the list of attendees. The body separates content into distinct sections: key points discussed, outcomes and decisions, and follow-up actions.
Keeping outcomes and follow-ups apart from the general discussion makes the log scannable. A reader looking for what was decided or what they need to do does not have to read the whole discussion.
Use cases
Project and team meetings
Keep a consistent record of regular meetings so decisions and actions are not lost between sessions.
Client and stakeholder meetings
Share an agreed summary afterwards to confirm what was decided and who owns what.
Governance and compliance
Maintain a dated, attributable record of decisions where an audit trail is needed.
How to use it
Tips and common mistakes
- Circulate the log within a day while people still remember the meeting.
- Every action should have one named owner and a date. Actions assigned to a group tend not to happen.
- Write decisions as complete statements so they make sense without the surrounding notes.
Build better plans, faster
Join the waitlist for early access to curated insights, flexible templates, and rapid iteration across strategy, planning, and project management.