Skip to main content
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?
The daily brief auto-sends by default, because it contains only exceptions and pace. Set its time, audience, and channel in the reporting cadence 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, 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: targets from KPI definitions, budgets from the plan registered in the data dictionary.
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 Exceptions 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 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 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.
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.
Last modified on October 30, 2026