Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Standard Operating Procedures

Monthly Reporting Pack SOP

A standard procedure for producing the monthly marketing reporting pack: data pull, reconciliation, checks, commentary, review, distribution and archive.
SOPbeginner6 min readUpdated

Owner, trigger and scope

The marketing analyst owns the procedure and produces the pack. The head of marketing reviews the commentary, signs off the pack and owns the distribution list. If the analyst is unavailable, a named deputy runs the same SOP; the pack does not wait.

The trigger is the close of the calendar month. The procedure runs in the first working days of the new month, on a fixed timetable agreed with the head of marketing and published to the pack's readers, so nobody asks for numbers before they exist.

The scope is the recurring monthly pack: the agreed set of channel, campaign and outcome metrics, a short commentary and any agreed appendices. Ad hoc analysis requests, quarterly business reviews and dashboard changes are out of scope. Changes to which metrics appear in the pack go through the head of marketing and are made between packs, never during production. The wider rhythm of weekly, monthly and quarterly reporting belongs to the marketing reporting cadence playbook.

Before you start: inputs and access

InputSourceNotes
Last month's packArchiveThe structure and definitions to repeat
Report templateMonthly marketing report templateLayout, sections and metric definitions
Metric definitions and targetsHead of marketingThe KPI list, ideally mapped as a KPI tree
Access to ad platforms, analytics and CRMOwners of each systemRead access is enough
Annotations logAnalytics ownerKnown outages, launches and site changes
Pause and launch logsPaid media teamExplains changes in spend and delivery

Confirm access to every source the day before the month closes. A lost login on the first working day is the most common reason a pack is late.

The procedure

  1. Freeze the period

    Agree and record the exact period, time zone and pull date. Most sources keep adjusting recent data as late conversions arrive, so pull at the same point each month, after the delay your sources need to settle. Note the pull date on the pack's cover. If anything is pulled later, mark it, so readers know which figures may move.

  2. Pull the data

    Export each source using saved reports or queries, not fresh ad hoc filters, so that the definitions match last month. Pull ad platform spend and results, GA4 sessions and conversions, and CRM or sales outcomes. Save the raw exports in the month's folder with their pull date before you touch them; the raw files are how anyone checks the pack later.

  3. Reconcile the sources

    Compare totals across sources: spend in each platform against the finance figure, platform conversions against analytics conversions, analytics leads against CRM leads. Some gaps are expected and explained in the platform versus analytics discrepancies guide. Your job here is to check the gap is in its usual range and to investigate any gap that has moved.

  4. Run data checks

    Run the standard checks from the data quality guide: missing days, sudden step changes, unassigned or other traffic growing, duplicate transactions, test traffic, and campaign names that do not match the naming convention. Check the annotations log for known outages. Any issue found is either fixed in the source, corrected in the pack with a note, or flagged to the reader.

    Where the pack reads from warehouse tables, the tutorial on writing data tests for marketing tables turns these checks into queries that run with every load, so most failures surface before the month closes.

  5. Write the commentary

    Write a short commentary per section: what changed against last month and against target, the most likely reason, and what the team will do about it. Use the launch, pause and annotation logs as evidence rather than guessing. Separate what the data shows from what you infer. Keep each section short enough that a busy reader gets the point from its first sentence.

  6. Review and sign off

    Send the draft to the head of marketing with a list of open data issues. They review whether the commentary is fair and complete and whether anything will surprise readers. Address their comments, then record the sign-off with a name and date. If a data issue cannot be resolved in time, the pack goes out with the issue clearly flagged rather than delayed indefinitely. One-off analyses outside the pack get the fuller check in the routine for reviewing an analysis before it is shared.

  7. Distribute and archive

    Send the signed-off pack to the agreed distribution list in the agreed format, on the agreed day. Save the final pack, the raw exports, the reconciliation notes and the sign-off together in the archive folder for the month. Lock the folder or mark it final, so that later corrections are made as a new version rather than an invisible overwrite. When an error is found after the pack has gone out, follow the tutorial on correcting a number after a report has gone out.

Illustrative example — not a real result

Reconciliation catching a duplicated conversion

Saltmarsh Gin, an invented spirits brand, produces its pack on the 4th working day. During reconciliation the analyst sees analytics purchases at 1,240 for the month against 1,010 orders in the shop platform, a gap far wider than the usual 5 to 8%. The data checks show a purchase event firing twice on one payment method since a checkout update on the 17th. The pack goes out on time with corrected figures from the shop platform, a flagged note on the analytics numbers, and an incident raised with the analytics owner. The head of marketing signs off with the note left in.

QA checks

A quick sense check helps too: read the summary as a sceptical reader would and ask which figure you would challenge first.

Before the pack is sent, the analyst confirms each of these and the reviewer spot-checks a sample:

  • Period, time zone and pull date are stated on the cover and match across sources.
  • Definitions match last month's pack, or any change is noted.
  • Totals reconcile within their usual ranges, and any unusual gap is explained.
  • Data checks run, with every issue fixed, corrected or flagged.
  • Charts and tables show the same figures as the summary.
  • Commentary explains every large movement and separates fact from inference.
  • Sign-off recorded with a name and date.
  • Archive contains the raw exports, the reconciliation notes and the final pack.

Hand-offs and records

The pack is handed to its readers through the agreed distribution, and the head of marketing presents it where a meeting is involved. Data issues found during production are handed to the analytics owner as tickets, with the evidence attached, so they are fixed at the source rather than corrected by hand every month. Requests that arrive from readers for new metrics are logged and considered at the next pack change, not added on the spot.

The records this SOP keeps are the monthly archive folder, the sign-off note, and a production log noting the pull date, open issues and how each was handled. Over time that log shows which sources cause the most trouble and where a fix upstream would save hours every month.

If the pack still takes days even with this procedure in place, the diagnosis of a monthly marketing report that takes days times each step and traces the hours to their cause.

Common mistakes

These mistakes rarely break a single pack; they slowly erode trust in every pack that follows.

  • Pulling at different points each month. Late-arriving data makes months incomparable. Freeze the period the same way every time.
  • Redefining metrics mid-production. A filter changed in a hurry breaks comparison with last month. Change definitions between packs.
  • Hiding discrepancies. Readers find gaps eventually. Show and explain them.
  • Commentary that restates the chart. Say why it moved and what happens next.
  • Fixing data in the pack, not the source. The same correction reappears every month.
  • Skipping the archive. Without raw exports, nobody can answer questions about last quarter's numbers.
  • Late sign-off requests. Reviewers rushed on the day miss problems. Book review time in advance.

Frequently asked questions

Why freeze the reporting period before pulling data?

Several sources keep updating figures for days after a period ends, as late conversions arrive and data is processed. Pulling at a fixed, agreed point means the numbers in the pack match what anyone else pulling at the same point would see, and later restatements can be explained.

Should the pack use platform figures or analytics figures?

Decide once and write it into the pack's notes. Most teams report channel performance from each platform and overall outcomes from analytics or the business's own system, and show the gap rather than hiding it. The platform versus analytics discrepancies guide explains why the figures differ.

Who should sign off the monthly pack?

The head of marketing, or whoever presents the numbers to the business. They are not checking arithmetic but whether the commentary is fair and whether anything in the pack will surprise its readers.

Terms used on this page

Frameworks

Where this page is used

Part of these learning paths

Also related

Sources

  1. Google Analytics Help — Google Analytics Help

Related