How to Write a Project Update Email

The project update email is the unsung workhorse of modern business communication. It is sent by the thousands each day across every industry, and it is almost universally written badly. Most project updates are either so vague the reader learns nothing ("on track, no blockers") or so dense the reader scrolls past in three seconds. The sweet spot, a project update that informs without exhausting, is a learnable craft with clear rules.

A strong project update email answers three questions in under 200 words: what happened, what is next, and what does the reader need to do. Everything else is commentary. This guide provides templates, structures, and language patterns to write updates your clients, stakeholders, and executives actually read.

Why Most Project Updates Fail

Three failure modes dominate the genre.

The everything dump. The sender writes every activity since the last update in chronological order. The reader sees a wall of text and scans for the line that affects them, then closes the email. Detail drowns significance.

The hopeful vagueness. The sender writes "things are going well, we are on track, no blockers at this time." The reader gains no information and loses trust in future updates. Confidence without specifics reads as spin.

The scattered structure. The sender mixes status, risks, decisions needed, and next steps in one paragraph. The reader cannot find what they actually need. Structure is the single most underrated element of project updates.

"The information is not the problem. The sorting of the information is the problem. A project update that puts everything in one big bag forces the reader to do work you should have done." Josh Bernoff, Writing Without Bullshit

The Four-Section Framework

A project update email works when it separates four types of information cleanly.

Section 1: Status summary. One sentence. On track, at risk, or off track, with a reason.

Section 2: Progress since last update. Three to five bullet points of specific accomplishments.

Section 3: Risks and blockers. Anything threatening the timeline, budget, or quality, with what is being done.

Section 4: Decisions needed or next steps. What the reader needs to do, and by when.

Every section earns its place. None is longer than it needs to be. The reader can scan any section in under ten seconds.

Three Copy-Paste Templates

Template 1: Formal Client Project Update

Use this for external clients, executive stakeholders, and formal consulting or agency contexts.

Subject: [Project Name] weekly update, [Date]

Dear [Client Name],

Status: [On track / At risk / Off track]. [One sentence reason.]

Progress this week:
- [Specific deliverable completed, with quantifiable detail]
- [Specific deliverable completed, with quantifiable detail]
- [Specific deliverable completed, with quantifiable detail]

Risks and mitigations:
- [Risk description]. Mitigation: [specific action being taken]. Owner: [name]. Target resolution: [date].

Decisions needed from you:
- [Specific question or decision]. Recommended answer: [option]. Needed by: [date].

Next milestone: [Specific deliverable and date].

Please let me know if any of the above needs discussion. I am available this week on [specific days] for a 15-minute call if useful.

Regards,
[Your Name]
[Your Role]

Template 2: Warm Internal Project Update

Use this for cross-functional team updates, internal stakeholders, and contexts where brevity blends with warmth.

Subject: [Project] update, week of [date]

Hi team,

We are on track to hit the [milestone] by [date], with one risk we are actively managing.

What got done this week:
- [Accomplishment, specific]
- [Accomplishment, specific]
- [Accomplishment, specific]

One risk to flag: [risk]. Here is what we are doing about it: [action and owner]. I will update next week on whether this is resolved.

Two things I need from this group:
- [Name]: could you confirm [decision or input] by [day]?
- [Name or group]: need sign-off on [item] so we can start [next thing].

Next checkpoint: [Date and deliverable].

Thanks all,
[Your Name]

Template 3: Short Executive Update

Use this for C-suite stakeholders, board members, or any context where the reader has less than one minute to process the update.

Subject: [Project] status, [Date]

[Name],

Status: [On track / At risk / Off track].

This week: [One sentence summary of most important progress].

Risk: [One sentence on biggest risk and what is being done].

Needed from you: [One sentence, specific, with deadline]. Or: No action needed.

Next update: [Date].

[Your Name]

This template stays under 60 words. It forces the writer to sort what matters. Executives read short updates twice. They rarely read long ones once.

Bad Version vs Good Version

Bad:

Subject: Quick update

Hi all,

I wanted to send a quick update on where things stand with the migration project. Things are going well overall. We have been working through a lot of the initial tasks and the team has been doing a great job. We did run into some challenges with the data validation piece but we are working on it. Some of the integration points are a little more complex than we originally thought but we should be okay. Let me know if anyone has any questions or concerns.

Thanks, Amy

Why it fails: no specific status, no concrete accomplishments, risks hidden behind euphemism ("a little more complex"), no ask, no date, and ends with an open question that puts the work on the readers.

Good:

Subject: Migration project status, Week of Oct 7

Hi all,

Status: At risk. The integration layer is running 8 days behind due to the API rate-limit issue we identified last Friday.

This week:

• Completed data validation on Region 1 (14M records, 99.98% clean)
• Cut over Region 2 read paths to the new system; no user-facing impact
• Documented the API rate-limit issue and submitted Ticket 4421 to the vendor

Biggest risk and mitigation:

• Vendor ticket response expected by Wednesday. If vendor does not respond by then, we execute Plan B (chunked requests with 90-second delays), which adds 4 days to the timeline. Owner: Priya.

Decision needed this week:

• Whether to go with Plan B or extend timeline if vendor responds late. I recommend Plan B. Need your sign-off by end of day Thursday.

Next milestone: Region 3 cutover, Oct 28 (may slip to Nov 1 pending above).

I am available for a 20-minute call Thursday morning if helpful.

Thanks, Amy

Why it works: crisp status label, specific numbers, named risk with named owner and specific fallback plan, clear decision ask with recommended answer and deadline, and a next milestone date.

Status Label Discipline

The most common failure in project updates is the wrong status label. Writers label projects "on track" to avoid difficult conversations, then surprise stakeholders when the timeline slips. Clear, honest status labels are a form of professional integrity.

Status Label	When to Use	What Readers Infer
On track	All milestones likely to hit on schedule	Continue current approach
At risk	One or more significant threats to timeline, budget, or quality	Attention needed, mitigation underway
Off track	Milestone will slip or deliverable compromised	Executive escalation, re-plan required
Blocked	Cannot proceed without external decision or resource	Immediate action needed from specific party
Complete	All committed deliverables shipped	Transition to steady-state

Use "at risk" earlier than feels comfortable. A project labeled "at risk" in week two that recovers by week four is remembered as well managed. A project labeled "on track" in week two and "off track" in week four is remembered as mismanaged.

"The status on a project update is a promise to your stakeholders that the words you use mean what they normally mean. Drift in those words is drift in your credibility." Ann Handley, Everybody Writes

Cadence and Timing

Different projects require different update cadences. Matching the cadence to the project type improves both stakeholder satisfaction and your own signal-to-noise ratio.

Project Type	Update Cadence	Best Day
Consulting engagement with weekly cycles	Weekly	Friday morning
Software development sprints	Every two weeks	End of sprint
Executive initiatives	Monthly with weekly exception updates	First Monday of month
Agency or client creative work	Weekly	Same day each week
Internal tiger team projects	Twice weekly	Tuesday and Thursday
Long-horizon programs	Monthly strategic + weekly tactical	Combination
Crisis or incident response	Daily or hourly as needed	Real-time

Send at a consistent day and time. Stakeholders who know the update arrives every Friday at 10 a.m. plan their reading around it. Erratic timing erodes the update's value.

Language Patterns That Build Trust

Small word choices shape how your update lands.

Weak Phrasing	Stronger Phrasing	Why
We are working on	We completed	Past-tense specific outcome
Making good progress	Shipped X, Y, Z this week	Named artifacts
Minor delay	3-day delay against original target	Precise magnitude
Some challenges	Specific risk named with owner	Transparency
Will need to discuss	Decision needed by [person] by [date]	Clear ownership
Should be fine	Resolution expected by [specific date]	Commitment
Hopefully	Likelihood assessment with rationale	Calibrated confidence
Moving parts	Specific dependencies named	Precision

"Every sentence in a business update either adds information or steals space. There are no neutral sentences." Stephen Pinker, The Sense of Style

Handling Bad News in a Project Update

Reporting that something is off track is the hardest update to write. Avoiding the truth almost always backfires. The update before the bad news goes out is the moment when your credibility compounds or erodes.

A straightforward structure works. State the bad news in the first line. Explain the cause in one sentence. Describe the impact specifically. State the action being taken and by whom. Give a specific date when more information will be available.

Do not apologize in the update itself unless the cause was specifically your team's error. Apologies mixed with status updates blur both.

Status: Off track. The launch will slip from December 1 to December 15.

Cause: Our QA cycle identified a data integrity issue in the new pipeline that requires fixing before release. The fix is straightforward but requires 10 business days.

Impact: The marketing campaign already booked for Dec 1-8 will need to be rescheduled. I have reached out to [name] in marketing to align on new dates.

Action: Engineering team is executing the fix. Daily standups added. Target fix completion Nov 25, QA validation Nov 28, revised launch Dec 15.

Next update: Nov 20 with fix status.

If anyone needs to escalate, I am available today between 2 and 5 PM.

This template keeps respect for the reader while telling the truth. It does not minimize, catastrophize, or obscure.

Project Update Emails for External Clients

Client updates have an additional consideration. The client is not just tracking status. They are also evaluating whether to continue the engagement. Your update is a small performance review each week.

Client updates should emphasize:

• Outcomes that connect to the client's business goals, not just activities you completed
• Visibility into risks before they become surprises
• Specific decisions needed from the client, with deadlines
• Proactive identification of scope changes and their implications

The tools and templates from Corpy on cross-jurisdiction business operations can be useful when updates involve international work, and the document workflows at File Converter Free help prepare the client-ready artifacts that often accompany project updates (PDFs, converted spreadsheets, branded reports).

Tracking Update Effectiveness

Professionals who send many project updates benefit from light metrics on their own performance.

Open rate. If your stakeholders are not opening your updates, the problem is usually the subject line, the send time, or the perceived irrelevance of previous updates.

Response rate on decision asks. If you asked for a decision last week and no one decided, you may be burying the ask too deep.

Time to response on risks flagged. When you flag a risk, how fast do stakeholders engage? Long delays suggest you are not flagging early enough or with enough specificity.

The productivity systems explored at When Notes Fly offer approaches to batching update writing, and cognitive research from What's Your IQ explains why stakeholders process short structured updates far better than long ones. For project managers juggling many updates across clients, a simple spreadsheet tracker of send times, read confirmations, and response rates often identifies improvements within a few weeks.

Making Project Updates a Professional Advantage

Most professionals send project updates reluctantly, treating them as overhead. The professionals who treat updates as a core craft of their work often become known as the people other teams copy when new project management templates are needed.

A reputation for clear, honest, well-structured updates compounds over years. It leads to being trusted with larger projects. It leads to being invited to lead cross-functional initiatives. It leads to being quoted in senior leaders' updates to their own stakeholders.

"You are always presenting to someone. The project update is that presentation, just without the slides." Roy Peter Clark, Writing Tools

The craft is not complicated. Four clear sections. Honest status labels. Specific numbers. Named owners on every risk and decision. Consistent cadence. Over time, this small discipline becomes visible to everyone you work with.

For related communication guidance, see our articles on how to write a project status update and internal memo template professional format.

References

1. Bernoff, J. (2016). Writing Without Bullshit. Harper Business. https://withoutbullshit.com/book

2. Handley, A. (2014). Everybody Writes. Wiley. https://annhandley.com/everybodywrites/

3. Pinker, S. (2014). The Sense of Style. Viking. https://stevenpinker.com/publications/sense-style

4. Clark, R. P. (2008). Writing Tools: 55 Essential Strategies for Every Writer. Little, Brown. https://www.poynter.org/

5. Project Management Institute. Communication Management Standards. https://www.pmi.org/learning/library/

6. Harvard Business Review. How to Write a Status Update That Actually Gets Read. https://hbr.org/2021/02/a-simple-way-to-communicate-effectively-at-work

7. Grammarly Blog. How to Write Professional Status Updates. https://www.grammarly.com/blog/business-writing/

8. Purdue Online Writing Lab. Business Writing Best Practices. https://owl.purdue.edu/owl/subject_specific_writing/professional_technical_writing/

Frequently Asked Questions

What should a project update email include?

A strong project update uses a four-section framework: status summary in one sentence, progress since last update in three to five bullet points, risks and blockers with specific mitigations and owners, and decisions needed or next steps with deadlines. Total length should stay under 200 words. Every section should be scannable in under ten seconds. The single most important element is an honest status label. On track, at risk, and off track are the three most common, and using them accurately builds stakeholder trust.

How often should you send project update emails?

The cadence depends on project type. Consulting engagements and agency work typically use weekly updates on the same day and time. Software development sprints use every-two-week updates. Executive initiatives often combine monthly strategic updates with weekly tactical ones. Crisis or incident response may require daily or even hourly updates. The key principle is consistency. Stakeholders who know the update arrives every Friday at 10 a.m. plan their reading around it. Erratic timing erodes the update's perceived value.

How do you report bad news in a project update?

State the bad news in the first line. Explain the cause in one sentence. Describe the impact specifically. State the action being taken and by whom. Give a specific date when more information will be available. Do not apologize in the update itself unless the cause was specifically your team's error. The straightforward approach preserves credibility. Minimizing or obscuring bad news almost always backfires when stakeholders feel they were not warned early enough. Honesty earlier is easier than honesty later.

When should you use the at risk status label?

Use at risk earlier than feels comfortable. A project labeled at risk in week two that recovers by week four is remembered as well managed. A project labeled on track in week two and off track in week four is remembered as mismanaged. The at risk label signals that one or more significant threats exist to timeline, budget, or quality, and that mitigation is underway. This gives stakeholders time to support you and signals professional transparency rather than hopeful vagueness.

How long should a project update email be?

Under 200 words for most audiences, under 60 words for executives. The temptation to write longer updates usually reflects the writer's desire to demonstrate effort rather than the reader's need for information. Executives in particular read short updates twice and long updates rarely once. The discipline of fitting an accurate update into a tight word count forces the writer to sort what matters, which is the real value of a good update. Brevity is the craft.

What phrases should you avoid in a project update email?

Avoid vague phrases like making good progress, minor delay, some challenges, should be fine, and hopefully. These sound like status reports but convey no actual information. Replace them with specific counterparts: shipped X and Y this week, 3-day delay against original target, specific risk named with named owner, resolution expected by specific date, and likelihood assessment with rationale. Every sentence in a business update either adds information or steals space. Cut sentences that add nothing.

Should you send separate updates to different stakeholders?

Often yes. Executives need a 60-word version. Internal team members need a working-level version with more detail on dependencies. External clients need a version that connects outcomes to their business goals rather than listing activities. Writing one update per audience takes more time but improves signal quality significantly. A common pattern is writing the detailed internal version first, then producing the executive version by deleting, and the client version by translating activities into business outcomes. This three-version approach typically takes 30 minutes per week per project.