A routine progress note needs a different opening from a delay or an approval request. Keep the project name in the subject, then name the news or action. The client should understand why you sent the email before opening an attachment.
Routine weekly progress email
Use the routine message when work is moving within the agreed plan. Report a finished result rather than every task you touched. Include the next outcome and its date so the client knows what to expect.
Subject: [Project name] update for [date]
Hi [client name],
[Completed work] is ready. You can view it at [link].
I am now working on [next outcome], with delivery planned for [date].
No action is needed from you at this stage. The agreed scope, cost, and delivery date are unchanged.
I will send the next update on [date].
Thanks,
[your name]
Keep the no-action sentence only when it is true. If you need something, replace it with the item and deadline. Check scope, cost, and timing before saying they are unchanged.
If nothing was finished, replace the opening with the current state and what you are doing next. Do not invent progress to fill the template. For help choosing what belongs in a regular note, use the weekly client update guide.
Project delay email
Send a delay notice when the agreed date is no longer possible. Do not hold it until the next scheduled update. State the affected work first, then explain the cause and the effect on the client's plan.
Subject: [Project name] delivery date has changed
Hi [client name],
[Deliverable] will not be ready on [agreed date] because [confirmed cause].
The effect on your plan is [effect]. I am taking [next action] to address it.
I have not confirmed a revised delivery date. I will send the revised plan, or explain what remains unresolved, by [date and time].
[Action the client needs to take now, or confirmation that no action is needed.]
Thanks,
[your name]
Use the unconfirmed-date wording when you still need information. If you have a supported revised date, replace that paragraph with the date and any condition it depends on. Label an estimate as an estimate.
Add a brief apology when you broke a commitment. Keep the explanation factual, without blaming the client or describing every internal discussion. The advice on how to tell a client bad news covers responsibility and follow-up.
Email asking for approval
Use an approval email when you cannot proceed without a decision. Name the exact version under review and ask the person who can approve it. A request for general feedback is different from permission to begin the next stage.
Subject: Approval needed for [project name] by [date]
Hi [client name],
[Deliverable and version] is ready for approval at [link].
Please confirm whether I can proceed with [specific next step] using this version by [date and time, including time zone].
If changes are needed, please list them in [agreed reply channel] before that deadline.
I will wait for your approval before starting [dependent work]. A later decision will affect [delivery or booking affected].
Thanks,
[your name]
Choose a deadline based on the work that follows, not an arbitrary demand for speed. Replace the final sentence with the known effect of a late decision. Do not claim a delivery date will move unless that follows from the schedule.
Link directly to the version you want approved. Remove outdated attachments and explain where the client should answer. Silence is not approval unless your agreement explicitly defines it that way.
Scope change email
Use a scope change message before starting work outside the agreement. Separate the requested addition from the original work and explain the available choices. Follow the contract's approval process for changes to cost or obligations.
Subject: Decision needed on [project name] scope change
Hi [client name],
[Requested addition] is outside the agreed work of [original scope].
I can add [defined extra work] for [additional cost]. The delivery date would change from [current date] to [proposed date].
Alternatively, we can keep the agreed scope and [existing delivery plan].
Please confirm your choice through [agreed approval process] by [date]. I will not start the additional work without approval.
Thanks,
[your name]
Use confirmed estimates in the cost and date placeholders. If you need to assess the request first, say when you will send a proposal instead of filling those spaces with guesses.
Remove the date-change sentence if timing is unaffected, and say so directly. If your own estimate missed work already promised, explain that separately. Do not present your omission as a new client request.
Project finished email
Send a completion email when you have delivered the agreed work. Give the client the files and instructions they need to use it. Keep delivery separate from acceptance when a final review is still required.
Subject: [Project name] final delivery
Hi [client name],
I have delivered [completed agreed work]. The final files are at [link], and the handover instructions are at [link].
Please complete [acceptance step required by the agreement] by [date] using [agreed reply channel].
[Support included in the agreement] is available until [date]. For help, contact me through [support channel].
Thank you for working with me.
[your name]
Remove the acceptance paragraph if approval is already recorded. Include support terms only when agreed, and replace the support paragraph if there is no ongoing support. Check file access from the client's view before sending.
Keep invoices separate when they need their own payment instructions. The completion email should make the handover clear without adding an unexpected obligation.
Before sending your status update email to a client
Read the filled message without opening its links. The client should know the current state and their next action from the email alone. Use the advice on writing an update clients will read to remove detail that belongs in an attachment.
Check every placeholder, date, recipient, and link. Copy the subject into the subject field rather than leaving it in the body. Keep a dated record of the message and any resulting decision so nobody has to reconstruct the plan from memory.
For longer projects, keep an ordered update history alongside email delivery. The email thread problem explains why separate replies and inboxes make past decisions hard to find. A saved template helps you write the next message, while a shared record helps both people understand what was agreed.