Trending Topics

Making the case for standard company assignments

A shared playbook for first-alarm companies cuts guesswork, keeps critical tasks from slipping and frees the IC to focus on strategy

Engine, truck, and command in sync.png

We’ve all heard the mantra: “As the first line goes, so goes the fire.” To be fair, the statement doesn’t give truck companies much credit, so let’s broaden it: The actions of the first-alarm companies dictate the remainder of the incident. If everyone arriving on scene is working from the same standard playbook, incidents can run more smoothly and efficiently.

Structural firefighting isn’t easy, but it can be simple. One way to simplify it is through standard company assignments.

| READ MORE: One fireground, one language: The power of standardized radio communications

What standard company assignments look like

Standard company assignments begin at the organizational level, long before an incident occurs. Companies should be assigned and staffed adequately to fulfill their traditional responsibilities. Traditional engine or ladder companies should consist of an officer and two or three firefighters.

Whenever possible, companies should perform the traditional functions for their type:

  • Engines: confinement, extinguishment, exposure protection and water supply
  • Trucks: forcible entry, search, ventilation, overhaul and utility control

A standard operating procedure or guideline (SOP or SOG) on company assignments provides a list of critical fireground tasks and the companies expected to perform them. For example, the first-arriving engine would be assigned to fire attack, the first-arriving truck to search. The second engine company would be assigned water supply and to pull a second line. The next truck would be assigned ventilation, and so on. This concept allows tactical decisions to occur at the company level, leaving the incident commander to focus on strategy. It also improves accountability because it removes the guesswork.

Staffing situations

While fireground tasks should be assigned to the company best suited for them, crews should be cross-trained in all fireground responsibilities. Not every department has a ladder truck, but that doesn’t mean truck work gets passed over. Those tasks are still essential, so an engine crew may need to search or provide ventilation if a ladder company isn’t available.

This can be a challenge for volunteer departments, but it can work with adequate training and disciplined deployment. For example, if a volunteer department requires three or more personnel to be on board before an engine company rolls out the door, that crew is better suited to function as an engine company than it would be with only two firefighters in the cab.

Staffing shortages are a challenge for volunteer, combination and career departments alike, and they can push departments toward a piecemeal approach on scene. We need to be careful not to shrink our response capabilities just because of staffing. While most fireground tasks can be completed by two people, a crew’s efficiency and safety improve exponentially as you add a third, then a fourth firefighter. Leaders should avoid deploying crews of fewer than three.

Why a playbook matters

Incident commanders often rely on checklists to make sure critical tasks are completed, and many fireground tasks have to happen in the first few minutes on scene. Some ICs assign these tasks as the incident is expanding and as companies arrive, but this “as it happens” approach leaves little room for error.

We have RECEO-VS and SLICERS to help ensure fireground priorities are met, but how do you actually put those into play? (RECEO-VS: Rescue, Exposures, Containment, Extinguish, Overhaul - Ventilation and Salvage; SLICERS: Size-up, Locate the fire, Identify and control flow path, Cool the space from safest location, Extinguish the fire, plus Rescue and Salvage.)

With some planning and coordination, standard assignments can help you get there. This isn’t a concept reserved for large, career-staffed departments; even smaller departments that rely on mutual aid can make it work. It just takes some planning and coordination.

Using standard, pre-determined assignments may sound stringent and restrictive, but flexibility can be built in to address situations that don’t go as planned. Like a quarterback on a football field, an incident commander can call an audible and change the play if needed. The key is that audibles remain the exception and don’t become the rule.

“We’ll figure it out when we get there” is not an effective tactical plan, but plenty of departments get by on it. This works until it doesn’t. What happens when something gets missed or isn’t completed? Even if staffing limitations restrict how fully you can standardize, you should still have a framework in place that helps ensure incident objectives are carried out properly. That framework prevents freelancing and helps ensure critical tasks aren’t missed. If everyone knows who’s doing what before the fire even happens, the operation goes smoothly.

Borrowing a concept from the Navy

A standard framework doesn’t remove the IC’s authority or eliminate the check-in at the command post; it simplifies it. As companies arrive on scene, the IC simply confirms their assignment. This mirrors a concept David Marquet wrote about in “Turn the Ship Around!” Marquet, a Naval officer, implemented intentional leadership aboard his submarine, the USS Santa Fe. Once he confirmed his crew knew their roles and responsibilities, he told them to simply inform him of their intentions. If he agreed, he confirmed them.

For example: “Captain, I intend to submerge the ship. We are in water we own, water depth has been checked and is four hundred feet, all men are below, the ship is rigged for dive, and I’ve certified my watch team.”

Marquet: “Very well.”

This approach had several effects. It was efficient and simple, cutting out micromanagement and excessive back-and-forth. It gave the crew genuine ownership: They weren’t just being told what to do, they were part of the decisions being made. And it required people to think about things one level above their position, which trained them for advancement and broadened their perspective on the operation.

As a fire officer, you can lean into this same approach. The simplicity and efficiency fit the fireground well, and we know micromanagement stunts professional growth. The broader perspective it builds improves situational awareness.

On the fireground, it might sound something like this:

Battalion 1: Battalion 1 is on scene with heavy smoke from the eaves of a two-story wood-framed residence. I’m establishing Oak Street Command.
Engine 1: Engine 1 is on scene, stretching a line.
Battalion 1: Affirmative, Engine 1.
Truck 3: Truck 3 is on scene, doing a primary search.
Battalion 1: OK, Truck 3 primary search.
Engine 2: Engine 2 on scene, establishing water supply.
Battalion 1: Command copies, Engine 2 has water supply.

These standard assignments should cover all initial, critical fireground actions, including:

  • Forcible entry
  • Fire attack
  • Search
  • Water supply
  • Ventilation
  • Utility control
  • RIC

If your radio procedures require more detail, that’s fine; the goal is to streamline communication, not eliminate it.

Without a playbook, operations get complicated and radio traffic increases unnecessarily. We’ve all heard something like this: “Truck 2 is approaching the scene, Command.

What’s our assignment?” In a more organized environment, the Truck 2 officer already knows their assignment, or at least knows what to expect.

“Yeah, but what if …?”

If you’ve spent any amount of time in the fire service, you are familiar with the “yeah, but, what if” argument. We identify and communicate a need for change and it seems like a good idea, then someone says, “Yeah, but what if ….?” We hear it a lot when discussing change, and it’s a useful perspective to keep, even when it’s frustrating to the person proposing the change because it exposes blind spots.

What if the second-due engine arrives first, or a truck company gets pulled to another incident? Both are realistic, valid concerns. If arrival order differs from expected, firefighters and officers should be aware of it and be ready to take a different assignment. If a company is unavailable, another one should replace it, and that substitution should be communicated over the radio to all responding units.

In many small and mid-sized departments, crews are cross-trained, and search, while generally viewed as a truck company responsibility, is a job an engine crew can do just as well. If Ladder 1 is unavailable and gets replaced by an additional engine company, that substitution should be communicated clearly and early to prevent confusion at the scene. For example, when announcing the assignment over the radio, the dispatcher might say this: “Engine 4 responding in place of Truck 2.” When Engine 4 arrives and checks in with the IC, they should expect to be assigned truck company duties.

Making it work across jurisdictions

These concepts need to be backed by clear, effective policies and procedures. In larger, self-sufficient departments, that’s straightforward. But what if your department is small and relies on mutual aid? That’s where inter-agency cooperation comes in. Fire service leaders need to sit down with their neighbors and iron out these details before implementing them. Ideally, guidelines and procedures affecting multi-agency actions should be developed jointly.

No matter where you work, there’s a jurisdictional border where the rules might change, sometimes marked by nothing more than an address. Cross from 2648 to 2650 North Street, and you’re suddenly in another department’s territory. If departments share services, this can get complicated fast. Imagine the confusion if the playbook at 2648 is different from the one at 2650, just because of a line on a map: same type of building, different rules, right next door to each other. It’s imperative that fire service leaders coordinate procedure development to reduce confusion and streamline operations.

Departments can develop joint procedures while still preserving their own identity and autonomy. The color of the apparatus or the patch on the sleeve may differ, but everyone shares the same objectives: life safety, incident stabilization, and property conservation. Working together toward those objectives seamlessly improves both service delivery and firefighter safety.

If your department’s capabilities match your neighbors’, things get easier. From a command standpoint, this lets you streamline operations: if you need an engine company on a task, you simply assign the next available engine. That frees you up to manage the incident, not the individual task. An IC preoccupied with organizing people into ad hoc teams at the scene isn’t available to focus on the bigger picture.

Final thoughts

Standard company assignments aren’t about rigid, one-size-fits-all fireground choreography. They’re about removing guesswork so people can do their jobs well under pressure. When engine and truck crews know their traditional roles going in, when departments cross-train for the gaps, and when neighboring agencies iron out their differences ahead of time, the incident commander is freed up to do the one thing only they can do: Manage the incident, not the individuals in it.

None of this requires a large budget or a big city staffing model. It requires planning, cross-training, honest conversations with mutual-aid partners and a willingness to build a framework before the call comes in. The “yeah, but what if?” questions are worth asking, and the answers are worth writing down, because a plan that only works when everything goes right isn’t a plan at all.

Get the first-in companies operating from the same playbook, and the rest of the incident tends to run more smoothly.

We need a plan that standardizes our response. But how do we do that in the dynamic world of emergency services?

Greg Rogers is a retired battalion chief from the Ridge Road Fire District in Greece, New York, where he developed and implemented programs that improved service delivery and firefighter safety. He is also a nationally certified fire instructor with experience in emergency vehicle operations, engine company operations and building construction. Rogers previously served as a content developer for Lexipol. In addition to his fire service experience, Rogers has a background in maritime search and rescue and law enforcement with the U.S. Coast Guard and Coast Guard Reserve. Rogers holds a bachelor’s degree in fire department administration and has studied at the National Fire Academy as well as the U.S. Coast Guard Chief Petty Officer Academy.