Span of Control in Fire Emergencies: AIIMS 2025 Guide

Span of control is one of the core ideas that keeps emergency operations manageable. In simple terms, it is the number of people, teams or reporting elements that one supervisor can effectively direct, monitor and support without becoming overloaded.

In Australian fire and emergency management, span of control sits within the Australasian Inter-service Incident Management System (AIIMS). AIIMS is designed to let organisations scale an incident-management structure as an incident grows, while keeping reporting lines clear and workloads manageable.

What does span of control mean?

Span of control describes the number of reporting relationships that one supervisor can manage effectively. The important word is effectively. A supervisor must be able to allocate work, understand changing risks, receive information, monitor progress, make decisions and support the people reporting to them.

It is therefore not simply a question of how many firefighters are standing in one place. A Sector Commander may supervise several team leaders, and each team leader may supervise their own crew. The total number of people involved can be large while each individual supervisor still has a manageable number of direct reports.

Span of control in AIIMS 2025

AFAC is the custodian of AIIMS. The 2025 edition is the current national incident-management doctrine used across Australian fire, emergency-service and land-management organisations. It preserves the scalable, all-hazards approach of earlier editions while strengthening safety, information management, recovery and the way complex multi-agency incidents are supported.

Span of control operates alongside the other AIIMS principles. In practice, these principles work together rather than as separate boxes:

Is the correct span always three to seven?

Older publicly available AIIMS-related material commonly describes an effective span as roughly three to seven direct reports, with around five often treated as desirable. That remains a useful way to understand the concept, but it should not be treated as a fixed safety limit that automatically works in every situation.

The appropriate span depends on factors such as:

• incident complexity and rate of change
• risk to personnel and the public
• experience and competence of the people being supervised
• geographic separation of crews or teams
• communications quality and radio congestion
• how similar or different the assigned tasks are
• the amount of information the supervisor must process
• whether the supervisor is also carrying another significant operational function.

A supervisor dealing with several experienced leaders performing similar work in a stable situation may manage a wider span than someone controlling dispersed resources in rapidly deteriorating conditions. The number alone does not tell you whether the span is safe.

Why span of control matters on the fireground

Fire incidents generate information quickly. Conditions change, crews move, resources arrive, objectives are updated and safety problems emerge. A supervisor who has too many direct reporting relationships can become a bottleneck.

An overloaded supervisor may struggle to:

• maintain an accurate picture of where crews are and what they are doing
• notice changing fire behaviour or emerging hazards
• receive and prioritise radio traffic
• confirm that instructions have been understood
• provide resources or relief when requested
• coordinate with other functions or agencies
• look ahead instead of reacting only to the latest problem.

The danger is not just slower administration. When supervisory capacity is exceeded, information can be missed, accountability can weaken and risk controls can become less reliable.

A simple operational example

Consider a developing bushfire with several crews working across different parts of the incident. Early in the response, an Incident Controller may directly manage a small number of resources or key leaders. As additional appliances, aircraft, strike teams and agencies arrive, the same arrangement may no longer be workable.

The structure can then expand. Operational resources may be grouped into sectors or divisions, with commanders appointed to manage those areas. Instead of receiving individual reports from every appliance, the higher-level supervisor receives consolidated information from the designated commanders.

This is the important relationship between span of control and scalability: the organisation grows in a controlled way as the workload grows.

When should the structure be expanded?

Do not wait until communications have collapsed. Warning signs that span of control may be becoming unmanageable include:

The answer may be to delegate responsibility, create another supervisory layer, separate geographic areas, establish or strengthen an incident-management function, assign support staff or redistribute resources. The appropriate solution depends on the incident.

Span of control and unity of command

Span of control answers the question: How much can one supervisor effectively manage? Unity of command answers another important question: Who does each person report to?

The two concepts support each other. Adding more supervisors without clear reporting relationships can create competing instructions. Keeping one clear reporting line but placing every resource under the same supervisor can create overload. A sound incident structure needs both manageable supervisory loads and clear command relationships.

Multi-agency incidents add another layer of complexity. AIIMS is designed so organisations can work together within an integrated structure while retaining the legal, organisational and specialist responsibilities that apply to them.

Span of control within an Incident Management Team

The concept is not limited to crews on the fireground. It also matters inside an Incident Management Team. As an incident grows, the Incident Controller cannot personally perform every management task. Functional responsibilities are delegated and staffed to match the needs of the incident.

AIIMS 2025 places increased emphasis on areas including safety, recovery, information flows, Planning, Intelligence, Finance, Investigations, Public Information, community engagement and volunteer management. That makes effective delegation and manageable supervisory relationships increasingly important during complex incidents.

The aim is not to build the largest possible IMT. It is to build the structure the incident actually needs, then expand, contract or reorganise it as those needs change.

Field perspective: what good span of control feels like

Practical checks for supervisors

When assessing your own span of control, ask:

1. Who reports directly to me? Can I name them without hesitation?
2. Do they know who they report to? Reporting lines should be understood, not assumed.
3. Can I monitor their safety and progress? If not, the supervisory load may be too broad or too dispersed.
4. Am I receiving more information than I can process? Communication volume is a workload indicator.
5. Am I still able to think ahead? A supervisor who can only react to immediate problems may need support or delegation.
6. Has the incident changed? A structure that worked 30 minutes ago may no longer suit the current risk and complexity.
7. Can something be delegated safely now? Early delegation is usually easier than restructuring after overload occurs.

What the public and workplaces can learn from the concept

AIIMS is professional incident-management doctrine. A household should not try to build an imitation Incident Management Team during an emergency. However, one lesson transfers well: do not load every emergency task onto one person.

In workplaces, emergency-control organisations and other formal arrangements should follow their approved emergency plans, procedures and training. At home, preparation can simply mean agreeing beforehand who calls Triple Zero, who helps children or a person with additional needs, who collects pets and where everyone meets.

Those arrangements are practical preparation, not AIIMS command appointments. During an emergency, the public should follow official warnings and directions from emergency services.

Common misconceptions

“Five people is always the correct span.”

No. Around five is a useful traditional benchmark, but complexity, risk, communications, geography and competence affect what is manageable.

“More supervisors always make an incident safer.”

No. Extra layers that are not needed can slow communication and create confusion. The structure should be scalable and proportionate to the incident.

“Span of control only applies to firefighters in the field.”

No. The principle applies throughout incident management, including teams performing planning, logistics, intelligence, public information and other functions.

“If everyone can hear the radio, everyone can report directly to the Incident Controller.”

That defeats the purpose of a structured reporting system. Communications technology does not remove the human limits on attention, supervision and decision-making.

Training and current AIIMS material

AFAC publishes the current AIIMS manual and supporting resources. The nationally recognised 22612VIC Course in the Australasian Inter-service Incident Management System (AIIMS) is current on the national training register and is intended for personnel who need to work within an AIIMS structure.

AFAC states that the AIIMS Principles course supports people working in a team-based AIIMS incident-management structure. Role-specific IMT responsibilities require additional training and organisational approval. Reading this article is therefore useful study support, but it does not authorise anyone to perform an AIIMS role.

Current AFAC AIIMS information →

Related FireRescue guides

• AIIMS 2025: Australia’s Incident Management System Explained
• Command and Control Leadership: Why It Matters in Emergencies
• Bushfire Management Strategy

Conclusion

Span of control is not about finding a perfect number and applying it mechanically. It is about ensuring that each supervisor has a workload they can genuinely manage while maintaining safety, situational awareness, communication and timely decision-making.

As an incident expands, the structure should expand with it. When conditions simplify, unnecessary layers can be reduced. That ability to scale while keeping responsibilities clear is one of the reasons span of control remains a core part of Australian incident-management practice.

Official and authoritative sources checked

• AFAC — Australasian Inter-service Incident Management System (AIIMS), current 2025 edition information
• AFAC — AIIMS 2025 Manual release information
• AFAC — Course in AIIMS Principles and 2025 training updates
• training.gov.au — 22612VIC Course in the Australasian Inter-service Incident Management System
• Australian Disaster Resilience Knowledge Hub — historical AIIMS material used only to explain the development of span-of-control guidance

Corrections and operational experience: FireRescue Training Hub welcomes source-backed corrections and useful operational observations from current or former emergency-management practitioners. Current AFAC doctrine and agency procedures should always take priority where terminology or practice changes.