The Internal Communications Playbook for Public Safety

In most agencies, leadership communicates plenty. The trouble is that important information is spread across email, group texts, a Facebook group, a shared drive and the station bulletin board, with no single source of truth and no way to know wh

This playbook is the practical side of that problem. It walks you through sorting what you send, scoring how well your current setup works, cutting channels down to the ones that earn their place, assigning every message type to a channel, and confirming that the important messages actually land, including with members who aren't at the station. Each step has a worksheet you can copy and use with your officers.

1Step 1: Sort information before you send it

Before you fix how information moves, sort what kind of information you're actually moving. Not everything belongs in the same channel, and treating every message the same way is part of why the important ones get lost. (For why the default setup fails, see why the group text is not a communications plan.)

Roughly, department information falls into four categories:

• Safety-critical and time-sensitive. A road closure affecting response, an equipment recall, a change to standard operating guidelines that takes effect immediately.
• Operational and recurring. Schedules, staffing needs, apparatus status, training assignments.
• Administrative. Certification deadlines, benefit enrollment windows, policy updates that take effect over time.
• Cultural and morale. Recognition, milestones, community events, new member introductions.

Each has a different tolerance for delay and a different need for confirmation. A safety notice needs acknowledgment, not just visibility. A cultural announcement doesn't need to interrupt anyone's shift. When every category runs through the same group text at the same volume, urgent items get the same weight as trivial ones, and people stop being able to tell the difference.

Then set a cadence. Daily operational information, such as staffing and schedule notices, can run on its own cycle. Weekly or monthly items, like training reminders and administrative deadlines, belong on a slower cycle so they don't compete with daily traffic. Safety-critical information should never wait for a scheduled cycle; it needs its own immediate path with confirmation built in. The goal is that members know roughly where to look for each kind of information, and roughly when to expect it.

2Step 2: Score your communications health

Next, get an honest picture of where you stand. This self-assessment looks at six areas: how many channels members must monitor, whether messages are targeted and owned, whether acknowledgment is tracked, whether history is searchable, and whether people who aren't at the station still get what they need. It takes about seven minutes. Do it yourself, then have a company officer and a less-frequent member do it too and compare answers.

Self-assessment worksheet

Score each question using the points shown. Average the questions in each area to get an area score from 0 to 100.

1. Channel clarity and fragmentation
2. • To stay aware of important department information, how many separate places must a member check (email, text threads, a Facebook group, a bulletin board, apps, word of mouth)? One or two clear channels = 100; three or four = 50; five or more = 0.
   • Is there one recognized source of truth for official announcements? Yes = 100; no = 0.
2. Audience targeting
3. • Can you send a message to a specific shift, station or role rather than everyone? Yes = 100; no = 30.
   • Do members mostly get information relevant to them, rather than everything going to everyone? Yes = 100; no = 40.
3. Delivery confidence
4. • Does every important type of communication have a clearly accountable sender or owner? Yes = 100; no = 0.
   • For genuinely urgent messages, do you have a mechanism that reliably reaches people quickly? A dedicated alerting method people actually see = 100; group text only = 50; email and hope = 20.
4. Acknowledgment tracking
5. • When a policy or message requires acknowledgment, can you track who has read and acknowledged it? Yes = 100; no = 0.
   • Do you currently require acknowledgment for critical items such as policies and safety notices? Yes = 100; no = 50.
5. Searchable history and retrieval
6. • Can a member easily find a past announcement or policy later, without hunting through old email and texts? Yes = 100; no = 0.
   • Is important information retained and searchable rather than lost in chat threads? Yes = 100; no = 30.
6. Reaching the right people
7. • Is critical information available to members who aren't at the station, through mobile or remote access? Yes = 100; no = 30.
   • Do shift or location gaps cause people to miss information? Rarely = 100; sometimes = 50; often = 0.

Reading your scores

• 85 to 100: Strong.
• 70 to 84: Developing well.
• 50 to 69: Needs attention.
• 30 to 49: Significant gaps.
• 0 to 29: High priority.

One rule overrides the averages: if you have no way to track acknowledgment of required communications, treat that as a priority no matter how well the other areas score. If you can't show who read a critical notice, you can't show it was communicated.

Any area at 60 or below points to a fix later in this playbook:

• Channel clarity low: define a channel framework and name one source of truth (Steps 3 and 4).
• Targeting low: set up the ability to reach a specific shift, station or role. When everything goes to everyone, important messages get tuned out.
• Delivery confidence low: give each message type an owner and one dependable path for urgent messages. "Email and hope" is not a delivery method for anything time-sensitive.
• Acknowledgment low: add read and acknowledgment tracking for your most critical communications (Step 5).
• Searchable history low: keep announcements and policies somewhere members can search and retrieve them. Information people can't find again is only half-communicated.
• Reaching people low: make critical information available on mobile so volunteers, off-duty members and multi-station personnel get it without being physically present (Step 6).

3Step 3: Reduce before you add, and pick a channel of record

If your department is dealing with missed information right now, the instinct is to add something: a new app, a new group, a new reminder system. Resist that until you've looked honestly at what you already have. Members don't maintain five habits; they maintain one or two and let the rest slide. A new app on top of the text thread, the email and the board gives them a sixth thing to check. (More on this in our piece on having too many channels.)

Work through this list with your officers:

1. Count every channel currently in use, including the group chat nobody remembers agreeing to join.
2. For each one, ask who actually checks it, and how often.
3. Identify channels that have quietly died: still technically active, ignored by most of the roster, but still receiving messages out of habit.
4. Retire those before adding anything new.
5. Name one channel of record: the place where anything that must reach every member lives, in a form someone can go back and check.
6. Tell the whole roster what each surviving channel is for.

The channel of record doesn't have to be fancy. It has to be consistent, and it has to be the answer every time, not just when it's convenient. Text threads, hallway conversations and quick mentions at roll call can still exist to coordinate and reinforce. They can't replace it. If information only ever lived in a text thread that half the department muted, it wasn't actually delivered.

4Step 4: Assign every message type a channel

Each channel is good at something specific. The mistake is using them interchangeably instead of deliberately.

• Text or app notification: short, time-sensitive, personal. Things a member needs to see in the next few minutes.
• Email: detail, documentation and a permanent record, like a policy change or benefits update. A poor fit for anything urgent.
• Bulletin board or station screen: information that benefits from being seen repeatedly by anyone who walks past. Depends entirely on physical presence.
• In-person briefing: anything that benefits from discussion, questions and tone. Only reaches whoever is in the room.
• Required acknowledgment: anything where you need proof that a specific person saw it.

Channel assignment worksheet

List the message types you actually send (shift schedule changes, open shift requests, safety bulletins, training reminders, policy updates, apparatus out of service, recognition, community events, and so on). For each one, fill in:

1. Message type.
2. Urgency: immediate, same-day or routine.
3. Does it require action or acknowledgment? Yes or no.
4. Sensitivity: can it ever appear on a public channel, or is it internal only?
5. Audience: everyone, or a specific shift, station or role?
6. Lifespan: does it matter for an hour, a week, or until the next revision?
7. Primary channel and a one-line reason.
8. Backup channel.
9. Owner: who is accountable for sending it.

When the sheet is done, check it for four problems:

• Urgent messages assigned only to passive channels, like email or a bulletin board.
• Required actions with no acknowledgment path.
• Sensitive or internal messages assigned to public channels, like a public website or social media.
• Routine content overusing interruptive channels, like push alerts or texts for a social event.

Then group the result by urgency: what goes out immediately, what goes out the same day, and what runs on the routine cycle. That's the start of your written rules in Step 7.

5Step 5: Confirm that the message landed

"I sent it" is not the same as "they got it." Sending a message is not the same as it being received, receiving it is not the same as reading it, and reading it is not the same as understanding it. Most departments only verify the first. (More on making sure your message actually landed.)

Reserve acknowledgment for what actually needs it. A reminder about a social event doesn't need a confirmed read receipt. A change to a safety procedure does. A new duty schedule does. The line is simple: if getting it wrong could put someone in the wrong place, out of compliance, or at risk, the message needs a way to confirm it landed.

Acknowledgment tells you a message was seen, not that it was understood. For high-stakes items, add a read-back: have the person state the change in their own words. It's a habit borrowed from radio communication because it works, and it surfaces misunderstandings while they're still cheap to fix.

6Step 6: Reach the members who aren't at the station

Every agency has a core group that is around constantly, and a larger group that isn't: volunteers with full-time jobs, part-timers, off-rotation staff, members on light duty, people covering a different station. Don't under-communicate with them because they aren't your daily regulars. They respond to the same calls and are bound by the same policies. (More on reaching members who aren't at the station.)

Nobody decides to leave them out. It happens because so much information travels by proximity: roll call, shift briefings, a board, a hallway conversation. Proximity always favors the same people.

• Identify the categories that can't depend on being at the station: schedule changes, policy updates, safety notices, and anything that affects whether a member shows up prepared.
• Send those through a channel that works the same for someone who was in yesterday and someone who hasn't been in for two weeks.
• Don't treat a briefing as the record. Put a written version where the whole roster can see it.
• Watch for patterns. If the same members keep getting caught off guard, fix the channel, not the people.
• Ask less-frequent members directly whether they feel they're getting the same picture as everyone else.

Then run the test: pick a member who wasn't at the station this week and ask what they know about the last policy change, schedule adjustment and safety notice. If their answer is noticeably thinner than a daily regular's, your system is working for part of your roster and failing the rest.

7Step 7: Write simple rules and reassess

Turn your worksheet into a short written rule set the whole department can follow. Keep it to a handful of plain lines, for example:

1. Our channel of record for anything every member must see is ______.
2. Immediate, safety-critical messages go out on ______ and require acknowledgment.
3. Same-day operational messages go out on ______.
4. Routine and administrative items go out on ______ on a set weekly or monthly cycle.
5. Recognition and community news go on ______, separate from operational traffic.
6. Anything discussed at a briefing that affects the whole roster is also posted on the channel of record.
7. Each message type has a named owner.

Communication drifts back toward fragmentation over time as new apps and habits creep in. Re-run the self-assessment periodically, and any time you add a channel or change leadership.

A real communications plan doesn't need to be complicated. It needs to sort information by urgency, deliver it through a channel suited to that urgency, and confirm it reached the people who needed it. If you can't say with confidence whether every member on every shift saw last week's policy change, start with Step 1.

At First Arriving, we built our platform around these same principles: station dashboards that keep operational information visible, targeted messaging by station, division and role, and required acknowledgments so you know who's read what, on desktop, web and mobile.