Copilot in Outlook and Teams: Practise Meeting Summaries and Follow-up Emails You Can Trust

What can go wrong with an automatic summary

A summary can be readable and still wrong. Common errors include treating a suggestion as a decision, assigning a task to the wrong person, merging two dates, or omitting a disagreement. These mistakes matter more in follow-up emails because people act on them.

The goal of this exercise is not speed alone. It is a follow-up email that every participant would agree accurately reflects what was decided.

Check meeting settings before you rely on Copilot

Microsoft documents that organisers can set Copilot in Teams meetings to be available during and after the meeting, or only during the meeting. For use after the meeting, transcription needs to be on. Organisational policies may restrict these options, and participants should know when transcription is used.

If Copilot is unavailable for a meeting, take your own notes. Do not assume a summary exists because a recording link exists.

• Confirm the organiser's Copilot setting before the meeting.
• Follow your organisation's consent and notice rules for transcription.
• Note who is responsible for the final minutes.
• Avoid sharing sensitive topics in meetings where transcription policy is unclear.

Practise on a fictional email thread first

Create a short fictional thread between three colleagues planning a training session. Include one confirmed item (venue booked), one proposal (start at 10 am), one disagreement (whether Sales attends) and one open question (budget approval). Then ask Copilot in Outlook to summarise the thread, where available.

Summarise this thread in four headings: Decisions, Proposals not yet agreed, Disagreements, Open questions. For each item, name who said it. Do not convert proposals into decisions. If an owner or date is not stated, write 'not stated'.

Turn the checked summary into a follow-up email

Compare the summary to the thread. The venue is the only decision. The 10 am start is a proposal. Sales attendance is disputed. Budget approval is open. Correct anything that does not match, then ask for a short follow-up.

Draft a polite follow-up email using only the checked summary below. List the one confirmed decision, ask the group to confirm the 10 am proposal, request a decision on Sales attendance by a date I will add, and ask who will approve the budget. Keep it under 120 words.

A review checklist for every follow-up

Before sending, read the draft against your notes or the transcript. Ask one participant to confirm if a decision is significant or contested. Remove confident language about anything still open.

• Each decision was explicitly agreed, not merely suggested.
• Every owner has accepted the task.
• Dates and times include the time zone for international teams.
• Disagreements are reported fairly, not hidden.
• No confidential detail is copied to people outside the meeting.

Bringing this practice to a team

Teams in India, the US, the UK and the UAE often lose time to unclear follow-ups across time zones. A workshop can practise this summary-and-review routine with fictional threads, then agree a team rule for when AI summaries need human confirmation.

The Hindi course covers email and meeting workflows for individuals. Corporate sessions are scoped separately; Microsoft licences and admin configuration remain your organisation's responsibility.