Post-All-Hands Recap Broadcast

This template is for sending a single follow-up broadcast after an all-hands meeting. It summarizes the main announcements, decisions, recording access, and any actions people need to take. It is meant to replace scattered recap emails, chat posts, and verbal follow-ups with one clear message.

Send it soon after the meeting, while the discussion is still fresh and people can act on it. It works best when the all-hands included policy updates, org changes, launches, or decisions that affect a broad audience. If the meeting was purely social or had no follow-up items, a recap broadcast may not be necessary.

Usually the meeting owner, internal communications lead, or an executive sponsor sends it. The sender should be someone who can accurately confirm the final decisions and next steps. If multiple leaders spoke, one person should own the recap so the message stays consistent and easy to scan.

Only use acknowledgment when the recap includes mandatory policy, compliance, safety, or change-management actions that people must confirm. For a normal informational recap, acknowledgment is usually unnecessary and can create alert fatigue. If you do require acknowledgment, make the action explicit and keep the message focused on what must be confirmed.

Include the headline outcome first, then the key announcements, decisions made, recording or deck access, and the one primary action people need to take. If there are multiple follow-ups, group them clearly by audience or owner so readers can find what applies to them. Avoid turning the broadcast into meeting minutes; it should be a short, usable summary.

An ad-hoc recap often buries the important points, mixes in side commentary, or leaves out the next step. This template gives you a repeatable structure that follows the inverted pyramid: most important fact first, then supporting details, then links and actions. That makes it easier for employees to scan, understand, and act without asking for clarification.

Yes. You can tailor the recap for the full company, a department, a region, or a specific project audience. Keep the core structure the same, but swap in only the announcements and actions that matter to that audience so the message stays relevant and concise.

Common links include the meeting recording, slide deck, project tracker, policy page, or task board. If your broadcast tool supports pins, comments, reactions, or acknowledgment tracking, use them to make the recap easier to find and confirm. The template works best when the links point directly to the next action, not to a general folder.

The biggest mistakes are burying the main takeaway, listing too many updates, and failing to name a clear next step. Another common issue is using vague language like 'several things were discussed' instead of stating what changed and what people need to do. Keep the recap plain, specific, and short enough to read in one pass.