Copilot in Teams: How to Turn Every Meeting Into a Decision Table
Most meetings don’t fail because they run long. They fail because people leave with different ideas of what was agreed. A week later the same topic is back on the agenda, someone asks “didn’t we decide this already?”, and nobody can say who owned the next step.
A conservative estimate is that 20–30% of meeting time goes on revisiting decisions that weren’t captured properly the first time. For a 100-person organisation, that adds up to a lot of salary spent going round in circles.
Microsoft 365 Copilot in Teams is one of the quickest ways I’ve found to close that gap. Not just because it summarises the meeting, but because you can ask it to turn the discussion into a decision table: what was decided, who owns it, why, and what happens next. Here’s how I use it with clients.
From summaries to decisions
Early meeting AI produced transcripts and long summaries. They were useful, but the decision, if it appeared at all, was buried among discussion points. Copilot in Teams can now work with the structure of a meeting: the topics raised, the options debated, where people agreed or disagreed, and the point where the group converged.
That distinction between discussion and decision is what matters. A summary tells you what was said. A decision record tells you what changed.
What a Copilot decision table looks like
At the end of a meeting, or during it, ask Copilot to produce a structured table. This is the prompt I use:
“Create a table of every decision made in this meeting with the columns Decision, Owner, Rationale and Next step. Then list action items with owner and due date, and flag any action without a clear owner or deadline.”
The output looks like this:
| Decision | Owner | Rationale | Next step |
|---|---|---|---|
| Move the CRM go-live to 3 November | Project lead | Data migration testing needs two more weeks | Update the plan and inform the sales directors |
| Approve the extra licences for the support team | IT manager | Ticket volume has grown 30% since Q2 | Raise a purchase order this week |
| Pause the supplier review until Q1 | Procurement | Contract renewal isn’t due until March | Add it to the January steering agenda |
The Rationale column is the one people underestimate. Six months later, when someone asks why a decision was made, the answer is there, drawn from the discussion itself rather than from someone’s memory.
Action items that actually get done
Vague commitments like “I’ll look into it” fill meeting notes and rarely turn into work. Asking Copilot to list each action with a named owner and a due date, and to flag anything missing either, gives the organiser a chance to fix gaps before everyone leaves the call.
From there, you can turn actions into tracked tasks in Planner or To Do, or paste the table into a Loop component that the team keeps updating. The gap between “we agreed” and “it’s in someone’s task list” shrinks to minutes.
Catching up people who missed the meeting
One of my favourite uses: a senior stakeholder who joined late or missed the meeting can simply ask Copilot, for example “What did we decide about the Q3 budget?” or “What was the final position on the supplier contract?”, and get an answer grounded in the transcript. That replaces watching back an hour-long recording.
Where it adds the most value
- Board and executive meetings: a consistent first draft of decisions and rationale gives the company secretary a much better starting point for the minutes.
- Project steering committees: a running decision log supports governance and post-project reviews.
- Risk and compliance committees: a structured record of who decided what, and on what basis.
- Sales and customer meetings: follow-ups promised to customers are captured and can be copied into the CRM.
The culture shift
When decisions are reliably recorded with owners and reasons, two things happen. People stop taking frantic notes and actually take part in the discussion. And accountability goes up: it’s harder to dodge an action, and easier to challenge a decision that was made without good reasoning. Over time, the quality of decisions improves, not just the speed of follow-up.
Getting it set up
- Licences: users need a Microsoft 365 Copilot licence. See Copilot licensing explained.
- Meeting policies: enable transcription in your Teams meeting policies, because Copilot’s full meeting capabilities rely on it.
- Templates: agree a standard decision-table prompt for each meeting type (board, steering group, project stand-up).
- Review before sharing: make the organiser responsible for checking the table before it’s distributed. AI drafts, humans approve.
- Records and retention: in regulated industries, confirm how transcripts and recaps fit your retention and records-management policies.
As with every Copilot capability, the hard part isn’t switching it on. It’s changing habits. I cover the human side in Copilot readiness is human, not technical.
FAQ
Does Copilot need the meeting to be recorded?
Copilot’s meeting features rely on transcription. Depending on your settings, Copilot can work during the meeting without a saved recording, but recaps after the meeting require the transcript to be kept.
Can Copilot get decisions wrong?
Yes, especially when a decision was implied rather than stated. Get into the habit of saying decisions out loud (“so we’re agreed that…”), and have the organiser review the table before sharing it.
Who can see the decision table?
Copilot only works with meeting content that the person asking has access to. Once you share the table in a chat, channel or email, normal Microsoft 365 permissions apply.
Related reading: Why most Copilot projects fail · Before you turn on Copilot
