What is the role of the incident command?

The Incident Commander (IC) is the primary decision maker during a major incident. Their job is to delegate tasks and listen to input from subject matter experts to ultimately bring the incident to resolution. They are by default the highest-ranking individual on any major incident call, regardless of day-to-day rank. The decisions made by the incident commander are final.

Your job as an Incident Commander is to listen to the call and oversee the incident Slack room in order to provide clear coordination, recruiting others to gather context and other important details. You should not be performing any actions or remediations, checking graphs, or investigating logs. Those tasks should be delegated as you should focus on the greater incident as a whole.

An IC should actively be considering next steps and backup plans at every opportunity, in an effort to avoid getting stuck without any clear options to proceed. The main job is to keep things moving towards an eventual resolution.

How to Become an Incident Commander

Becoming an incident commander requires substantial training and experience. It is important to have these basic qualifications before considering the role of incident commander:

• A business understanding of what your service or product does for its users.
• The ability to accept and consider advice swiftly and efficiently.
• The ability to make quick decisions in a chaotic environment.
• The ability to take and maintain control during any level of severity.

It’s important to read up on incident management and an incident commander’s role. One of the best ways to learn is to shadow a current incident commander for a one-week shift. This will help you gain experience and give insight into how incident commanders handle incidents and what it’s like on the front lines. In order to practice what you’ve learned, have a current incident commander reverse shadow you for a week. You will be the one responding to incidents and taking calls, but the other incident commander will be there in case you need help.

Skills Needed

There are certain skills needed to be an incident commander. These skills, detailed below, are necessary to build and grow in order to be a successful Incident Commander.

Ability to Follow Process

It’s critical for a company to have a process in place when incidents arise. An incident commander should know how to follow this process and how to enforce it during an incident. Process guidelines can range from mobilizing stakeholders to external communications, and everything in between.

Effective Communication

An incident commander needs to know how to communicate clearly and effectively, giving as much detail as possible, so there is no confusion in terms of the makeup of the incident or the processes needed to resolve swiftly. An incident commander also needs to be able to delegate tasks, coordinate, and give instructions across all key stakeholders. The communications process is often handled during the incident itself to provide status updates to users, executive leadership, and other key stakeholders.

Time Management With Intention

An incident commander needs to use time boxing when delegating tasks. This involves informing people when to expect a check in regarding their progress on a task and remember to give people more time if they ask for it. When major incidents involve various technical teams and other cross-department communication, is it critical to ensure teams have time to not only execute on their responsibilities, but give other teams time in order to progress towards a resolution.

Proactive Listening

Be flexible. Although the incident management process is important to follow, every incident is different, so it’s necessary to listen to advice and make decisions that will keep the incident moving to its eventual conclusion and be able to evaluate the risks and rewards of each decision you make.

____

Being a competent and effective guiding force during an incident is the difference between minutes and hours of downtime and dollars lost. However, an incident commander is only as strong as the resources they are given. If a company has a poor incident management process, it can be difficult to solve incidents efficiently and effectively.

To learn more about being an Incident Commander, check out PagerDuty’s Incident Commander documentation today.

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Incident commander" – news · newspapers · books · scholar · JSTOR (August 2010) (Learn how and when to remove this template message)

The incident commander is the person responsible for all aspects of an emergency response; including quickly developing incident objectives, managing all incident operations, application of resources as well as responsibility for all persons involved. The incident commander sets priorities and defines the organization of the incident response teams and the overall incident action plan. The role of incident commander may be assumed by senior or higher qualified officers upon their arrival or as the situation dictates. Even if subordinate positions are not assigned, the incident commander position will always be designated or assumed. The incident commander may, at their own discretion, assign individuals, who may be from the same agency or from assisting agencies, to subordinate or specific positions for the duration of the emergency.

In the United States, most agencies use an Incident Commander for the roles and responsibilities as defined under the National Incident Management System as a part of the Incident Command System.[1]

The incident command system in a Canadian EMS scenario

• Incident Commander – oversees all operations at the incident.[2]
  • usually one of the first officers on scene.
  • assessment of the scene.
  • establish command as well as command centre.
  • request required resources.
  • initiates triage.
• triage officer – oversees all patient assessment, tagging and movement to treatment areas
• treatment officer – oversees all treatment and the treatment area
• transportation officer – oversees all ambulance movement, priority, identity, and destination of patients.
• staging officer – oversees all acquisition, release and distribution of resources.

Duties in a US fire-fighting scenario

• Obtain briefings and guidelines for level of involvement from requesting agency and/or prior Incident Commander.
• Obtain delegation of authority if requesting agency desires Team to assume operational control and/or under unified command to allow all affected jurisdictions shared responsibility.
• Ensure incident safety.
• Establish Incident Command Post and operational plan if not already accomplished.
• Maintain contact with state fire marshal and ERC.
• Provide other command assistance as requested by agency/jurisdiction.
• Coordinate the multiple aid from interagencies like: USFS, BLM, BIA, state, county, city and volunteer fire/emergency resources.

See also

• Advanced disaster management simulator
• Incident management team
• Incident command post
• Incident command system

References

1. ^ "Chapter 7: THE INCIDENT COMMAND SYSTEM (ICS)". Center for Excellence in Disaster Management & Humanitarian Assistance. Archived from the original on April 23, 2008. Retrieved 2011-09-28.
2. ^ Vahradian, S. "Emergency Medical Responder Workbook Canadian Edition" Chapter29 Prentice Hall 2003

External links

• Incident Commander Crisis Training Simulation Software

Retrieved from "https://en.wikipedia.org/w/index.php?title=Incident_commander&oldid=934674858"

The incident commander is the decision maker when an incident strikes. They create the incident action plan, which is crucial for controlling incidents quickly once they occur. In this piece, we’ll explain the role and responsibilities of an incident commander and why having an incident action plan is crucial to keeping operations running at all times.

When an emergency occurs, you call 911 and wait for first responders to arrive. These individuals are trained to tackle emergencies—all while staying calm and collected. Company incidents, like data breaches or labor strikes, usually aren’t concerning in terms of physical safety, but they also require immediate attention because of the impact they can have on your company’s bottom line. 

In this piece, we’ll explain the role and responsibilities of an incident commander and why having an incident action plan can be crucial to keeping operations running at all times. 

What is an incident commander?

The incident commander is responsible for all aspects of incident response. Usually a member of the IT or DevOps team, this person defines and organizes the incident action plan and leads the decision-making process when crises arise. 

The incident commander (also called an incident manager) is the lead point of contact for team members during an emergency business situation. In these high-stress situations, they are in charge of delegating tasks to incident response teams. 

Incident commanders must be skilled at seeing the big picture if they hope to break down complex incidents into manageable pieces. Without an incident commander, it’s easy for project defects, system errors, and miscommunication to occur. When you’re part of a large or multi-unit team, the incident command post is key to keeping your operations running smoothly. 

What does an incident commander do?

While incidents don’t occur every day, incident commanders may take on a full-time role in bigger organizations because they have many responsibilities to keep them busy. As an incident commander, you'll spend most of your time preparing for incidents, learning from past incidents, and managing an incident once it occurs. 

1. Prepare for incidents

Incident commanders must prepare for a range of events that can negatively affect the company. While you can’t predict everything that will happen, you can set up foolproof incident operations to handle a variety of scenarios as they occur in real time. This type of operational preparation includes:

• Setting up communication channels

• Creating a general incident action plan

• Training team members on the incident action plan

• Regularly reviewing incident safety measures

Tip: Project management can help your team establish an incident action plan. As an incident commander, you’ll share this plan with everyone in the company through your online management system.

2. Create an action plan

Once an incident occurs, you can put your leadership qualities into action by thinking quickly on your feet. Because every incident is unique, preparation only goes so far. You must first analyze the incident and determine how to address it. Use the incident operations plans you made earlier as a jumping off point, and modify the plans depending on the situation’s specific needs. 

Deciding what to do during an incident includes:

• Making a step-by-step action plan

• Identifying which team members are needed

• Prioritizing tasks based on safety and company needs

• Communicating the plan to team members

Tip: The decision process during an incident can be high stress for any incident commander. You may receive recommendations from team members during this stage, but you must take overall responsibility for deciding what to do. You’ll excel in this role if you’re well-versed in gathering information and problem solving.

3. Delegate tasks

After you figure out how to handle a major incident, you’ll quickly need to delegate authority and tasks. It’s essential for team members to know their responsibilities so the incident action plan can function properly.  

For larger incidents, set up an incident management team to make the response process easier. The team can help you with:

• Debugging

• Research

• Information security

• Process briefings

Tip: Being an incident commander isn’t a job you can do by yourself. You’ll need help from other teams to manage incidents effectively and stabilize the company for future operations. You can assign deputy incident commanders to help you delegate and oversee tasks.

4. Oversee and align teams

After you delegate tasks, transition yourself into a facilitator role as teams try to control the incident. Help team members as needed and ensure everyone understands what they’re supposed to do. Because everyone is working in a time-sensitive environment, you’ll also assist with any communication issues. 

A communication plan can help your team understand who should be getting which notifications and when to loop in other teams or departments. As part of your communication plan, clarify which channel team members should use and when, how frequently different details should be communicated, and who is responsible for each of the different channels.

Tip: As an incident commander, you’ll be responsible for resource management during the execution phase of the incident action plan. If your team members need additional resources, it’s up to you to get those resources for them. You’ll establish a unified command and help manage the logistics of the operation. 

5. Keep teams calm and focused

Some incidents can cause a lot of stress for team members within the company. For example, if the company experiences a temporary loss of data, you must keep everyone calm and focused. 

Team morale can fluctuate depending on the incident. If team members must work remotely, it’s also critical to promote remote collaboration in addition to incident management.

Tip: Keep your team calm and focused in high-stress situations by mixing empathy and urgency. Give team members a moment to gather their thoughts and emotions before you push them into immediate action. Once they compose themselves, you can emphasize the importance of a quick response. 

6. Escalate issues and review

When an incident is too complex for your team to handle alone, it’s up to you to escalate the issue to assisting agencies or departments. This may include seeking help from stakeholders or senior management. If escalation isn’t needed to handle the incident, then you can begin a detailed follow-up of the incident instead. 

The final step of an incident response is the post mortem meeting. THis i a chance for you and your team to assess how well you handled the incident. Make sure to evaluate and review:

• The speed of response

• Overall task performance

• The level of incident control

• Your personal performance as incident commander

• Your incident action plan’s efficiency

• The risk for future related incidents

Tip: The goal of the post mortem is to learn from things that went well during incident response—as well as the things that went wrong. That way, the next time an incident occurs, you can manage your team members more efficiently and feel more confident about whatever comes your way. 

5 areas of the incident command system (ICS)

The incident command system (ICS) is a standard organizational structure you can follow if you want to respond to incidents quickly and have the support you need to manage every aspect of an incident. 

Like a company project, an incident requires planning, logistics, and a clear operational process to control. The difference with an incident is that the stakes are higher and the timeline is shorter. 

1. Command: The incident commander sits at the top of the incident command structure. You may have other members help with management, such as a liaison officer or a public information officer. Team members in the command section set objectives and provide overall guidance on the incident. 

2. Planning: The incident commander is involved in the planning section of the incident command system. Depending on the size and scope of the incident, you may invite others to help you create the incident action plan. 

3. Logistics: The logistics section provides available resources and direction to support the incident action plan. When the operations team has questions about how to execute tasks within the action plan, they can discuss their questions with both the incident commander and members of the logistics team. 

4. Operations: In the operations section, team members organize resources provided for them by the incident commander and the logistics team. They’ll receive direction on the incident action plan and use the resources to carry out the action plan. 

5. Finance/administration: The incident action plan costs money to carry out and the finance and administration team will guide team members financially and track costs related to the incident. As the incident commander, you will work with the finance team to allocate funding for the incident action plan. 

Other roles that may work with the incident commander in these sections of the ICS include:

• Tech lead: Having a tech lead in a senior response position can be helpful for planning, logistics, and operations. This person helps the incident commander determine why the incident occurred. They can then help create the incident plan and work with the technical team to put the plan into action. 

• Communications manager: A communications manager is an essential role when controlling an incident because stakeholders and customers will need to know what’s going on. While the incident commander and technical team work quickly to fix the problem, the communications manager shares status updates so internal and external parties are kept updated on the incident. 

• Customer support lead: If the incident in question is customer-facing, a customer support lead is crucial for managing incoming communications from customers, whether that be tickets, phone calls, or social media posts. This person ensures customers are taken care of while the incident commander works to fix the problem.

As incident commander, you’ll be the point of contact for all departments when an incident occurs and through the entire incident action plan response process. It’s up to you to plan and execute the action plan and ensure it runs smoothly. 

Improve incident response with project management software

Determination and organizational skills can help you manage a team efficiently. Incidents often come with heavy time constraints, but with the right tools, you’ll feel prepared to come up with solutions quickly.

Project management software can improve incident control by streamlining communication across your organization and implementing response processes that your team feels comfortable putting into action.