Project Update and Status Report Email Templates Clients Actually Read

Clients do not leave because a project is a week late; they leave because they found out by asking. A predictable status email, sent on the same day each week in the same format, is the cheapest way to look organised and to surface problems while they are small. The four templates below cover the weekly report, a milestone, a delay, and the closing email, all short enough to read on a phone.

Quick summary

• Same subject pattern every time: "[Project] update - week [N]" so it can be searched and filtered.
• Four fixed headings: Done, Next, Waiting on, Risks. Empty headings stay in with "none"; consistency is the point.
• Dates, not durations: "by Thu 6 Aug", not "in a few days".
• One decision needed, clearly marked, with your recommendation, or the words "no decisions needed this week".
• Sent from the project lead's name@yourdomain.com, with a shared projects@ address in CC so a colleague can pick up the thread if the lead is away.

The format that gets read

• Same subject pattern every time: "[Project] update - week [N]" so it can be searched and filtered.
• Four fixed headings: Done, Next, Waiting on, Risks. Empty headings stay in with "none"; consistency is the point.
• Dates, not durations: "by Thu 6 Aug", not "in a few days".
• One decision needed, clearly marked, with your recommendation, or the words "no decisions needed this week".
• Sent from the project lead's name@yourdomain.com, with a shared projects@ address in CC so a colleague can pick up the thread if the lead is away.

Template 1: weekly status report

Subject: [Project] update - week [N] of [total]

Hi [First name],

Status: [On track / At risk / Behind] for [launch or completion date].

Done this week
- [item]
- [item]

Next week
- [item], by [date]
- [item], by [date]

Waiting on you
- [item], needed by [date] to protect the [milestone] date

Risks
- [risk and what we are doing about it, or "none"]

Decision needed: [decision, with recommended option], by [date]. (Or: no decisions needed this week.)

Budget / hours: [used] of [total] ([percentage]).

Reply to this email with anything; I read replies the same day.

[Full name]
[Title], [Company]

Template 2: milestone complete

Subject: [Project]: [milestone] complete

Hi [First name],

[Milestone] is done and ready for you to review: [link or attachment].

What to check: [two or three specific things, e.g. the wording on the pricing page, the mobile layout of the booking form].
How to give feedback: reply to this email or add comments in [tool]; one consolidated list is easiest for us.
By when: [date]. If we hear nothing by then we will treat it as approved and move to [next milestone], so we can hold the [completion date].

Next up: [next milestone], starting [date].

Thanks,
[Full name]

Template 3: delay or risk notice

Subject: [Project]: [milestone] date moving from [old date] to [new date]

Hi [First name],

I want to flag a change before it becomes a surprise. [Milestone] will land on [new date] rather than [old date].

Why: [one honest reason, e.g. the supplier delivered the wrong part / the approval on [item] came four days later than planned / we underestimated [task]].

Effect on the overall date: [none / [completion date] moves to [new date]].
What we are doing: [one or two specific actions].
What would help from your side: [item, or "nothing needed"].

If the new date causes a problem, tell me today and we will look at [option, e.g. re-ordering the remaining work to protect [priority]].

Sorry for the change,
[Full name]
[phone]

Template 4: project closure and handover

Subject: [Project] complete - handover and next steps

Hi [First name],

[Project] is complete. Thank you for the trust and the quick decisions along the way.

Delivered
- [item]
- [item]

Handover
- Files and logins: [where they are]
- Documentation: [link]
- Warranty / support: [what is covered, until when, how to ask: support@[yourdomain].com]

Final invoice: [number] for [amount], attached, due [date].

Optional next steps we discussed: [item], [item]. No action needed unless you want to pick one up.

If you were happy with the work, I would be grateful for a short review; I will send a separate note with a link.

Best regards,
[Full name]
[Title], [Company]

Timing

Send the weekly update on the same weekday and hour every week, ideally Thursday or Friday morning so the client can act before the weekend. Send a milestone email the day it is ready, not with the weekly report. Send a delay notice the moment you know, and before the client could have noticed. Send the closure email within two days of delivery, together with the final invoice, so the project ends on a clear note. Store every update in a folder per project; the thread is your record if scope or dates are ever disputed.

Mistakes that make updates useless

• Skipping a week because "nothing happened". Nothing happening is exactly what the client wants to know about.
• Burying a delay in paragraph four of a cheerful update.
• Updates with no dates, so nobody can tell whether "next week" slipped.
• Sending a 900-word narrative instead of headings; it will not be read on a phone.
• Asking for three decisions at once; pick the one that unblocks the most work.
• Updates from a personal address or from whoever was free that day, so the client has three threads with three people.

Common questions

How often should I send status updates?

Weekly for projects longer than a month, twice weekly during a launch, and one email per milestone for short jobs. Ask the client at kick-off which day suits them and stick to it.

What if the client never replies to updates?

That is normal and often means they are satisfied. Make sure any decision or dependency has a clear "if we hear nothing by [date]" default so silence does not stall the project.

Should I use a project tool instead of email?

Use both. Tools hold the detail; the weekly email is the summary the client actually reads and the record you can forward to their boss. Keep the email complete on its own.