Best Copilot Prompts for Meeting Notes

Business Updated September 25, 2026 by GenPrompto
Prompt
Based on this meeting, summarize the key points discussed and any decisions that were made. Grouping related points together, rather than listing them chronologically, produces a summary that reads as organized.

What this does

Summarizes meetings and extracts action items from Copilot's actual real meeting content -- transcripts and calendar context.

Copilot prompts for meeting notes work best when they draw on the actual meeting content Copilot has access to — a Teams transcript, calendar context, or your own notes — rather than a generic request with no meeting content behind it.

What this produces

A structured summary built from actual meeting content, an action items list with owners pulled from what was genuinely discussed, and a follow-up email draft grounded in the actual outcomes of the meeting.

Variations

Three ready-to-copy versions for meeting notes in Copilot.

Structured Summary Version
Based on this meeting, summarize the key points discussed and any decisions that were made. Group related points together rather than listing them in the order they came up, so the summary reads as organized rather than a chronological transcript.
Action Items Version
From this meeting, pull out action items — who owns each one and by when, if that was actually discussed. If ownership or a deadline wasn’t explicitly stated for something, flag that clearly rather than guessing or leaving it out entirely.
Follow-Up Email Version
Draft a follow-up email to the team based on this meeting’s actual outcomes, highlighting next steps clearly. Keep it concise enough that a busy recipient can scan it quickly and immediately see what they’re responsible for.

Who this is for

Microsoft 365 users working with Copilot’s meeting integration in Teams — for a platform-agnostic approach to live meeting note-taking, Prompt for Meeting Notes covers that broader case.

Example Output

Working from the actual meeting content produces a summary genuinely reflecting what was discussed, rather than a generic template with placeholder language. The action items version, pulling from what was genuinely said, produces a list with actual ownership attached where that was discussed, rather than vague tasks with no accountability.

Tips for better results

  • Make sure Copilot actually has access to the meeting content — transcript, notes, or context — before asking for a summary, since it can’t summarize what it can’t see.
  • Ask explicitly for action items with owners, since a general summary request may not surface this level of detail on its own.
  • Review any generated summary against your own memory of the meeting before sending it, especially for anything with real consequences.
  • For a follow-up email, ask for next steps to be highlighted clearly, not buried in a general recap.

What didn’t work as well

Asking for a meeting summary with no actual meeting content accessible produces something generic or simply unable to proceed, since there’s nothing real to summarize. Actual access to meeting content is what makes this integration genuinely useful over a manual summary written from memory.

FAQ

Does Copilot need a transcript to summarize a meeting?

This depends on your current Teams and Copilot setup — check current documentation for what’s required in your specific environment.

How accurate are action items pulled automatically?

Review them against your own memory of the meeting, since automated extraction can occasionally miss nuance or misattribute an action.

Can this work for meetings I wasn’t able to attend?

If a transcript or recording is available and accessible, yes — this is one of the more genuinely useful applications of this kind of integration.

Should I edit the generated follow-up email before sending?

Yes — review and personalize it the same as you would any AI-assisted communication before sending it to your team.

Related