Your clients don't read your reports. Send this instead

Your clients don’t read your reports because a report shows data, while a client wants a decision. It also lands weeks after the moment to act, and it lives in a PDF or a dashboard instead of the place where they spend their day. Send them a short written update every week, in the channel they already use, that says what moved, why, and what you are doing about it.

How do you know your clients aren’t reading your reports?

Clients don’t write back to say they skipped the PDF. The signs are quieter:

• You send the report and get no reply, or a “thanks!” within thirty seconds.
• The monthly call opens with questions the report already answered.
• The client asks you to “just send the topline” or “tell me what I need to know.”
• Someone on their side forwards a single chart to their boss and ignores the other eleven pages.

AgencyAnalytics, which sells a client reporting platform, lists almost the same signals in its own guide to unread client reports, including clients who ask for a summary over Slack or email instead of opening the report. When a dashboard vendor writes a full guide about unread reports, the problem is widespread.

Why do clients ignore the monthly report?

It shows data, not decisions

A typical report is a collection of answers to questions the client never asked: sessions, users, bounce rate, top pages, channel split, twelve charts with arrows. The client opens it with one question in mind, “is this working and do I need to do anything?”, and the report makes them dig for the answer.

People skim. In Jakob Nielsen’s analysis of 45,237 page views (2008), users read about 20% of the text on an average page. Your report gets the same treatment, so whatever the client needs to know has to sit in the first lines they read. In most reports, the first lines are a logo and a date range.

It arrives after the moment to act

A monthly report on October’s numbers goes out in the first week of November. If paid search started bleeding on 9 October, the client hears about it nearly a month later, from a chart, after the budget is spent. Either you already called them about it, which makes the report redundant, or you didn’t, which makes the report an awkward confession.

Problems happen on Tuesdays. Monthly reporting is too slow to be the place where a client learns about them.

It lives outside where the client works

A PDF attachment or a dashboard link asks the client to stop what they are doing, open something, and switch into analysis mode. Whatever requires a click and a context switch gets postponed, and postponed reports become unread reports.

The client’s working day happens in Slack, Teams, email threads or WhatsApp. The message that gets read is the one that shows up there, readable in the preview, without opening anything.

What clients actually want from you

Strip the report down to what a client does with it, and three questions are left:

1. What moved? The one or two changes that matter this week, in plain numbers.
2. Why? Your best explanation, stated with the confidence you actually have. “Probably” is fine. Silence is not.
3. What are we doing about it? The action you are taking, or the decision you need from them.

Everything else is reference material. It belongs somewhere the client can find it if they want to check your work, not in the message they read on Monday morning.

This is also where the agency’s value shows. Anyone can export a chart from GA4. Saying “organic is down 12% because the pricing page lost its ranking after the redesign, we are restoring the old title tags today” requires judgment, and judgment is what the client pays you for. A report full of charts hides that judgment. A three-line update puts it up front.

Send this instead: a short weekly written update

The alternative is simple to describe and takes discipline to keep:

• Weekly, on the same day, so it becomes a habit on both sides. Monday morning works because it covers a full week and sets up the next one.
• Written, in sentences, short enough to read in the notification preview. No attachment.
• In the client’s channel, wherever they already talk to you: a shared Slack channel, a Teams chat, an email thread they actually reply to.
• Led by the change, then the reason, then the action. Numbers back up the story.
• Ending with one question that asks for a decision, not “let us know if you have any questions.”

A quiet week gets a quiet update: “Nothing unusual, traffic and leads in line with the last four Mondays, we keep going with the plan.” That line has value too. It tells the client someone is watching.

An example structure

The update below is an illustrative example written for this article. The client, the numbers and the causes are made up to show the format.

Week of 5 October, Acme Outdoor (illustrative example)

What moved: online orders were up 14% on the previous week, almost entirely from Google Ads. Organic sessions were down 9%.

Why: the autumn sale campaign went live on Tuesday and is converting better than the summer one. The organic drop comes from two blog posts that fell off page one after last week’s rewrite.

What we’re doing: shifting €300 of the weekly budget from brand search to the sale campaign through Sunday. Restoring the original intros on the two posts today.

One question for you: the sale ends Sunday. Do you want to extend it by a week, given the numbers?

Full data in the usual dashboard if you want to dig.

A client can read it on their phone between two meetings and reply “yes, extend it”. The agency has a decision on record by Monday lunchtime.

Why the weekly update works where the report fails

	Monthly PDF or dashboard link	Weekly written update
What the client sees first	A cover page or a grid of charts	The change that matters
Interpretation	Left to the client	Written by you
Delay before a problem surfaces	Up to five weeks	A few days
Where it lands	Attachment or external link	The channel they already use
Effort to read	Open, scroll, interpret	Read the preview
What it invites	Silence, or “thanks!”	A reply with a decision

The update also changes what the monthly call is for. When the client already knows what happened week by week, the call stops being a slow read-through of charts and becomes a conversation about what to do next.

The cost: writing it every week, for every client

The honest objection is time. Writing a good update means opening GA4 for each client, comparing the week with the right baseline, working out why something moved, and putting it in plain words. For five clients that is a slow Monday morning. For fifteen it is a day.

For a handful of clients, write it by hand until you know what a good update looks like for each. Past that, automate the first draft. We compared the options for getting GA4 numbers into Slack, from a forwarded email to a dedicated tool, in How to send a GA4 weekly report to Slack. For the full process (what to include, cadence, formats and tools), see our client reporting guide for agencies.

This is the job we built Dialytics for. It reads your client’s GA4 and posts a weekly digest in Slack every Monday morning: what moved, why it probably moved, and the one point worth your attention. Between Mondays it only speaks up when a number is unusual for that day of the week. Anyone in the channel can mention the bot in the thread to ask a follow-up, and it remembers previous weeks. You still add the judgment only you have; the digest does the digging.

Start with one client next Monday

Pick the client whose reports get the least response. Next Monday, before you touch the monthly deck, send them five lines: what moved, why, what you are doing, one question. Do it four Mondays in a row and count the replies. That count says more about your reporting than any open rate.