What this template is for
Use the template for the report a marketing team sends to its leadership or its client each month, and for the version the team itself reads at its monthly review. The shape is fixed on purpose: a summary with the decisions at the top, results against targets, performance by channel, experiments and learnings, risks, and next month's priorities. The reader who stops after the first section has the decisions; the reader who continues has the evidence for them.
The report is a reporting document, not a dashboard and not an analysis. A dashboard answers "what is happening now" for whoever looks; the dashboard design guide covers how to build one, and the report draws its numbers from it rather than duplicating it. Channel teams have their own deeper reports, which this one summarises: the social media reporting guide and the SEO KPIs and reporting guide describe the channel-level versions, and one line per channel is what reaches this page. The results table is a flattened KPI tree: outcome first, drivers beneath it, so that a miss can be traced to its cause.
The template
The report is a set of short sections, two of which are tables. Keep the order; the summary is written last and placed first.
Report sections
| Field | What to write |
|---|---|
| Period, author and audience | The month, who wrote the report, who it is for, and the date it was sent |
| Summary | Three to five sentences: the headline result against target, the main reason, the one thing that changed, and what is being decided |
| Decisions | The decisions made this month and the decisions the reader is asked to make, each with an owner and a date |
| Results against targets | The results table below: outcome KPIs first, then drivers |
| Channel performance | The channel table below: one line per channel with spend, the channel's own KPI, the change and a one-line explanation |
| Experiments and learnings | Tests concluded this month with the result and the decision; tests running; what was learned that changes the plan |
| Risks and issues | What threatens next month's targets, what broke this month and whether it is fixed |
| Next month | The priorities for the coming month and the targets they serve |
| Definitions | Where each metric is defined and sourced, so that the numbers can be checked |
Results table
| KPI | Target | Actual | Last month | Status | Note |
|---|---|---|---|---|---|
| One row per KPI, outcomes first | From the plan | This month | For comparison | On track, at risk or missed | The reason, in one line |
Channel table
| Channel | Spend | Channel KPI | Change | Note |
|---|---|---|---|---|
| One row per channel | This month against plan | The metric the media plan gave this channel | Against last month or target | What happened and what changes |
How to fill each section
Summary and decisions
Write the summary last, once the rest of the report exists, and put it first. It states the headline result against the target, the main reason for the gap or the beat, the one thing that changed in the month and what is being decided. Decisions are listed as actions with owners and dates, divided into made and requested. If the decisions section is empty, the report has not finished its job; even "no change: continue the plan" is a decision when it is written down.
Results against targets
The results table carries the plan's KPIs in the plan's order: business outcomes first, then the marketing drivers beneath them, so that a miss on revenue can be traced to orders, to conversion or to traffic. Targets come from the plan unchanged; the temptation to restate them is how targets drift. Status is a word, not a colour alone, and the note gives the reason in one line. A KPIA metric tied directly to an objective. with no target in the plan does not belong in the table; it belongs in the channel section or the definitions. When the reason for a gap is not yet known, the method in explaining a change in a marketing metric finds it before the note is written, rather than after a wrong reason has been circulated.
Channel performance
One line per channel, with spend against plan, the channel's own KPI as the media plan defined it, the change and a sentence of explanation. Writing that sentence as what happened, so what and now what makes it end in a decision rather than a description. Judge each channel on its role: a demand-creation channel on reach and assisted outcomes, a capture channel on CPACost of each conversion. or ROASRevenue generated per unit of ad spend., retention on repeat rate. The channel teams' own reports hold the detail; what reaches this page is the line that a leadership reader needs in order to approve a change. The change column is only fair when both periods contain the same weekdays and holidays and neither is still collecting late conversions, and the rules for comparing periods in marketing reports set out how to line them up.
Experiments, risks and next month
Experiments are reported as hypothesis, result and decision, including the flat results, because the learning log is built from this section. A product-page test reported on add-to-cart rateShare of sessions in which a product was added to the cart. should show the change in conversion beside it, so readers can see whether the extra adds became orders. Risks name what threatens next month's targets and what broke this month, with whether it has been fixed; a tracking outage reported here saves an argument about the numbers later. Next month lists the priorities and the targets they serve, so that the following report has something to compare itself with.
Definitions
Every metric in the report has a definition — formula, grain, filters, source — and the report says where those definitions live rather than restating them. The metrics layer and definitions guide explains why numbers drift between tools and how a shared definition prevents the report and the dashboard disagreeing. A reader who cannot check a number will eventually stop trusting all of them.
Filled example
The sections and both tables are completed below for an invented footwear retailer's October report; the figures are illustrative.
Bobbinlark & Finch: October 2026 marketing report
| Section | Bobbinlark & Finch's October report |
|---|---|
| Period, author and audience | October 2026; written by the head of marketing for the managing director and the finance director; sent 5 November 2026 |
| Summary | Revenue of £412,000 was 3% under the £425,000 target, on orders slightly ahead of plan and an average order value £4 below it; the boot range launched a week late and its first week's demand landed in November. Paid social efficiency improved for the third month after the creative refresh. Email delivered a quarter of revenue at almost no cost. We are asking for approval to move £8,000 from display into paid social for November and to bring the December sale forward by four days |
| Decisions | Made: pause the broad display line (owner: paid media lead, done 28 October); extend the "boot fit guide" creative into November (owner: paid social manager). Requested: move £8,000 of display budget to paid social (finance director, by 8 November); confirm the sale start of 7 December instead of 11 December (managing director, by 10 November) |
| Experiments and learnings | Concluded: free-returns message in the product page hero, variant +6.2% add-to-basket rate, guardrail (return rate) unchanged at 24%; shipped 24 October. Running: size-guide placement test, ends 12 November. Learning: fit reassurance, not price, moved October's conversion; the November creative follows it |
| Risks and issues | Risk: courier capacity in the sale week; the fallback courier is contracted from 1 December. Issue: the purchase event double-fired on 3–4 October after a theme update; corrected on 5 October, and the reported orders exclude the duplicates. Risk: stock of the two best-selling boot sizes runs out by mid-November on current demand; a reorder lands 20 November |
| Next month | Boot range at full availability; display budget moved to paid social; sale creative and email sequence signed off by 25 November; target £480,000 revenue and 11,000 orders |
| Definitions | All metrics per the KPI dictionary v4 in the metrics layer; revenue is net of returns within 30 days as recorded at month end; ROAS uses platform-attributed revenue for channel lines and the attribution model in the dashboard for the blended figure |
| KPI | Target | Actual | Last month | Status | Note |
|---|---|---|---|---|---|
| Revenue (net) | £425,000 | £412,000 | £388,000 | At risk | AOV down; boot launch slipped one week |
| Orders | 9,400 | 9,560 | 8,900 | On track | Email and paid social ahead of plan |
| Average order value | £45.20 | £43.10 | £43.60 | Missed | Lower boot mix in the first three weeks |
| Blended ROAS | 5.6 | 5.7 | 5.3 | On track | Display pause and paid social efficiency |
| New customers | 3,600 | 3,410 | 3,250 | At risk | Display cut reduced new-customer reach; watching November |
| Repeat rate (90-day) | 31% | 33% | 32% | On track | Boot-care email sequence |
| Site conversion rate | 2.9% | 3.1% | 2.8% | On track | Free-returns test shipped |
| Channel | Spend | Channel KPI | Change | Note |
|---|---|---|---|---|
| Paid search | £31,000 (plan £30,000) | CPA £11.40 | −6% vs September | Brand and boot queries up; shopping feed fixed on 9 October |
| Paid social | £28,000 (plan £28,000) | ROAS 4.2 | +12% vs September | "Boot fit guide" creative; prospecting CPA £19 |
| Display | £6,000 (plan £10,000) | New-customer CPA £41 | Paused 28 October | Broad line underperforming; retargeting line kept |
| Email and SMS | £1,800 (plan £2,000) | Revenue £103,000 | +9% vs September | Boot-care sequence; unsubscribe rate 0.2% |
| Organic search | £0 media; £4,000 content | 61,000 sessions | +4% vs September | Boot guides ranking; two product pages lost position after the theme update |
| Organic social and creators | £5,500 (plan £5,000) | 142,000 engaged reach | +18% vs September | Two creator videos over-delivered; one post removed for a claim issue |
Common mistakes
- Charts instead of decisions. Twenty charts and no decision is a dashboard printed out. The decisions section is the reason the report exists.
- Targets restated to fit the result. Quietly changing the target is how a plan stops being checked. Targets come from the plan; if the plan was wrong, say so in the risks and change the plan.
- The summary written first. A summary drafted before the tables are filled describes what the author expected. Write it last and place it first.
- One metric for every channel. Judging each channel on last-click return makes reach channels look wasteful and capture channels look heroic. Each channel is judged on the role the media plan gave it.
- Flat tests left out. A report that lists only winners teaches that experiments always work, which is false and makes the learning log worthless.
- Silence about broken tracking. An outage that is not reported becomes an argument next month about why the numbers moved. Say what broke, when it was fixed and how the figures were corrected.
- Definitions nowhere. A number that cannot be checked is eventually disbelieved. Point to where each metric is defined and sourced.
The plan this report measures against and the briefs behind each campaign are in the templates library.
