Weekly Stakeholder Update Prompt
Produces a concise management-ready weekly update focused on outcomes, project status, risks, cross-team relevance, and next-week priorities.

Purpose: Produces a concise management-ready weekly update focused on outcomes, project status, risks, cross-team relevance, and next-week priorities.
How to use it
Paste the prompt into Microsoft 365 Copilot near the end of the week. Ensure it can access the relevant weekly emails, meetings, notes, tasks, and documents. Verify confidential information, status labels, owners, and metrics before sharing the update.
Prompt
ROLE
Act as a senior communications manager drafting a concise, management-ready weekly update.
CONTEXT
You are preparing a weekly update for my manager, coworkers, and key stakeholders. The audience is time-constrained and expects clarity, prioritization, and business relevance.
INPUT
Use all relevant information from my emails, meetings, notes, tasks, and documents from the past week.
OUTPUT REQUIREMENTS
- Tone: professional, direct, outcome-focused
- Length: max 10–12 bullet points total
- Avoid fluff, repetition, and unnecessary context
- Focus on impact, progress, and priorities
- Use clear section headers and short bullets
- Highlight risks and dependencies explicitly
STRUCTURE
1. KEY ACHIEVEMENTS (this week)
- 3–5 bullets
- Focus on outcomes and impact, not activity
- Include metrics or business value where possible
2. PROGRESS ON PRIORITIES
- Status of key projects or initiatives
- Use labels: On track / At risk / Delayed / Completed
- Keep each item to 1 line
3. RISKS & BLOCKERS
- Explicitly name issues impacting delivery
- Add owner and next step per item
4. STAKEHOLDER RELEVANT UPDATES
- Only include updates that matter cross-team
- Focus on decisions, alignment, or dependencies
5. NEXT WEEK FOCUS
- 3–5 clear priorities
- Outcome-oriented, not task lists
6. SUPPORT NEEDED (optional)
- Clearly state where input, decisions, or escalation is required
QUALITY BAR
- Every bullet should answer: “Why does this matter?”
- No vague statements like “working on” or “progressing”
- Prefer quantified or decision-oriented wording
- Remove anything that does not help decision-making
FINAL STEP
- Tighten language for brevity
- Ensure logical flow and no duplication
- Make it ready to copy-paste into email or Teams messageSources
Original WorkWithAI prompt; no external factual source required.
Last reviewed: · By Arnaud Llamas Bravo


