Julia Moser·
Raw meeting notes in, stakeholder-ready update out. Wins, risks, asks — under 200 words, no fluff. My steering committee actually reads these now.
Compresses messy project notes into a sub-200-word stakeholder update with wins, risks, and explicit asks.
Stakeholder Update from Raw Notes
You are a project communications assistant. Turn my raw notes into a stakeholder update that busy people will actually read.
Project: {{project_name}}
Audience: {{audience}} (steering committee, sponsor, cross-functional leads — pick their altitude)
Raw notes (messy, unordered, may contain venting):
{{raw_notes}}
Last update's open items (so we close loops): {{previous_open_items}}
Write the update with exactly these sections:
**Status line** — one sentence: overall trajectory plus the single most important thing that changed since last time. Choose one honest color: green (on track), amber (at risk, recoverable with named action), red (needs intervention now). Never inflate to green to avoid questions.
**Wins** — max 3 bullets. Only outcomes, never activity ("migrated 40% of customers" yes, "held workshops" no).
**Risks & issues** — max 3, each in one line: the risk, the impact if it lands, what we are doing about it, and whether we need anything. An issue without an owner and next step does not belong here — put it in Asks instead.
**Asks** — the decisions or resources we need from THIS audience, each with a deadline and what happens if we do not get it by then. If there are no asks, write "No asks this week" — do not invent some.
**Closed loops** — one line per previous open item: resolved, carried (why), or dropped (why).
Rules: under 200 words total. No jargon, no passive voice hiding responsibility ("it was decided" is banned). Strip all venting from the notes but keep the facts inside it. If my notes contradict themselves, flag the contradiction to me instead of picking silently.
Ergebnisse
## Update: CRM Migration — Week 29
**Status: Amber.** Data migration passed the 60% mark, but the vendor's API rate limits now put the September 1 cutover at risk — recoverable if we get the decision below by Friday.
**Wins**
- 62% of customer records migrated and verified — zero data-loss incidents so far.
- Sales team pilot went live Monday; 14 of 18 reps active in the new system in week one.
- Legacy contract archive fully exported, closing our biggest compliance exposure.
**Risks & issues**
- Vendor API throttling caps us at ~4% of records per day; at this pace, cutover lands Sept 12, not Sept 1. Mitigation: vendor offered a paid burst tier — see Asks. Owner: Julia.
- Two pilot reps report duplicate contact records; root cause identified (legacy merge rule), fix ships this week. Owner: IT / Sandro.
**Asks**
- Approve CHF 3,400 for the vendor burst tier by **Friday, July 24** — without it, cutover moves to Sept 12 and collides with the sales kickoff.
**Closed loops**
- Training budget: approved and booked — resolved.
- Reporting dashboard scope: carried; blocked until duplicate fix lands.
(Contradiction flag: your notes say both "pilot feedback positive" and "reps refusing to log in" — I used the login numbers; confirm the sentiment line before sending.)
---
**Editor notes (not part of the update):**
- Word count of the update body: 194 — under the 200 limit.
- Stripped from your notes: the paragraph venting about the vendor call tone. Kept the fact inside it (burst tier offered, CHF 3,400) — that became the Ask.
- The amber status is justified by a dated, named recovery action (Friday decision). If the committee approves the burst tier, next week's update opens green; if not, the status line should move to red rather than staying amber a second week — amber twice in a row on the same risk reads as drift.
- Suggested subject line for the email: "CRM Migration W29: Amber — one decision needed by Friday". Deadline in the subject doubles the odds the ask is read before the meeting.
Modell: Claude Haiku 4.5
3 Likes1 SavesScore: 3