Skip to Content
ID
2-508-1050
Name
Incident Management Team
Status
Published
Updated
11/18/2019 3:59:42 PM
Released
06/19/2018
Description
An Incident Management Team (IMT) provides incident management or support during incidents or events that exceed a jurisdiction's or agency’s capability or capacity. Teams may include members of local, state, tribal, territorial, and Federal entities; Nongovernmental Organizations (NGO); and private sector organizations. Teams encompass various agencies and jurisdictions.
Resource Category
Incident Management
Primary Core Capability
Operational Coordination
Secondary Core Capability
 
Resource Kind
Team
Overall Function
The IMT: 1. Deploys to manage emergency responses, incidents, or planned events requiring a higher capability or capacity level than the requesting jurisdiction or organization can provide 2. Assists with incident management activities during all-hazards events, including natural and human-caused events, as well as planned events 3. Assumes management of the incident for the requesting jurisdiction or agency, or supports a local Incident Commander (IC) or Unified Command and its IMT in managing an incident or event 4. Directs and tracks tactical resources that the Authority Having Jurisdiction (AHJ) and other supporting organizations provide 5. Performs Command, Operations, Planning, Logistics, Finance/Administration, Safety, Public Information, and Liaison functions, as the incident requires 6. Coordinates with Emergency Operations Center (EOC) personnel, AHJ, and Agency Administrators regarding incident management objectives and support 7. Typically supports incident management activities of a corresponding incident complexity; for example, a Type 2 IMT typically supports a Type 2 incident 8. Has short- and long-team configurations; long-team configurations include additional positions and capabilities to meet an incident's needs based on results of a complexity analysis
Composition and Ordering Specifications
1. Discuss logistics for deploying this team, such as working conditions, length of deployment, security, lodging, transportation, and meals, prior to deployment 2. Discuss available facilities for establishing an Incident Command Post (ICP), including their proximity to the incident 3. Discuss team relief or replacement, as well as team member overlap to allow for smooth operational transition 4. Discuss the need for specialty capabilities, such as effective response to hazardous materials, law enforcement events, structural fire, or wildland fire 5. Discuss staffing and equipment needs based on the complexity of the incident, such as the need for deputies and assistants or the need to provide 24-hour coverage 6. Requestor conducts an incident complexity analysis and discusses the results with the provider to identify necessary levels of support; typical incident complexity factors include: a. Threat to life, property, and the environment b. Extent or severity of damage or harm c. Need for 24-hour staffing d. Length of expected deployment periods e. Impact to the population f. Geographic extent of the incident g. Organizational complexity and number of jurisdictions involved h. Availability of resources I. Political, social, and economic sensitivities j. Level of public and media attention 7. Requestor and provider discuss IMT responsibilities and authority throughout the incident 8. An IMT working outside of its sponsoring entity's authority may need authorization from the requesting jurisdiction or agency, such as a Delegation of Authority, Financial Spending Authority, Letter of Direction, or Mission Assignment 9. Requestor and provider discuss existing incident command structures and other coordinating entities, such as Federal, state, tribal, territorial, and local governments; EOC; Multiagency Coordination (MAC) Groups; and Joint Information Systems (JIS) 10. As an incident grows geographically and in number of jurisdictions, the IMT should ensure that appropriate authorizations are in place, such as a Delegation of Authority from a regional or state entity 11. An all-hazards IMT may be a multidisciplinary group representing law enforcement, public health and medicine, fire, EMS, urban search and rescue, and other fields 12. Requestors should consider ordering the closest available resource to manage expanding incidents until a more qualified and capable resource is available 13. Team may also provide a transition from the response to recovery phase 14. Requestor and provider discuss tactical capabilities available through the AHJ, such as hazardous materials response or technical rescue teams, and order these resources separately if not available 15. Requestor and provider discuss the need for additional personnel or capabilities, such as Geographic Information Systems Specialists or Analysts, staging area managers, fatality management personnel, or other technical specialists 16. Requestor and provider discuss the need to include trainees on the team 17. Requestor and provider discuss the process and expectations for documentation; ordering, tracking, and managing resources; tracking and managing personnel hours; ensuring adequate personnel accountability; ensuring personnel safety and welfare; managing contracts and Memorandums of Understanding (MOU); and managing communications processes and equipment
Supporting Core Capabilities
None
Components
Component Notes  
MINIMUM PERSONNEL PER TEAM1. These team members represent minimum personnel for short-team configurations and do not include trainees or technical specialists. 2. For Type 1 and Type 2 teams, short-team configurations typically include 26 personnel and long-team configurations typically include 44 personnel.
Component Types
Type Attribute
Type 1Same as Type 2
Type 215
Type 312
MANAGEMENT AND OVERSIGHT PERSONNEL PER TEAMAn additional IC (Type 1, 2, or 3) may fill the role of deputy IC if the IC or requesting jurisdiction or entity requests it.
Component Types
Type Attribute
Type 11 – National Incident Management System (NIMS) Type 1 Incident Commander
Type 21 – NIMS Type 2 Incident Commander
Type 31 – NIMS Type 3 Incident Commander
SUPPORT PERSONNEL PER TEAM1. IMT types and capabilities are tied to incident complexity. 2. An IMT of different complexity Type may manage or support the incident until an appropriately Typed IMT can deploy. 3. Command and general staff type should match the IMT type, though subordinate positions, such as Unit Leaders, are not tied to incident complexity and may be of a single type. 4. Personnel meet the minimum qualifications indicated in the appropriate position qualifications system, such as the National Qualifications System (NQS). Position typing schemes may vary depending on the qualifications system the AHJ uses. 5. Type 4 teams composed of 7 to 10 command and general staff positions may exist for local or regional incident management but are not a NIMS typed resource. 6. Teams include two or more Operations Section Chiefs, who may serve as deputy, as Operations Section Chief for different operational periods, or as planning assistant. 7. Long-team configurations typically include additional positions, such as Service Branch Director, Support Branch Director, Facilities Unit Leader, Supply Unit Leader, Food Unit Leader, Medical Unit Leader, Ground Support Unit Leader, Ordering Manager, Communications Technician, Communications Center Manager, Documentation Unit Leader, Demobilization Unit Leader Geographic Information Systems Specialist, two Division/Group Supervisors, Air Tactical Group Supervisor, Air Support Group Supervisor, Cost Unit Leader, Time Unit Leader, Compensation/Claims Unit Leader, and Procurement Unit Leader. 8. The IMT may include an Intelligence and Investigations Section Chief, based on incident needs. 9. The IMT may include technical specialists in specific areas, such as public health, access and functional needs (AFN), volunteer management, fire behavior, and more. 10. Both short- and long-team configurations typically include several discretionary positions and trainees. 11. The computer technical specialist is not a NIMS typed position.
Component Types
Type Attribute
Type 11 – NIMS Type 1 Public Information Officer 1 – NIMS Type 1 Safety Officer 1 – NIMS Type 1 Liaison Officer 2 – NIMS Type 1 Operations Section Chief 1 – NIMS Type 1 Planning Section Chief 1 – NIMS Type 1 Logistics Section Chief 1 – NIMS Type 1 Finance/Administration Section Chief 1 – NIMS Type 1 Air Operations Branch Director 1 – NIMS Type 1 Communications Unit Leader 1 – NIMS Type 1 Situation Unit Leader 1 – NIMS Type 1 Resources Unit Leader 1 – NIMS Type 1 Geographic Information Systems Specialist 1 – Computer technical specialist
Type 21 – NIMS Type 2 Public Information Officer 1 – NIMS Type 2 Safety Officer 1 – NIMS Type 2 Liaison Officer 2 – NIMS Type 2 Operations Section Chief 1 – NIMS Type 2 Planning Section Chief 1 – NIMS Type 2 Logistics Section Chief 1 – NIMS Type 2 Finance/Administration Section Chief 1 – NIMS Type 1 Air Operations Branch Director 1 – NIMS Type 2 Communications Unit Leader 1 – NIMS Type 1 Situation Unit Leader 1 – NIMS Type 1 Resources Unit Leader 1 – NIMS Type 1 Geographic Information Systems Specialist 1 – Computer technical specialist
Type 31 – NIMS Type 3 Public Information Officer 1 – NIMS Type 3 Safety Officer 1 – NIMS Type 3 Liaison Officer 2 – NIMS Type 3 Operations Section Chief 1 – NIMS Type 3 Planning Section Chief 1 – NIMS Type 3 Logistics Section Chief 1 – NIMS Type 3 Finance/Administration Section Chief 1 – NIMS Type 3 Communications Unit Leader 1 – NIMS Type 1 Situation Unit Leader 1 – NIMS Type 1 Resources Unit Leader
Personnel Management Capabilities Per TeamPersonnel criteria are flexible parameters for identifying the level of capability to manage the incident.
Component Types
Type Attribute
Type 1Typically manages more than 500 personnel
Type 2Typically manages up to 500 personnel
Type 3Typically manages up to 200 personnel
Electronics and Office Equipment Per TeamThe IMT needs resources to create, duplicate, and distribute an Incident Action Plan for each operational period, in addition to other Incident Command System (ICS) documents and forms.
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Same as Type 3
Type 3Electronic and office equipment commensurate with the mission assignment
Personal Protective Equipment (PPE) Equipment Per Team Member1. PPE requirements are based on the position, the nature of the incident, and the environmental conditions experienced or expected. Not all positions require PPE. 2. PPE is mission specific and may vary by work environment; it includes protective footwear, protective clothing for skin exposure, eye and ear protection, respirators, gloves, and masks.
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Same as Type 3
Type 3Appropriate Personal Protective Equipment (PPE), if necessary
COMMUNICATIONS EQUIPMENT PER TEAMThe IMT arrives with or can order portable radios, repeaters, portable cellular towers, mobile communications units, mobile command posts, and other communications support equipment as necessary to provide communications for the incident.
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Same as Type 3
Type 3Communications equipment commensurate with the mission assignment
Administrative Support Supplies Per Team1. Office supplies are per section of the team. 2. Teams should use an established resource tracking system, such as T-cards or another inventory system.
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Same as Type 3
Type 3Basic office supplies and electronics equipment necessary to support development and distribution of IAP, maps, and other mission needs for 72 hours of continuous operations
706706706706
Notes
References
Reference
FEMA, NIMS 509: Incident Commander
FEMA, NIMS 509: Public Information Officer
FEMA, NIMS 509: Safety Officer
FEMA, NIMS 509: Liaison Officer
FEMA, NIMS 509: Logistics Section Chief
FEMA, NIMS 509: Operations Section Chief
FEMA, NIMS 509: Planning Section Chief
FEMA, NIMS 509: Finance/Administration Section Chief
FEMA, NIMS 509: Air Operations Branch Director
FEMA, NIMS 509: Situation Unit Leader
FEMA, NIMS 509: Resources Unit Leader
FEMA, NIMS 509: Communications Unit Leader
FEMA, NIMS 509: Geographic Information Systems Specialist
FEMA, NIMS 509: Geographic Information Systems Analyst
FEMA, NIMS 509: Facilities Unit Leader
FEMA, NIMS 509: Supply Unit Leader
FEMA, NIMS 509: Food Unit Leader
FEMA, NIMS 509: Medical Unit Leader
FEMA, NIMS 509: Ground Support Unit Leader
FEMA, NIMS 509: Ordering Team Leader, pending publication
FEMA, NIMS 509: Communications Technician
FEMA, NIMS 509: Air Support Group Supervisor
FEMA, NIMS 509: Air Tactical Group Supervisor
FEMA, NIMS 509: Cost Unit Leader
FEMA, NIMS 509: Time Unit Leader
FEMA, NIMS 509: Procurement Unit Leader
FEMA, NIMS 509: Compensation/Claims Unit Leader
FEMA, NIMS 509: Service Branch Director
FEMA, NIMS 509: Support Branch Direct
FEMA, NIMS 509: Documentation Unit Leader
FEMA, NIMS 509: Demobilization Unit Leader
FEMA, National Incident Management System (NIMS), October 2017
All-Hazards Incident Management Teams Association (AHIMTA), Interstate Incident Management Team Qualifications System (IIMTQS) Guide, May 2016
AHIMTA, Inter-state Mission Ready Package All-Hazards IMT Type 3, August 2014
National Interagency Fire Center (NIFC), National Interagency Mobilization Guide, March 2017