When to Use This Message
Send a Project Status Update when:
- Stakeholders need to know how a project is progressing without asking directly.
- You're at a regular checkpoint (weekly, biweekly) where an update is expected.
- Something has changed — a delay, a risk, a milestone hit — that people should know about.
- You want a written record of progress for future reference.
Message Writing Tips
- Lead With the Overall Status: State up front whether things are on track, at risk, or delayed — don't bury this in the details.
- Summarize Key Progress Since the Last Update: Focus on what's changed or been completed, not a full restate of the entire project history.
- Flag Risks or Blockers Clearly: If something needs attention or help, call it out explicitly rather than mentioning it in passing.
- Note What's Coming Next: A brief look-ahead helps stakeholders anticipate upcoming decisions or dependencies.
Frequently Asked Questions
How often should I send status updates?
It depends on the project, but a consistent cadence (weekly is common) helps stakeholders know when to expect news instead of asking ad hoc.
What if there's bad news to report?
Report it clearly and promptly rather than softening or delaying it — pair it with what you're doing about it to keep the update constructive.
How long should a status update be?
Short enough to read in under a minute for most stakeholders — link out to detailed documentation for anyone who wants more depth.