Shell IMH Navigator
⌘K
Incident Management Handbook
8.9 guidance

Command Work Products - CIR Reporting

IC/UC Routine or Recurring Critical Information Requirements (CIR)

Depending on the size, scope, and longevity of the incident response external reports maybe distributed and received by the Unified Command. Below is a sample schedule of some reporting times based on best practices and response experience. These reports can be delivered via three different communication methods:

  • Report - written report provided as requested within the IMS organization
  • Briefing - verbal report provided during a meeting/briefing or other specified time to requested

. Display - written report displayed as part of the Situation Status Board or other location as requested.

Example of Routine or Recurring CIR Reporting Type/Timeline Type Example Times
Agencies assigned to incident summary report from the Liaison Officer (LOFR) Report 0600 - Daily
Adversely impacted and involved stakeholders & surrounding community report from the LOFR Report 0600 - Daily
Updated Form 209 Incident Status Summary Report provided by Situation Unit Leader (SITL) Report 0600 & 1700 or Prior to Planning Meeting
Operational Status Update prior to Objectives Meeting and key trigger points in the response (milestones/operational constraints/challenges/future operations) from OSC/PSC/Salvage/Logistics Briefing Prior to Objectives Meeting, as necessary
Media Talking Points updated and provided by Public Information Officer (PIO) Report 0600 - Daily
Continuous display of Common Operating Picture (SITL & COP Specialist) Display Ongoing
Weather Report, Trajectories, and Daily Meeting Schedule from Planning Section Chief (PSC) & SITL Display 0600, 1200 & 1800
Burn Rate from Finance Section Chief (FSC) Report 0600
Report on media climate including social media outlets by Public Information Officer (PIO) Report/ Briefing 0600
Handbook Pages243
PartB — Incident Management
Section8.9 CIR Reporting
Typeguidance