Weekly client status report template

A client status report should reduce questions. Too many reports create new ones.

Long decks, copied task lists, and optimistic traffic lights hide the information a client actually needs: what changed, what happens next, and what requires their attention.

Use the same format every week

A useful update has six sections.

1. Summary

Two or three sentences. State the overall position without theatre.

The campaign build is on track for the 18 August launch. Creative is in final review. Tracking setup is waiting for access from the client analytics team.

2. Completed

List outcomes, not activity.

Good:

• Homepage concept approved
• Tracking plan signed off
• First 12 campaign assets delivered

Weak:

• Attended meetings
• Worked on designs
• Sent emails

3. Next

Show what the agency will finish before the next update.

4. Decisions needed

Put client actions in one place. Include an owner and deadline.

Decision	Owner	Needed by	Effect if late
Approve final copy	Client lead	Tuesday	Creative delivery moves

5. Risks and changes

State what changed, how serious it is, and what is being done.

Do not hide a risk until it becomes an issue. Clients are usually more comfortable with an early problem and a clear response than a late surprise.

6. Time, budget, or scope

Use the commercial measure appropriate to the engagement:

• hours used and remaining
• retainer position
• approved change requests
• review rounds remaining
• milestone fee status

Track time beside the client work so the report does not require a separate reconstruction.

Build the report from the work

The project board, decision log, meeting notes, and time entries should contain everything needed.

If the project lead must message six people to prepare the update, the source of truth is incomplete.

An AI agent can prepare a first draft from the latest tasks, notes, blockers, and decisions. A person should still review the message, add judgment, and own what goes to the client.

Keep the report visible

Publish the update in the shared client space. Send a link rather than copying several versions into email and chat.

Keep previous updates. The history becomes useful when someone asks when a decision changed or a risk first appeared.

A reusable template

Copy this:

Overall status

One honest paragraph.

Completed this week

Next week

Decisions required

• Decision — owner — due date

Risks or blockers

• Risk — response — owner

Scope and time

The update should take minutes to review. If it takes 20 minutes to understand, it is probably trying to replace the project itself.