Shell IMH Navigator
⌘K
Incident Management Handbook
8.8 guidance

Command Work Products - Critical Information Requirements

IC/UC CIR Identification

CIRs are developed and provided by the Incident Commander (IC) or Unified Command (UC) to identify criteria requiring immediate and routine notifications to the IC/UC through the Incident Management Team. These requirements are essential for maintaining situational awareness for the IC/UC, increasing their ability to make key decisions in a timely manner and enhancing the operational response posture to mitigate further adverse impacts.

A fully actionable CIR should contain six parts
· What is to be reported? · How quickly it is to be reported? · Who is receiving the information? · How is the information being provided?
· Who is reporting the information? · Is the information required to be provided on a recurring basis?
Examples of Immediate Reporting CIRs Examples of Recurring CIRs
· Death or injury · Status of responders - health & well being (morale, stress)
· Public health impacts · Report safety process changes
· Any breach in security zone · Summary of surrounding community impacts
· Impacted sensitive areas beyond protection · Major public health concerns
· Confirmed wildlife impacts · Performance of assigned personnel
· Loss or breach of containment · Response staffing considerations
· Change in source control/spill volume/incident complexity · Review of established incident end points
· Any incidents within the incident · Success of Incident Action Plan Implementation
· Loss of major tactical resources · Report of cleanup/recovery metrics
· Unplanned VIP visits en route/planning/arriving · Critical resource gaps
· Adverse media, protest plans, interview requests · Changes in media/public interest
· Adverse political/influence · Summary of demobilization metrics
· Special requests from agencies · Periodic incident cost analysis
Handbook Pages242
PartB — Incident Management
Section8.8 Critical Information Requirements
Typeguidance