Stakeholder status update that gets read

Convert raw project notes into a crisp status update with a clear status colour, what changed, risks, and exactly what you need from readers.

LLazyPrompt(@lazyprompt)Business & StrategyGenerateWorks with any model
No ratings yetSign in to rate
Save 0 Fork Report
Prompt template
Turn my raw notes into a stakeholder update.

Project: {{project}}
Reader: {{audience}}
Reporting period: {{period}}
Raw notes:
{{notes}}

Write an update that a busy reader can absorb in under 90 seconds:
1. **Status line**: overall status (On track / At risk / Off track) with one sentence of justification. Be honest; do not default to green. Base it on the notes and tell me if the notes suggest a different status than I implied.
2. **Headline** (one sentence): the most important thing to know this period.
3. **Progress**: 3 to 5 bullets of outcomes, not activities.
4. **Risks and blockers**: each with impact, owner, and the mitigation date.
5. **Decisions or help needed**: explicit asks with a name and a date. If there are none, say "No asks this period."
6. **Next period**: top 3 priorities.

Tone: {{tone}}. Use plain language, no jargon, no filler openers. Keep the update under 250 words. After it, add a two-line version suitable for a Slack message.
Example output
**Status: At risk.** The CRM source is delayed by vendor API limits and budget is running 5 points above plan. **Headline:** Three of five data sources are migrated, but the CRM delay may push final cut-over back by about two weeks unless vendor support is extended. **Progress** - 3 of 5 sources live and validated - Duplicate-record test complete: 2% rate identified, cleanup rules drafted - Cut-over runbook reviewed with IT **Risks and blockers** - CRM vendor API limits: delays 2 sources; owner Raj; mitigation: batch throttling by 21 March. - Budget at 55% used versus 50% planned; owner Finance partner; review by 18 March. **Decisions needed:** VP Operations to approve 2 extra weeks of vendor support by 17 March. **Next period:** finish source 4, deduplicate records, rehearse cut-over. **Slack version:** Migration at risk: 3/5 sources done, CRM delayed by API limits. Need approval for 2 more weeks of vendor support by 17 Mar.

Why it works

The prompt forces an honest status and explicit asks, which are the two things stakeholders actually want. Paste unedited notes; the tidying is the model's job.

Licensed CC0 (public domain) Version 1 · history