How do I turn messy meeting notes into decisions and action items?

Treat your notes as evidence of what was written, not permission to fill in gaps. Sort them into four buckets: discussion, decisions, actions, and open questions. Preserve uncertainty in the wording. For example, “Everyone liked blue version” may indicate a preference, but it does not necessarily mean the group formally chose it. “Sam to check wording?” is uncertain, so don’t list Sam as the confirmed owner.

A cleaned draft could start like this:

Discussion: The group discussed shortening the launch-page headline and reviewed a blue version.

Possible preference, not confirmed decision: The notes say everyone liked the blue version; confirm whether it was selected.

Open questions: Is a legal review required? Has the launch date changed? When is the next discussion?

That keeps useful context while showing what still needs confirmation.

Use the strongest wording your notes support. Put an item under Decisions only when the notes clearly show that the group settled it—for example, “Decision: use the blue version.” If the notes only say people liked it, write that as discussion or a preference to confirm. Avoid upgrading “consider,” “maybe,” or “seemed to agree” into “approved.”

If you’re unsure, label the item “Decision to confirm” and ask a neutral question in the follow-up: “Did we decide to use the blue version, or is that still under consideration?” This makes the uncertainty visible without assigning blame. A decision record should say what was decided and, when helpful, include its scope or a brief reason. It shouldn’t silently turn an idea into a commitment.

A useful action states a concrete next step, one accountable owner, and a due date. Based on your notes, you can capture the action without inventing the missing date:

Action: Ask the design team about the relevant dates. Owner: Priya (as recorded in the notes; confirm if needed). Due: Not recorded—confirm.

If the task itself is unclear, write the specific question to resolve it: “Which dates should Priya ask design to confirm?” If there are several contributors, still name one person to coordinate the next step and list others as contributors only if that role is clear. Don’t turn “Sam to check wording?” into an assigned action until someone confirms Sam owns it.

Copy this structure and leave unknowns visible instead of guessing:

Meeting: [name or topic] Date: [date, if known]

Decisions

• [Decision stated clearly in the notes]
• [If uncertain: Decision to confirm—question for attendees]

Discussion

• [Relevant context, options considered, or preferences—not presented as decisions]

Actions

• [Next step] | Owner: [name or “to confirm”] | Due: [date or “to confirm”]

Open questions

• [Question] | Who will confirm: [name or “to confirm”] | By: [date or “to confirm”]

Worked draft from your notes:

Decisions

• Decision to confirm: Did the group select the blue version, or only express a preference?

Discussion

• The group discussed shortening the launch-page headline.
• The notes say everyone liked the blue version.

Actions

• Ask design about relevant dates | Owner: Priya, per notes | Due: to confirm.
• Check whether a legal review is needed | Owner: to confirm | Due: to confirm.

Open questions

• Has the launch date changed? Who can confirm, and by when?
• Is the next discussion planned for next week? Confirm the date and attendees.
• Is Sam responsible for checking the wording, or was that only a suggestion?

Before sending, add a short note such as: “Please reply with corrections, especially for items marked to confirm.” That gives people a clear chance to resolve gaps.