There is a version of Community Risk Reduction that looks like this:

A prevention bureau develops programs. A fire marshal conducts inspections. A public education specialist visits schools. A CRR coordinator tracks data and reports outcomes to leadership.

And somewhere across the hallway, the engine company goes out on calls, comes back, cleans equipment, trains, and waits for the next alarm.

This model is not wrong. Prevention bureaus matter. Fire marshals matter. Public education matters. Data matters.

But this model is incomplete — and its incompleteness is one of the primary reasons CRR programs struggle to scale, sustain momentum, and produce the outcomes they are designed to achieve.

CRR that lives exclusively in a prevention bureau has a ceiling. And that ceiling is the size of the prevention bureau.

The only way CRR reaches the scale a community actually needs is when company officers understand their role in it — and embrace it.

The Most Influential Position in the Fire Service

Ask any experienced fire service leader where culture is actually shaped in a fire department and the answer is almost always the same.

Not at the chief level.

At the company level.

The company officer — captain, lieutenant, or whatever title the jurisdiction uses — is the most influential position in the daily life of a fire department. They set the tone for how the crew approaches every shift. They model what is valued and what is dismissed. They determine what gets done and what gets deferred. They are the translation layer between organizational priorities and actual behavior.

When a chief says CRR matters, that statement means something.

But when a company officer says CRR matters — and then demonstrates it in how they lead the crew, how they approach calls, how they spend time in the community — it becomes real in a way that no policy document or prevention campaign ever can.

Company officers do not just influence CRR. They determine whether it takes root in the culture or quietly fades into the background.

What the Company Level Sees That Prevention Bureaus Cannot

There is a category of community risk intelligence that exists nowhere else in the fire service except at the company level.

It is generated every shift, on every call, in every neighborhood the crew serves.

The elderly resident who answered the door confused and disoriented during a medical call — and whose home showed signs of significant hazards that had accumulated unaddressed.

The apartment building where the crew has been called four times in six months for the same recurring issue that nobody has formally identified as a risk pattern.

The block where three homes in a row have no working smoke alarms — discovered during a gas leak response when the crew was briefly inside each structure.

The commercial occupancy where the back exit is routinely blocked by delivery pallets every time the crew passes by.

The neighborhood where a recent demographic shift has brought a significant population of residents who do not speak English and who have had no contact with any fire department prevention program.

None of this intelligence appears in NFIRS reports. None of it shows up in inspection databases. None of it reaches the prevention bureau unless a company officer decides to do something with it.

The company level is the most prolific generator of community risk intelligence in any fire department. The tragedy is that in most departments, most of that intelligence is never captured, never shared, and never acted upon.

The Notice Name Nudge Notify Framework in Action

The framework introduced at the Vision 2020 Symposium 9 by Fire Chief Kris Blume of Meridian Fire Department — Notice, Name, Nudge, Notify — is not a prevention bureau tool.

It is a company officer tool.

Notice: the company officer creates a culture where crews pay attention beyond the immediate incident. What risk conditions exist here beyond the reason we were called? What does this address tell us that our data doesn’t already show?

Name: the company officer helps the crew develop the habit of identifying specific risk factors rather than accepting vague impressions. Not “that place looks rough” but “that home has no working smoke alarms, significant hoarding conditions, and an elderly resident who appears to be living alone without regular contact with family or services.”

Nudge: the company officer empowers crews to take small, immediate actions when appropriate — offering a smoke alarm, providing a resource, making a brief safety observation — rather than treating every prevention opportunity as something that requires a formal program and a scheduled visit.

Notify: the company officer creates a reliable pathway for risk intelligence to move from the crew to whoever can act on it — whether that is the prevention bureau, a community partner, a social services agency, or department leadership.

This framework produces results when company officers make it part of how the crew thinks about every call. It produces nothing when it remains a conference concept that never makes it into the apparatus bay.

The Cultural Permission the Company Officer Grants

One of the most underappreciated aspects of the company officer’s role in CRR is the cultural permission they extend — or withhold — every single day.

When a crew returns from a medical call and the company officer asks “what did you notice about that home that we should know about?” — that question grants permission. It signals that observation is part of the job. That prevention thinking is expected. That the crew’s eyes and ears in the community have value beyond the incident they were dispatched to handle.

When a crew returns from the same call and the company officer says nothing — or worse, signals through tone or behavior that the call was routine and forgettable — that silence also grants permission. It signals that what matters is the response, not what was observed. That prevention is someone else’s job. That the only thing worth discussing is what happened on the call, not what the call revealed about the community.

Neither of these outcomes requires a formal policy. Neither requires training. They emerge entirely from the culture the company officer creates through daily behavior and daily choices.

A chief can mandate CRR. A prevention bureau can develop CRR programs. A city council can fund CRR initiatives.

But a company officer can make CRR real — or keep it theoretical — in ways that none of those levers can fully reach.

The EMS Connection

In most departments, the majority of what company-level crews do every day is EMS.

And EMS is one of the richest sources of community risk intelligence available to the fire service — if company officers are equipped and encouraged to treat it that way.

The repeat medical calls at the same address. The patient whose medication management is clearly deteriorating. The assisted living facility that generates a disproportionate share of lift assists. The neighborhood where overdose calls are clustering in ways that suggest a pattern rather than isolated incidents.

These are not just EMS calls. They are risk signals — and the company officer is in the best position to recognize them, name them, and ensure they reach someone who can act on them.

An EMS call handled well saves one person.

An EMS call handled well and observed carefully — with the risk intelligence captured and shared — may prevent the next call entirely.

That is the difference between response and Community Risk Reduction. And it happens, or does not happen, at the company level.

The Practical Reality of Competing Priorities

None of this is simple. Company officers are managing real demands — staffing shortages, training requirements, equipment maintenance, administrative responsibilities, and call volumes that in many departments leave little room for anything beyond response readiness.

Acknowledging that reality is important. The argument here is not that company officers should add CRR to an already overwhelming workload as a separate obligation.

The argument is that CRR thinking — the habit of noticing risk, naming it, nudging where possible, and notifying where needed — is not an addition to the company officer’s job.

It is a different way of doing the job they are already doing.

The crew is already going on calls. The company officer is already leading debrief conversations. Crews are already passing through neighborhoods, entering homes, interacting with residents. The calls are already happening.

What changes is not the activity. What changes is the question the company officer asks about that activity.

Not just: did we handle that call well?

But also: what did that call tell us about this community — and what should we do with that information?

That shift in question does not require more time. It requires a different orientation — and a company officer who models it consistently.

What Leadership Must Provide

Company officers cannot do this alone. And it is not reasonable to expect them to without organizational support.

Department leadership must make the expectation clear. CRR participation is not optional or collateral. It is part of how the department defines its mission and measures performance. Company officers need to hear that explicitly — not once in a strategic plan document, but consistently, in the language leaders use, in the metrics they track, and in the conversations they have.

A simple mechanism for capturing and sharing risk observations must exist. A company officer who wants to share a risk observation should not have to navigate a complex reporting process to do so. The friction between observation and notification must be low — or the intelligence will be lost before it reaches anyone who can act on it.

CRR contributions should be recognized. When a company officer’s observation leads to a prevention visit that identifies a significant hazard, that outcome should be visible. When a crew’s notification results in a social services referral that changes a resident’s situation, the crew should know it happened. Recognition does not require elaborate ceremony. It requires acknowledgment — and acknowledgment signals that the behavior is valued.

Training and context help. Company officers who understand how risk data is used, how prevention programs are developed, and how their observations connect to broader CRR strategy are more likely to engage meaningfully. Connecting company-level crews to the CRR process — not just asking for their observations but showing them what happens with those observations — builds investment that sustains over time.

The Ceiling That Doesn’t Have to Exist

Return to the model described at the beginning of this article — the prevention bureau doing prevention work while the engine company waits for alarms.

That model produces a certain level of CRR activity. It may even produce good outcomes within its boundaries.

But it has a ceiling. And that ceiling is determined entirely by the capacity of the prevention bureau.

The model that breaks through that ceiling is one where the company officer is a genuine participant in CRR — not as a substitute for prevention staff, but as an extension of the department’s risk intelligence and risk reduction capacity into every neighborhood, every shift, every call.

In that model, the reach of CRR is no longer limited by how many prevention staff the department can fund. It is extended by every crew, on every apparatus, on every call.

That is what CRR at the company level actually means.

And the company officer is the person who decides whether it happens.

Brent Faulkner, MAM, FO, is the CEO and Founder of Virtual CRR Inc.
A retired Battalion Chief from Anaheim Fire & Rescue, Brent brings 28 years of fire service experience, including leadership in structure fires, wildland operations, hazardous materials response, EMS incidents, and specialized rescue operations. He also served 17 years on a Type 1 Hazardous Materials Response Team.

A defining moment in Brent’s career came while leading Critical Infrastructure Protection (CIP) efforts at a DHS-recognized Terrorism Fusion Center. There, he oversaw initiatives to safeguard critical infrastructure from terrorism, natural disasters, and emerging threats — an experience that shaped his passion for Community Risk Reduction and ultimately led to the creation of Virtual CRR.

Brent holds a Master’s Degree in Management, a Bachelor’s in Occupational Studies, and Associate Degrees in Hazardous Materials Response and Fire Science.