The client report that actually gets read

The monthly report is the most-produced and least-read artefact in social media work. Twelve slides of charts, an impressions number nobody can act on, and a client who skims for the one line that says whether this is working.

That skim is the whole document. Everything else is you demonstrating effort, which is a bad thing to be paid for and a worse thing to be judged on. A report is not evidence of work; it is an instrument for making the next month's decisions.

Here is the version that gets read, and the parts to delete.

Start with the answer

The first line of the report answers the question the client actually has: is this working, and what are we changing?

Not "here's what we did in March." Something like:

March: the customer-story posts outperformed everything else by a wide margin, so April shifts to two of those a month and drops the industry-commentary slot. One post drove 14 profile visits and 3 inbound messages — the highest of the year.

Everything after that first paragraph is support for a claim already made. If a client reads only the top of the page, they have the answer, and they will trust the rest more for not having to hunt for it.

The one-page structure

Five blocks, one page, same order every month. Consistency matters more than completeness — a report whose shape changes each month cannot be compared with the last one, which is most of what a report is for.

1. The verdict. Two or three sentences. Working, not working, what changes.

2. What went out. Volume and mix, stated plainly. "11 posts: 4 customer stories, 3 product, 2 opinion, 2 hiring." This is the only place effort belongs, and one line is enough.

3. What worked, with the actual post. Not a chart — the top two posts, embedded or quoted, with one sentence on why you think each landed. Clients engage with their own content far more than with any metric about it, and "why it landed" is the part they cannot get from a dashboard.

4. What did not, and the hypothesis. The block most people delete, and the one that builds the most trust. A named underperformer with a specific reading — "the two product posts led with the feature rather than the problem" — proves you are reading results rather than collecting them.

5. Next month, and what you need. Three to five bullets of what you will do, plus an explicit list of what you need from them and by when. This is where the report stops being a rearview mirror and starts causing something.

Which metrics to keep

Report metrics the client can act on and that are plausibly caused by the work.

Keep:

• Reach or impressions, as context only, one number, no chart.
• Engagement rate, because it is comparable across post sizes in a way raw likes are not.
• Profile visits and follows from content — the nearest honest proxy for "people wanted more."
• Anything countable that touches pipeline: inbound messages, demo requests, link clicks to the page that matters, applications for an open role.
• A qualitative line. Who engaged, not how many. "Two heads of engineering at target accounts commented" outranks a thousand impressions and no report format captures it automatically.

Drop:

• Follower count as a headline. It moves slowly, it is easy to game and it rarely causes anything.
• Every chart with fewer than three months of data. Two points is not a trend; presenting it as one trains the client to over-react to noise.
• Platform-native "engagement scores." Different definitions per platform and not comparable.
• Anything you cannot explain the cause of. If you cannot say why it moved, it is decoration.

Reporting a bad month

Every account has them, and how you report the third bad month determines whether there is a fourth.

Three rules:

Say it in the first line. Burying a bad month in slide nine reads as concealment when it is discovered, and it always is. Leading with it reads as control.

Distinguish the two kinds of bad. "The content underperformed" and "we published four posts instead of eleven because material never arrived" are entirely different problems with different owners. Conflating them is either taking blame you do not deserve or hiding a dependency that needs fixing. Say which one it was, without editorialising.

Bring a change, not a reassurance. "We'll keep at it" is what a client hears as nothing. One specific alteration, with what you expect it to do, is what keeps the next month funded.

The failure mode worth naming: smoothing a bad month by finding a metric that happened to go up. Everyone can tell, and it costs more credibility than the bad month did. If the data is thin, say the data is thin — honest measurement survives a quarter of noise far better than a curated one does.

Frequency and format

Monthly, not weekly. Weekly reporting on social is mostly noise and turns into a treadmill that consumes bucket-four time you are not being paid for.

One page, in the body of an email or a shared doc. Not a PDF attachment, not a slide deck, not a dashboard link. The report should be readable on a phone in ninety seconds without a login. Dashboards fail as reports for one reason: a dashboard shows numbers, and a report makes an argument.

Quarterly, go longer. Once every three months there is enough data for an actual trend, and that is the meeting where you discuss strategy, scope and rate. The monthly one-pager is not the place for that conversation.

The compounding benefit

There is a second reason to write reports this way, and it shows up months later.

A year of one-page reports that each name a hypothesis and a result is an argument for your rate that no proposal can match. It is also the record that settles disagreements about what was agreed, which is the same reason approvals need a trail. Reports written as decisions accumulate into evidence; reports written as dashboards accumulate into nothing.

Across a book of clients this is exactly the part that decays under load — the fifth client's report gets written at 11pm and quietly becomes a metrics dump. SelfSM keeps what was published, what was approved and what it produced attached to each brand, so the monthly report is assembled from a record rather than reconstructed from memory.

FAQ

What should be in a social media report for a client? A verdict in the first two sentences, what went out, the top posts with why they worked, what underperformed and your hypothesis, and next month's plan with what you need from the client. One page, same structure every month.

Which social media metrics actually matter to clients? Engagement rate, profile visits and follows from content, and anything countable that touches pipeline — inbound messages, demo requests, relevant link clicks. Follower count and raw impressions are context at best and misleading as headlines.

How often should I report to a social media client? Monthly for the one-pager, quarterly for the longer strategic review. Weekly reporting on social is mostly noise and consumes unbilled time without improving decisions.

How do I tell a client a month went badly? In the first line, distinguishing content that underperformed from work that could not happen because material never arrived, and paired with one specific change you are making. Burying it reads as concealment; leading with it reads as control.

Should I send a dashboard link instead of a report? No. A dashboard shows numbers; a report makes an argument about what to do next. Clients who receive dashboard links stop opening them within about two months.