Project Status Update Email: Examples for Teams and Clients

A status update should help someone understand the state of the work without attending another meeting. The reader usually needs to know what changed, whether the schedule still holds, and whether you need a decision.

Choose the detail for the audience. A teammate may need a technical blocker, while a client may need its effect on delivery.

An update when the work is on schedule

Subject: Help-center project update: 9 October

Hi team,

The navigation and first three articles are approved. We’re on schedule to send the remaining drafts on 15 October.

This week, we completed the search labels and checked the links in the onboarding section. Next week, we’ll finish the billing articles and test the mobile layout.

No decisions are needed today. The draft folder is linked below.

Thanks, Alex

“No decisions are needed” prevents readers from searching for an implied request. Use it only when that is true; don’t bury a request in an attachment.

An update when the schedule is at risk

Subject: Brochure update: decision needed on product photos

Hello Amira,

The text and layout are ready, but we are still missing the final product photos. If we receive them by Tuesday, we can keep the 16 October proof date.

Otherwise, we can send a proof with labeled placeholders on Friday or move the complete proof to the following week.

Which option would work better for your review?

Kind regards, Lee

This tells the client what the blocker changes and which choice is theirs. A vague “slight delay” can be harder to plan around than a specific revised date.

Keep updates consistent

Use the same project name and a recognizable date in the subject so people can find earlier reports. If you send updates weekly, avoid repeating every completed task from the beginning of the project. Include what changed since the last update.

Separate facts from estimates. “The draft is complete” and “We expect approval tomorrow” are different kinds of statements, even if they appear in the same paragraph.

When you describe when work began or how long it has lasted, practice since and for in work emails. Check that the wording also reflects whether the activity is still underway.

For completed actions, practise past simple versus present perfect in work emails. Compare a dated action such as “I sent it yesterday” with an update such as “I’ve sent it,” then check that the current status is still accurate.

If a decision changes the plan, update the shared schedule as well as the email. For a formal transition to another owner, use a project handover email. If you need information before you can write the update, see how to ask for a status update.