What this playbook covers and when to run it
The playbook covers the recurring flow of marketing numbers to the people who use them: who the audiences are, what each needs to know, the agreed definitions underneath, the weekly, monthly and quarterly reports, the data checks that make them trustworthy, and the follow-up that turns a report into a decision. It does not teach how to design dashboards or choose an attribution model; the dashboard governance guide and the analytics guides own those.
Run it when reporting has grown by accretion: a report for every request, numbers that differ between meetings, and a monthly pack that takes days to assemble. Run it also when a new head of marketing or a new finance partner arrives; the first few months are the best time to agree what gets reported and to whom. Once in place, the playbook runs continuously and is reviewed each year.
It is part of the playbooks library, and the paid search, paid social, SEO and planning playbooks all hand their results to it. The monthly reporting pack procedure sets out the exact steps for producing the monthly pack.
Roles and responsibilities
- Marketing analyst. Owns the metric layer, the data checks and the production of every report. Writes the first draft of the commentary and keeps the decision tracker.
- Channel leads. Own the explanation of their channel's numbers. Review their section before the pack goes out and act on anomalies raised in the weekly view.
- Head of marketing. Owns the audience list and the questions each report answers. Signs off the monthly pack and presents the quarterly review.
- Finance partner. Owns the reconciliation with the company's financial numbers, especially spend and revenue, and attends the monthly and quarterly reviews.
The tension that this playbook manages is between the analyst, who wants consistent definitions, and the channel leads, who know the context behind the numbers. The commentary review step gives both a voice: the analyst produces the numbers from the agreed layer, and the channel leads explain them.
Cadence, inputs and outputs
| Cadence | Owner | Inputs | Outputs |
|---|---|---|---|
| Weekly | Marketing analyst, channel leads | Platform and analytics data, budget pacing, last week's anomalies | A short weekly view: pacing, anomalies, actions |
| Monthly | Marketing analyst, head of marketing | Reconciled channel data, spend from finance, CRM pipeline and revenue | The monthly pack with commentary and decisions |
| Quarterly | Head of marketing, finance partner | Monthly packs, quarterly objectives and targets | Quarterly business review against objectives; inputs to planning |
Each cadence feeds the next. Anomalies from the weekly view are explained in the monthly commentary, and the monthly packs become the evidence base for the quarterly review. When a cadence is skipped, the next one inherits unexplained numbers, so protect the dates as firmly as any campaign deadline. Each cadence also needs a fixed comparison basis, and the rules for comparing periods in marketing reports cover aligning weekdays and holidays, month-to-date figures and days still collecting late conversions.
The playbook in phases
Define audiences and questions
Start with people, not metrics. List the audiences for marketing numbers: channel leads, the head of marketing, finance, the leadership team, perhaps sales. For each, write the few questions they need answered and the decisions they make with the answers. Channel leads need to know whether spend is on pace and whether anything broke. The head of marketing needs to know whether the plan is on track and where to intervene. Leadership needs to know what marketing contributed to the business. Then decide the cadence each audience can act on. A board does not need weekly pacing; a channel lead cannot wait a month to learn tracking broke. The result is an audience map that every report must fit.
Set the metric layer
The metric layer is the agreed set of definitions every report draws from: what each KPIA metric tied directly to an objective. means, how it is calculated, which source it comes from and who owns it. Build it from the plan's objectives using a KPI tree, so each channel measure connects to a business outcome. Write down the source choice for each metric explicitly: conversions from analytics or from the platform, revenue from the CRM or from finance. For web metrics drawn from GA4Google's event-based analytics platform., record the property, the event and the reporting identity used. The analyst owns this document. Without it, every meeting starts by arguing about whose number is right.
Build the weekly view
The weekly view is short and operational. It shows spend against plan by channel, the main outcome measures against recent weeks, and anomalies: anything that moved sharply, any tracking gap, any campaign that stopped delivering. It is not a performance judgement; a single week is too noisy for that. The analyst prepares it from the metric layer, and channel leads respond to anomalies in writing before the next week's view. Keep it to a page or a single dashboard tab. If people start adding sections, check whether those questions belong in the monthly pack instead. A weekly view that grows becomes a monthly pack nobody reads every week. In business-to-business teams, the weekly pipeline review is a separate meeting with sales about stuck opportunities, and its recurring themes belong in the monthly pack.
Run the monthly pack
The monthly pack explains performance. It follows the monthly reporting pack procedure: data is pulled and checked, reconciled with finance for spend and with the CRM for pipeline and revenue, laid out in the agreed template, and annotated with commentary. Each section answers the same three things: what happened, why we think it happened, and what we will do. The what, so what, now what framework for report commentary shows how to write and test each of those three parts. The performance reporting guide covers how to present channel results fairly. Channel leads review their sections before release. The head of marketing signs off, and the pack goes out on a fixed working day each month. Decisions made in response go into the decision tracker.
Hold the quarterly review
The quarterly review steps back from channels to objectives. The head of marketing presents progress against each objective in the quarterly plan, with the finance partner confirming spend and revenue. The marketing P&L guide shows how to present marketing's contribution in the terms finance uses, including ROIProfit relative to cost. where it can be fairly estimated. Be explicit about the limits of AttributionAssigning conversion credit to touchpoints. in this review: a channel's credited results depend on the model, and the audience should know which model was used. Review the decision tracker: were last quarter's decisions carried out, and did they work? The review's findings feed the next planning cycle. The quarterly marketing review template gives the review a fixed layout, from decisions requested and results against plan to next quarter's changes and asks. Brand measures that move too slowly for the monthly packs can enter this review through a quarterly brand health report, which leads with one headline measure and marks each movement as real or too early to tell.
Report audiences and the questions each answers
Every report should be able to say, in one line, whom it is for and what question it answers. If it cannot, it is a candidate for retirement. This table is a starting point; adjust the audiences to the organisation.
| Audience | Cadence | Questions the report answers | Report |
|---|---|---|---|
| Channel leads | Weekly | Is spend on pace? Did anything break or move sharply? | Weekly view |
| Head of marketing | Monthly | Is the plan on track? Which channels need attention? What did we decide? | Monthly pack |
| Finance partner | Monthly | Does marketing spend reconcile? What is the pipeline and revenue picture? | Monthly pack, finance section |
| Leadership team | Quarterly | What did marketing contribute against objectives? What changes next quarter? | Quarterly review |
| Sales leadership | Monthly | How many qualified leads, from where, and how did they convert? | Monthly pack, pipeline section |
Data checks sit underneath all of these. Before any report goes out, the analyst confirms that each source refreshed, that tracking volumes look normal, that spend matches the platforms and that any known data issues are noted in the commentary. A report that goes out with a silent data problem does more damage than a report that goes out late with an honest note. The measurement plan framework is a useful reference for keeping those checks complete.
An education provider cutting its reports from fourteen to four
An online education provider's marketing team produces 14 recurring reports, built over three years for different requests. The analyst spends about six working days a month assembling them, and the head of marketing and the finance partner regularly quote different lead numbers. The team runs this playbook, builds an audience map and a metric layer, and retires 10 reports. The remaining four are a weekly view, a monthly pack, a finance reconciliation tab and a quarterly review. Assembly time falls to about two days, the pack goes out on the third working day, and the lead number in every meeting now comes from the same definition.
Measuring the playbook
The playbook works when the right people get trusted numbers on time and act on them. Operating signals include whether each report went out on its scheduled day, how many data issues were found after release rather than before, how many reports exist outside the audience map, and how long the monthly pack takes to produce. A rising count of ad-hoc report requests usually means an audience's questions are not being answered by the regular cadence.
Decision signals matter more. Track how many decisions the monthly pack and quarterly review produce, how many are carried out by their date, and whether the next review checks them. Reporting that never leads to a decision is overhead. The Google Analytics help centre documents how reports and explorations calculate their metrics, which is worth checking whenever a definition in the metric layer is questioned.
When assembling the reports consumes more time than reading them, the diagnosis of a monthly marketing report that takes days separates export, definition, audience, dashboard and data-quality causes.
Common mistakes
- One report for everyone. A single dashboard trying to serve channel leads and the board serves neither. Build per audience.
- No agreed definitions. Without a metric layer, every meeting relitigates whose number is right. Write it down and assign an owner.
- Numbers without commentary. Readers invent their own explanations. Say what happened, why and what is next.
- Judging performance weekly. A single week is noise. Use the weekly view for pacing and anomalies, and judge performance monthly or quarterly.
- Hiding data problems. A silent tracking gap undermines trust for months. Note known issues in the commentary.
- Decisions nobody follows up. If the next review never checks last month's decisions, reporting becomes ritual. Keep a decision tracker.
