You have a recap, a draft email, and a Word brief. Fluent is not the bar. Open the three artifacts and check names, numbers, and anything that sounds like a promise. If you cannot point to the meeting, the thread, or the file, it does not ship.
Names, numbers, commitments. Then the send button.
This is the same habit as AI Judgment and Copilot Basics Lesson 4. Here it is applied to the three apps you will actually send from.
Core principles
- Highest risk: names, dates, owners, prices, "we agreed," "you will."
- If Work IQ may have mixed a file into the email, open the citation or cut the sentence.
- Recap ≠ minutes. Say "draft recap, please correct" if you were not in the room.
- You still send. Copilot does not.
Go deeper: AI Judgment — verification scaled to stakes
Check yourself
When is the Word / Outlook / Teams chain actually finished?
Generation is not the send. Verification is what makes the output yours. Same bar as AI Judgment.
Do this in Copilot
Send only after the verify pass. Pin one line: "For [project], I check names, numbers, and promises before Outlook or Word leaves my machine."
Paste the email draft and the Word keepers. Do not send from Copilot.
Audit the chain before send
I am about to send this email: [PASTE] and keep this in Word: [PASTE]. Audience: [WHO]. List every name, number, owner, date, and promise. For each, ask me whether it was in the meeting transcript, the email thread, or the Word source file. Flag anything that would be oversharing if this audience should not see the source. Do not invent a missing source. If you are unsure, say so. I will only send what I can defend.
Did you run this in Copilot? Mark complete when you have tried it.
RecordedNavigate: press j for next lesson,k for previous.