Broadcast Send Checklist

It prompts the sender to verify the audience, headline, timing, links, accessibility, readability, and owner approval before release. It also provides one clear call to action: reply with “Ready to send” or contact the communications owner. Use it as a final broadcast gate, not as the announcement itself.

The person preparing or scheduling the broadcast should complete the checks. A communications owner or designated approver should confirm sign-off when the message affects a broad audience, carries operational risk, or supports a change-management announcement. The sender remains responsible for resolving missing checks before publishing.

Use it before each internal broadcast, including recurring announcements when the audience, links, timing, or wording may have changed. It is especially useful for urgent updates, policy rollouts, safety notices, and messages sent to multiple locations or teams. Routine low-risk messages can still use a shortened version if your process allows it.

No. It supports a disciplined pre-send review but does not replace an emergency-notification plan, required posting, incident procedure, or legal review. For safety alerts, confirm that the message reaches the required audience, states what is happening and what people must do, and uses acknowledgment tracking when a mandatory read is needed.

A frequent failure is releasing a broadcast with a correct-looking message but an incorrect audience, broken link, unclear timing, or missing approval. Another is adding several competing calls to action. This checklist keeps the final review focused on one primary action and the contact who can resolve questions.

Yes. Add checks for translations, regional timing, legal review, incident-command approval, accessible attachments, or audience segmentation as needed. Keep the core language reusable by using role names such as communications owner rather than tenant-specific people or dates.

It can be posted before an approval workflow to collect a visible “Ready to send” response and questions in comments. The template itself does not prove that a formal approval, read receipt, or delivery event occurred. Enable acknowledgment only when the broadcast is mandatory to read, such as a policy, compliance, or safety notice.

An ad-hoc review depends on memory and often misses accessibility, audience, or link checks. This template creates a repeatable broadcast checkpoint with a named next step and space for questions. It is still a checklist, so high-risk communications should pair it with your escalation and approval process.