Copilot in Teams: meeting summaries that aren't garbage.
Default Copilot meeting summaries are mediocre — a bulleted list of who said what, no structure, no actions. This lesson covers the four workflows that turn meeting Copilot into a real productivity layer: recap with structure, catch-up on missed meetings, pre-meeting briefings using past conversations, and action-item extraction that actually captures commitments.
The mental model
Generic recaps are useless. Structured recaps change how meetings work.
The trick is in what you ask after the meeting ends. Don't accept Copilot's default summary. Prompt it specifically for the structure you need: decisions made, action items by owner, open questions, follow-up commitments.
Workflow 01 Post-meeting recap with the right structure
Ask for the recap you actually want
After the meeting, open the Copilot chat for the meeting. Don't accept the default summary; prompt for structure.
The prompt that works
Best use cases
- Standups and team meetings
- Customer calls
- Project sync meetings
- Any meeting where actions need to flow to someone afterward
Workflow 02 Catch up on a meeting you missed
Get briefed in 2 minutes
Missed a meeting? Open it in Teams, open the Copilot recap, and prompt as if you'd attended.
The prompt that works
Best use cases
- Meetings you had to skip but needed context on
- Recurring meetings you don't always attend
- Cross-team meetings where you're a stakeholder, not core attendee
Workflow 03 Pre-meeting briefing across past conversations
Walk into the next meeting with full context
Before a meeting with a specific person or team, ask Copilot to brief you on past Teams conversations with them.
The prompt that works
Best use cases
- 1:1s with reports or managers
- Customer-facing meetings
- Cross-functional syncs
- Anywhere context from past conversations would help
Workflow 04 Extract real action items, not vague todos
Force commitments into a structured list
Generic Copilot action items are usually too vague to act on ("Sarah to follow up on the proposal"). Prompt for specificity.
The prompt that works
Best use cases
- Internal team meetings with multiple workstreams
- Customer meetings where commitments matter
- Project kickoffs and reviews
- Any meeting where people leave with different memories of what was agreed
Final challenge: a Teams-driven workweek
For one work week, treat every Teams meeting as having a Copilot follow-up step. After each meeting:
- Run the structured recap prompt (Workflow 1)
- Forward the recap to participants — replacing your usual "here's what I think we agreed" email
- Use the action-item prompt (Workflow 4) to extract real commitments
- For meetings you missed, run the catch-up prompt (Workflow 2)
- Before next week's 1:1s, run the pre-meeting prompt (Workflow 3)
Track how much meeting-related admin time decreased.
What you can do now
- Get structured meeting recaps instead of generic bullet lists
- Catch up on missed meetings in 2 minutes instead of 30
- Walk into any 1:1 with full historical context from past chats
- Extract real, owner-and-deadline-attached action items
- Know when to trust Copilot's recap vs. when to verify against the recording