Internal Communications Messaging Brief

This template is used to collect the core inputs needed before drafting an internal communication: the request, audience, key messages, channel, and deadline. It gives communications, HR, and operations teams a single brief to work from instead of piecing together details from email threads. Use it for announcements, policy updates, org changes, and employee-facing reminders. It is not meant to replace the final draft or approval workflow.

Use it whenever the message will affect a defined employee audience, requires coordination, or may need legal or HR review. It is especially useful when the request comes from a stakeholder who knows the business need but not the communication format. If the message is simple, low-risk, and already fully specified, a brief may be unnecessary. For anything with multiple stakeholders or sensitive content, the brief prevents rework.

Usually the requestor, manager, HR partner, or communications lead completes it before drafting begins. In some teams, the comms owner fills it out during a kickoff call and then confirms details with the requestor. The important point is that one accountable person owns the brief and can answer follow-up questions. That reduces back-and-forth and keeps the audit trail clear.

It fits policy changes, benefits reminders, leadership updates, event announcements, process changes, and operational notices. It also works for messages that need audience segmentation, such as location-specific or role-specific communications. If the message is public-facing or customer-facing, this is the wrong template. If the message includes sensitive employee data, the review section becomes especially important.

Use it every time a new internal message needs drafting, especially when the message is not routine. For recurring campaigns, you can reuse the same structure and update the audience, channel, and deadline fields each time. That keeps the brief consistent and makes it easier to compare requests over time. For one-off urgent notices, the same form still helps capture the minimum necessary details.

Include the three most important points the audience must understand after reading the message. Add supporting links or assets only if they are needed to complete the action or verify the information. Keep the language specific and actionable, not a full draft. If there are phrases that must appear or must be avoided, note them here so the draft stays aligned.

The review section flags whether legal or HR review is required, whether the message contains PII, and whether consent or disclosure language is needed. That helps teams route the brief before drafting or sending anything sensitive. It also creates a record of who requested the communication and what constraints apply. For regulated or employee-sensitive topics, that record is often as important as the message itself.

Yes. You can adapt the channel field for email, Slack, intranet, SMS, town hall scripts, or manager talking points. You can also add conditional logic for different audience types, approval paths, or required assets. The structure stays the same, but the routing and review notes can change based on your workflow. That makes it easy to standardize intake without forcing every request into the same communication format.