Project Status Update Email — 3 Word-for-Word Professional Templates

A good project status update is short, structured, and honest. It tells stakeholders what they need to know without requiring a meeting. These three templates cover the three most important update types: on track, delayed, and escalation.

Original Message

I need to send a project status update to my stakeholders but I am not sure how to structure it.

Professional Version

Subject: Project Update — [Project Name] — Week of [Date]

Hi [Name/team],

Here is a quick update on [project name].

Status: On track
Completed this week: [item 1], [item 2]
In progress: [item 3]
Coming up next: [item 4, expected by date]
Blockers: None at this stage

Next update: [date]. Let me know if you have any questions.

[Your name]

Polite Version

Subject: ESCALATION: [Project Name] — [Issue]

Hi [Name],

I am escalating an issue with [project name] that requires your attention.

Issue: [specific problem]
Impact: [consequences if not resolved — delivery date / budget / client relationship]
Decision needed: [what you need them to decide or approve]

Options:
Option A: [brief description]
Option B: [brief description]

I recommend Option [A/B] because [brief reason]. I need a decision by [date] to avoid [consequence].

Available to discuss at your convenience.

[Your name]

Firm Version

Subject: Project Update — [Project Name] — Revised Timeline

Hi [Name],

I wanted to flag a change to the [project name] timeline.

Status: Behind schedule
Reason: [specific cause — scope change / dependency delay / resource issue]
Revised delivery date: [new date]
Impact: [brief description]
Actions underway: [what you are doing to address it]

I will keep you updated and flag any further changes as early as possible. Please let me know if you would like to discuss.

[Your name]

When to Use This Template

For regular weekly or bi-weekly stakeholder updates on an active project
When the project is running behind schedule and you need to communicate a revised timeline
When an issue requires a decision or action from a senior stakeholder or sponsor
When onboarding a new stakeholder who needs a clear picture of current project status

Common Mistakes to Avoid

Burying a delay in the middle of a long update: If the project is delayed, say so in the first sentence. Stakeholders scan status emails — if the bad news is buried, they may miss it, and that creates a bigger problem when they find out later.

Sending a status update with no specific next steps or dates: "Progress is ongoing" tells the reader nothing actionable. Every update should include a specific next milestone and date so stakeholders know what to expect and when.

Escalating without proposing a solution: Bringing a problem without options puts the entire burden on the stakeholder. Even a partial solution shows you have thought it through and makes it easier for them to act quickly.

Frequently Asked Questions

How often should you send project status updates?

Weekly is standard for most projects. Increase frequency if there is a risk or a blocker. Decrease to bi-weekly for stable, long-running projects. Always send an update immediately when there is a significant change to timeline, budget, or scope — do not wait for the scheduled update.

What should a project status email include?

Status (on track, at risk, delayed), what was completed, what is in progress, upcoming milestones, blockers or risks, and any decisions needed. Keep it brief — stakeholders want the key points, not a full project log.