Daily Inspections To Station Dashboards | A Joint Webinar with Integration Partner PSTraxRegister Here! →
Real-Time Internal Communications Platform for Public Safety & LocalGovContactSupportStatus
Blog

Internal Communications for a Combination Department

A combination department should run one information system for career and volunteer members, not two tracks. Safety-critical updates need a confirmed, mobile-accessible channel that tracks acknowledgment, volunteers need an equally timely path to the same information, recognition should reach everyone, and company officers should relay information both ways.

Dave Iannone
Founder & Chief Product Officer
August 17, 2026
Two groups of responders in different work gear greet each other in a station apparatus bay.

A combination department is not one department with two schedules. Communicate it that way and you will build two departments by accident.

A combination department puts career and volunteer members under one name, one chief, one set of apparatus and one mission. It does not automatically put them under one information system, and that gap is where many combination departments quietly split into two departments that happen to share a building.

I have seen this happen without anyone intending it. Career staff get information through the normal channels of a workplace: shift briefings, staff meetings and internal systems they check because it is part of the job they are paid for. Volunteer members get information through whatever reaches them around the rest of their lives. If nobody designs for that difference, volunteers simply get less of it, later, and with more gaps.

Neither group did anything wrong. The organization built its communication habits around whoever was easiest to reach, and the easiest to reach is almost always the paid staff who are present on a predictable schedule.

The Trap Is Built Into the Schedule, Not the People

Career members work a defined schedule. That makes them easy to brief, easy to catch at shift change and easy to reach through channels that assume regular presence, like a station whiteboard, a daily roll call or a staff meeting.

Volunteer members participate around jobs, families and everything else in their lives. Some show up several times a week. Others show up for calls and scheduled trainings. No two schedules look alike, which means any communication system built on “people will see this because they are here” excludes a meaningful share of the department by design.

That is the trap. Nobody decided volunteers matter less. The default tools, the ones that work fine for a fully career or a fully volunteer department, simply do not work for a department that is genuinely both, unless someone deliberately accounts for the difference.

Two Departments in One Is the Failure Mode, Not a Feature

Some combination departments respond to this gap by running two communication tracks: one for career staff and one for volunteers, each with its own rhythm and content. That feels practical in the moment. It is also exactly how a department ends up with two cultures that do not trust each other, do not fully understand what the other group does day to day, and each assume the other gets preferential treatment.

I have heard both sides of that resentment in the same department, sometimes in the same week. Volunteers who believe career staff get the real information first and volunteers get whatever trickles down. Career staff who believe volunteers are treated as guests rather than full members and are left out of decisions that affect the whole house. Both perceptions can be partly true at once, and both are corrosive to a department that needs everyone functioning as one team on the fireground, on a call or in a patrol car.

Safety-critical and operational information, in particular, cannot run on two tracks. A protocol change, an SOG revision, an equipment recall or a policy update has to reach every qualified person regardless of pay status, on the same timeline, with the same expectation of comprehension. Splitting that by employment category creates liability exposure with a schedule attached.

Design for the Difference, Not Around It

The fix is not to pretend career and volunteer members have identical availability. They do not, and pretending otherwise just recreates the same gap under a different name. The fix is to design the communication system around that real difference on purpose.

Separate delivery from urgency, and account for presence. Anything safety-critical needs a delivery method that does not depend on being physically present at a specific time, because many of your volunteers will not be there when it is announced at a shift briefing. That usually means a confirmed, mobile-accessible channel with a way to track who has actually seen and acknowledged the message, rather than assuming word gets around.

Give volunteers a real path to the same information career staff get by default. If career staff learn about a change at a Tuesday staff meeting, volunteers need an equally real, equally timely way to get the same information, not a watered-down version that arrives a week later because someone eventually remembered to mention it. Sometimes that means rethinking meeting schedules. More often it means building a reliable written channel that does not depend on anyone being in the room.

Do not let recognition and culture split along the same line. Communication also covers the announcements, recognitions and department news that make people feel part of the same organization, beyond the operational traffic. If volunteers only hear about milestones, promotions or losses secondhand, well after career staff knew, that absence sends its own message about who counts as a full member.

Use the first-line supervisor as the bridge. Company officers who work with both career and volunteer members are often the most trusted relay precisely because they see both groups operate. Equip them to carry information and concerns both ways, for both groups, rather than assuming the role only serves whoever happens to be on duty with them.

Ask volunteers directly what is working. Career communication habits are built into daily operations, so they get tested and adjusted constantly. Volunteer communication often does not get the same scrutiny, because leadership assumes it is working until someone says otherwise, usually on their way out the door. Ask the question before that happens.

One Department Requires One Information System

None of this means career and volunteer members need identical schedules or identical roles. The differences between the two are real and worth respecting rather than erasing.

What they need is equal, reliable access to the same information at the same standard, delivered in a way that accounts for different availability instead of assuming everyone is equally easy to reach. A combination department that gets this right feels like one organization to its members. One that does not gets a slow, quiet split into two, built entirely out of who happened to be in the room when the important things were said.

At First Arriving, we built our platform so the same message can reach members on station dashboards, the web and a mobile app, targeted by station, division or role, with read receipts that show who has seen it. That way, being off shift or off site does not mean being out of the loop.

Frequently asked questions

Why do volunteers in combination departments often miss information?

Most communication habits assume regular presence, such as shift briefings, roll call and staff meetings. Volunteers participate around jobs and families, so channels built around who is in the building leave many of them out.

Should career and volunteer members get separate communications?

Not for operational or safety-critical information. Protocol changes, SOG revisions, recalls and policy updates should reach every qualified member on the same timeline with the same expectation of comprehension.

What is the best channel for safety-critical updates in a combination department?

Use a channel that does not depend on physical presence: written, accessible on a phone, and able to show who has seen and acknowledged the message.

About the author

Dave Iannone

Founder & Chief Product Officer

Founder of Firehouse.com and Firefighter Nation, a veteran entrepreneur and lifelong first responder and leader.

More from the Blog

October 6, 2026

The Group Text Is Not a Communications Plan

October 1, 2026

Did Your Message Actually Land?

September 22, 2026

The Officer Is Your Communication Hub

Get a single, real-time view of everything that matters.

See how departments put the right information on every screen — in the station, on the desktop, and in the field. Schedule a walkthrough tailored to your agency.

Get a Quote / Request a Demo

No spam. We’ll only use your info to schedule your demo. See our privacy policy.