The Incident Controller: Role, Authority and Identification

Key Takeaways

• The Incident Controller (IC) is the single person with overall responsibility for managing an incident under AIIMS, reflecting the principle of unity of command.
• An Incident Controller’s authority comes from formal delegation through legislation, agency arrangements, or both. The title alone does not provide authority.
• The IC sets incident objectives, approves the Incident Action Plan (IAP), coordinates resources, and maintains overall accountability for responder safety.
• The Incident Controller and Officer in Charge are related concepts but represent different forms of responsibility. One is an incident management role, while the other is usually an organisational position.
• The role scales with incident complexity, from managing all functions directly at Level 1 to leading a fully established Incident Management Team at Level 3.
• When control transfers between Incident Controllers, a formal handover ensures continuity, shared understanding, and clear accountability.
• Clear identification, such as AIIMS role vests or tabards, helps responders quickly recognise decision-makers during complex incidents.

The Incident Controller is the person with overall responsibility for managing an incident under the Australasian Inter-service Incident Management System (AIIMS). The role involves establishing incident objectives, approving the Incident Action Plan (IAP), coordinating resources, and maintaining accountability for the overall response.

In a complex emergency involving multiple agencies, clear leadership and decision-making are essential. The Incident Controller provides that single point of accountability, ensuring all responding organisations work towards common objectives under the AIIMS principle of unity of command.

For emergency services professionals, procurement teams, and organisations implementing AIIMS, understanding the Incident Controller role is essential. The role determines who has responsibility, how decisions are made, and how teams coordinate during an incident..

At Reflective Fabrications, we manufacture Australian-made AIIMS identification vests and tabards designed to help Incident Management Teams quickly identify key roles during emergency operations. This guide explains what an Incident Controller does, where their authority comes from, how the role changes across incident levels, and why clear identification matters.

What Is an Incident Controller?

An Incident Controller is the person appointed with overall responsibility for managing an incident under AIIMS.

At any point during an incident, there is only one designated Incident Controller. This reflects the AIIMS principle of unity of command, where all personnel work towards shared objectives under a clearly identified leader.

The Incident Controller is responsible for:

• establishing incident objectives
• approving the Incident Action Plan (IAP)
• coordinating resources and agencies
• maintaining responder safety
• providing strategic direction throughout the response

The Incident Controller leads the Incident Management Team (IMT), although the size and structure of that team depends on the complexity of the incident.

During smaller incidents, the Incident Controller may perform multiple functions directly. As the incident grows, responsibilities are delegated to Operations, Planning, Logistics, and Public Information Officers, while the Incident Controller retains overall accountability.

Where the Incident Controller’s Authority Comes From

The Incident Controller’s authority comes from formal delegation under relevant legislation, agency policy, or both. It does not come from the title itself.

The organisation with legislative responsibility for managing the incident, commonly the control agency, appoints the Incident Controller and delegates the authority required to direct the response.

AIIMS provides the framework, terminology, and management structure for coordinating incidents, but it is not the source of statutory power. The extent of an Incident Controller’s authority depends on the legislation, jurisdiction, and agency arrangements that apply to the incident.

Because authority is linked to formal appointment, clear identification of the Incident Controller on scene is essential. Role-specific vests or tabards help responders, supporting agencies, and decision-makers quickly recognise who holds responsibility for managing the incident.

Core Responsibilities of the Incident Controller

Once appointed, the Incident Controller is accountable for the overall management of the incident. While responsibilities may vary depending on the type, size, and complexity of an incident, the core functions remain consistent.

The Incident Controller is responsible for:

• Setting incident objectives that define what the response is aiming to achieve.
• Approving the Incident Action Plan (IAP) to establish strategies, priorities, and resource requirements for each operational period.
• Coordinating agencies and resources to ensure all responding organisations work towards common objectives.
• Maintaining responder and community safety by considering risks and making informed decisions.
• Providing strategic direction, including major operational priorities, public information decisions, and resource allocation.

The Incident Controller does not manage every task personally. As incident complexity increases, operational responsibilities are delegated to members of the Incident Management Team (IMT), including Operations, Planning, Logistics, and Public Information Officers.

Delegation allows the response structure to expand while ensuring the Incident Controller remains responsible for overall coordination, decision-making, and accountability.

Qualities of an Effective Incident Controller

While the Incident Controller role is defined by authority and responsibility, effective incident management also depends on strong leadership capabilities.

An effective Incident Controller needs to:

Maintain Situational Awareness

The Incident Controller must understand what is happening, what risks are developing, and how conditions may change. This enables timely decisions based on accurate information.

Communicate Clearly

During complex incidents, information must move quickly between agencies, teams, and decision-makers. Clear communication helps maintain shared understanding across the response.

Make Decisions Under Pressure

Incident Controllers often make decisions with incomplete information and changing circumstances. They must balance urgency, risk, available resources, and community impacts.

Delegate Effectively

As incidents grow, no single person can manage every function. Effective delegation ensures specialist teams can operate while maintaining overall coordination.

Adapt to Changing Conditions

Incidents rarely follow the original plan exactly. An effective Incident Controller adjusts objectives and strategies as new information becomes available.

Incident Controller vs Officer in Charge

The terms Incident Controller and Officer in Charge are sometimes used interchangeably, but they describe different responsibilities.

An Incident Controller is appointed specifically to manage an incident under an incident management framework such as AIIMS. An Officer in Charge is generally a position within an organisation’s normal command or rank structure.

In many situations, the same person may perform both roles. However, the distinction remains important because operational control of an incident comes from the Incident Controller appointment, not simply from rank or seniority.

Understanding this difference helps avoid confusion during multi-agency responses, where several organisations may have personnel present but only one person has overall responsibility for managing the incident.

How the Role Scales Across Level 1, 2 and 3 Incidents

The Incident Controller’s responsibility remains consistent across all incident levels. What changes is the amount of support, delegation, and coordination required. 

At every incident level, there remains one Incident Controller responsible for establishing objectives, approving the Incident Action Plan, and maintaining overall accountability.

The difference is not the level of authority, but the amount of coordination required. A Level 3 incident may involve multiple agencies, larger resource requirements, and extended operations, requiring the Incident Controller to focus more on strategic leadership rather than direct task management.

Handover and Continuity of Control

Because AIIMS operates on the principle of unity of command, there can only be one Incident Controller responsible for an incident at any given time.

When responsibility transfers to another person, a formal handover process ensures continuity and prevents confusion. This may occur due to shift changes, incident escalation, fatigue management, or the arrival of a more appropriate officer.

A clear Incident Controller handover should include:

• the current situation and incident status
• existing incident objectives and priorities
• resource allocation and capability
• key risks and safety considerations
• current Incident Action Plan arrangements
• confirmation that responsibility has formally transferred

The incoming Incident Controller should receive a complete understanding of the incident before accepting responsibility. The transfer should be clearly communicated to the Incident Management Team, responding agencies, and other relevant personnel.

A structured handover ensures everyone understands who is responsible for directing the response and maintains the principle of clear accountability throughout the incident.

Identifying the Incident Controller On Scene

During a multi-agency incident, quickly identifying the person responsible for overall coordination is critical.

Emergency responders, liaison officers, supporting organisations, and external agencies need to know who holds decision-making responsibility. Clear role identification reduces delays, improves communication, and supports effective coordination.

Under AIIMS, Incident Management Team roles are commonly identified using colour-coded vests or tabards displaying the person’s assigned function.

The Incident Controller is typically identified by:

• a white AIIMS role vest or tabard
• clear “INCIDENT CONTROLLER” role identification
• highly visible lettering suitable for operational environments
• durable construction designed for repeated emergency use

For organisations procuring AIIMS identification equipment, role clarity is essential. Identification garments should be easy to recognise, operationally practical, and consistent with AIIMS role structures. Our guide to AIIMS vests and tabards explains role colours, labelling requirements, and garment specifications to help ensure consistent identification across Incident Management Teams.

What Has Changed in AIIMS 2025

The AIIMS 2025 edition continues to build on Australia’s established incident management framework while providing updated guidance for increasingly complex emergency environments.

For Incident Controllers, the updated framework reinforces the importance of:

• maintaining unity of command
• coordinating across multiple organisations and jurisdictions
• developing clear incident objectives
• using structured planning processes
• maintaining effective information flow throughout the response

As incidents become more complex, the Incident Controller role increasingly requires coordination across agencies, community stakeholders, and specialist teams.

Organisations reviewing their emergency management procedures, training programs, or identification equipment should ensure they align with the latest AIIMS guidance.

Clear Identification Supports Effective Incident Management 

An Incident Controller can only lead effectively when everyone involved understands who is responsible for directing the response.

Clear identification supports:

• faster decision-making
• stronger communication between agencies
• clearer reporting lines
• improved accountability during emergency operations

For emergency services, councils, contractors, and organisations operating within AIIMS structures, reliable role identification is an important part of preparedness.

Reflective Fabrications manufactures Australian-made AIIMS vests and tabards designed for operational environments, helping Incident Management Teams quickly identify key roles during critical incidents.

Whether you are replacing existing equipment, expanding an Incident Management Team, or standardising role identification across your organisation, our team can help develop solutions suited to your operational requirements. Talk to our team about role-specific identification solutions designed for operational use.