Lesson 9 Overview
This lesson provides a brief summary of the Basic Incident Command System for Initial Response course content. After reviewing the summary information, you will receive instructions for taking the course Final Exam.
Lesson 1: Course Overview (NIMS & ICS Review)
  • NIMS provides the Nation with a standardized framework for incident management.
  • ICS, a part of NIMS, is a management system used to meet the demands of incidents large or small, planned or unplanned.
  • The NIMS Management Characteristics:
    1. Common Terminology
    2. Modular Organization
    3. Management by Objectives
    4. Incident Action Planning
    5. Manageable Span of Control
    6. Incident Facilities and Locations
    7. Comprehensive Resource Management
    8. Integrated Communications
    9. Establishment and Transfer of Command
    10. Unified Command
    11. Chain of Command and Unity of Command
    12. Accountability
    13. Dispatch/Deployment
    14. Information and Intelligence Management
Lesson 2: Incident Command and Unified Command
  • Chain of Command is the line of authority that flows down through the organizational structure.
  • Unity of Command means that each individual will be assigned and report to only one supervisor.
  • Unity of Command is different from Unified Command; Unified Command is established when no one jurisdiction, agency, or organization has primary authority, therefore there is no one clear Incident Commander. These multiple agencies work together to communicate and make command decisions.
  • Communication during an incident may be formal or informal
    • Formal communications must be used for work assignments, resource requests, and progress reports.
    • Informal communication is used to exchange incident or event information only. 
  • All levels of leadership on an incident should understand and practice the leadership principles, have a commitment to duty, and take actions that prioritize the safety of personnel.
  • Clear communication is the responsibility of all responders in order to accomplish incident objectives. Incident Management Assessments may be conducted by leadership after an incident to help personnel process what happened and why.
  • ICS utilizes a Modular Organization so that the organization can expand and contract as an incident grows and shrinks. This modular organization helps maintain an effective span of control.
  • Manageable span of control with Modular Organization is accomplished by organizing resources into Teams, Divisions, Groups, Branches, or Sections. Leadership in each organizational level holds a unique title.
  • The flexibility allowed for in ICS does is not override the importance of Common Terminology. Common Terminology must be used to maintain clear communication, whether formal or informal.
Lesson 3: Delegation of Authority and Management by Objectives
  • Authority is the right or obligation to act on behalf of a department, agency, or jurisdiction.
  • The scope of authority that an Incident Commander has is determined by existing laws, policies, and procedures. Additional authority may be delegated when necessary. 
  • Delegation of authority is the process of granting authority to an individual or agency to carry out specific functions during an incident.
  • Delegation of authority does NOT relieve the granting entity of the responsibility for that function. Authority can be delegated; responsibility cannot.
  • When needed, a delegation of authority should contain elements related to restrictions, external implications and considerations, and planning and communication processes.
  • Authority is implemented by the Incident Commander through the management of objectives. Effective Incident Objectives should be SMART. Objectives are not tactics or strategies; they state what needs to be accomplished, not how to do it.
  • Objectives are a part of the Incident Action Plan, which is completed each operational period and outlines incident-specific information. It is created through a process known as the Operational Period Planning Cycle (Planning P).
  • Incident Command, as well as Command and General Staff, should also have a working knowledge of other preparedness plans, such as EOPs, SOGs, SOPs, and mutual aid agreements.
Lesson 4: Functional Areas and Positions
  • The Incident Commander oversees the incident, sets incident objectives, and approves the IAP.
  • Command Staff include the Public Information Officer, Safety Officer, and Liaison Officer.
  • The Incident Commander also oversees four sections of the ICS organizational structure: Operations, Planning, Logistics, and Finance & Administration. Each of these sections is responsible for a different function during an incident; Sections are led by the General Staff who report to the Incident Commander. General Staff are titled as Section Chiefs.
  • Operations directs and coordinates all incident tactical operations.
  • Planning maintains resource and situation status, prepares the IAP and other documents, and looks beyond the current operational period to anticipate potential future problems or events.
  • Logistics is responsible for all support requirements, including communications, facility supplies, medical needs, and food and drink for incident personnel.
  • Finance/Administration provides administrative and financial support services. This includes handling claims related to property damage, injuries, and fatalities.
  • ICS Forms help communicate and organize information between Command, Command Staff, General Staff, and other incident personnel.
Lesson 5: Incident Briefings and Meetings
  • Different meetings and briefings are used during the Incident Action Planning Process to share information.
  • Briefings should be concise and may occur at the staff, field, or section level.
  • Information shared during a briefing includes the current situation and objectives, safety issues and emergency procedures, work tasks, facilities and work areas, communication protocols, expectations, resource acquisition procedures, work schedules, and questions or concerns. 
  • The Operational Period Briefing is led by the Incident Commander to present the IAP. Command and General Staff will also participate to share important information.
Lesson 6: Organizational Flexibility
  • NIMS requires organizational standardization use of Common Terminology; however, ICS is still flexible due to its Modular Organization.
  • Functions and positions within the organizational structure are activated and filled based on the needs and demand of an incident. The ICS organizational structure will expand and contract with the incident.
  • Personnel may hold multiple titles within an incident’s organizational structure, but the titles must keep consistent with NIMS titles. Titles may not be shortened or combined.
  • Proper Resource Management is essential to maintaining an accurate and up-to-date picture of resource utilization and needs.
  • Incidents are typed based on size and complexity. Incident types move from Type 5 as the least complex to Type 1 as the most complex.
Lesson 7: Transfer of Command
  • Transfer of Command is the process of moving the responsibility for incident command from one Incident Commander to another Incident Commander or Unified Command.
  • Transfer of Command should take place face-to-face when possible and include a complete briefing that captures essential information.
  • The transfer of command briefing should include elements such as the situation status, incident objectives and priorities, current organization, resource information, incident communications plan, etc.
  • A notification of the time and date that the transfer of command becomes effective should be communicated to all incident personnel.
Congratulations!

You should now be able to demonstrate knowledge of how to manage an initial response to an incident.

The course specifically discussed:

  • Incident Command and Unified Command
  • Delegation of Authority & Management by Objectives
  • Functional Areas & Positions
  • Incident Briefings and Meetings
  • Organizational Flexibility 
  • Transfer of Command 
  • Application of ICS for Initial Response 
Checkmark next to Course Overview, checkmark next to Incident Command and Unified Command, checkmark next to Delegation of Authority and Management by Objectives, checkmark next to Functional Areas and Positions, checkmark next to Incident Briefings and Meetings, checkmark next to Organizational Flexibility, checkmark next to Transfer of Command, checkmark next to Application Activity, checkmark next to Course Summary.