Incident Management Teams (IMTs)

by

Incident Management Teams: How Large Fires Stay Organized

If you’ve followed wildfires for any length of time, you’ve probably heard phrases like “they’ve ordered a team” or “a Type 1 IMT is taking over tomorrow.”
Behind those phrases is one of the most important – and least understood – parts of modern fire response: incident management teams.

This post is a plain‑language walkthrough of what those teams are, when they get called in, and why they matter so much for how big fires play out.

The Incident Command System in a Nutshell

At the core of large‑fire management is the Incident Command System (ICS). It’s a standardized way to organize people, decisions, and logistics during chaotic/complex events.

On any sizeable fire, ICS breaks the work into four main sections:

  1. Operations
    • The “doing” people.
    • Directs crews, engines, aircraft, dozers.
    • Decides where to build line, where to go direct, and where to back off.
    • IMTs also respond to non-fire disasters like floods, volcanic eruptions, terrorist attacks, or pandemics. Here, Operations may supervise flood-fighting, urban search and rescue, managing shelters, supporting health care, or cleaning up debris.
  2. Planning
    • The “thinking and mapping” people.
    • Orders resources and tracks ones which have already arrived.
    • Builds an Incident Action Plan (IAP) each operational period that tells each person their assignment and who they’re working for.
    • Tracks fire growth, weather, resource needs, and potential future scenarios for the incident.
    • Develops and distributes forecasts, maps, and reports.
    • Documents what happened.
    • Demobilizes resources once they are no longer needed.
  3. Logistics
    • The “getting stuff where it needs to be” people.
    • Food, water, fuel, hose, radios, porta potties, sleeping areas, showers.
    • Delivering supplies to the field, handling all transportation needs.
    • Building and managing a large base camp.
  4. Finance / Administration
    • The “money and paperwork” people.
    • Tracks costs, contracts, time, damage claims, and compensation.

Section Chiefs report directly to the Incident Commander. Each Section supervises Unit Leaders.
Several positions report directly to the Incident Commander: Public Information Officers, Safety Officers, Liason Officers, and others as designated by the IC.

ICS can be used to organize anything from a wedding or funeral up to a major earthquake or massive wildfire. Even a fairly small incident uses the same skeleton structure – it’s just scaled down. A single person might fill several roles on a small fire; on a massive one, an Incident Management Team might be in charge, with dozens or hundreds of people working using ICS as their command structure.

What Is an Incident Management Team?

An incident mangement team or IMT (formerly called an Incident Command Team) is a pre‑built group of people who are trained and qualified to plug into the ICS structure and supervise a complex incident. More details on IMT positions, here:

Think of an IMT as a traveling crew of professionals that can arrive on a fire and stand up a full-blown organization within a day or two:

  • An Incident Commander (IC) to take overall responsibility for the team
  • Section Chiefs for Operations, Planning, Logistics, and Finance
  • Support positions including: Situation Unit Leader, GIS mapping specialists, Incident Meteorologist, Fire Behavior Analyst, Air Operations Branch Director, Medical Unit, Ground Support Unit Leader, Equipment Time Recorder, Demobilization Unit Leader, Base Camp Manager.
  • All of the official positions are usually filled with people that have been trained and ‘qualified’ for the position thru actual work assignments in that position.

Local units (CAL FIRE units, National Forests, National Parks, counties, cities, NGOs) can run plenty of fires with their own organization, often referred to as a ‘Type III Team”. But once things reach a certain scale or complexity, they often order a Type I or Type II Team.

Types of Incidents: From Local Grass Fire to Major Disaster

Incidents are “typed” from Type 5 (smallest, least complex) to Type 1 (largest, most complex).

Very roughly:

  • Type IV or V
    • Handled by the first-arriving units.
    • An engine captain or local officer is the Incident Commander.
    • Lasts a few hours to maybe a day.
    • Example: a small roadside fire put out by initial attack, or a fire that will be contained within a day or two.
  • Type III
    • A “short” or local team steps in.
    • Fire may last several days.
    • More than a handful of resources: multiple crews, engines, maybe aircraft.
    • Logistics can be handled with local businesses, e.g. pizza, burritos, sack lunches.
    • Still mostly managed by the home unit, but using the ICS framework more formally.
    • Maybe 100-200 people committed to the incident.
  • Type II
    • A regional or national team.
    • Hundreds of personnel, expanded logistics (full fire camp, catering).
    • Significant complexity: private property, multiple jurisdictions, heavier political pressure, longer duration.
  • Type I
    • The most complex, highest‑stakes incidents.
    • Often thousands of personnel, major infrastructure at risk, evacuations, fatalities or serious injuries, national attention.
    • Teams are deeply experienced and vetted; they’re expected to handle very high consequence decisions.

In practice, the terminology is in flux: many agencies now talk about “Complex Incident Management Teams” instead of separate Type I and Type II labels, but the idea is the same – the team is matched to the complexity, not just the size. Cal Fire has 6 IMTs in California, all classified as Type I. There are around 40 CIMTs in the US, as of 2026, 8 of which are based in California.

When Do They Order a Team?

Local units (CAL FIRE units, National Forests, National Parks, etc.) decide whether to request a team based on complexity, not just acreage.

Some triggers that push an incident toward a larger team:

  • Fire will clearly last multiple days or weeks
  • Multiple communities or critical infrastructure are threatened
  • Incident crosses jurisdictional boundaries (e.g., federal / state / county)
  • Heavy use of aviation, night operations, or specialized resources
  • Need for large camp operations (feeding and housing hundreds or thousands)
  • High political visibility or media pressure
  • Additional complexity such as:
    • Firefighter or civilian fatalities / serious injuries
    • Large evacuations
    • Sensitive environmental or cultural sites

On a medium-complexity fire like the Floriston Fire (currently burning in the Truckee River Canyon, as we write this):

  • You’ve got steep, rugged terrain, limited access, and a major interstate corridor nearby.
  • It’s burning in a place where wind and topography can align for big runs.
  • Hundreds of homes could be impacted if the fire aligns with the winds and makes major moves toward Verdi.
  • The fire made a good run in the first few hours, but then ran out of gas, and was barely spreading.
  • These factors make the fire a good candidate for a Type III team, with the potential to move to a more complex team if it starts growing, again.

On the Dome Fire near Yosemite:

  • Likely also a Type III incident
  • The fire sits in a remote wilderness but is relatively close to Wawona and Yosemite West, with a lot of values at risk.
  • Yosemite has its own deep bench of experienced fire managers, so they can manage a lot in‑house before ever needing an outside team.
  • The National Park Service has many career fire personnel in California they can call on to support a Type III incident.
  • If the fire threatens to grow into a long‑duration, high‑risk event, they can bring in a regional or national team.

How the Handoff Works

When a team is ordered, there’s always a transition period:

  1. In-briefing
    • The local unit and current incident leaders brief the incoming team:
      • Fire behavior
      • Weather
      • Values at risk
      • Current strategy and tactics
      • Political and community context
  2. Shadowing
    • For a day or so, the incoming team often shadows the existing organization.
    • They learn local roads, personalities, issues, and ongoing plans.
  3. Transfer of Command
    • A formal moment when the new IC assumes command.
    • From then on, the team runs the incident, but still answers to the host agency administrator (a forest supervisor, park superintendent, CAL FIRE unit chief, etc.). This arrangement is formalized in a written ‘delegation of authority’.
  4. Two-Week Rotations
    • Teams typically stay up to 14 days before rotating off.
    • When they leave, another team can take over using the same ICS template, with another structured transition.

This modular, repeatable structure is what lets the system handle long campaigns: many of the firefighters stay on the fire (depending on their work schedule), as do many of the supporting personnel/contractors, but the teams rotate through it.

When Federal lands are impacted by wildfire, the local unit (Forest Service, BLM, Park Service, etc.) uses a web-based computer system called WFDSS (Wildland Fire Decision Support System) to evaluate the incident, develop management/suppression objectives, and document their decision-making process. This process often includes running predictive fire behavior models to assess the fire’s potential for future spread, the likelihood the fire will impact important values-at-risk, and potential resource needs to mitigate these threats.

Why Teams Matter (Beyond the Fireline)

When we talk about “firefighting,” most people imagine saw teams, hand crews, engines, and aircraft. But on a big incident, the success or failure of that work depends heavily on the team behind the scenes.

Incident management teams:

  • Make strategic choices:
    • Direct vs. indirect attack
    • Where to accept fire growth and where to draw the line
    • When to go all‑in to protect a town, and when to back off for firefighter safety
  • Balance competing goals:
    • Protect communities like Wawona or Yosemite West
    • Deal with smoke impacts, tourism, politics, and public perception
    • Try to minimize negative effects/resource damage from firefighting, itself
  • Manage risk to firefighters
    • The Operations Section works directly with fireline leaders to choose tactics that balance risks to firefighters with potential firefighting gains.
  • Keep the machine running
    • You can’t cut line if you don’t have food, fuel, hose, medics, and a place to sleep.
    • Good logistics and planning can be the difference between an effective firefight and a clusterf#ck!

When you hear about firefighters dying in entrapments or accidents, these are often the result of systemic failures as much as individual decisions. Good teams are constantly trying to avoid repeating those mistakes, especially in places that are notorious for explosive fire growth.

The Succession Problem: Who Will Run These Teams Next?

One issue that doesn’t get talked about much outside the fire world is IMT succession.

To become a Type 1 Incident Commander (or a Section Chief at that level), you don’t just take a class. You have to:

  • Work your way up through multiple positions (firefighter, squad boss, crew boss, division supervisor, strike team leader, operations, etc.).
  • Accumulate years of experience on complex fires across different fuel types and regions.
  • Complete a pile of training and task books, each of which requires supervised performance on real incidents.

Realistically, starting from scratch, it can take 20–30 years to become fully qualified in some of the top roles.

On top of that:

  • Many of the people who built the system were Vietnam-era vets who were fast‑tracked into leadership roles because they already had experience with logistics, helicopters, and command in chaotic environments.
  • For a long time, there wasn’t a strong focus on grooming their replacements – because we had so many highly experienced people in those roles.
  • Transferring qualifications across agencies (Forest Service, BLM, Park Service, state, local) is often bureaucratically painful, which slows down development of new leaders.

The result:
A lot of teams are still anchored by very senior people, and the system is racing to bring up a new generation of qualified leaders before the old guard fully retires. There has been concern about ‘brain drain’ with DOGE cuts and large losses of senior Federal employees.

Why This Matters for the Public

If you live in or near fire country, incident management teams are the reason:

  • There’s a plan behind the daily chaos you see on webcams and in the smoke.
  • Briefings, evacuation notices, and road closures aren’t just random – they come out of a coordinated process.
  • When a new team rolls in, they can plug into the same framework that was running yesterday, instead of reinventing the wheel.

They’re also where some of the hardest, least visible decisions get made:

  • Do we risk firefighters lives putting them down in a canyon below Yosemite West again?
  • Do we allow a backing fire in wilderness to keep burning for ecological benefit, knowing we’ll get angry calls about “letting it burn”?
  • Should we conduct this firing operation, even though it will kill thousands of acres of trees?
  • Should we extend this exhausted crew for a few more days, so we can complete this section of fireline?
  • How should we cooperate with the Department of Homeland Security ICE agents that just showed up who want to detain some of the Hispanic contract crewmembers?

The Human Side of Incident Command Teams

Many people think that the Incident Commander’s job is to tell the firefighters where to go and what to do, but in reality, the IC’s job is a political one. They are the public face of the incident, and their most important job is to make sure their team is working well together, that everyone knows what their job is, and that they’re covering all of their bases.

It’s easy to think of incident command teams as a smooth, faceless machine: plans in, decisions out. In reality, every IMT is made up of real human beings with their own histories, blind spots, tempers, traumas, and stress thresholds.

These folks:

  • Work long hours with little sleep for weeks at a time
  • Juggle pressure from politicians, agency administrators, communities, and the media
  • Carry the weight of decisions that can mean life or death for firefighters and residents
  • Deal with their own interpersonal conflicts: disagreements over tactics, clashing personalities, competing egos, and burnout
  • Feel deep responsibility for the people who work under them

Inside a team, not everyone sees risk the same way. Ops might want to push harder; Safety may want to pull back; Plans might show up with some new intel that torpedoes the previous strategy; the HR Unit might be dealing with a sexual harassment claim against a Section Chief or Unit Leader. People argue. Feelings get hurt. Sometimes folks don’t get along at all. But the machine has to keep running, so the team has to resolve conflicts and stand shoulder‑to‑shoulder in front of a room full of firefighters and answer for the plan.

Remember that the next time you see “a team” has taken over a fire. Behind that label is a group of tired, skilled, imperfect humans trying to do the least‑bad thing, often in a no‑win landscape, while managing not just fire behavior and weather, but also their own internal dynamics. The system looks rigid on paper, but on the ground it’s held together by relationships, trust, and sometimes a lot of uncomfortable conversations. When it works well, it’s because they have effective leadership that can help them work through the messy relationships and come together around a clearly articulated, achievable plan.