Co-authored by Marcus Edwards and the
Western Fire Chiefs Association
Modern fire departments respond to everything. A 911 call today can mean a structure fire, a cardiac arrest, a hazmat spill, or a mental health crisis. That operational complexity created a software problem that built up over decades. CAD systems, incident reporting, training records, scheduling, and payroll each grew their own vendors, their own standards, and their own data silos. WFCA refers to the goal of solving this as achieving a “Common Operating Picture (COP).” Most departments are still working toward it, and understanding how they got here explains why the path forward is harder than it looks.
For most of that history, software decisions followed a familiar pattern. You bought what the incumbent vendor sold, accepted that it probably wouldn't work the way you were promised, and worked around it. The institutional memory of bad software rollouts runs deep in fire departments. Chiefs who lived through a failed implementation or a records management migration that took two years longer than planned don't forget it. That experience shaped a professional culture with a reasonable default toward new technology. Wait, be skeptical, and only move when staying put becomes genuinely untenable.
That posture is still present in most departments, and yet something has shifted in the last several years that makes it harder to sustain. Across WFCA's western membership, the conversation is moving. Chiefs who have attended Fire Tech U, WFCA's technology education platform for fire service leaders, describe arriving with skepticism and leaving with specific implementation questions. The question fire chiefs are bringing to those sessions has moved from whether modern software is worth the disruption to figuring out how to modernize without adding another disconnected system to the pile.
“Between Fire Chiefs who have faced situations like the one described above, to data analysts entering into the fire service bringing a more professional approach to technology, to the shift in desire to create a better technology procurement system, the “old way” of doing business should no longer be the norm. Technology education by trusted sources is readily available- smart leaders will engage that education”
- Mark Niemeyer, CEO WFCA
That is a meaningful change. Understanding what drove it matters for any fire department leader trying to figure out where their organization stands right now.
Five Generations, One Station
Part of what makes this shift complicated is that fire departments are navigating it with workforces that span a wider generational range than almost any other profession. The U.S. fire service currently has five generations serving simultaneously, from Traditionalists to Gen Z, each with fundamentally different relationships to technology and different expectations of what a modern workplace should look like.
Career veterans may be less inclined toward rapid technological adoption, while younger generations, particularly Gen Z, thrive in technology-rich environments and may become frustrated by outdated systems or resistance from older colleagues. That tension plays out at the kitchen table every shift. A 24-year-old firefighter who has never navigated a workplace without a smartphone sits across from a 20-year veteran who built their career on experience, instinct, and systems that worked even when the software didn't.
Fire chiefs are managing both of those people, and the software they choose sends a message to each of them. Millennials and Gen Z expect a technologically advanced environment that promotes a culture of innovation and continuous learning. That expectation is no longer abstract. It is showing up in where people apply and whether they stay.
The recruiting implication is direct. Departments that still manage shift trades through a whiteboard and run payroll corrections through a spreadsheet are broadcasting something to candidates whether they intend to or not. Transparent scheduling systems, functional bidding processes, and mobile-first tools are no longer premium features. For a generation of firefighters who have had a supercomputer in their pocket since high school, they are table stakes.
The generational pressure was building before 2020. COVID accelerated it in a way nobody anticipated, and the mechanism was specific. Before the pandemic, it was essentially unheard of for a fire chief to meet a vendor over video. The culture of the fire service ran on handshakes, site visits, and in-person demos, and almost none of that translated to a video call. Departments discovered almost overnight that they could evaluate software, negotiate contracts, and close deals without anyone getting on a plane. The chiefs with modern, cloud-based systems could navigate remote processes more flexibly, and the ones who couldn't felt that gap.
That comfort with virtual evaluation opened doors that had been closed for years. Departments that would never have looked at a new scheduling platform, a new records system, or a new payroll integration suddenly had both the time and the mechanism to do it. Software categories that had been ignored got evaluated. Vendors that had counted on inertia to keep their contracts found themselves in competitive conversations for the first time.
At the same time, legacy vendors got worse. Departments locked into multi-year contracts watched support response times stretch, per-user pricing climb, and feature requests disappear into a backlog with no timeline. The frustration built during that period hasn't dissipated. Chiefs who've been through a bad implementation ask harder questions the second time.
Then NERIS replaced NFIRS, and the forced evaluation accelerated further. As WFCA's own migration guide notes, data reporting under NFIRS could be delayed by more than a year in some instances, and the variability in data quality was significant. NERIS was built to change that, with near real-time reporting and the ability to interoperate with other systems. But many NFIRS vendors never made the transition, leaving departments with no choice but to find a new vendor entirely.
For departments that were already more open to virtual evaluation after COVID, that search widened quickly. Scheduling software, payroll integrations, and communications tools all came up for review in ways they wouldn't have a few years earlier.
WFCA sits at a vantage point no single vendor has. As the association representing fire chiefs across the western United States, it sees what happens across an entire membership of departments simultaneously, including which questions keep coming up, where the conversations are stuck, and what separates the organizations moving forward from the ones that aren't. No implementation partner or software vendor sees that picture.
Fire Tech U offers one window into how that picture is changing. The webinar series has progressed from foundational technology integration toward AI, data infrastructure, and implementation strategy, tracking the questions member departments are actually bringing to the table.
Sourcewell, one of WFCA's cooperative purchasing partners, recently released Advancing the Future of Fire-Rescue Operations, a free guide built specifically for fire rescue agencies looking to modernize. Fire departments are still structurally set up to buy hardware rather than software, and procurement processes rarely account for SaaS evaluation well. A guide like this exists because the gap is real and departments are asking for help navigating it.
“Best Practice, specifically around technology strategies, is present in some but not prominent in all. One goal of the WFCA is to continue educating fire service leaders around “outcomes first, technology last”. Every department should have a technology strategy that compliments their strategic plan. Failing to do so results in impulse purchases, as opposed to planned procurement”- WFCA
The resistance hasn't gone away. According to the NFPA's 2025 Industry Trends Survey, 44% of respondents across skilled trades cite implementation costs as the primary obstacle to technology adoption, followed by a lack of training or knowledge at 25%. Another 20% anticipate resistance within their organization to adopting new technologies at all. Fire service leaders report similar pressures.
The fuller picture of what fire chiefs are managing goes well beyond adoption metrics. A chief is responsible for the mental health and physical safety of every person in the department, including crises that have nothing to do with technology. They are accountable for millions in tax-funded spending, with scrutiny that increases with department size. And they are constantly navigating workers' comp claims, wage theft risk, grievances, audits, and union negotiations. Technology decisions land inside all of that.
Software typically fails in the months before go-live. After a contract is signed, many vendors hand the account to a new contact and leave the department to manage the full rollout on their own. Crews are running 48 to 96-hour schedules throughout. Vendors frequently oversell capabilities during procurement and underdeliver once implementation begins. When things go sideways, the department absorbs the consequences. Framing a failed transition as purely a leadership problem misses how much of the setup was working against the department from the start.
Most fire chiefs already know how to bring their organization through something hard. They have done it after line-of-duty deaths, after serious accidents, after contentious union negotiations. They get in front of the crew, explain the why, and stay visible until the organization has moved through it. Technology adoption asks for exactly the same thing. FireRescue1's 2024 state-of-the-industry survey found that 49% of firefighters say poor agency leadership has a high impact on retention, and when a technology transition goes badly, it rarely stays contained to the software. It becomes the symbol for everything the crew already felt about how the department communicates and makes decisions.
Proof of concept before full rollout is one of the most consistently underused tools fire leadership has. Most RFPs require only a written response. A vendor can submit a 200-page document without showing a single screenshot of how the product actually works, and many do. Running a real pilot with a defined group after the RFI but before formally kicking off an RFP teaches more about a department's operational complexity in two weeks than any demo will surface. It also creates internal champions who can speak credibly to the rest of the crew from peer experience rather than management mandate. That peer-to-peer credibility carries more weight in a fire department than anything that comes down from leadership.
One of the most consistent themes in conversations with fire chiefs who have been through a software transition is how quickly the vendor relationship changes after the sale. The attention that characterized the procurement process often doesn't survive the first six months. Feature requests discussed in demos don't show up on the roadmap. Support tickets that were promised same-day responses take days or weeks. The contact who knew the department's specific setup gets replaced by someone who doesn't know the department's rules or the fire service at all. A chief calls to ask about a shift trade and the person on the other end asks what a shift trade is.
The fire department management software market is growing at a compound annual rate of 10.8% through 2033, which means more vendors, more competition, and more pressure on incumbents to cut costs rather than improve service. Departments that sign a five-year contract with a company whose roadmap doesn't reflect their actual operational needs are going to feel that gap more acutely over time.
The departments that get this right treat the vendor relationship as an ongoing partnership with mutual expectations, not a transaction that concluded at go-live. They establish clear escalation paths before anything goes wrong. They ask specifically how feature requests get prioritized and what the timeline for resolution looks like. And they find out, before they sign, whether the department will be talking to the same team six months after implementation as they were during the sales process.
There is no single moment when a fire department is ready to modernize. Fire departments sit at very different points on that path, ranging from those still recovering from a transition that went badly, to those mid-evaluation, to those already past go-live and working out how to get more from the systems they have.
The departments navigating this well are the ones that treat technology adoption as an organizational change initiative from the start, giving it the same internal structure and leadership investment they would bring to any major operational decision. They form a committee early, one that deliberately pulls in tech-savvy junior members alongside command staff, because the people closest to daily operations often surface problems that leadership doesn't see from the top. That group assesses options, makes decisions, and carries the message back to the organization in a way that command mandates alone never do. The platform and implementation matter, but neither works without that internal structure in place before anyone signs a contract.
On April 23, WFCA and Stationwise are bringing together chiefs and practitioners who have been through this firsthand to talk about what technology change actually asks of fire department leadership, including the parts that no vendor demo covers. Register here.
