Use this template when the update rhythm is already defined and you need a repeatable message structure.

It works best for active projects where the client needs visibility without being overloaded by internal details. This page is most useful as the execution asset that supports Client Status Update Workflow for Freelancers and Consultants, not as a standalone communication fix.

What this template is for and not for

Use it for:

  • recurring project updates after the communication rhythm is already agreed,
  • situations where the client needs one clear summary plus one clear next action,
  • projects where progress, blockers, and approvals need a repeatable format.

Do not use it for:

  • first-time kickoff communication,
  • scope-change negotiation,
  • long retrospective reports,
  • replacing the live project record itself.

What this template should help prevent

  • vague updates that reassure but do not clarify anything,
  • reactive client check-ins caused by inconsistent communication,
  • approvals getting buried in long email threads,
  • progress notes living only in your head.

When to use it

  • once per week for active projects,
  • at the same point in the week whenever possible,
  • after you review the live project record.

If you still have not defined the communication rule, start with Client Status Update Workflow for Freelancers and Consultants. This page should not be your first entry point for communication strategy.

Before you send it

Check these first:

  • the project record is current,
  • the milestone status is honest,
  • any client action has a date,
  • one approval owner is named if review is required.

Weekly status update template

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

Hi [Client Name],

Here is this week's project update.

1. Progress this week
- [completed item]
- [completed item]

2. Current status
- [on track / at risk / blocked]

3. Blockers or dependencies
- [what is blocked, delayed, or waiting]

4. What we need from you
- [feedback / approval / files / decision]
- Needed by: [date]
- Approval owner: [name]

5. What happens next
- [next milestone or action]
- Expected timing: [date or range]

6. Notes
- [optional implementation note, risk, or reminder]

Thanks,
[Name]

How to use it well

  • Keep the format stable so the client learns where to look.
  • Name one clear client action if a response is required.
  • Link to the relevant file, portal, or review point instead of over-explaining in the message itself.
  • Log changed dates or decisions back into the system of record after sending.

Small implementation notes

  • Keep “Progress this week” factual. Do not pad it to make the week sound bigger than it was.
  • Keep “Current status” to one honest label. If the project is blocked, say blocked.
  • Put the real deadline under “What we need from you” instead of hiding it in Notes.
  • If you use a portal or workspace, let the template point to that location rather than trying to duplicate the full review context in email.

Common misses or edge cases

  • If there is no client action this week, say that clearly rather than leaving the expectation fuzzy.
  • If several people can review, still name the final approval owner.
  • If the project is blocked by missing client input, state the dependency directly and calmly.

If the update needs a decision

When the message asks for approval, feedback, files, or a timing decision:

  • name the exact action needed,
  • name who should respond,
  • give the date or review window,
  • avoid mixing that request with a new scope discussion.

If the message is starting to include scope negotiation, switch to Change Request Workflow for Freelancers and Consultants instead.

When the update is ready

The template has been used well when:

  • the update explains current status without extra clarification,
  • required client actions are visible,
  • the message matches the live project record,
  • you can reuse the same structure next week without rewriting it from scratch.

What to do next