Skip to main content
A Briefing is a cross-source AI synthesis surface. Where a Pulse delivers analysis for one source (or one source group) at a time, a Briefing combines many of them into a single big-picture view that runs once per calendar month and lands as a PDF in your destination.
Briefings are available on any paid plan (Starter, Pro, Enterprise). Limits vary by tier — see Plan limits below.

​
What a Briefing is made of

​
How it works at a glance

  1. You compose the briefing in /admin/briefings/[id] — add rows, drop sources or source groups into each row, give them titles.
  2. You press Save — the server runs a fresh AI pass: per-row commentary, then an overall summary across all rows.
  3. Once committed, you can send a snapshot — Chartcastr renders a multi-page PDF and delivers it to your chosen destination.
  4. A monthly cron fires the same flow automatically on your scheduled day-of-month + time.

​
Pages in this section

Use cases

Playbooks for the four jobs Briefings nail first — client reporting, board prep, pitch prep, all-hands.

Briefing rows

How rows and row items work, what counts toward your per-row item budget, and how source groups expand inside a row.

Overall review

The page-level AI summary, per-row commentary, and how AI titles are generated.

Save & commit

The explicit save model, AI regeneration, and why edits are blocked while a commit is in flight.

Snapshots & delivery

Monthly PDF snapshots, the once-per-calendar-month throttle, and destination delivery.

The /admin/briefings page

A walkthrough of the list view, composer, settings, and snapshot history pages.

​
Plan limits

Limits scale with your tier. Active means non-archived.
A source group counts toward the items-per-row budget by the number of sources inside it, not as one item — this matches how the briefing renders the group’s child charts side-by-side.

​
Why Briefings vs. Pulses?

Pulses are the heartbeat — frequent, single-source, optimised for “is anything moving?”. Briefings are the monthly retrospective — wide-angle, cross-source, optimised for “what’s the overall picture and what should we do about it?”. They share data (Briefings reuse the latest Pulse output for each item) but solve different jobs.