Incident command system basics explained
Learn how the incident command system organizes a community response, from the incident commander and command staff to span of control and unified command.
Contents
- How the ICS structure is built
- Command staff and general staff roles
- Span of control and unified command
- Questions about incident command for communities
- What are the incident command system basics?
- How does the incident command system work in simple terms?
- What does the incident commander do?
- How does unified command differ from a single incident commander?
The incident command system is a clear way to organize people and tasks when a community faces an emergency. It gives one incident commander the authority to set goals and direct the response. Roles are written down, so volunteers and staff know who reports to whom. The system grows or shrinks with the size of the incident.
How the ICS structure is built
The incident command system builds from the top down, with the incident commander setting objectives for the whole response. Under that person sit four functions that cover the main work: operations, planning, logistics, and finance and administration. Each function is called a section and has a section chief who answers to the incident commander. Small incidents may combine several of these functions in one person, while large ones split them apart.
Command staff and general staff roles
Command staff advises the incident commander and does not run a section of its own. The command staff covers public information, safety, and liaison with other organizations. The general staff runs the four sections that carry out operations, planning, logistics, and finance. In local response, this split lets one person speak for the response while others handle information and worker safety.
Span of control and unified command
Span of control means the number of people one supervisor can direct well, and the incident command system keeps that number small. When a supervisor has too many people reporting, the response adds another layer or splits the work into teams. Unified command applies when several agencies share authority over one incident and set joint goals together. A single set of objectives then guides every agency, which helps community incident management run smoothly.
Questions about incident command for communities
What are the incident command system basics?
The incident command system basics are a single commander, clear reporting lines, and a shared set of objectives. The system uses named roles so each person knows their task and their supervisor. It expands for a large incident and contracts when the work slows down.
How does the incident command system work in simple terms?
The incident command system works by putting one incident commander in charge of the response and its goals. That commander assigns sections for operations, planning, logistics, and finance as the incident requires. Everyone reports through a short chain, so information reaches the commander without confusion. The structure changes as the incident grows or shrinks.
What does the incident commander do?
The incident commander sets the objectives for the response and has overall authority for the incident. This person decides which sections to open and who leads each one. The commander also approves the plan for the next period and adjusts it as conditions change. The role can pass to another trained person through a formal handover.
How does unified command differ from a single incident commander?
Unified command shares authority among agencies that each have a legal role in the incident. Those agencies set joint objectives and speak with one voice on the plan. A single incident commander holds authority within one organization or one clear chain. Unified command fits incidents that cross agency boundaries, such as a fire that also affects a water system.