Team Leader Pre-Brief Broadcast

This template is for a manager-only broadcast sent before a broader announcement goes public. It gives team leaders the headline fact, timing, expected impacts, and the one action they need to take so they can prepare their teams. It is not the public announcement itself and should not read like a policy memo.

Use it when managers need advance notice to answer questions, coordinate coverage, or support a change rollout. It fits planned changes, policy updates, org changes, system launches, and other announcements where leaders need context before employees hear it. Do not use it for routine FYIs that do not require manager action.

It is usually sent by HR, Communications, Operations, or the business leader owning the change. The sender should be the person or function that can answer questions, confirm timing, and provide the next step if leaders need help. If the message affects safety, compliance, or staffing, the accountable leader should be clearly named.

It can, but only when the pre-brief is mandatory for managers to read before the public announcement or before a rollout begins. If you need confirmation that leaders saw the message, set acknowledgment on. If it is simply informational, do not require acknowledgment because that creates unnecessary friction.

It is event-based, not recurring. Send it once per announcement, or in stages if the change is complex and leaders need multiple updates. If the same issue keeps coming back, consider a standing change-communication process instead of repeated ad hoc broadcasts.

Include what is changing, when the public announcement happens, what managers should say or do, what they should not speculate on, and where to send questions. A good pre-brief also notes likely concerns, any talking points, and whether leaders should hold comments until the public message is live. Keep the body short and action-focused.

The biggest mistake is burying the key fact or mixing the pre-brief with the full public announcement. Another common issue is giving managers too many actions, which makes the message hard to repeat consistently. Avoid vague language like 'big changes are coming' and avoid asking leaders to share details before the approved announcement window.

An ad-hoc message is easy to send but often inconsistent, incomplete, and hard to track. This template gives you a repeatable structure with the headline fact first, a single call to action, and space for questions or acknowledgment. That makes it easier to keep leaders aligned and reduces the chance of mixed messages reaching employees.

Yes. You can tailor the audience, timing, talking points, and action items for a specific department, site, or rollout phase while keeping the same structure. The key is to preserve the one-message, one-action format so the broadcast stays easy to scan and repeat.