Review edition · Complete text lesson. Platform screenshots are being prepared.
Suppose you could…
Turn a meeting into decisions and next steps
Distinguish agreed decisions, confirmed actions and suggestions; preserve missing owners and dates rather than inventing them.
Time is a practice estimate. Pause or return whenever you need.A useful little possibility.
A polished recap can accidentally turn “someone should” into a commitment. You’ll make a concise follow-up from a fictional meeting. Your result: a decision log, an action list and a draft message that people can verify before you send it.
Let’s make a start.
Minute 0–2: underline the explicit approval and the one confirmed delivery commitment in the sample.
Minute 2–5: submit the prompt and sample in a new conversation. Read the action list against the actual words spoken.
Minute 5–8: find any invented owner, calendar date or agreement. Ask for one precise correction, then edit the follow-up yourself.
Minute 8–10: save the reviewed log and draft message. This lab does not send anything or create calendar events.
Your sample material
Fictional training material. No real customer information needed.
FICTIONAL MEETING NOTES — WELCOME-SHEET TRIAL M1. Manager: “Let’s approve a two-week front-desk trial, with printing up to 60 euros.” M2. Jo: “I will prepare a first draft by Thursday.” M3. Manager: “We have not agreed the start date yet.” M4. Sam: “A QR code might be useful.” M5. Jo: “I can ask about a QR code, but I am not committing to adding it.” M6. Manager: “Someone needs to collect feedback. We’ll decide who at our next check-in.” M7. No date for that check-in appears in these notes.Download sample .txt ↓
Create a meeting follow-up from the notes below. Separate: 1) confirmed decisions, 2) confirmed actions with owner, stated due date and source ID, 3) suggestions not agreed, 4) unresolved questions. Use “not agreed” where an owner or date is missing. Preserve relative dates exactly; do not convert “Thursday” without knowing the meeting date. Do not treat “might,” “can” or “someone should” as commitments. End with a draft message under 100 words asking participants to confirm or correct the summary. Do not send it. NOTES: [Paste the sample input here.]
Keep personal and confidential information out of external AI tools. Start with the sample material.
Turn a first try into your thing.
Challenge any line that assigns feedback collection to Sam or promises a QR code. Neither is supported.
Ask: “Show the source phrase that supports each confirmed action; move anything unsupported to open questions.” Then remove internal note IDs from the outward-facing message if they would confuse recipients, while keeping them in your review copy.
Pause for the “aha.”
A meeting recap is an account of decisions, not an opportunity to make new ones. Words of possibility and words of commitment must stay distinct.
Dates also require context. A model can produce a plausible date for Thursday without knowing which week the meeting happened. Missing information should remain missing until someone confirms it.
Useful beats convincing.
Check these against your actual output. Your answers stay on this device; this is self-review, not automated grading.
Finished your first try? Reveal a worked example ↓
Decision: Approve a two-week front-desk trial with a printing limit of 60 euros (M1).
Confirmed action: Jo — prepare first draft — due Thursday, calendar date unconfirmed (M2).
Suggestion: Consider a QR code; including one is not agreed (M4–M5).
Open questions: Trial start date; feedback collector; next check-in date (M3, M6–M7).
Draft message: “Thanks, everyone. We agreed to a two-week front-desk trial with printing up to 60 euros. Jo will prepare a first draft by Thursday; please confirm the calendar date. The start date, feedback owner and next check-in date are still open. A QR code was suggested but not agreed. Please correct anything I’ve missed or misrepresented.”
Why it works: it makes the unknowns actionable without assigning them to people who did not agree.
A new case. Your own approach.
Apply the review principles to these new facts, not the previous sample’s specific numbers or answers.
WITHOUT THE STARTER PROMPT: Summarise this new exchange: “Pat: I could review it. Morgan: I’ll email the outline tomorrow. Team: Let’s postpone launch until we know the venue.” What is actually committed? Preserve “tomorrow” unless a meeting date is provided. Write one clarification question for Pat.
One possibility leads to another.
Use the method after a personal planning conversation or volunteer meeting. Compare the recap with the other person’s recollection before treating it as a shared plan.
Your reusable workflow card ↓
WORKFLOW: DECISIONS, ACTIONS, UNKNOWNS Inputs: permitted meeting notes, date/context if known, intended recipients. Extract: decisions / confirmed actions / unagreed suggestions / open questions. For every action: owner, stated due date, supporting phrase. Review: test commitment wording; never infer consent, owners or calendar dates. Output: reviewable log plus a short draft follow-up inviting corrections. Human step: confirm sensitive details before sending. My team’s preferred format: __________Download workflow .txt ↓
You tried something. That counts.
Keep a note of what you made or what surprised you. It stays in this browser.