(Return to ReadyIndy_EOP)  (Were you really looking for the archived IncidentActionPlan from ReadyCity2014?

The Incident Action Plan (IAP) is only a COMPONENT of our overall Emergency Operations Plan (EOP).

• And each IAP is only for 1 specific Ops Period (eg 24-hr, or Weekly plan).  So an incident may well have several IAPs.
• Each successive IAP is built & approved BEFORE the commencement of that OpsPeriod.
• Therefore know that while one OpsPeriod's IAP is being executed, 
  the leadership team is planning ahead, building & finalizing the IAP for the upcoming OpsPeriod.
• And there is a standard cadence for this planning process, called the Planning-P.
• Putting that Planning-P process into a standardized hour-by-hour timeframe is called a 'Battle-Rhythm'.
• Many/most Emergency Mgmt Agencies have a predefined, default Battle-Rhythm.
• And as affiliated teams have worked together, they've sync'd their battle-rhythms to coordinate more effectively.
•  Example:  @IDHS @HamiltonCoEOC ... and @ReadyIndy... had complementary battle-rhythms.

The Incident Action Plan (IAP) for an OpsPeriod could be officially maintained as ICS Form 202 by the Planning Section.

Or in the interest of simplicity complete ICS Form 201 (as a summarized briefing) - with essentially all the same info, and more.   Here's FEMA's complete set of ICS forms you may need.  An extensive IAP will be built as 1 set, consisting of several/many of these ICS forms.

When setting Objectives, think S.M.A.R.T:  
Strategic/Specific, Measurable, Attainable, Results/Research-based, Time-bound.

Example:  #ReadyCity2013 Exercise SMART Objectives (public link)  (Edit SMART spreadsheet) 

Alternative Formats:

• The following IAP format (simple) may be used if practical.
  (perhaps especially in the early hours of an incident).
• The matrix IAP sheet within the ReadyIndy Workbook - has a column for each OpsPeriod. 
• A more basic looking google-doc, much like we'd use for an Event Action Plan.  (template)