The point of in-app Copilot is a chain, not three isolated tricks. Take one live meeting. Recap it. Turn the recap into a follow-up email. Land the keepers in the Word file from Lesson 1. Each hop is a chance to leak the wrong thread or invent an owner.
Three apps, one object of work. Do not start three chats.
If one app is missing Copilot, do that hop in Chat with the file or thread attached. The chain still counts.
Core principles
- One object of work. Same project name in Teams, Outlook, and Word.
- Carry [Cite] and [Not stated] forward. Do not clean them up by guessing.
- The Outlook send is not the archive. The Word file is.
- Stop if the audience changes. A client email is not the Teams recap with the greeting swapped.
Related: Chat, Pages, Notebooks, Loop — the email is not the archive
Check yourself
What should travel with the work from Teams to Outlook to Word?
Each hop is a leak or invention risk. Flags travel. Guessing to look finished is the failure.
Do this in Copilot
Run the chain on this week's meeting. Save the Word file. Do not send the email until Lesson 5.
After Teams recap, paste this in Outlook (or Chat). Then paste the keepers into Word.
Hand the recap to the next app
Project: [FIVE WORDS]. I am moving this meeting recap into a follow-up email, then into a working brief. Recap: [PASTE, INCLUDING YOUR FLAGS]. Audience for the email: [WHO]. Do not add owners or dates that are [Not stated]. Draft the email under 150 words. Then list the five keepers that belong in the Word brief, each with its source (transcript / chat / my note). Omit anything I would not forward to this audience.
Did you run this in Copilot? Mark complete when you have tried it.
RecordedNext lesson: Verify before you send →
Navigate: press j for next lesson,k for previous.