Taking and handing over command
Taking command
The first qualified person to reach the incident takes command and says so on the channel responders are using: their name, the time, the incident name, and where the command bridge is. They open an activity log and start the incident briefing.
Command passes only by formal transfer, whatever the seniority of the person arriving. A senior leader who arrives gets a briefing, then either takes command through a formal transfer or supports the Incident Commander in place.
Transferring command
Command may transfer when a more qualified person arrives and both agree, when the incident outgrows the current Incident Commander, at shift change, or when the Incident Commander is too tired to continue.
- 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.
Shift handover
| # | Item |
|---|---|
| 1 | Current objectives and progress against each |
| 2 | Status of every assignment, with who owns it now |
| 3 | Open decisions and who is waiting on them |
| 4 | Commitments made to executives, customers, regulators, insurers and law enforcement |
| 5 | Safety and wellbeing concerns, including who has worked too long |
| 6 | Known unknowns, and what would change the plan |
| 7 | Times of the next meetings, briefings and executive updates |
| 8 | Where the logs, timeline and evidence register are |
| 9 | 30 minutes of overlap between outgoing and incoming people |
Set a maximum shift length before the incident, give the Safety Officer authority to enforce it, and roster relief from the first night. Extended incidents has starting limits and rotation for incidents that run for weeks.
Decision log
Keep a decision register from the first hour. Every decision that commits people, money, systems or a public statement gets an entry.
Each entry has a number, the time, the decision, the options considered, what was known, who decided, the authority used, and what would reverse it. The Incident Commander keeps it in the activity log until Planning is staffed, and then the Documentation unit keeps it on the decision register form.
A decision stands until a new entry reverses it. Each incoming Incident Commander reads the open entries before taking command. Decisions from executives arrive through the executive briefing and the executive decision request, and go in the register with the executive group as the decider.
Scripts
Say these word for word until they are habit. Fill the brackets before you speak. The executive briefing has its own agenda.
Script for taking command
This is [name]. As of [time and time zone], I am the Incident Commander for [incident name]. The command bridge is [where]. [Name] is the Operations Lead. Send status to [name] and decisions to me. The next briefing is at [time].
Script for announcing a transfer
This is [incoming name]. As of [time and time zone], I have taken command of [incident name] from [outgoing name], who briefed me from the [ICS 201 / current Incident Action Plan]. [Outgoing name] is now [new role / off shift until time]. The objectives, assignments and channels are unchanged. The next update is at [time].
Script for opening the objectives meeting
This is the objectives meeting for [incident name], setting objectives for operational period [start] to [end]. I am [name], Incident Commander. [Name] is recording decisions in the register. Present: [names and positions, or unified command members]. First, progress on the current objectives: [1: met / not met, new time]. [2]. [3]. Since the last period: [changes in scope, severity, type or outside parties]. Open decisions: [entry numbers]. For the next period I propose these objectives, each with an outcome, a measure and a time: [1]. [2]. [3]. Command emphasis: [priorities, constraints, risk tolerance]. Period length: [hours]. Questions on the objectives only. Tactics wait for the tactics meeting at [time]. [Unified command: each member confirms agreement.] Items for the executive group: [list].
Script for opening the operations briefing
This is the operations briefing for [incident name], operational period [start] to [end]. I am [name], Planning Section Chief. Roll call by section. [Incident Commander] will give command emphasis, then [Situation unit] the situation, then [Operations Section Chief] the assignments, then Logistics, Safety, Public Information and Liaison. Save questions for the end of each part.