How to Write a Project Update for Your Manager with Copilot
Status updates are routine, expected, and easy to mess up. Copilot can structure your messy notes into a clear update your manager will actually read.
What it is
Writing project updates is one of those tasks that takes more time than it should. You know what’s happened. You know what’s blocked. You know what you need from your manager. But putting it into a clean update, in the right tone, in the right structure, takes longer than the update should ever take. Copilot can fix this.
Give Copilot the facts: project name, status (Green/Amber/Red), what’s progressed since last update, what’s blocked, what you need (a decision, support, a resource). Ask for a structured update with clear headings. Out comes something your manager can read in 30 seconds — and act on. The whole exercise takes you 5 minutes instead of 25.
The deeper benefit is that consistent updates build trust. Managers learn to expect the same format every time, scan the parts they need, and act on the ‘help needed’ line. Project status moves from ‘something to chase’ to ‘something I can rely on’. That’s worth investing 5 minutes in, every week.
When to use this
- When your manager asks for a status update and you have 5 minutes, not an hour.
- When you’re sending a regular project update and want consistency.
- When you need to escalate a blocker and want the right tone.
- When you’re moving from messy progress notes into something a manager will read.
How to do it
- List the project name, current status, and time period.
- Add key progress points (what changed since the last update).
- Note any blockers, risks, or things you need from your manager.
- Ask Copilot to format as a structured email or Teams message.
- Use clear headings: Status, Progress, Risks, Next steps, Help needed.
- Review and ensure dates, owners, and numbers are accurate.
- Send.
Best practices
- Lead with status and impact, not background. Your manager doesn’t need the warm-up paragraph.
- Use consistent headings. Status, Progress, Risks, Next steps, Help needed — every time.
- Be explicit about decisions required. ‘Need approval to proceed by Friday’ beats ‘might need approval’.
- Keep it to 6-10 lines unless asked for more. Brevity is professional.
Common mistakes
- Writing 600 words when 100 will do. Long updates don’t get read.
- Burying the ask. ‘Help needed’ should be obvious, not hidden in paragraph 4.
- Forgetting to mention what’s blocked. If you only report progress, you signal everything is fine when it isn’t.
The Copilot Readiness Guide gives you the 25-question scorecard, the 4-category risk audit, and the 30-day plan to fix permissions, content quality, and sensitive content before go-live.
Get the Copilot Readiness Guide — $39 →FAQ
How do I write a project status report with Copilot?
In Word, click Copilot and prompt: ‘Draft a project status update for [project name] including progress, risks, and next steps.’ Provide context (current state, recent decisions) for better output. The Word Agent (rolled out April 2026) can edit your existing doc directly rather than starting fresh.
Can Copilot pull project data from Planner or Project?
Yes — with the right connectors enabled. Copilot Chat can reference Microsoft Planner tasks and Project for the web schedules to draft status updates with real data. Ask ‘Summarise the current state of [project name] from Planner and write a status update’.
What should I include in a Copilot project update prompt?
Five things: project name, recent decisions, current status (on track / at risk / delayed), key milestones, and the audience (your manager, leadership, the whole team). The more context you give, the less generic the output. ‘Update on X project’ produces fluff; ‘Status update on X project, audience is our exec team, focus on the budget risk we discussed last week’ produces something useful.
How do I make Copilot status updates sound less generic?
Give Copilot specifics: numbers, names, real risks, exact decisions. Copilot fills in gaps with plausible-sounding generic content, which is exactly what makes status updates feel hollow. Front-load the prompt with real data and Copilot uses it; leave gaps and Copilot invents.