A simple meeting notes workflow using AI responsibly. Capture, summarize, action items, and follow-ups with guardrails and templates.
Last updated: February 27, 2026
Summary
This workflow turns messy meeting notes into clean outcomes: decisions, action items, owners, and deadlines.
It is designed to be fast and consistent, not perfect. The goal is to leave every meeting with a shared truth.
Use it with the Job Search AI Workflow for interview prep and the Founder Ops AI Workflow for recurring ops meetings.
You can run it manually or paste it into any AI tool that can rewrite and format text.
Who it is for
Operators who run recurring meetings and hate chaos.
Engineers and founders who need decisions documented fast.
Small businesses doing client calls, sales calls, and internal planning.
Anyone who leaves meetings with “wait, what did we decide?”
What you get
A consistent notes format that makes follow-up automatic.
A decision log you can search later.
An action list with owners and deadlines.
A short recap you can post to Slack or email.
Guardrails to keep sensitive data out of your prompts.
Steps
Start with the right raw input. Use one of these:
Bullet notes you typed during the meeting
Transcript excerpt (trim it first)
Agenda plus rough notes
Do not paste sensitive data. Replace names with roles if needed.
Normalize the notes in 60 seconds. Before using AI, quickly clean:
Remove repeated lines and filler
Replace names with roles (PM, Eng, Client)
Mark unclear spots with [UNCLEAR]
The cleaner the input, the better the output.
Extract decisions first. Ask the AI to list decisions made, including what was decided and why.
If no decision was made, it should explicitly say “No decisions recorded.”
Extract action items with owners and dates. Every action item must have:
Action (imperative verb)
Owner
Deadline (or “TBD”)
If the owner is not clear, it should flag it.
Capture risks and open questions. Create two lists:
Risks: what could block progress
Open questions: what needs an answer
This prevents “we forgot the hard part” later.
Publish the recap and confirm. Post the recap to your team channel or email with:
Decisions
Actions
Open questions
Ask for corrections within 24 hours. That is how you build a reliable decision log.
Templates
Copy, paste, and run this after any meeting.
Template 1: Meeting recap prompt
Turns raw notes into a clean recap.
Task: Convert these raw meeting notes into a clean recap.
Rules:
- Do not invent facts. If something is unclear, mark it [UNCLEAR].
- Keep it short and scannable.
- Use this exact output format.
Output format:
Title:
Date:
Attendees (roles only):
Context (2 bullets max):
Decisions:
- Decision | reason
Action items:
- Action | owner | deadline
Risks:
- risk
Open questions:
- question
Notes:
[Paste raw notes here]
Template 2: Action list only
Use when you only want tasks.
Extract action items from these notes.
Rules:
- One action per line.
- Must include owner and deadline. If missing, write "owner: TBD" or "deadline: TBD".
- Use the format: action | owner | deadline
Notes:
[Paste raw notes here]
Template 3: Decision log entry
Use for high-stakes meetings.
Create a decision log entry from these notes.
Rules:
- Only include decisions actually made.
- If there are none, say "No decisions recorded."
- Keep each decision to 2 lines max.
Output format:
Decision:
Why:
Alternatives considered:
Owner:
Date:
Follow-ups:
Notes:
[Paste raw notes here]
Common mistakes
Copying the whole transcript. Trim it first or you get noise.
No owners. Tasks without owners are fantasies.
No deadlines. “Soon” is not a plan.
Letting AI guess. If it is unclear, it should say so.
Not confirming the recap. The decision log only works if people correct it.