Turn Meeting Notes into Action Items Without Inventing Owners

Extract commitments, not guesses. Preserve the exact source line for each action, separate decisions from suggestions, and use unknown for an owner or deadline that the notes do not establish.

Published by HiddenPrompts · Updated

4 min read

Start with a deliberately incomplete meeting

Imagine a small team preparing a product demonstration. These are invented training notes, not a customer transcript. Line N1 says, “Maya will send the revised demo script by Friday.” N2 says, “We should improve the signup page.” N3 says, “Noah will investigate the coupon error; deadline not agreed.” N4 says, “The release date remains undecided.” A useful summary must preserve the distinction between a commitment, a suggestion and an unresolved decision. Asking for a polished action plan without defining that distinction invites plausible but unsupported assignments.

Define what counts as an action

For this exercise, an action is an explicit commitment to do work, even if the deadline is missing. A suggestion without an agreed owner belongs in an open-question list. A decision describes an agreed state and does not automatically become a task. That means N1 and N3 become action items, N2 becomes a question, and N4 remains an unresolved decision. This classification rule is more important than requesting a “senior project manager” persona. It gives a reviewer an observable standard instead of a tone preference.

Make the input and output inspectable

Number the notes before inserting them into the prompt. Require four columns: source ID, action, owner and deadline. Permit the literal value unknown. Ask for a second section containing open questions, with each question linked to a note. Do not quietly convert Friday to a calendar date unless the meeting date and timezone are supplied. A relative deadline can be preserved verbatim while a scheduling system waits for clarification. This avoids introducing certainty merely to satisfy a rigid table shape.

Review against the authored reference

The worked example below is a reference answer created for this exercise, not output from a live model run. Compare your own result row by row. The action list should contain two items. Maya owns the demo-script action and Friday is its stated deadline. Noah owns the coupon investigation and the deadline is unknown. A signup-page task assigned to a designer is a failure, even if that task would be sensible. A guessed release date is also a failure. Rewriting a sentence for clarity is acceptable if its commitment and uncertainty remain unchanged.

Test the difficult cases

Run a second exercise with N1 changed to “Maya might send the script.” Under our rule this is no longer an explicit commitment. Then add two notes giving different deadlines for the same task. The answer should flag a conflict rather than choose whichever date appears last. Finally, supply notes containing no actions at all. An empty action list with an explanation is better than an invented plan. Record each input, prompt version, model identifier and observed failure before revising the template. Change one requirement at a time so you can tell which change helped.

Move from a summary to a workflow safely

Treat extraction as a draft, not permission to create tickets or email owners. Have a person confirm unresolved assignments and normalize dates before transferring them to a work tracker. If you automate the transfer, validate the required columns and preserve the note IDs in the created records. The checkpoint is not optional just because the prose looks professional. Measure unsupported assignments and missed explicit commitments separately; an output can be complete but inaccurate, or accurate but incomplete. Remove personal or confidential meeting details before using a public demonstration.

Worked example

Authored teaching example, not a recorded model response.

PROMPT
Extract explicit commitments from notes N1–N4 above. Return source | action | owner | deadline. Use unknown for missing facts. List suggestions separately.

AUTHORED REFERENCE ANSWER
N1 | Send revised demo script | Maya | Friday (calendar date unknown)
N3 | Investigate coupon error | Noah | unknown
Open questions: N2 — Is a signup-page change approved, and who owns it? N4 — When will the release date be decided?

How to check the result

Reject invented owners or dates. Count missed explicit commitments separately. Keep suggestions out of the action list unless your own agreed policy explicitly includes them.

Sources and further reading

Related prompts

Learn the method

Testing Method · Contact

Prompt Structure Checker