Meetings: Recaps, Actions, and Follow-Ups

You join the launch meeting eleven minutes late. The discussion is already moving and you don't know which decisions are settled. You could message a colleague and wait for a hurried catch-up. Or you can ask Copilot and get the missing context in about thirty seconds. That convenience comes with a review job: the answer may attach an owner or deadline that nobody agreed to.

Three meeting experiences, three moments

Teams gives you three related but distinct experiences, each at a different point in the meeting's life:

A transcript is a text record of what was said. A recording is the audio or video. Neither one is "Copilot," and neither is "Recap." Keeping the words straight keeps the workflow straight. Live Copilot helps you understand the conversation as it happens. Recap gives you a place to return to the materials. Intelligent Recap adds a layer of AI-generated organization on top of them.

One thing the presence of a Recap does not tell you is what license you have. Recap shows up because a meeting produced artifacts, not because a particular entitlement is active. Live transcript querying during a meeting needs Microsoft 365 Copilot, while base Intelligent Recap can come from either Teams Premium or Microsoft 365 Copilot. Don't reason backward from "I can see a Recap" to "I must have Copilot." We'll map the tiers properly in Chats, Channels, and What Your License Covers.

Live questions need a source boundary

A vague "what happened?" gets you a vague answer. A useful in-meeting prompt has four parts: a time scope (the whole discussion, one topic, the last few minutes), the question you need answered, an output format (bullets, a table, a decision log), and an evidence boundary: a rule against inventing owners, dates, or commitments.

That last part matters most. "Someone should review privacy" is a suggestion. "Elena will review privacy by Friday" is an explicit assignment with an owner and a date. Copilot cannot always tell them apart on its own, so you tell it: include an owner or date only when a participant stated it, and write "Not stated" for anything missing. End live prompts that way and your notes stop manufacturing commitments.

Live-only Copilot leaves no transcript

Some meetings need Copilot's help without a saved transcript or recording. The conversation may be sensitive, candid, or legal-adjacent. In the live-only configuration, the organizer chooses the setting and participants can ask questions during the meeting. The workflow creates no saved transcript or recording. Anything you need later therefore has to be captured before the meeting ends.

Check the state before you rely on it. The organizer must have selected live-only, and neither transcription nor recording can have started. If either starts, the meeting is no longer following that workflow. Before leaving, copy verified decisions and actions into the approved notes or task system.

Read AI notes as a draft

Intelligent Recap gives you tidy meeting notes and recommended tasks. Start there, then check the work. In this example, the meeting settled one fact: "the pilot will begin on 18 August." Elena agreed to draft the customer email, and Marco agreed to check telemetry before launch. Neither action received a deadline. A privacy review was raised, but nobody accepted it.

The generated log says Elena's email is due 18 August, Marco's check is due 18 August, and Elena owns the privacy review. None of those claims is supported. One launch date has been copied onto two tasks, while the unassigned review has landed on the nearest named person. Trace each row back to the discussion. Keep "before launch" as context, and use "Not stated" when the meeting supplied no owner or date.

Before a recommended task reaches your follow-up list, check four points. Did someone accept it? Is the owner right? Was the due date stated? Was the original statement a decision, a proposal, or an open question? If the evidence doesn't settle those points, put the task in a "to confirm" list until someone does.

Audio, video, and call recaps

Beyond a single meeting, Copilot can spin several related meetings into a podcast-style audio recap, handy when a kickoff, a risk review, and a handoff form one decision thread. It covers up to eight meetings, specifically needs Microsoft 365 Copilot, and is stored for about 60 days. Preserve any real decision somewhere durable before that window closes.

Video recap stitches narrated highlights from a recording, up to 100 per recording, but a highlight is only a pointer. "The team selects the blue dashboard" can turn out to be "let's treat blue as the proposal and decide after Friday's test" once you watch the surrounding clip. Check the context before you promote a highlight to a decision.

Call recaps follow the same discipline. Review any call in five buckets: the caller's issue, facts explicitly confirmed, actions only proposed, actions explicitly agreed, and unresolved questions. That way "I can ask billing whether a credit is possible" never hardens into "billing will issue a credit." When a call has a known date, convert relative deadlines: "I'll update you tomorrow" becomes an actual calendar date you can hold someone to.