Monthly Client Reports That Clients Actually Read
Short answer: Most agency reports are written to demonstrate effort, which is why they're long and why they go unread. Clients want three questions answered: did we get what we're paying for, what happens next, and is anything needed from us. A report that answers those in one page gets read; a fourteen-page deck of activity gets skimmed and forgotten, and the effort it demonstrates goes unnoticed anyway.
Why long reports fail
They're built around what you did rather than what the client got. Activity lists, task counts, hours by category. All of it is evidence of effort and none of it answers whether the client's situation improved.
They also arrive too late to be useful. A report on last month lands mid this month, describing decisions already made. By the time the client reads it, nothing in it is actionable.
If your report exists to prove you were busy, the client didn't need a report — they needed to be able to see the work as it happened.
The one-page structure
1. What you got this month
Outcomes and deliverables, not tasks. Three to five lines. "Homepage rebuilt and live" rather than "completed 23 tasks in the website workstream."
2. What's next
The next month's focus in three lines. This is the section clients actually read, because it's the only forward-looking part.
3. What we need from you
Named, with dates. Most agency delays trace to something outstanding on the client's side, and most clients genuinely don't know what's blocking. Putting it in the report once a month recovers real time.
4. Anything worth flagging
Risks, changes, decisions coming up. Optional, and only when there's something real.
That's it. If it takes more than twenty minutes to produce, it's too detailed, and the extra detail is going unread.
Where numbers belong
Performance metrics belong in reports where the client bought a metric — paid media, SEO, lead generation. In those cases lead with the number and its trend.
Where the client bought delivery rather than a metric, activity counts add nothing. "Completed 34 tasks" invites the question of whether 34 is good, which you can't answer.
The better version of a report
The strongest position is that the monthly report contains no surprises, because the client has been able to see the work all month. Then the report is a summary of something known rather than the first time they're finding out — and it takes ten minutes because the record already exists.
That also removes the awkward version of this problem: a month where less happened than usual, where the report becomes an exercise in making thin activity look substantial.
Frequently asked questions
What should be in an agency monthly client report?
What the client received this month, what's happening next month, what's needed from them, and anything worth flagging. Outcomes rather than task counts, and short enough to be read in two minutes.
How long should a client report be?
One page. If it takes more than twenty minutes to write, it's more detailed than anyone will read, and the additional effort produces no additional credit.
Should client reports include hours worked?
Only where the engagement is priced by time. On fixed-fee work, hours invite scrutiny of something that isn't the basis of the price.
How do I make reports easier to produce?
Keep the underlying record current so the report is a summary rather than a reconstruction. Most report effort is archaeology — working out what happened — not writing.
The short version
One page. Got, next, needed from you. Outcomes not activity. Twenty minutes maximum.
And the best report is one the client could already have read for themselves. See how — 7 days for $1.