Meeting notes that lead to action

Start with the purpose of the meeting and the decision it needs to reach. This gives a reader who could not attend enough context to understand the notes. Record the date and participants only when they are needed by your team. A short topic heading is more useful than a long chronological transcript. Separate decisions from discussion. A decision should say what was agreed and why it matters. An action should identify one owner and a due date. If no owner was agreed, mark it unassigned rather than guessing. Put unresolved questions in their own section so they are not mistaken for approved work. Before sharing, read the notes from the perspective of someone outside the conversation. Replace vague phrases such as handle the issue with a concrete next step. Check that dates include the year and, where relevant, the time zone. Remove customer details, credentials and personal information that the recipients do not need. Use a new copy for each meeting. Keep the shared version stable so people can refer to the same decisions later. Pastzo links are unlisted, not secret: anyone with an unprotected link can read it. Choose an expiration that matches the useful lifetime of the notes, and use a password when the subject requires an additional access check.

Meeting: [topic]
Date: [date]
Purpose: [decision or outcome]

Decisions
- [decision and reason]

Actions
- [action] | Owner: [name] | Due: [date]

Open questions
- [question] | Follow-up: [owner]

Next check-in: [date]