Skip to main content
Fill in the register below. Grayed E.g. text is Doughnut Labs’ filled-in answer; delete it and write your own. Each cadence answers a different question: the daily brief flags exceptions and pacing, a weekly report catches what needs attention now, a monthly report checks the target, a quarterly review checks the strategy, and an annual review sets next year’s plan. Every cadence is a rollup of the flat file’s dated rows, not a new report; see data quality and rollup concepts for how that works, and report writing concepts for matching reporting frequency to decision frequency.
Two roles appear in the register. Drafted by can be a person or an AI agent connected to the flat file and your sources of truth. Approved by is always a person: the report owner reads, edits, and approves before a report goes out. Auto-send is that owner’s standing rule to skip the per-report approval for a cadence, set here once rather than decided send by send. Pick the channel each audience actually reads; one team wants everything in Slack, another wants email, another wants a doc. A daily brief usually auto-sends, since it reports only exceptions; whether anything else does is yours to decide.

The register

One row per scheduled job. The first row is the data load, not a report; it is what makes every report below it cheap to produce. Templates: weekly, monthly, quarterly, annual. Leave a row blank for a cadence you don’t yet produce; most brands start with the fill, the daily brief, and a monthly report, and add weekly once spend justifies it.

Fixed dates the schedule depends on

Two cadences hang off dates only your team knows. Record them here so “three days before the meeting” and “before planning starts” resolve without asking anyone.

Where sent reports go

Every sent report gets logged in its archive: weekly, monthly, quarterly, annual. The daily brief is not archived; its numbers already live in the flat file, and yesterday’s brief has no reader.
Type: brief
Domains: reporting
Provides: reporting-cadence
Uses: flat-file, kpi-definitions, library:report, process:daily-brief, report-template
Triggers: “Set up our reporting schedule” · “When should each report go out?” · “Who approves the weekly report?” · “Make the daily brief auto-send”Asks, in order:
  1. Which cadences do you produce now? Options: reporting-cadence#the-register.
  2. For each, when does it run and who approves it? Options: your answer.
  3. Drafted by a person or an AI agent? Options: reporting-cadence (Person, AI agent).
  4. Should any of them auto-send? Options: yes or no.
  5. Where does each audience read it? Options: reporting-cadence (delivery channels).
  6. When is the quarterly review meeting and annual planning kickoff? Options: your answer. Skip when: no quarterly/annual cadence.
Output: Filled schedule register plus fixed dates; drives scheduling for reporting processes.

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