Meeting Summary Prompts for Decisions and Actions

This reviewed prompt collection is for managers, project teams, assistants, and consultants. Remove confidential information before using an external AI and verify the output with participants.

When to use these prompts#

Use this page when you need prompts that transform user-supplied notes or transcripts into decisions, actions, owners, due dates, open questions, and confidence-marked ambiguities. Replace every bracketed variable with verified, non-sensitive information before using a template in your own AI product.

Inputs to prepare#

• authorized notes or transcript
• meeting purpose, date, and participant roles
• known decisions and items still under discussion
• action owners and deadlines stated in the source
• desired summary audience and level of detail
• required output format or template
• terms, project names, and acronyms
• privacy, retention, and distribution restrictions

Draft prompt templates#

1. Structured meeting summary#

Purpose: Separate confirmed decisions from discussion and uncertainty.

Summarize [MEETING NOTES] for [AUDIENCE]. Use only statements present in the notes. Output: purpose, key discussion, confirmed decisions, action items with owner and due date, open questions, risks, and parking-lot items. If an owner, date, or decision is ambiguous, write “not confirmed” and quote the relevant note rather than inferring.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

2. Decision and action register#

Purpose: Extract accountable items in a reviewable table.

From [NOTES OR TRANSCRIPT], create two tables. Table 1: decision, status, decision maker as stated, evidence excerpt, and follow-up. Table 2: action, owner as stated, due date as stated, dependency, and confidence. Do not convert suggestions into decisions or assign an owner who was not named.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

3. Follow-up email from approved summary#

Purpose: Prepare a concise participant message after facts are checked.

Using this approved meeting summary [SUMMARY], draft a follow-up email to [PARTICIPANTS]. Include confirmed decisions, action items, due dates, open questions, and the next checkpoint. Do not add interpretation or commitments. End with a request for corrections by [DATE].

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

Why the structure matters#

Meeting notes often contain proposals, interruptions, and incomplete statements. These prompts separate decisions from discussion, preserve ambiguity, and prevent the model from assigning responsibility merely because a name appeared nearby.

Weak prompt and what it misses#

Summarize the meeting and assign action items to the right people.

The prompt encourages the model to infer who is “right” rather than use explicit assignments. It lacks privacy rules, output structure, and a way to distinguish decisions from suggestions.

Human review checklist#

• Confirm authorization before uploading notes or transcripts.
• Verify decisions, owners, and deadlines with the source and participants.
• Remove personal, legal, HR, or security-sensitive details not needed in the summary.
• Check that proposals were not converted into commitments.
• Distribute the summary only to the intended audience.

Testing and maintenance#

1. Use original, non-sensitive sample values when testing a prompt.
2. Retest examples after material changes to the prompt, page, or AI product.
3. Check factual preservation, requested format, missing-data behavior, and task-specific risks.
4. Update the visible test date when a material retest is completed.
5. Keep the site operator responsible for the final human review.

A dated operator attestation is sufficient for the site's internal publication check; full chat transcripts are not retained or published.