The All-Hands Progress Report, Written for You

The All-Hands Progress Report, Written for You

Release note + use case story. Briefings are now live on every paid Chartcastr plan. Full product docs: Briefings overview. This post is one of four use case playbooks, see all of them in the Briefings use cases page.

Every monthly all-hands has the same problem: someone has to assemble it.

Heads of function get an email asking for "your top three updates by Wednesday." Half reply on time, half reply with a wall of text on Thursday afternoon. A leadership chief-of-staff stitches it into a slide deck. The CEO opens the deck Friday morning, edits the framing, and presents it that afternoon.

The deck is mostly the same shape every month. The metrics underneath each section are the same metrics every month. The only thing that genuinely changes is what happened, and that is exactly what AI cross-source synthesis is good at writing the first draft of.

Briefings replace this entire workflow with a one-time setup.

The all-hands shape, in Briefings

A typical monthly all-hands has 4–7 sections. Each section gets one row in the briefing:

Each row pulls in the relevant source or source group, the analytics tool, the CRM, the support tool, the HRIS, whatever you use for that function. The AI writes per-row commentary explaining what changed and why, anchored to the actual numbers.

Then the overall review sits on top: a synthesis across every row that names the themes, what's working across multiple functions, where there's friction, and what the company should be paying attention to.

"Leadership stops writing the recap from scratch"

The single biggest unlock is the overall review. For most leadership teams, the all-hands recap is written by one person staring at six different dashboards trying to find the through-line. The AI does that synthesis natively. It's reading every row's commentary and looking for cross-cutting themes.

You don't take the AI's recap as the final word. You take it as the first draft. By the time you read it, half the work of "what should we tell the company this month" is already done, and the half that's left is the half a human should be doing, which is interpretation and framing.

Setup: how to make the briefing match your all-hands rhythm

A few choices that hold up across many cycles:

• Schedule the snapshot for the morning of the all-hands. Briefings deliver on a configurable day of month + time in your org timezone. If your all-hands is the last Friday at 10am, schedule the briefing for that Friday at 8am.
• Pick a destination that the leadership team already checks. The PDF lands wherever you tell it to, pick the channel or inbox the team will see first thing in the morning.
• Lock the row titles once they feel right. "Product." "Go-to-market." "People." The AI stops re-titling and your team learns to skim the briefing in the same shape every month.
• Use the briefing description as a steering wheel. "Monthly all-hands recap. Audience is the whole company. Emphasise progress against quarterly goals. Flag risks but don't dwell on them." That paragraph is fed to the AI at every layer and changes the tone of the commentary.

What this looks like the morning of the all-hands

You wake up. The PDF is already in the destination you configured. The cover page has the period label. Page 2 is the overall review, the "state of the company this month" page, written for you.

You read it once. You note the two themes the AI surfaced and the one it missed. You spend 20 minutes editing the leadership talking points around those themes. You walk into the all-hands with a deck that has fresh numbers, fresh AI commentary, and fresh framing, and you got there in under an hour instead of three days.

What you stop doing

• Stop sending the "your top three updates by Wednesday" email.
• Stop chasing function leads on Thursday afternoon.
• Stop hand-writing a paragraph under each chart that says "engagement is up because of the X feature launch", the AI does that, anchored to the numbers.
• Stop building the same deck shape from scratch every month.

What you keep doing

• Keep deciding the framing. The AI tells you what the numbers are doing. You decide what story the company needs to hear.
• Keep curating the sources. The briefing only synthesises what's in front of it. If a key source isn't connected, it isn't in the recap.
• Keep editing for tone. Especially when the news is hard. AI commentary is honest about numbers but it doesn't know the room the way you do.

Why monthly is the right default for company recap

Weekly is too noisy, a single bad week dominates the framing. Quarterly is too slow, themes ossify before leadership has a chance to react. Monthly is the cadence that matches how most companies actually run, and it's exactly the cadence Briefings are designed for.

For leadership offsites, board prep, or one-off "state of the company" moments, the manual snapshot path lets admins trigger an off-cycle run without breaking the monthly rhythm.

Start with the section you already write

The fastest way to validate this for your team is to build a one-row briefing that mirrors the section of the all-hands you personally write. Give it the same source, the same framing, and the same audience. Run a manual snapshot before the next all-hands.

If the AI commentary saves you 30 minutes that month, expand it to the whole deck. If it doesn't, the briefing description probably needs sharpening. Either way, you'll know in one cycle.

Read more

Full product reference: Briefings overview. Other use case playbooks: Briefings use cases. How the page-level synthesis is generated: overall review & AI commentary.