Client Reporting
How to Present Bad News in a Client Report
Every account has a bad month eventually. What actually damages client trust usually isn't the dip in the numbers — it's finding out the person managing the account either hid it or seemed surprised by it.
Lead with it, don't bury it
Burying a bad number in the middle of a report, hoping it slides by, almost always backfires — clients notice, and now they're wondering what else might be downplayed. Putting it up front, plainly, signals you're not afraid of the number and you're already on it.
Explain the cause, specifically
Vague explanations read as excuses. Specific ones read as competence, even when the news is bad.
Better: "A platform algorithm change on the 12th cut our organic reach roughly in half — we saw the same pattern across several other accounts too."
Always pair the number with a next step
A bad number with no response attached leaves the client to wonder if you've even noticed. The plan doesn't need to be elaborate — it needs to exist and be stated plainly.
Don't oversell the recovery
It's tempting to promise things will bounce back next month to soften the moment. If they don't, you've now had two bad months and a broken promise, which is worse than one bad month handled honestly.
Clients rarely leave over a single bad month. They leave when they feel like they can't trust what they're being told — a bad number delivered honestly and specifically usually builds trust, even though it feels like the opposite in the moment.
The pattern that actually matters
One rough month, framed well, is a non-event. A pattern of rough months with the same vague explanation each time is a real problem — and no amount of good framing fixes that. Honest reporting only works if the plan you describe each month is actually followed through on.
Consistent reporting, even in the tough months
FixiWeb delivers the same reliable report every period, good months and bad, so nothing quietly gets skipped when the numbers aren't great.
Get Early Access