Block 10: Incident Complexity Level 
Identify the incident complexity level as determined by Unified/Incident Commanders, if available or used. Incident types are based on the following five levels of complexity:
- Type 5 Incident Characteristics:
- Ad hoc organization managed by a Type 5 Incident Commander.
- Primarily local resources used.
- ICS command and general staff positions are not activated.
- Resources vary from two to six firefighters.
- Incident is generally contained within the first burning period and often within a few hours after resources arrive on scene.
- Additional firefighting resources or logistical support are not usually required.
- Type 4 Incident Characteristics:
- Ad hoc organization managed by a Type 4 Incident Commander.
- Primarily local resources used. o ICS command and general staff positions are not activated.
- Resources vary from a single resource to multiple resource task forces or strike teams.
- Incident is usually limited to one operational period. However, incidents may extend into multiple operational periods.
- Written Incident Action Plan (IAP) is not required. A documented operational briefing will be completed for all incoming resources.
- Type 3 Incident Characteristics:
- Ad hoc or pre]established Type 3 organization managed by a Type 3 Incident Commander
- The IC develops the organizational structure necessary to manage the incident. Some or all of ICS functional areas are activated, usually at the Division/Group Supervisor and/or unit leader level.
- The incident complexity analysis process is formalized and certified daily with the jurisdictional agency. It is the IC's responsibility to continually reassess the complexity level of the incident. When the assessment of complexity indicates a higher complexity level, the IC must ensure that suppression operations remain within the scope and capability of the existing organization and that span of control is consistent with established ICS standards.
- Local and non]local resources used.
- Resources vary from several resources to several task forces/strike teams.
- May be divided into divisions.
- May require staging areas and incident base.
- May involve low complexity aviation operations.
- May involve multiple operational periods prior to control, which may require a written Incident Action Plan (IAP).
- Documented operational briefings will occur for all incoming resources and before each operational period.
- ICT3s will not serve concurrently as a single resource boss or have any non-1 incident related responsibilities.
- May require a written Delegation of Authority.
- Type 2 Incident Characteristics:
- Pre-established incident management team managed by Type 2 Incident Commander
- ICS command and general staff positions activated.
- Many ICS functional units required and staffed.
- Geographic and/or functional area divisions established.
- Complex aviation operations.
- Incident command post, base camps, staging areas established.
- Incident extends into multiple operational periods.
- Written Incident Action Plan required for each operational period.
- Operations personnel often exceed 200 per operational period and total personnel may exceed 500.
- Requires a written Delegation of Authority to the Incident Commander.
- Type 1 Incident Characteristics:
- Pre-established Incident Management Team managed by Type 1 Incident Commander.
- ICS command and general staff positions activated.
- Most ICS functional units required and staffed.
- Geographic and functional area divisions established.
- May require branching to maintain adequate span of control.
- Complex aviation operations.
- Incident command post, incident camps, staging areas established.
- Incident extends into multiple operational periods.
- Written Incident Action Plan required for each operational period.
- Operations personnel often exceed 500 per operational period and total personnel may exceed 1000.
- Requires a written Delegation of Authority to the Incident Commander.