Turn Messy Meeting Notes Into a Report and Slides

Turn fictional meeting notes into a checked report and five clear slides. Illustrated teaching example. These visuals are not a recording of the Claude interface. COPY THE PROMPTS: Sort the notes Read the labelled meeting notes below. Separate observations, agreed decisions, explicit commitments, suggestions and unresolved questions. Keep the source note IDs beside each item. Preserve tentative language. Do not invent facts, owners, deadlines or approvals. If a field is absent, write "not agreed" or "not recorded", as appropriate. Extract commitments Using only the meeting notes, create an action list with task, explicitly agreed owner, deadline, scope of commitment and source note ID. Put suggestions without an agreed owner or deadline in a separate open-questions section. Do not turn a review deadline into a completion promise. Do not assign an action to the person who merely suggested it. Write the report Using the checked evidence list and labelled source notes, draft a one-page status report for leadership. Include current position, observed results, agreed actions and unresolved decisions. Keep 5 October tentative, EUR 600 unapproved, and the pilot at 12 people. Keep source note IDs beside factual claims. Do not invent time savings, overall success rates or approval. Use concise English. Build five slides Create exactly five slides from the checked report: current position, observed results, agreed actions, unresolved decisions, and next review. Give each slide one main point. Keep numbers and qualifications consistent with the report. Keep the pilot at 12 people, 5 October tentative and EUR 600 unapproved. Put supporting note IDs in the speaker notes. Use readable text, and do not invent charts or performance claims. Audit both outputs Compare the report and five-slide deck with the original labelled meeting notes. For each factual claim, show its source note ID and any mismatch. Check numbers, owners, dates, approvals and tentative wording. Flag omissions and contradictions. Do not treat the report as independent evidence for the slides. Return corrections separately so I can review them before applying. SOURCE NOTES N01 09:00 Maya: onboarding portal pilot, 12 colleagues, keep scope small. N02 Leo: 9 of the 12 completed the first task in this test. The other 3 could not start because their accounts lacked permission. No time-saved measurement. N03 Nina: I will review the permissions for those three accounts by 22 September 2026. That is a review deadline, not a promise that every issue will be fixed then. N04 Leo: I will send a revised quick-start guide by 23 September 2026. N05 Raj: Could we add an afternoon training session? No decision, owner or date agreed. N06 Maya: Keep this pilot at 12 people. Do not add more users until we have reviewed the remaining access issues. N07 Raj: The supplier quoted EUR 600 for optional training. Estimate only. No spending approval given. N08 Someone mentioned 5 October 2026 as a possible wider launch date. Maya: tentative only, no launch approved. N09 Maya: I will check the pilot results at our next review on 24 September 2026. N10 No customer rollout or response-time improvement was measured in this meeting. N11 Maya: Leadership needs a one-page status report and five slides. Keep the open questions visible. N12 End of notes. No other owners, deadlines, budget approvals or decisions recorded. Claude Docs and Slides announcement (16 September 2026; availability varies): https://claude.com/blog/cowork-is-now... All people, company details and meeting records in this lesson are fictional. Check important claims against the original notes. Use only information you are allowed to share. Everyday AI Playbook — practical AI for work. #AIAtWork #ClaudeAI #Productivity CHAPTERS 00:00 One meeting. Two useful outputs. 00:24 The new document workflow 00:51 The raw notes 01:21 Step 1: preserve the evidence 01:49 A question stays a question 02:15 Step 2: extract the actual commitments 02:44 Step 3: write for the decision maker 03:13 A report that keeps uncertainty visible 03:44 Two details that must survive 04:12 Step 4: build exactly five slides 04:42 A slide needs an accurate headline 05:10 Step 5: catch a planted error 05:41 The final checks 06:10 Try it on one meeting