Agencies
Monthly marketing report: what to include and what to cut
How to build a monthly report someone actually reads: which numbers go in, in what order, how much writing it needs, and which questions it has to answer.
Also available in: Português · Español
The monthly report is the most produced and least read document in marketing. The cause is almost never the design: it's that it answers questions nobody asked, and leaves the three that matter unanswered.
The questions it has to answer
Before picking a single number, decide which questions the document will settle. In almost any operation they're these:
How much was invested and what came back? The headline number, no detours.
Did it improve or worsen against last month, and why? A comparison without a cause settles nothing.
What was done, and what effect did it have? The month's decisions, with their outcomes.
What happens next month? The concrete commitment.
A report that answers those four in two pages beats a thirty-page one that leaves them implicit.
What goes in and what doesn't
What goes in is what can change a decision. Everything else comes out.
In practice that means: spend, results, cost per result, and how those three moved across the months. Then the breakdown by channel and by campaign, but only down to the level someone will actually look at.
What's almost always surplus: Ads Manager screenshots, full campaign lists including ones that barely spent, reach and impression metrics with no context, and a "next steps" section copied from last month.
A useful test: for each block of the report, ask what the reader would do differently if that number were double. If the answer is "nothing", the block adds nothing.
Order matters
The structure that works starts at the conclusion and descends into detail, not the other way around.
First, three or four lines of interpretation: how the month went, why, and what's next. Then the headline numbers. Then the breakdown. Appendices last, for anyone who wants to verify.
This respects how people actually read: most read the first screen and skim the rest. If the conclusion is on page twenty-two, it reached nobody.
Compared to what
One decision defines the document's usefulness: what the month gets compared against.
Against last month is the most common and the most misleading, because months have different numbers of business days, commercial dates and seasonality.
Against the same month last year is better for seasonal businesses, and requires having the data.
Against target is the most honest when a target exists and was agreed. When it doesn't exist, say so rather than inventing a comparison that happens to look favorable.
What matters is picking one basis and keeping it. Changing the comparison basis to suit the month is the fastest way to lose credibility.
The bad month
Every report eventually meets a month worse than the last, and how it's presented defines the relationship.
What works: say it in the first line, give the concrete cause and the plan. "Cost per lead rose twenty-two percent; the main cause was creative saturation after eight weeks live; three new pieces are in production for week one."
What doesn't work: burying it on page eleven, surrounding it with metrics that went up, or explaining it with "the algorithm changed."
A bad month explained with cause and plan builds more trust than a good month presented without context. The reader knows bad months exist; what they're judging is whether the team saw it coming.
Who reads it changes the document
The same month needs different reports depending on who receives it, and trying to serve everyone with one produces a document that serves nobody.
The business owner wants to know whether the investment is justified. Three numbers and the trend; the ad set breakdown is noise to them.
The marketing lead wants to know what to move. The breakdown, the comparisons between campaigns, what's working.
The operations team wants full detail, and that detail lives better in a dashboard than in a PDF.
The practical answer isn't writing three documents: it's writing one in layers — conclusion on top, detail below, appendix linked — and letting each reader stop where it serves them.
The metric-that-went-up trap
There's a quiet vice in monthly reports: leading with whatever number rose.
If cost per result got worse but reach grew, it's tempting to open with reach. Nobody lied, and the report still misinforms — because the reader concludes the month was good.
The discipline that prevents it is deciding the headline metrics before the month, not after seeing the results. Pick three or four, report the same ones every time, and whether they rise or fall they occupy the same place in the document.
It's uncomfortable in bad months and it's exactly what builds trust across a year.
The report that builds itself
The real cost of the monthly report isn't writing it: it's gathering the data. Exporting from three platforms, consolidating into a spreadsheet, checking the periods line up, building the charts.
That work repeats identically every month and is where most of the time goes. When the numbers arrive on their own, what's left is the part that actually requires judgment — the interpretation, the cause, the plan.
Worth measuring once: how many hours a month the collection consumes, multiplied by the number of clients. The figure usually surprises.
The section everyone copies from last month
"Next steps" is the part of the report most likely to be recycled verbatim, and readers notice faster than writers expect.
The fix isn't writing more — it's writing less, and specifically. Two or three items, each one something that can be verified as done or not done by the next report. "Optimize campaigns" fails that test. "Replace the three creatives that have been live since July" passes it.
A side effect worth having: a report whose commitments are verifiable forces the next report to open by saying whether they happened. That single habit does more for the document's credibility than any amount of design.
A minimum format that works
For anyone building theirs from scratch, this structure covers most cases:
One page of interpretation answering the four questions. A table with spend, results and cost per result by channel, with the chosen comparison. A chart of the last six months. A short list of what was done and what's next.
Everything else is an appendix, and the appendix can be a link to a dashboard instead of twenty pages of screenshots.
For the discipline of separating what decides from what merely moves, see vanity metrics.
If the document goes to a client rather than an internal team, see how to present results to a client. And for the structure of a report that updates itself, see the paid traffic report.
Frequently asked questions
How long should a monthly report be?
As long as it takes to answer three or four questions. A thirty-page report doesn't get read, and what doesn't get read doesn't inform.
Does the monthly report replace the weekly one?
No. The weekly one corrects course; the monthly one evaluates decisions. They're documents with different jobs.
Should I just send the dashboard instead?
The dashboard shows the numbers; the report says what they mean. The dashboard doesn't replace the interpretation, it makes it verifiable.
What do I do when the month was bad?
Say it in the first line, with the cause and the plan. A bad month explained builds more trust than a good month presented without context.