Prompting Guide
How to Prompt Copilot to Summarize Meeting Notes
The notes are messy on purpose. The summary doesn't have to be.
Microsoft 365 Copilot is good at turning a scrawl of half-finished sentences, timestamps, and names into a readable account of what a meeting actually decided. It is not good at reading your mind about which of the many things said in that meeting actually mattered, which is why "summarize these notes" so often comes back either too long to be useful or too short to be trusted. The fix is the same four-part prompt structure that works for almost any writing task: say what the meeting was, what kind of summary you need, what shape it should take, and what you'll double check before you send it on.
Microsoft 365 Copilot summarizes meeting notes better when the prompt gives it context (what the meeting was and who the summary is for), the task (a summary with action items, not a transcript cleanup), the format (decisions, action items with owners, and open questions, as separate sections), and a checking instruction (flag anything unclear about who owns what). If the meeting happened in Teams with live transcription on, you can also pull a recap from the meeting chat or the Recap tab and feed that into the prompt instead of typing notes from scratch.
Published
Try it with your own meeting notesPaste your notes in and get decisions, action items, and open questions sorted out, free, no account needed.Try it freeKey Takeaways
- Separate what was decided from what was merely discussed. Meeting notes often blur the two, and a summary that keeps them blurred can turn a suggestion into something people think was agreed.
- Ask for action items with an owner and, if one exists, a deadline. An action item with no name attached rarely gets done, and a summary that lists one anyway just hides the gap.
- If the meeting was in Teams, check the Recap tab and the meeting chat first; Copilot's own summary there can be a faster starting point than writing notes from scratch.
- Tell Copilot who the summary is for. A summary for the people who were in the room can skip context a summary for someone who missed it cannot.
- Ask it to flag anything ambiguous about ownership or decisions, then check those flags against your own memory of the meeting before sending the summary on.
Copy and Paste
Prompts You Can Use Today
A full meeting summary with action items
Summarize these meeting notes for the people who attended, plus one teammate who missed it: [paste your raw notes here]. Split the summary into three sections: Decisions Made, Action Items (with an owner's name and a deadline if one was mentioned), and Unresolved Questions that weren't resolved. If an action item has no clear owner in my notes, say so instead of guessing who it was.
Replace the bracketed notes with your actual notes, including abbreviations, half sentences, and names as you wrote them.
Separating decisions from discussion
Read these meeting notes and tell me, as two separate lists, what was actually decided versus what was just discussed or floated as an idea without a clear agreement: [paste your notes]. Be strict about the difference. If the notes are ambiguous about whether something was decided, put it in a third list called Unclear.
Use this when a meeting covered a lot of ground and you're not sure which parts actually landed as decisions.
Starting from a Teams meeting recap instead of raw notes
Here's the recap Copilot generated for this Teams meeting: [paste the recap from the meeting chat or Recap tab]. Turn it into a short summary with three sections: Decisions Made, Action Items with an owner for each, and Unresolved Questions. If the recap itself doesn't name an owner for an action item, flag that instead of guessing.
Use this when the meeting had live transcription on; the recap already captures who spoke and what was said, so you're reshaping it rather than starting from scratch.
Checking a summary against the original notes
Compare this meeting summary against my original raw notes and tell me if anything in the summary states something as decided that my notes only show as discussed, or assigns an action item to someone my notes don't actually name: [paste the summary], [paste your original notes].
Run this on Copilot's own summary, or on one a teammate wrote, before it's sent around as the official record.
Turning notes into a message to send in the team chat
Turn this meeting summary into a short message I can post in our team chat, written in a casual but clear tone, with the action items as a simple list people can scan quickly: [paste your summary or raw notes]. Tag each action item with who owns it, using the format "Name: task".
Useful when the summary itself is solid but needs reformatting for a chat channel instead of an email or document.
The Structure
The four parts of a prompt that produces a usable summary
The same pattern that works for any writing task applies to meeting notes: context, task, format, and a check before you trust it.
Context: what the meeting was and who's reading
Say what kind of meeting this was and who the summary is going to: the people who were in the room, or someone who missed it and needs the background too. The right level of detail depends entirely on who's reading.
Task: a summary with action items, specifically
"Clean up these notes" and "summarize this meeting with action items" point Copilot at different jobs. Say what you actually want out the other end: decisions, action items, open questions, or all three.
Format: sections and how action items should look
Ask for action items with an owner's name and a deadline where one exists. Without that instruction, Copilot may list a task without saying who's responsible for it, which quietly reproduces the same ambiguity the meeting may have left behind.
Checking: decided versus discussed
Tell Copilot to flag anything ambiguous about whether something was actually agreed or just floated as an idea. This single instruction catches the most common and most damaging kind of meeting-summary mistake.
Before And After
What changes when you ask for decisions and action items specifically
The prompt most people start with is "summarize these meeting notes," with the raw notes pasted below. Copilot will produce something, usually a reasonably faithful paraphrase of the notes in order, but it won't necessarily separate what the room agreed to from what someone merely suggested, and it won't necessarily notice that an action item has no owner attached.
The same request, rewritten: "Summarize these meeting notes for the people who attended, plus one teammate who missed it. Split the summary into three sections: Decisions Made, Action Items (with an owner's name and a deadline if one was mentioned), and Unresolved Questions that weren't resolved. If an action item has no clear owner, say so instead of guessing." The notes are identical. The output is now something a team can actually act on, because the prompt told Copilot exactly what distinctions to preserve instead of letting it flatten everything into one undifferentiated paragraph.
The instruction to flag a missing owner rather than guess one is doing a lot of the work here. Meeting notes frequently record that something needs to happen without recording who's doing it, usually because it felt obvious in the room. It stops being obvious the moment the summary gets forwarded to someone who wasn't there, and a prompt that surfaces the gap is more useful than one that quietly papers over it.
Common Mistakes
What turns a summary into a source of confusion
These are the gaps that make a meeting summary create more disagreement than the meeting itself.
Letting "discussed" become "decided"
A summary written without that distinction in mind tends to state everything with the same confident tone, including ideas that were only floated. Readers who weren't in the room have no way to tell the difference unless the summary makes it explicit.
Action items with no owner
If the notes don't name who's responsible for a task, a summary that lists the task anyway without flagging the gap just moves the ambiguity downstream, where it's harder to notice and more disruptive to catch late.
Writing for the room instead of the reader
A summary meant for someone who missed the meeting needs context the people who were there don't. Not saying who it's for leaves Copilot guessing at a reading level, and it will often guess for the people already in the room.
Sending the summary as the only record
A summary condenses by design, which means something gets cut. If a decision carried real weight, like a budget or a deadline change, it's worth confirming the summary captured it correctly rather than treating the AI-written version as the definitive record.
Sourced From Microsoft
Starting from a Teams meeting recap instead of raw notes
If the meeting happened in Teams, you may not need to write notes from scratch at all. Copilot in Teams meetings summarizes key discussion points, including who spoke and what they said, and it also suggests action items and answers questions in real time, during or after the meeting. After the meeting ends, you can access Copilot from the meeting chat and from the Recap tab, which is where that summary and those suggested action items live.
There's one condition worth knowing before you count on this: to see Copilot's conversation history after the meeting ends, live transcription has to have been turned on during the meeting. If it wasn't, there's no recap waiting for you afterward, and raw notes taken during the meeting become the only material you have to work with.
It's also worth knowing that Copilot won't work in meetings that are hosted outside your own organization, so a recap won't be available for a meeting someone else's company set up and invited you to, even if live transcription looked like it was running. In that case, your own notes taken during the call are what you'll be summarizing from.
Before You Send It
What to check before a meeting summary goes out
Read the Decisions Made section against your own memory first. If something in that section was actually still up for debate when the meeting ended, it needs to move to Unresolved Questions before this goes anywhere, since a summary that overstates consensus can cause people to act as though a decision is final when it isn't.
Check every action item for an owner. If Copilot flagged one as having no clear owner, either in your notes or in a Teams recap, that's not a loose end to clean up quietly before sending; it's useful information that someone in the meeting needs to resolve, and burying it defeats the purpose of flagging it in the first place.
If the summary is going to someone who missed the meeting, read it as though you were that person. Does it make sense without the context everyone in the room already had? If not, that's the gap to fix before it goes out, not after someone asks a confused question in reply.
When This Isn't The Right Tool
When to write the summary yourself instead
A meeting where a disagreement never got resolved, and the summary needs to represent that disagreement accurately without taking a side, is worth drafting yourself at least once before handing the material to a prompt. Nuance about who said what and how firmly they meant it is exactly the kind of thing that gets smoothed away in an automated pass, often without anyone noticing until later.
If the notes themselves are too sparse to summarize honestly, and no Teams recap exists because live transcription wasn't on, the right move is to go back and fill in the gaps from memory while the meeting is still fresh, not to ask Copilot to infer what probably happened. A confident-sounding summary built on thin notes is worse than an honest one that says "notes were light this week" and leaves it there.
Summarizing one meeting is the easy part
The harder skill is knowing which details belong in the summary and which belong in a follow-up conversation. Nightschool AI's Copilot first week at work course walks through real inbox, document, and meeting scenarios in Outlook, Word, Excel, and Teams.
Frequently Asked Questions
What should I paste into the prompt when asking Copilot to summarize meeting notes?
Paste your actual notes close to verbatim, including abbreviations and half sentences, or a Teams meeting recap if one exists. The value is in the raw material; a well-worded prompt with no notes to work from has nothing real to summarize.
How do I stop Copilot from confusing decisions with things that were just discussed?
Ask explicitly for decisions and discussion points to be listed separately, and tell it to flag anything ambiguous about whether something was actually agreed. This one instruction catches most of the confusion before it reaches the summary.
Where do I find a Teams meeting recap?
After the meeting ends, check the meeting chat and the Recap tab. A recap only exists if live transcription was turned on during the meeting, and Copilot does not work in meetings hosted outside your own organization.
Should action items have an owner listed in the summary?
Yes, with a deadline if one was mentioned. If your notes or recap don't name an owner for a task, ask Copilot to flag that gap rather than quietly skip it or guess at who's responsible.
Can Copilot summarize meeting notes that are really messy?
Yes. Messy notes with abbreviations and half sentences are fine to paste in as is; Copilot can usually work with them better than with notes you've tried to tidy up first, since tidying can accidentally drop detail.
What's the difference between asking for a summary and asking for a transcript cleanup?
A transcript cleanup just tidies the wording of what was said. A summary condenses and organizes it into decisions, action items, and open questions for someone who needs the outcome, not the play-by-play.
Should I send the summary Copilot writes without reading it first?
Read it against your own memory of the meeting first, especially the Decisions Made section and every action item's owner. A summary is a strong first draft, not a record you should treat as final without a check.
Can I ask Copilot to write a short version for someone who missed the meeting?
Yes. Ask for a short version aimed at someone who wasn't there, and say what matters most to that specific person. A summary written for the room and one written for someone catching up need different context.
A clear meeting summary takes barely any time with the right prompt
The prompt is reusable every week. Spotting what to double check is the skill worth building.