Skip to main content
The monthly report answers a different question than the weekly one: did we hit the target, and why? It’s built by rolling up the flat file rows whose dates fall in the month, the same rows the weekly reporting process already checked week by week. Like every cadence, it can be drafted by hand or by an AI agent on the schedule in reporting cadence; the report owner approves what goes out.
This process uses the data dictionary, the flat file, and the monthly report template.

What you’ll end up with

  • A correct set of monthly totals: raw numbers summed from the month’s weeks, every ratio recalculated from those totals.
  • A three-to-five-page report, filed in the monthly report archive, explaining what drove the result, not just what it was.

Before you start

  • Every week in the month has been loaded and checked through the weekly reporting process. A monthly rollup built on unchecked weeks inherits every one of their errors.

The process at a glance

1

Roll up the month

Sum the raw flat file inputs across the month’s weeks, then recalculate every ratio from the totals.
2

Check the rollup

Confirm the monthly totals reconcile against the individual weekly reports.
3

Analyze

Compare against target and prior periods, and work down the KPI tiers to explain what drove the result.
4

Write

Fill in the monthly report template, executive summary last.
5

Quality check and deliver

Have a second reader check it, then send with the headline and the ask.
6

File it

Log the report in the monthly report archive and register it if it’s a recurring cadence in the data dictionary.

1. Roll up the month

Filter the flat file to every row whose date falls inside the calendar month, add up the raw inputs (spend, revenue, orders, and so on), and only then recalculate every ratio, ROAS, conversion rate, contribution margin, from the summed totals. A spreadsheet pivot table does the summing in a few clicks, and an agent does it as arithmetic; see the flat file template for the exact steps.
Never average the four weekly ratios directly. A week with unusually high or low volume, a promotion, a stockout, a big push, gets the same weight as an ordinary week in a simple average, which produces a monthly number that doesn’t match what actually happened. See data quality and rollup concepts for a worked example of how far off this can be.
Daily rows make month boundaries a non-issue: the date decides which month a row belongs to. If you still load the file weekly by hand, a week can straddle the boundary; pick one rule, assign the straddling week whole to the month holding its final day, record it in the data dictionary’s decision log, and apply it the same way every month.

2. Check the rollup

Add the month’s four or five weekly totals for a single input, like ad spend, and confirm it matches the monthly sum. This lifetime-style check catches a missed or double-counted week before it reaches the report; if the numbers don’t reconcile, a week is either missing from the flat file or was pulled into the rollup twice.

3. Analyze

Compare the month against its target, against last month, and against the same month last year if the business has real seasonality. Work down the KPI tiers: when a tier 1 outcome missed or beat its target, the tier 2 drivers underneath it say why, and tracked metrics explain why a driver moved if that level of detail is needed. Check the change log for anything that happened during the month before concluding a cause.

4. Write

Fill in the monthly report template. Write the body first and the executive summary last, since it’s hard to summarize an analysis that isn’t finished yet. Every number in the report should answer what happened, why, and what to do about it; a number that only states a fact is data, not reporting.

5. Quality check and deliver

A reader other than the drafting actor reviews the report before it goes out. When a person wrote it, that’s a second reader; when an AI drafted it, the report owner is that reader. Ten minutes of fresh eyes catch more than an hour of re-reading your own work, and this is the cadence where an error does the most damage to credibility, since a monthly report usually reaches a wider or more senior audience than a weekly one. Send on the day the reporting cadence register records, with a short message stating the headline result and the ask.

6. File it

Log the report in the monthly report archive, including its headline result, so the archive stays useful as a scannable history rather than a folder of files nobody reopens.
Type: process
Domains: reporting
Provides: process:monthly-reporting
Uses: data-dictionary, flat-file, kpi-definitions, library:change-log, library:report, report-template:monthly, reporting-cadence
Hands off to: process:quarterly-reporting
Triggers: “Write the monthly report” · “Did we hit target this month?” · “Monthly recap for leadership” · “Roll up October”Asks, in order:
  1. Which month? Options: your answer. Skip when: cadence-triggered.
  2. Compare against same month last year too? Options: yes or no. Skip when: data dictionary flags seasonality.
Output: Rolled-up monthly totals (sum inputs, recompute ratios), reconciliation check, 3-5 page monthly report (exec summary last), filed in monthly archive with headline.

Get the complete Marketing OS

Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.

Have us run it for you

We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.
Last modified on November 2, 2026