Tristiks/Blog

Client Management

Client Status Update Email Templates (7 Situations)

By Suraj Rao9 min read

What You'll Learn

  • A good status update leads with one word for the overall status, then covers what's done, what's next, what you need from the client and the hours or budget used.
  • Send updates on a fixed day, keep them short, and give bad news early with a date and a plan rather than waiting until it can't be hidden.
  • Use the right template for the moment: routine weekly update, milestone, delay, blocked on the client, budget warning, retainer summary and project close.
Photo of hands typing on a laptop keyboard, beside the headline: client status updates that land

A client status update is a short, regular message that tells a client where their project stands: what's done, what's next, what you need from them and whether it's on time and on budget. It replaces "just checking in" emails from the client with information they didn't have to ask for.

Updates do more than keep clients calm. They create a written record of progress, flag problems while they're still small and make invoices easier to approve, because the client has watched the hours being used.

This post covers what every update should include, how to write one that gets read and seven copy-and-paste templates: the weekly update, a milestone, a delay, waiting on the client, a budget warning, a monthly retainer summary and the end of a project.

Why status updates matter

Most client frustration comes from not knowing what's happening. Communication problems are also a big reason projects fail: in PMI's 2013 Pulse of the Profession research on communications, respondents said ineffective communication was the primary contributor to project failure one third of the time.

For a freelancer or small agency, a weekly email is the cheapest fix there is. It takes 10 minutes, and it answers the questions a client would otherwise ask at the worst moment: on the invoice, or a week before launch.

How often to send depends on the engagement. As a rule, weekly suits most projects longer than a month, and twice a week or per milestone suits short ones. Our client management guide has a full table of rhythms for projects, retainers and ongoing support.

What every status update should include

Use the same structure every time, so the client knows where to look.

PartWhat it saysExample
Subject lineProject, type of update, date"Website redesign: weekly update, 20 Nov"
Overall statusOne wordOn track / At risk / Off track
DoneWhat was finished since the last update"Homepage design approved"
NextWhat happens before the next update"Build homepage and services page"
Needed from youSpecific asks, with dates"Feedback on the draft by Wednesday"
Hours or budgetUsed against the estimate"42 of 80 hours used"
RisksAnything that could move the date or cost"Copy for the About page not received yet"

One word for the overall status

Start with a single word, so the client knows the headline before reading anything else:

  • On track: the date and budget are safe.
  • At risk: something could move the date or budget if it isn't fixed this week.
  • Off track: the date or budget will change, and here's the new plan.

"At risk" is the most useful of the three. It gives the client a chance to help before the problem is real.

Include the hours, even on fixed-price work

On hourly work, the hours tell the client what the next invoice will look like. On fixed-price work, they show whether the scope is holding. If you're not sure how to compare hours used with work done, our guide to project budgets explains burn rate with a worked example.

Client status update templates

Change the details in brackets. Each template is short on purpose: a client should be able to read it in under a minute.

1. Weekly status update

Subject: [Project]: weekly update, [date]
 
Hi [Name],
 
Status: On track
 
Done this week:
- [Item]
- [Item]
 
Next week:
- [Item]
- [Item]
 
Needed from you:
- [Specific ask] by [day]
 
Hours: [42] of [80] estimated hours used.
 
Thanks,
[Your name]

Send it on the same day every week, even when there's little to report. "Quiet week, no blockers, still on track" is useful news.

2. Milestone reached

Subject: [Project]: [milestone] complete
 
Hi [Name],
 
Good news: [milestone, e.g. the design phase] is complete.
 
What's delivered:
- [Deliverable, with link]
- [Deliverable, with link]
 
What happens next:
- [Next phase] starts on [date], due [date].
 
Needed from you:
- Sign-off on [deliverable] by [date], so the next phase can start
  on time.
 
As agreed, I'll send the invoice for this milestone ([amount]) on
[date].
 
Thanks,
[Your name]

Asking for a written sign-off at each milestone helps later. If the client wants to change approved work, it's a new request, not a revision.

3. A delay on your side

Subject: [Project]: change to the [deliverable] date
 
Hi [Name],
 
Status: Off track
 
I want to let you know early that [deliverable] will be ready on
[new date] instead of [original date].
 
Why: [one honest sentence, e.g. the payment integration needed more
testing than I planned].
 
What I'm doing about it: [e.g. I've moved other work so this is my
priority this week].
 
What it means for you: [e.g. the launch date stays the same / moves
to (date)]. There's no change to the price.
 
I'm sorry for the change. I'll confirm progress on [day].
 
[Your name]

Give bad news as soon as you know it. A delay flagged two weeks ahead is a planning change. The same delay flagged the day before is a broken promise.

4. Blocked on the client

Subject: [Project]: waiting on [item]
 
Hi [Name],
 
Status: At risk
 
To keep [deliverable] on schedule for [date], I need:
- [Item, e.g. final copy for the About page]
- [Item, e.g. admin access to the hosting account]
 
If I have these by [date], we stay on track. After that, the
delivery date moves by the same number of working days the items
are late.
 
Thanks,
[Your name]

This is a factual note, not a complaint. If your contract or welcome email says late feedback moves the timeline, mention it. If it doesn't, it's worth adding next time; our guide to setting client boundaries has wording you can copy.

5. Budget warning

Send this the moment your tracked hours suggest you'll go over, not when you already have.

Worked example: a project has an 80-hour estimate. You've used 60 hours (75%), but only about half the work is done. At the same pace, the whole project will take about 60 ÷ 0.5 = 120 hours, 40 over the estimate. At $85 an hour, that's a $3,400 gap.

Subject: [Project]: budget check
 
Hi [Name],
 
Status: At risk
 
We've used [60] of the [80] estimated hours, and I estimate about
half of the work is complete. At the current pace, the project will
need around [120] hours in total.
 
The main reason is [e.g. the extra product pages added in week 3].
 
Options:
1. Keep the full scope: about [40] extra hours, roughly [$3,400],
   which I'll quote formally.
2. Keep to the budget: drop or postpone [items], which saves about
   [40] hours.
3. A mix: [option].
 
Could we agree which way to go by [date]? I'll keep work on the
agreed items going in the meantime.
 
[Your name]

If the overrun came from new requests, it's a change request, not a budget problem. Our guide to scope creep covers how to turn extra requests into paid change orders.

6. Monthly retainer summary

Subject: [Client]: [month] retainer summary
 
Hi [Name],
 
Here's a summary of [month].
 
Hours: [18] of [20] retainer hours used.
 
Work completed:
- [Item]
- [Item]
 
Still in progress:
- [Item], continuing into [next month]
 
Planned for [next month]:
- [Item]
- [Item]
 
The time report for the month is attached. If you'd like to change
priorities for next month, let me know by [date].
 
Thanks,
[Your name]

If the client regularly uses more hours than the retainer covers, raise it in this email rather than absorbing the extra. Our guide to retainers vs fixed-price projects covers how to handle overages.

7. End of project

Subject: [Project]: complete
 
Hi [Name],
 
[Project] is complete. Thank you for working with me on it.
 
Delivered:
- [Deliverable, with link]
- [Deliverable, with link]
 
Handover:
- Files and logins: [where, and how they were shared]
- Notes: [link to handover document]
 
Final invoice: [amount], sent on [date], due [date].
 
Final numbers: [76] hours against an estimate of [80].
 
If anything comes up in the next [two weeks], reply here and I'll
take a look. I'd also love to hear what worked and what I could do
better.
 
[Your name]

The last email is the one the client remembers. For everything that happens around it, from access removal to asking for a testimonial, see our client offboarding checklist.

Tips for status updates clients read

  • Lead with the status. One word in the first line. Details after.
  • Use dates, not "soon". "By Wednesday 26 November" can be planned around. "Soon" can't.
  • Make each ask specific. Say what you need, from whom and by when.
  • Keep it short. If an update is longer than a phone screen, move the detail into a link or attachment.
  • Send it on a fixed day. Predictability is half the value.
  • Share numbers. Hours used against the estimate, or work completed against the plan.
  • Put bad news first. Burying it in the fourth paragraph makes it look hidden.

Common status update mistakes

MistakeWhy it hurtsFix
Only writing when something is wrongEvery email from you feels like bad newsSend routine updates on a fixed day
Long paragraphsThe ask gets missedBullet points and a "Needed from you" section
No numbersThe invoice becomes the first surpriseInclude hours or budget used every time
Hiding a delayTrust drops when it comes outSay it early, with a new date and a plan
Vague asksNothing happensName the item, the person and the date

Where the numbers come from in Tristiks Grow

A status update is only as good as the numbers in it. Tristiks Grow keeps them in one place:

  • Hours against the estimate: give a project an estimated time and see the time tracked against it, with estimates on tasks too. See project time tracking.
  • What's done and what's next: the task board sorts tasks into Overdue, Today, This Week and Upcoming by due date, so the "Next week" list is mostly written for you.
  • A time report to attach: download a PDF time and activity report for a date range, or switch on Include report when you add tracked time to an invoice and the report for those dates goes with the invoice email. See time reporting software.
  • Invoices that match the updates: add the client's unbilled hours to an invoice in a few clicks, and hours already invoiced are locked so nothing is billed twice.

Frequently asked questions

How often should I send a client status update?

Weekly suits most projects longer than a month. For short projects, send one at each milestone or twice a week. For retainers, a short weekly note plus a monthly summary works well. Whatever you choose, agree it at kickoff and send it on the same day each time.

What should a project status update email include?

The overall status in one word, what's done, what's next, what you need from the client with dates, and the hours or budget used against the estimate. Add any risks that could move the date or the cost.

How do you tell a client a project is delayed?

As early as possible, in writing, with a short reason, the new date, what you're doing about it and what it means for them. Apologize once, keep the explanation to a sentence or two, and follow up when you said you would.

Should I send a status update if nothing has changed?

Yes. A short "no change, still on track, next update Friday" tells the client the project hasn't been forgotten and keeps the rhythm going. Skipping a week is often what prompts the anxious "any news?" email.

Wrap up

A good status update is short, predictable and honest: one word for the status, what's done, what's next, what you need and the numbers behind it. Send it on the same day every week, and send bad news the day you know it.

To see hours against each project's estimate and attach a time report to every invoice, try Tristiks Grow project time tracking free for 14 days.

Category: Client Management

Suraj Rao

Suraj Rao is the founder of Tristiks, the team behind Tristiks Grow and its desktop time tracker OneTrack. He writes about time tracking, client work and getting paid, and about DevOps, cloud and AI from years of building software.

All articles

Save time and money in one click

Tristiks Grow brings time tracking, clients, proposals, invoicing, and more into one place.

Free 14 day trial. No credit card required.