What Is an Incident Action Plan (IAP)?

Key Takeaways

• An IAP records the incident’s objectives, the strategies to achieve them, the resources required, and the timeframe for implementation.
• Every incident needs an IAP, but it doesn’t always need to be written. A short, routine job can run on a verbal plan.
• Under Unity of Command, an incident has one Incident Controller, one set of objectives, and one IAP at any given time.
• The planning function prepares the IAP; the Incident Controller approves it.
• IAPs are revised on a cycle, once per operational period, for as long as the incident runs.
• The AIIMS 2025 edition sharpened the requirements around what an IAP must contain and how information moves between planning and operations during multi-agency responses.

What is an Incident Action Plan (IAP)? An Incident Action Plan (IAP) is the document that outlines an incident’s objectives, the strategies, resources, and timeframe needed to manage an incident effectively.

Under AIIMS, every incident has an IAP, but its complexity depends on the size and nature of the event. At Reflective Fabrications, we work with organisations operating under AIIMS, giving us practical insight into the planning, coordination, and role identification that help incidents run safely and efficiently.

In this guide, you’ll learn what an Incident Action Plan is, why it matters, what it typically includes, and how it supports coordinated incident management.

What Does an IAP Actually Contain?

Every Incident Action Plan answers four key questions:

• What are we trying to achieve? The incident objectives.
• How are we going to achieve it? The strategies and tactics.
• What do we need to get it done? The resources required.
• By when? The timeframe for the current operational period.

That’s the core of it. In practice, the level of detail scales with the incident. For a small, contained job, this might be three or four points scrawled in a logbook. For a Level 3 response running across multiple agencies, it becomes a structured document covering the objectives, the organisation and reporting structure, resourcing, communications arrangements, and the safety considerations for the period ahead.

What doesn’t change is the purpose. An IAP exists to describe the operational objectives and strategy, keep operations continuous from one shift to the next, make sure resources are used effectively, and give the Incident Management Team (IMT) something concrete to brief from.

Who Prepares and Approves the IAP?

Under AIIMS, the Planning function prepares the Incident Action Plan (IAP). The Planning team gathers information about the incident, develops the objectives and strategies, and identifies the resources needed.

The Incident Controller reviews and approves the IAP. This separation is intentional. Planning develops the plan, while the Incident Controller is accountable for the final decisions.

Once the IAP is approved, the Operations function puts the plan into action. Their role is to carry out the objectives and tasks outlined in the IAP.

This process supports the AIIMS principle of Unity of Command. Every incident has one Incident Controller, one set of objectives, and one Incident Action Plan. Even when multiple agencies are involved, any agency-specific plans must align with the overall IAP.

Verbal Plan vs Written Incident Action Plan

A common misconception is that every Incident Action Plan (IAP) must be a formal written document. Under AIIMS, that’s not the case. The format of the IAP depends on the size, duration, and complexity of the incident.

• Verbal plan: Suitable for short, routine incidents that follow established procedures, such as a minor traffic incident or a tree blocking a road.
• Simple written plan: Used when an incident is expected to continue beyond the initial response. This may be as simple as notes in a logbook or incident record.
• Formal written IAP: Required for complex incidents involving multiple operational periods, multiple agencies, or significant resources.

The decision to move from a verbal plan to a written IAP is based on duration and complexity, not just incident size. A written plan helps everyone stay aligned, track resources, maintain clear objectives, and support smooth handovers between operational periods.

The Operational Period Cycle

An Incident Action Plan (IAP) isn’t created once and left unchanged. It is reviewed and updated at the start of every operational period for as long as the incident continues.

Each operational period follows the same cycle:

• Review objectives. The Incident Controller confirms the current objectives or updates them based on changing conditions.
• Update the IAP. The Planning function prepares the revised IAP and works with Operations and Logistics to confirm the plan is achievable.
• Approve the plan. The Incident Controller reviews and approves the updated IAP.
• Brief the team. The approved IAP is shared with supervisors during the operational period (or shift) briefing before work begins.
• Repeat the process. The cycle starts again at the next operational period.

This review cycle keeps everyone working towards the same objectives, supports smooth shift handovers, and allows the response to adapt as the incident evolves.

IAP Requirements by Incident Level

An incident can escalate between levels as conditions change, and the IAP escalates with it. A job that starts as a verbal Level 1 plan can, within hours, need to become a written document if it grows in scale or duration.

What Changed for IAPs Under AIIMS 2025

The AIIMS 2025 edition, endorsed by the AFAC Council and published in October 2025, replaces the 2017 edition as the current incident management framework used by fire, emergency service, and land management agencies across Australia.

While the five AIIMS functions remain the same, the 2025 edition provides clearer guidance on how Incident Action Plans (IAPs) are managed during complex, multi-agency incidents.

Key updates include:

• Stronger guidance on Unity of Command to help multiple organisations operate under a single Incident Management Team (IMT).
• Clearer requirements for each operational period, including what an IAP should contain.
• Improved coordination between Planning and Operations, ensuring information is communicated more effectively as an incident evolves.

For organisations using AIIMS, the 2025 edition is now the current reference. If your incident management procedures, documentation, or equipment are still based on older AIIMS editions, it’s worth reviewing them to ensure they align with the latest guidance.

Why Role Identification Matters for IAP Execution

An Incident Action Plan (IAP) is only effective if teams can execute it. While the IAP defines roles and reporting lines, those responsibilities also need to be clear in the field. AIIMS role identification vests and tabards help crews quickly identify key personnel, improving communication and supporting efficient decision-making during an incident.

Reflective Fabrications manufactures incident management vests and tabards in Melbourne, designed for the colour coding and role labelling used by AIIMS teams. If you’re building or updating an IMT kit, read our guide to AIIMS vests and tabards procurement. For a broader overview of the framework, including the five functions, incident levels, and how it compares with ICS, see What Is AIIMS?

Put Your Incident Action Plan Into Practice

A well-prepared Incident Action Plan (IAP) keeps teams aligned, resources coordinated, and incident responses running smoothly. To support effective execution, Reflective Fabrications manufactures AIIMS role identification vests and tabards in Melbourne, helping Incident Management Teams identify key personnel quickly and maintain clear command on the ground. Contact our team to discuss your requirements or explore our AIIMS incident management solutions.