Create intermediate Works with: Any AI

Stakeholder Update and Briefing Notes

Before after Has example

Prepare concise updates for senior people.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Turn my rough update into a concise briefing for a senior person. Audience and what they care about: [AUDIENCE_AND_PRIORITIES]. Project or topic: [PROJECT]. My raw notes: [PASTE_NOTES]. Decision or support needed: [ASK]. Maximum length: [MAX_WORDS] words.

Return:
BEFORE: my raw notes with problems marked in brackets ([detail the reader doesn't need], [buried ask], [status without meaning], [jargon], [no date], [no numbers]).
AFTER, in this order:
1. Bottom line (one sentence): where things stand and the ask.
2. Status in three bullets with a red, amber, or green marker and the reason for the color.
3. What changed since the last update.
4. Risks and issues: each with impact, owner, and mitigation.
5. Decisions or help needed, with a recommended option and a deadline.
6. Next steps and dates.
7. Optional appendix: supporting data.
TONE CHECK: plain words, no spin; bad news first when there is bad news.
FOLLOW-UP QUESTIONS: the three questions the reader is most likely to ask and a prepared answer for each.

Use only facts from my notes; mark gaps as [ADD DATA].

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Bottom line: The website launch is on track for 14 November; we need your approval for an extra 3,500 for accessibility testing by Friday.
Status: Design GREEN (approved); Build AMBER (payment integration two days behind); Content RED (legal review not started).
Changed since last update: new checkout flow added after customer testing.
Risks: legal review delay (impact: launch slip of a week; owner: Legal; mitigation: weekly check-in).
Decision: approve 3,500 (recommended) or accept testing after launch (risk of fixes later).
Next steps: Content legal meeting 17 Oct; QA starts 28 Oct.
Likely questions: "What if payment slips again?" Answer prepared. Gaps marked [ADD DATA].

• briefing
• stakeholders