Status updates
RawReply writes project status emails: what shipped, what's blocked, what's next — short enough that execs finish them. Paste your bullets; get a sendable update without the 'synergize' layer.
Weekly to stakeholders
Before
Hope this email finds you well. I wanted to provide a comprehensive update on the various workstreams currently in flight. We remain committed to excellence as we continue to iterate...
After
Quick status on Atlas: • Done: billing webhook retries shipped to staging • Blocked: waiting on legal for DPA redlines (since Mon) • Next: prod cutover Thursday if DPA lands Need anything else on your radar?
Delayed milestone
Before
Unfortunately due to unforeseen challenges we will need to revisit the timeline. We apologize for any inconvenience and appreciate your continued partnership.
After
Flagging a slip: the Aug 12 launch moves to Aug 19. Reason: vendor sandbox was down 2 days; integration tests blocked. New date has 1-day buffer. I'll send a revised checklist Monday.
All-clear / green week
Before
Pleased to report that all key performance indicators are tracking positively against our OKRs for this sprint cycle.
After
Green week on Checkout v2: load test passed, no Sev-1s, on track for Tuesday release. Only open item is the analytics event name freeze — need your +1 by EOD.
If it needs a table of contents, it's too long. Aim for done / blocked / next — scannable in under a minute. Details belong in the ticket or doc you link once.
No. Soft language forces a second email. State the slip, the cause, and the new date. Stakeholders can handle bad news; they hate surprise.
Follow-ups chase an unanswered ask. Status updates inform people who already expect a cadence. Different job, different tone.