Stakeholder-Tailored Weekly Status Update
Turn weekly notes into a concise status update tailored to the right stakeholder audience.
Customise & copy
Add the context you have. The prompt updates as you work.
List completed work, outcomes, milestones, or notable progress.
List current blockers, dependencies, uncertainties, or risks. Enter None if there are none.
List the main planned tasks or priorities for next week.
Choose the audience so the update can use the appropriate level of detail and emphasis.
Live prompt
4 fieldsConvert the provided weekly notes into a concise, professional status update for the selected stakeholder level. Use exactly these sections and headings: ## Accomplishments - Summarize {{accomplishments}} as clear, specific bullet points. ## Blockers and Risks - Summarize {{blockers_risks}} as clear bullet points. If none are provided, write "None reported." Do not invent risks. ## Next Week - Summarize {{next_week_tasks}} as clear, action-oriented bullet points. Adjust wording, detail, and emphasis for the Senior management audience. Preserve all factual meaning, omit unsupported claims, remove repetition, and avoid greetings, filler, hype, and closing remarks. Return only the status update.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"blockers_risks": "- Data migration for two enterprise accounts is still pending\n- Design resources are limited for the upcoming mobile release",
"accomplishments": "- Launched the self-service billing dashboard to 40 beta customers\n- Closed 18 priority support tickets\n- Improved invoice export speed by 25%",
"next_week_tasks": "- Review beta feedback and prioritize fixes\n- Complete migration validation\n- Prepare the mobile release checklist",
"stakeholder_level": "Senior management"
}A small ritual that works
How to use it
- 01Enter the week's accomplishments.
- 02List blockers or risks, or enter None if there are none.
- 03Add planned tasks for next week.
- 04Select the target stakeholder level.
Why it works
The prompt gives the task a clear transformation: turn weekly notes into a concise status update for a named audience. Its fixed headings create a predictable structure, while separate inputs for accomplishments, blockers, and next-week tasks help preserve the distinction between completed work, current concerns, and planned activity. Instructions to preserve factual meaning, remove repetition, and avoid unsupported claims establish useful boundaries for concise professional writing. The stakeholder selector also signals that wording, emphasis, and detail should change according to the reader.
Where it fails
The prompt is less suitable when the source notes need a format other than the three fixed sections, when important information does not fit naturally into accomplishments, blockers, or next-week tasks, or when the audience falls outside the five listed stakeholder levels. Its instruction to omit unsupported claims also limits what can be added when the notes are vague or incomplete.
Customisation tips
Add stakeholder options when the update will serve audiences with different information needs. Expand the section structure if the workflow regularly requires decisions, metrics, dependencies, or questions. Define formatting preferences such as maximum bullets, sentence length, or whether measurable figures should be retained. If source notes follow a consistent internal convention, describe that convention in the relevant variable helper text or prompt instructions.
Watch-outs
- The three content fields are required, so the input workflow should make it clear how to represent an empty category.
- The blocker instruction provides a specific phrase for an empty section; keep that wording aligned with any surrounding reporting convention.
- Audience adaptation is intentionally broad: the prompt names stakeholder levels but does not define exact differences in tone, detail, or emphasis for each one.
- The final instruction to return only the status update excludes greetings, explanations, and closing remarks, which may not fit workflows that require commentary or follow-up questions.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.