Draft an Update in Copilot Chat
Start at microsoft365.com/chat — not Agent Builder. Send the setup prompt, wait for Ready, paste messy weekly notes as your next message.
Lesson 1
No agent yet — prove the pattern.
In about fifteen minutes you should have a short update: three sections, under 200 words, gaps marked [Needs input] rather than invented numbers.
Core principles
- Outcomes over activity — what changed, not what you attended.
- If a number or date is not in your notes, [Needs input] — do not invent it.
- Max three bullets per section keeps it manager-scannable.
- The setup prompt prevents Copilot from drafting before it knows the rules.
- Use the sample notes below if you do not have your own chaotic week handy.
Check yourself
What should Copilot do when a metric is missing from your notes?
Invented metrics are the fastest way to lose manager trust. [Needs input] flags what you still owe — honest and actionable.
Do this in Copilot
Run the two-message flow with sample or real notes. Save the draft somewhere you can compare after personalization.
Copilot chat at microsoft365.com/chat — send this first, then paste your notes.
Simple prompt (send first)
When I paste my messy weekly notes in the next message, turn them into a short status update for my manager. Format: - Highlights (max 3 bullets) - Risks / blockers (max 3 bullets) - Next steps (max 3 bullets) Rules: - Outcomes over activity - If a number or date is not in my notes, write [Needs input] — do not invent it - Keep it under 200 words Do not draft the update yet. I will paste my notes in my next message. Reply "Ready — waiting for your notes." when you understand these rules.
- Two-message flow
- Negative constraints
- Sample notes (message 2):
- weekly dump — week ending 20 Jun (messy) === random notes === - Tue call w/ dealer re: NWG — they want updated phasing options before CFO review - pricing model v3 still w/ regional finance?? no reply yet - Project Helios: client loved moodboards, waiting on spec feedback (email 12 Jun?) - pipeline cleanup — moved 2 opps to Q3, one duplicate account fixed === email fragment (fwd) === From: facilities contact @ NWG "...pilot went better than expected but we cannot commit capex until autumn planning. Can you show a phased approach that keeps floor 3 live while we plan floors 4–5?" === meetings (half-remembered) === - internal sync: marketing wants case study quote — NOT approved yet - travel next week Amsterdam + Munich - forgot to log SF activity on Helios until Thursday === blockers / risks === - pricing data delay (region) - new CFO = shorter updates, hates fluff (boss said "lead with decisions needed") - dealer asking for competitor battlecard we don't have updated === wins? === - Helios concept direction aligned - NWG still engaged despite budget freeze metrics: [none handy]
Did you run this in Copilot? Mark complete when you have tried it.
RecordedNext lesson: Read It as Your Manager Would →
Navigate: press j for next lesson, k for previous.