Incident running now
Pick the line that describes you.
I found somethingVerify it, start the record and protect the evidence, in the PIVTR-D first hour.
I am the Incident CommanderWork the first 30 minutes below, in order.
I am taking over commandGet the briefing, agree the time, announce it.
I have been given a seatCheck in, get an assignment, open your job aid.
I am an executiveWhat the Incident Commander needs from you, and when you will hear.
The Incident Commander's first 30 minutes
Work the items in order. The same list is on the quick card and in the Incident Commander's job aid.
| # | Item | Done when |
|---|---|---|
| 1 | Take command out loud: your name, the time, the incident name and where the command bridge is. Open your activity log (ICS 214). | The announcement is in the channel and the first log entry has a time. |
| 2 | If someone was in command before you, take a briefing from them, using the ICS 201 if one exists. | You can say what is affected and what has been done so far. |
| 3 | Open a command bridge and an out-of-band channel, and record both in the ICS 205. Treat email, chat and identity as visible to the attacker until scoping shows otherwise. | Every responder has joined the out-of-band channel. |
| 4 | Size up: what happened, what is affected, what is still happening and what is unknown. | Each of the four has a written answer, even if the answer is unknown. |
| 5 | Set up to three objectives, each with an outcome, a measure and a time. Examples are in Writing objectives. | The objectives are written where every responder can read them. |
| 6 | Name an Operations Lead, or an Operations Section Chief from Type 3, and hand over the technical work. Stay off the keyboard. | The Operations Lead has accepted and briefed the technical responders. |
| 7 | Decide the incident type, 5 to 1, with the type chooser, and fill the positions it calls for. | The type is logged and each seat it calls for has a name against it. |
| 8 | Confirm your authority limits, and who approves anything above them. | You have the name and number of the executive above you. |
| 9 | Tell counsel if personal data, regulators, law enforcement, extortion or insurance may be involved. The clocks are in notification deadlines. | Counsel has acknowledged, or the log says why they were not called. |
| 10 | Set the times of the first briefing and the first executive update, using the update schedule for the severity. | Both times are announced and in the log. |
| 11 | Write the incident briefing (ICS 201) before the first briefing. | The ICS 201 is filed where the next Incident Commander will find it. |
| 12 | Check hours: who has been awake since when, and who relieves them. Record hazards and rest rules in the ICS 208. | Every responder has a relief time. |
When the 30 minutes are done
- Run the first operational period with the planning cycle and its meeting agendas. The schedule on that page sets each meeting time from the next period start, and the org chart builder draws the ICS 207.
- Issue the first status summary (ICS 209). Every executive update comes from it.
- Order what the response lacks on the resource request, and activate the retainer with its script.
- Check what this kind of incident adds to command in Command by incident type, and open the matching PIVTR-D scenario and sector pages. The PIVTR-D incident kit puts both on one sheet with the reporting clocks.
- Compare your forms with the filled set in the worked example.
- If the incident will run past three days, plan for it with Extended incidents.
Taking over command
- Brief the incoming Incident Commander face to face or by voice, using the ICS 201 or the current IAP.
- Walk the open decisions and every commitment made to outside parties.
- Agree the effective time. Until then, the outgoing Incident Commander stays in command.
- Announce the change to Command and General Staff, all responders, and outside parties who deal with the Incident Commander.
- Log it, with both names and the time.
Record it on the transfer of command form. Scripts for the announcement are in Taking and handing over command.
Given a seat
- Check in with Planning, or with the Incident Commander if there is no Planning Section yet, on the ICS 211. Give your name, your contact details and when you last slept.
- Get an assignment, the name of your supervisor and your relief time. Do no work on the incident until you have all three.
- Join the out-of-band channel and open an activity log (ICS 214).
- Work the "On taking the seat" list in your position checklist.
Executives
The Incident Commander needs four things from the executive who owns the incident:
- The Incident Commander's authority limits, confirmed: what they may isolate, shut down and spend without asking. A signed delegation of authority settles this in one page.
- One named executive who can approve anything above those limits, with a phone number that works out of hours.
- Decisions on the questions only executives can answer, when the Incident Commander brings them with options.
- Wait for the scheduled updates. They come from the Public Information Officer at the times the Incident Commander sets, so executives stay off the command bridge.
How the crisis team and the executive decision group support the incident is in Above the incident.