AI Meeting Notes Assistant: decisions, owners, deadlines
A three-step method that turns messy meeting scribbles into a one-page recap people actually act on — with three prompts to copy.
Most meeting notes fail the same way: they transcribe discussion instead of capturing commitments. The fix is a habit, not software. During the meeting, you only write three things — decisions, owners, deadlines. Everything else is background.
The three-step note method
- During the meeting: make three columns in your note — Decisions / Action items / Open questions. Every time someone says "ok we'll do it", capture who owns it and by when.
- Within 10 minutes after: tidy the notes. Trim the chatter, keep the commitments. This window is when memory is still accurate.
- Within 24 hours: send the recap to everyone in the room with "reply with corrections". Silence = agreement, and the written record becomes your team's shared truth.
Three prompts to copy-paste
- Clean up rough notes.
These are my raw meeting notes. Produce: Decisions (max 5), Action items (each with an owner and a deadline), Open questions. Keep it under 250 words. Notes: [paste]. - Extract only action items.
From these meeting notes, list every action item as one row each: task — owner — due date. If owner or date is missing, write "unassigned" or "not set" instead of guessing. Notes: [paste]. - Draft the recap email.
Write a 120-word meeting recap email for the team. Structure: 1 line summary, then Decisions, then Action items with owners and dates. Tone: plain, no corporate fluff. Facts: [paste cleaned notes].
What makes this beat a recording: you control what enters the notes. In a one-hour meeting, twenty things were discussed, maybe five mattered. If you only ever write decisions, owners and deadlines, your recap stays one page — even after AI cleans it. If you record first and summarize later, the AI will faithfully summarize noise.
Keep a standing folder: one note per meeting, named by date and meeting title. After three months you have a searchable record of who committed to what — which becomes your best evidence in debates about what "we agreed."
Start using this on your worst meeting of the week. You do not need every meeting to be brilliant — you need one clean recap that proves you listened.
How it works
- Open three columns (Decisions / Action items / Open questions) before your next meeting starts.
- Tidy the notes within 10 minutes, then run prompt #1 or #2 to clean them.
- Use prompt #3 to draft the recap email and send it within 24 hours asking for corrections.
Only with explicit consent — many regions require it, and secretly recording your boss or colleagues can backfire professionally. For most meetings, structured live notes plus the AI prompts below work just as well without the legal risk.
One page, max. Decisions (up to 5), action items with owners and dates, and 2-3 open questions. If your notes run longer than a page, you are transcribing — summarize instead.
Send the notes within 24 hours and ask for corrections by reply. The person who stays silent agrees by default, and your written record becomes the shared truth.
Only if your company policy allows it and participants know. Safer default: take rough manual notes, then feed them to AI after the meeting. Humans still control quality; AI just cleans up.
Strip customer names, salaries, and confidential numbers first. A good habit: ask the AI to work from anonymized notes. If the meeting is about layoffs, mergers or unreleased products, keep it fully offline.
Who this tool is for
This is for the person who ends up with the laptop open: project coordinators, assistants, product managers, team leads and outside consultants. It pays off most in cross-team meetings where the people affected were not in the room.
Formal governance is a different job. Board minutes, disciplinary hearings and regulatory meetings usually have a required format and retention rule, so do not replace them with this page. Recordings need consent, and consent rules vary by country and company.
How to read your result
The result is one page: decisions, action items and open questions. Read it against five tests.
- Decision test. Each line says what was decided, not what was discussed. A line starting with discussed is not a decision.
- Owner test. A named person, not the team. Unassigned is allowed and useful, because it shows the gap.
- Date test. A real date, not next week. If nobody knows, write not set so it gets chased.
- Count test. More than five decisions usually means the meeting did not decide. Move the rest to open questions.
- Open-question test. Something nobody in the room could settle, with the person who must answer it where possible.
- Recap test. Around 120 words: one-line summary, decisions, actions. Ask for corrections by a stated time, and say that silence counts as agreement only if you say so.
- Filing test. Name the file with the date and meeting title, and keep it in the team folder, not your desktop.
A worked example
On 22 October, four people spent 45 minutes on an onboarding redesign: Rafael from support, Lin from design, Tom from operations and Aisha as project manager.
Rough notes: welcome email too long; Lin suggests video; checklist duplicated in Notion and a spreadsheet; support gets the same questions; pilot three weeks; who owns FAQ; legal review maybe; next meeting Tuesday.
Decisions: replace the twelve-step welcome email with a four-email sequence, with the first email on day one; pilot with the next two cohorts for three weeks before changing the help centre; keep the checklist in Notion as the single source and remove the duplicate spreadsheet.
Action items: draft four emails — Lin — 28 October; remove the duplicate spreadsheet and redirect links — Tom — 26 October; confirm whether legal must review the data-retention paragraph — Aisha — 29 October; book the pilot review — Aisha — 12 November; collect the top five support questions — Rafael — 27 October.
Open questions: does the sequence need a video, which Lin will test with two users; which cohorts count as the pilot, which Aisha will confirm after the headcount update.
The recap email carries one summary line, the three decisions and the actions with owners and dates, then asks for corrections by noon on 23 October. The page stays one screen because the noise was never written down. If you use a prompt to tidy the notes, do not let it invent an owner or a date; keep unassigned and not set visible so someone has to resolve them.
Common mistakes
- A transcript in disguise. Two pages of who said what, with no commitments.
- Team or relevant colleagues as the owner. Nobody can be chased.
- Deadlines such as ASAP. Nobody can schedule them.
- One decision mixed with four ideas. Separate them or the action list becomes guesswork.
- Sending three days later, after the correction window has closed.
- Recording without telling people, or pasting customer names, salaries and unreleased plans into a chat AI. Anonymise or keep it offline.
- Keeping the only copy in a personal folder. The record disappears when you change roles.
- Putting your own opinion in the decision line. It belongs under open questions.