ICS
2Respond and manage

The planning cycle

An operational period is the time set for carrying out one set of objectives, as written in the Incident Action Plan. Each period gets its own objectives, assignments and briefing. The plan for the next period is written during the current one.

Incident or eventNotificationsInitial response and assessmentIncident briefing (ICS 201)Initial unified command meeting, if usedINITIAL RESPONSE, ONCEObjectives meetingCommand and General Staff meetingTactics meetingPlanning meetingIAP prepared and approvedOperations briefingExecute plan, assess progressOPERATIONAL PERIODOne lap per period.The next period startsafter the operations briefing.
The stem of the Planning P runs once, and its loop repeats every operational period.

Setting the period length

Start with 12-hour periods during active containment, so each shift has its own plan and briefing. Move to 24 hours once eradication and recovery are routine, and to longer periods for monitoring. The Incident Commander sets the length, and it goes in the IAP.

Writing objectives

An objective names an outcome, a measure and a time. It says what must be true, and leaves how to the tactics meeting.

Example

WeakStronger
Contain the ransomwareNo new encryption events on any host after 14:00 Tuesday, confirmed in EDR telemetry
Reset passwordsEvery account in the compromised group reset, with sessions and tokens revoked, by 18:00
Find out what happenedScope confirmed for the finance tenant, every affected host and account listed with evidence, by 09:00 Wednesday
Keep leadership informedStatus summary to the executive group at 09:00 and 17:00 each day until recovery is complete

The meetings

StepWhoProduces
Initial response and assessmentFirst respondersSize-up and first actions
Incident briefingOutgoing and incoming commandICS 201
Initial unified command meeting, if usedUnified command membersAgreed objectives, one organization and one Operations Section Chief
Objectives meetingIC or unified commandObjectives for the next period (ICS 202)
Command and General Staff meetingIC with Command and General StaffPriorities, constraints, decisions
Tactics meetingOperations, Planning, Logistics, SafetyWork assignments and resource needs
Planning meetingCommand and General StaffAgreement to the plan
IAP preparation and approvalPlanning prepares, IC signsThe Incident Action Plan
Operations briefingThe oncoming shiftAssignments delivered. The period starts
Execute and assessOperations, with Planning trackingStatus updates, changes flagged to command

Meeting agendas

The Planning Section Chief runs every meeting except the objectives meeting, which the Incident Commander runs. The lengths are starting points. Keep each meeting to its agenda and move side discussions out of the room.

Scripts for opening the objectives meeting and the operations briefing are on Command and handover.

MeetingFacilitatorLengthAgenda
Objectives meetingIncident Commander20 minutesReview progress against the current objectives. Set up to three objectives for the next period, each with an outcome, a measure and a time. Set command emphasis and the period length. Decide what goes to executives.
Command and General Staff meetingPlanning Section Chief30 minutesIncident Commander presents the objectives and emphasis. Each section and Command Staff member raises constraints, needs and decisions. Incident Commander decides or takes items to the executive group.
Tactics meetingPlanning Section Chief45 minutesOperations proposes groups and tasks for each objective. Planning checks them against scope. Logistics confirms people, tools and access. Safety reviews risk to people and physical processes. The result is an ICS 215 worksheet, the Safety Officer's ICS 215A and the resource orders.
Planning meetingPlanning Section Chief30 minutesSituation briefing. Operations presents the plan. Each section confirms it can support it. Incident Commander approves the plan in principle and sets the IAP deadline.
Operations briefingPlanning Section Chief20 to 30 minutesRoll call and the period. Incident Commander gives command emphasis. Situation and objectives. Operations delivers each group's assignment. Logistics gives the communications plan. Safety message. Public Information and Liaison notes. Incident Commander closes and the period starts.

A filled-in plan for one period is in the worked example.

A day in 12-hour periods

Example

TimeWhat happens
06:30Operations briefing for the day shift
07:00Day period starts. Night shift hands over and goes to rest
09:00Executive update from the status summary
11:00Objectives meeting for the night period
12:00Command and General Staff meeting
13:00Tactics meeting
14:30Planning meeting
16:00IAP signed
17:00Executive update
18:30Operations briefing for the night shift
19:00Night period starts. Day shift hands over and goes to rest
23:00Objectives meeting for the next day period, run by the night Incident Commander
00:00Command and General Staff meeting
01:00Tactics meeting
02:30Planning meeting
04:00IAP signed. It is briefed at 06:30

Each shift plans the other shift's period. Once the incident settles, switch to one 24-hour plan with a briefing at each shift change, and the night cycle drops away.

Schedule for your period

Set when the next operational period starts and how long it runs. The schedule places each meeting of the cycle before that start, using the spacing of the 12-hour example above. Move any meeting to fit the incident.

What goes in the IAP

  • Objectives and command emphasis (ICS 202)
  • Organization assignment list (ICS 203) or chart (ICS 207)
  • Assignment lists, one per group or division (ICS 204)
  • Communications plan (ICS 205)
  • Safety message (ICS 208)
  • Current situation summary

For Type 4 and 5 incidents the incident briefing (ICS 201) is the plan.

Adapted from the National Incident Management System, Third Edition (FEMA, 2017). Cyber adaptation, examples and templates by Habib Tora, licensed under CC BY 4.0. Not published by, endorsed by, or affiliated with FEMA or the Department of Homeland Security. Structure after Google's SRE Incident Management Guide. Companion to PIVTR-D.