> ## Documentation Index
> Fetch the complete documentation index at: https://docs.snowdoughnut.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Daily brief

> A short brief an AI agent produces each morning from the flat file: pacing, plus anything outside its normal range. Covers the template, the rules it follows, and when 'nothing needs attention' is the whole brief.

*This page is both the template and the process, because the producer is an agent: there is no human workflow to document, only the rules the agent follows and the format the reader gets.*

The daily brief is the push version of a dashboard. A person writing a daily report is usually a sign the dashboard is missing; an agent drafting one from the flat file costs nothing, reports only what moved, and reaches people who never open the dashboard. It answers one question: is anything outside its normal range today?

> [!NOTE]
>
> The daily brief auto-sends by default, because it contains only exceptions and pace. Set its time, audience, and channel in the [reporting cadence](https://docs.snowdoughnut.com/reporting-cadence.md) register. "Nothing needs attention" is a valid, complete brief; padding a quiet day teaches readers to skim.

## How it runs

**1. The flat file fill completes**

The agent writes yesterday's rows first, per the [flat file's daily fill](https://docs.snowdoughnut.com/flat-file-template.md#daily-fill-and-restatement), and runs the file's checks. A failed check becomes the brief's first line; a brief built on unchecked rows is worse than no brief.

**2. Compute pace**

Spend and the tier 1 metrics, month to date, using the [pace formula](https://docs.snowdoughnut.com/data-quality-and-rollup-concepts.md): targets from [KPI definitions](https://docs.snowdoughnut.com/kpi-definitions.md), budgets from the plan registered in the [data dictionary](https://docs.snowdoughnut.com/marketing-reporting-data-dictionary.md).

**3. Compare against normal ranges**

Each metric against the normal range recorded in its data dictionary block. Inside the range is silence. Day-over-day movement is never compared; it is noise by construction.

**4. Send**

Deliver per the register. An exception repeats in each day's brief until it returns to range or the owner acknowledges it, so a one-day glance can't bury a week-long problem.

## The template

**Status**

*E.g. Nothing needs attention. Spend pacing 98%, contribution margin pacing 101%.*

**Pacing**

| Metric | Month-to-date | Target | Pace |
| :- | :- | :- | :- |
| *E.g. Total marketing spend* | *E.g. \$42,300* | *E.g. \$43,000* | *E.g. 98%* |
| *E.g. Contribution margin (north star)* | *E.g. \$38,900* | *E.g. \$38,500* | *E.g. 101%* |
| *Add a row* | | | |

**Exceptions**

| Metric | Value | Normal range | First seen | Note |
| :- | :- | :- | :- | :- |
| *E.g. Meta ROAS* | *E.g. 4.8x* | *E.g. 3.2 to 3.8x* | *E.g. 2026-06-11* | *E.g. New creative outperforming; unknown whether it holds* |
| *Add a row* | | | | |

**Data notes**

*E.g. Conversion metrics for the last 2 days are estimates, restated as platforms settle.*

## Rules the agent follows

* Report a cause only when the [change log](https://docs.snowdoughnut.com/marketing-reporting-data-dictionary.md#decisions-and-changes) records one for the period; otherwise write "unknown, investigating." An invented explanation is worse than an honest gap.
* Never recommend a budget or bid change here. The brief observes; decisions route through [budget pacing](https://docs.snowdoughnut.com/budget-pacing.md) and the owner.
* Estimated rows are labeled, never presented as settled.
* The brief is not archived. Its numbers live in the flat file, and yesterday's brief has no reader.

## Related resources

* [Reporting cadence](https://docs.snowdoughnut.com/reporting-cadence.md) Where this brief's time, audience, and channel are set.
* [Flat file template](https://docs.snowdoughnut.com/flat-file-template.md) The daily fill the brief reads from.
* [Weekly reporting process](https://docs.snowdoughnut.com/weekly-reporting-process.md) The shortest written report; the brief never replaces it.
* [Report writing concepts](https://docs.snowdoughnut.com/report-writing-concepts.md) Why exceptions-only is the rule.

> [accordion] MCP wiring
>
> **Type:** process\
> **Domains:** reporting, budget\
> **Provides:** `process:daily-brief`, `report-template:daily`\
> **Uses:** `data-dictionary`, `flat-file`, `kpi-definitions`, `library:change-log`, `reporting-cadence`\
> **Hands off to:** `process:budget-pacing`
>
> **Triggers:** "What needs attention today?" · "Send the daily brief" · "Morning numbers" · "Anything off this morning?"
>
> **Output:** Exceptions-only brief (status, pacing table, exceptions with normal range and first-seen, data notes) sent per reporting cadence register; no archive, no recommendations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.