Client report: a weekly update a client reads in two minutes

A short weekly update that says what worked, what didn't, and what the client needs to approve.

2 live examples

The example: Creative report, week 42

A weekly update with one decision to make

Creative report, week 42

Open the examplePassword: sample. The names and numbers are made up.

What to notice

  • Its first lines carry the news and the ask: the new video is the best ad in the account, and replacements need approval by Thursday.
  • The three best ads are ranked, each with its click rate and cost per sale.
  • It sits behind a password, the way a real one would. The password is "sample".

The prompt that starts one like it

Write this week's client report as a single HTML page. Client: [name]. What happened: [your notes or data]. Open with two sentences saying what changed and what you need from them. Then show what's working, what's slipping, and what happens next week, with dates. Keep it under a two-minute read, then publish it on sharable.link with a password.

The example: IT service report for Ostrander & Vale LLP

A monthly service report with two decisions

IT service report for Ostrander & Vale LLP

Open the exampleThe names and numbers are made up.

What to notice

  • Both decisions sit near the top in a box labeled "Needs your decision by Fri, Dec 11", each with its cost and a recommendation.
  • The three slow replies aren't buried: the summary says all of them came on November 16, during a 95-minute sign-in outage, and a note further down says what changed since.
  • Each of the three risks has a level and a "We suggest" line, and two of them point back to a decision by its letter.

The prompt that starts one like it

Turn these notes into this month's service report for [client] as a single HTML page: [ticket numbers, response times, what was updated, anything that went wrong]. Open with a short summary of how the month went and what I need them to decide, with a date. Put the decisions and their costs first, then requests and response times against earlier months, what was patched, the risks I'm watching, and next month's dates. Tables must restack on a phone. Then publish it on sharable.link with a password.

Search for a client report template and you'll mostly find blank layouts to fill in. Those help with structure, but the hard part of a report is deciding what to say. So here's a finished one to learn from. The weekly sample sits behind a password, given on this page, and a second, monthly sample opens without one.

Who it's for

Anyone who owes a client a regular update: agencies, freelancers, consultants, and account leads with several clients. It suits weekly check-ins and monthly service reports, when a full deck would be too much and a chat message too little.

If your client has asked "so what's happening with this?" more than once, a short, predictable report usually stops the question.

What a good one contains

The details below come from the weekly sample, a creative report for a made-up outdoor brand. Its opening does most of the work.

  • The headline and the ask, first. A busy client may read only this. If you need a decision, it can't sit at the bottom of page three.
  • What's working, with evidence. Three ads ranked, each showing its click rate and cost per sale. Showing the creative itself beats naming it, since the client recognizes their own work at a glance.
  • What's slipping, said plainly. "Clicks have dropped three weeks running" builds more trust than a report that's only good news. Raise a problem before the client finds it, and bring the fix with it.
  • Next week, in concrete steps. Each line names an action, and two of the three name a day. Your client can see what's coming, and you've made a small promise you can keep.
  • Nothing that only you care about. Hours logged, tasks closed and internal process stay out, because none of them tells the client whether the ads are selling shoes.

A weekly that takes longer than two minutes to read has turned into a document, and documents get saved for later.

Keep it consistent

Use the same sections in the same order every time, so the client knows where to look. In a Claude conversation, paste last week's page with this week's notes and ask for the same structure with new content.

Keep a running note during the week, even in rough bullets, because reports written from memory on a Friday afternoon go vague. Before you publish, check each figure against its source and reread the opening. It should still be true if the client reads nothing else.

Update the same page each week if the client just wants the latest, since the link never changes. Publish a new page each week if they want to look back, and link to the earlier ones.

How to send it

With a password. It names the client and their numbers. One password per client is easy to remember from week to week.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add Claude Connector

Already have the file? Upload it here.

More in client work

  • Client proposal: Scope, timeline and price for one named prospect, on a page they can open on their phone.
  • Project status report: A regular page for a client's steering group: where the project stands and what they must decide.
  • Marketing report: The month's spend, results and recommendations, as a dashboard your client can open in any browser.
  • SEO report: A monthly report that ties organic search to leads or sales, for the client who pays for the work.
  • Case study: One client's problem, what you did and what changed, with numbers a prospect can check.
  • Statement of work: The scope, deliverables, dates and fees for one job, written down before the work starts.
  • All use cases

Keep reading