Homeland Security

Appendix E

Reporting

Reporting during an incident or CBRNE emergency is as important as the response. The CST must receive timely and accurate information to effectively support the response. The CST also provides timely and accurate information that reinforces the decision-making process at all tiers of the response. This appendix provides sample guidance on report formats and procedures in order to minimize communications and properly frame the actual events at the incident site. Sample reporting formats in this appendix provide the detailed information generally required by the chain of command.

REPORTING TIMELINES

 

E-1. Due to the potential catastrophic effects of a CBRNE situation, a timely DOD response at the state and federal levels will be critical. Personnel at all levels of the approval process will expedite their actions and communications to support these missions.

E-2. During operations, the reporting sequence will be from the CST to the state command EOC for internal distribution and external transmission to the NGB EOC. The NGB will assemble the provided information and transmit the needed information to the director of military support (DOMS).

E-3. Unit organic secure communications assets are the primary means to communicate classified information.

E-4. Copies of all warning, planning, alert, and execution orders published by the state NG command authority will be furnished to the NGB EOC for distribution.

NOTE. See Table E-1 for reporting timelines.

Table E-1. Reporting Timelines

Table E-1. Reporting Timelines

RESPONSIBILITIES

 

E-5. The CST is responsible for transmitting reports in accordance with the timelines specified in applicable OPLANs/OPORDs. Both state area coordinators (STARCs) and NGB EOC are responsible for 24-hour, 7-day per week coverage, prior to, during, and after operations.

REPORTS

 

E-6. The CST provides reports for CBRNE response to the state EOC. These reports are used to immediately notify appropriate authorities for any significant event or incident of national-level interest. The reports must be timely, concise, and include enough information to allow action addresses to fully understand the situation and provide information to other levels as required. For example, operational reports (OPREPs), deployment reports, SITREPs, RFS, and reports used during redeployments will be submitted according to OPLAN/OPORD/SOP requirements. (See Tables E-2 to E-8.)

OPERATIONS REPORT

 

E-7. An OPREP3 should be sent in the following situations (the list is illustrative and should not be considered all-inclusive):

    • Interstate movement of a CST.
    • Movement of a CST by rotary or fixed-wing aircraft.
    • A positive finding of CBRNE.
    • Injury of a member (such as type of injury and disposition), vehicle accident resulting in a loss of the vehicle, or injury to a civilian because of a CST action.
    • Significant loss or contamination of equipment. (such as contaminated, improved chemical agent monitor [ICAM], vehicle).
    • Additional CBRNE hazards discovered or identified at the incident site.
    • Receipt of significant intelligence of an anticipated WME-related terrorist act.

When to Submit OPREP3 Reports

 

E-8. All OPREP3 reports will be submitted as soon as possible after an incident has occurred and sent at Flash precedence. The goal is to make initial voice reports within 15 minutes of an incident, with message reports submitted within 1 hour of an incident. Initial OPREP3s must not be delayed to gain additional information. Follow-up reports can be submitted as additional information becomes available.

Method of Transmission

 

E-9. OPREP3s will be reported by the fastest means available, consistent with security constraints. Reporting methodology is as soon as possible using voice reporting and appropriate secure/nonsecure means followed by amplifying record copy communications. Secure communications will be used for all classified reporting.

E-10. Sample OPREPs are shown in Tables E-2, below, and E-3.

Table E-2. OPREP3 (Voice Format) (Example)

Table E-2. OPREP3 (Voice Format) (Example)

Table E-3. OPREP3 (Message Format) (Example)

Table E-3. OPREP3 (Message Format) (Example)

OTHER REPORTS

 

E-11. The CST is required to provide reports for response to operations utilizing the appropriate message formats. Reports will be submitted at periodic intervals (such as 1300Z and 0100Z) or, as scheduled by the state EOC/STARC/NGB-CS or as significant events occur throughout the phases of the operations. The following sample reports are included in this appendix:

Table E-4. Deployment Report Format (Example)

Table E-4. Deployment Report Format (Example)

Table E-5. Situation Report—
SITREP (FLASH) (Example)

Table E-5. Situation Report— SITREP (FLASH) (Example)

Table E-6. Request for Support (Example)

Table E-6. Request for Support (Example)

Table E-6. Request for Support (Example) (continued)

Table E-6. Request for Support (Example) (continued)

Table E-7. Request for Information (Example)

Table E-7. Request for Information (Example)

Table E-8. Redeployment Report Format (Example)

Table E-8. Redeployment Report Format (Example)

QUICK REFERENCE MESSAGE FORMATS

 

E-12. CST quick reference message formats include the postmission report and the SITREP (quick).

Postmission Report

 

E-13. The postmission report will be submitted to the state EOC/STARC (see Table E-9).

Table E-9. Postmission Report (Example)

Table E-9. Postmission Report (Example)

SITREP (Quick)

 

E-14. The SITREP (quick) report will be submitted to the state EOC/STARC (see Table E-10).

Table E-10. Situation Report (QUICK)

Table E-10. Situation Report (QUICK)

 



NEWSLETTER
Join the GlobalSecurity.org mailing list