Turn Meeting Notes into Action Items

Meeting notes often mix an idea, an assignment and a confirmed decision in the same sentence. An assistant can organize them, but a tidy table is not proof that the team agreed to it. Ask it to retain the distinction between what was said, what was decided and what still needs confirmation.

Prepare the information that matters

Use notes you are permitted to share. Add the meeting date and label speakers when you know them. If the notes say “next Friday,” provide the intended calendar date yourself or ask the assistant to flag it rather than calculate from an unknown context.

Use a service your organization permits for this material. A pasted excerpt is the assistant's source for this workflow; the prompt does not give it access to files, mail or meetings you have not supplied.

Copy the ready-to-use prompt

Turn the meeting notes below into a useful recap. Separate confirmed decisions, action items, open questions and proposals awaiting approval.
For every action, show the task, stated owner, stated due date and a short supporting excerpt. Write “Not assigned” or “Not agreed” when the notes do not specify an owner or date. Keep tentative suggestions tentative.
Do not invent assignments, approvals or dates. If a relative date cannot be resolved from the supplied meeting context, leave it as written and flag it for confirmation.

MEETING NOTES
[Paste the meeting date and notes here]

Work through a concrete example

CONFIRMED DECISION
Use the short application form.

ACTIONS
Draft the form | Maya | October 23 | “Maya will draft the form by October 23.”
Ask IT about access | Luis | Not agreed | “Luis will ask IT about access.”

AWAITING APPROVAL
Friday launch date.

OPEN QUESTION
When should Luis report back?

Why these choices matter

The launch remains a proposal and Luis does not acquire a fictional deadline. Each action has an evidence trail. A human reviewer still needs to confirm that the notes accurately represent the meeting; the assistant only sees the supplied record.

Review and improve the first answer

Check the recap against the original notes. Identify any invented owner, date or decision. Separate tasks that contain more than one action and show which person must confirm each unresolved point. Do not fill gaps by guessing.

Ask for a specific correction when the response misses the goal. Changing the requested format can improve readability; it cannot make an unsupported fact true. Return to your source when the answer changes a number, date, responsibility or condition.

Check the result before using it

1. Check every decision against an explicit decision in the notes.
2. Confirm names, owners and dates with attendees.
3. Keep missing deadlines visible instead of giving every task an artificial date.
4. Send the recap for review before treating it as the official record.

Fix the common failure patterns

Ask the attendees to correct the recap before it becomes the task record. Once confirmed, carry the actions into the team’s actual tracking system with the agreed owners and dates.

Find another task in the AI at Work prompt library, or continue with the related DeskPlain guides below.

Original DeskPlain prompts and fictional worked examples, prepared with AI assistance. Examples illustrate the intended reasoning; they are not captured model responses or a claim of testing across AI products. Read the editorial policy.