Operations Event Incident Reporting
OPREP-3 SIR Serious Incident Reporting
Submit OPREP-3 Serious Incident Reports (SIR) to the Commandant of the Marine Corps through the Marine Corps Operations Center (MCOC) within 30 minutes of awareness for significant events not at the national-level interest threshold.
T&R Event Details
- Event Code
- 0102-OPER-1101
- Source Policy
- MCO 3504.2A
- MOS Performing
- 0102, 0111, 0170
- Grades
- Sgt, SSgt, GySgt
- Sustainment Interval
- 12 months
- Evaluation-Coded
- No
- Readiness-Coded
- No
Role and responsibility
The unit watch officer or operations duty officer owns the OPREP-3 SIR synchronous voice report at the moment of event awareness. The S-3 operations staff drafts the asynchronous message report per Enclosure 4 format. The S-1 officer and adjutant support OPREP-3 SIR records retention and case file maintenance. The commander signs supplemental reports.
Source documents flow from the event or incident notification, the duty officer report, the unit muster sheet, the medical record (for injury or fatality), the law enforcement report (for criminal events), the safety board input (for mishaps), Enclosure 2 reportable events list, Enclosure 4 message format, and Enclosure 5 sample message. Outputs include the synchronous voice report log, the OPREP-3 SIR message report, the supplemental reports, the unit OPREP-3 case file, and the retained record per SECNAV M-5210.1.
OPREP-3 SIR is the standard Marine Corps serious incident report category. It routes to CMC through the Marine Corps Operations Center (MCOC) for events not at the national-level interest threshold or otherwise not covered under another flag word.
Trigger events
- Significant event or incident reportable per Enclosure 2 of MCO 3504.2A.
- Death of a Marine, Sailor, or DoD civilian.
- Serious injury requiring hospitalization.
- Suicide or attempted suicide.
- Mishap per MCO 3040.4 (coordinate with the safety board).
- Hazing event per Enclosure 6 (separate sub-page for hazing protocol).
- Sexual assault per MCO 1752.5A (separate sub-page for SAPR confidentiality protocol).
- Equipment loss or theft above the reporting threshold.
- Significant operational incident below the national-level interest threshold.
Processing workflow
- Identify the reportable event. Match against Enclosure 2 of MCO 3504.2A reportable events list per MCO 3504.2AMCO 3504.2A Paragraph 4. The list is a general guideline. When in doubt, submit a report.
- Confirm the OPREP-3 SIR category. The event is significant but not at national-level interest. PINNACLE-eligible events route per the PINNACLE sub-page.
- Submit the synchronous voice report to MCOC. The unit watch officer calls the MCOC voice number in Enclosure 3 within 30 minutes of awareness per MCO 3504.2AMCO 3504.2A Paragraph 4a(2)(a)2.
- Build the voice report content. The minimum voice report content includes date, time, location, unit or installation, personnel involved, and a general description of the event or incident. Do not delay the voice report past the 30-minute mark to obtain additional information.
- Coordinate with operations, legal, and SARC. Operations leads the message drafting. Legal reviews the report content. SARC coordinates sexual assault case factual content per the sexual-assault-and-hazing-report-protocol sub-page.
- Draft the OPREP-3 SIR message. Use the Enclosure 4 message format. Reference Enclosure 5 for the sample SIR message structure.
- Apply EDIPI rules. For non-SAPR reports, include only the EDIPI for personnel identification per DODI 1000.30DODI 1000.30 and MCO 3504.2AMCO 3504.2A Paragraph 5b. Do not include SSN or last four of SSN.
- Apply mishap coordination. For mishap events, coordinate with the safety board per MCO 3040.4MCO 3040.4. The OPREP-3 SIR runs in parallel with the mishap investigation report, not as a replacement.
- Route the message report. Submit to MCOC per Enclosure 3 message addressing. Include CMC WASHINGTON DC PPO and the higher headquarters as required addressees.
- Submit supplemental reports. Supplemental reports correct or add information. Do not delay the initial report. Submit supplements as facts develop.
- Retain the record. Archive the OPREP-3 SIR report per SECNAV M-5210.1SECNAV M-5210.1 and NAVMC DIR 5210.11E.
- File the unit OPREP-3 case file. Place the voice report log, the message report, the supplemental reports, and the supporting documentation in the unit OPREP-3 case file.
Systems of record and forms
Systems
- Marine Corps Operations Center (MCOC). Marine Corps OPREP-3 SIR receiving authority at HQMC.
- Unit OPREP-3 case file. Local archive of OPREP-3 SIR reports retained per SECNAV M-5210.1.
- Safety board investigation system. Parallel mishap investigation per MCO 3040.4.
Forms
- OPREP-3 SIR Message Format. Enclosure 4 of MCO 3504.2A.
- OPREP-3 SIR Sample Message. Enclosure 5.
- OPREP-3 Reporting Contact Information. Enclosure 3 MCOC contact data.
- Voice Report Log. Local log capturing the synchronous voice report content and time.
- Supplemental OPREP-3 SIR Report. Local template for supplemental reports.
Common pitfalls
- Initial voice report delayed pending complete information. The 30-minute timing window per MCO 3504.2AMCO 3504.2A Paragraph 4a(2)(a)2 takes precedence. Report what is known and supplement.
- Non-SAPR report includes SSN or last four. The OPREP-3 message exposes PII beyond the DODI 1000.30 framework. Use the EDIPI only per Paragraph 5b.
- Message format off-template. The OPREP-3 SIR message diverges from Enclosure 4 format. Use the Enclosure 4 message format and reference Enclosure 5 sample.
- Mishap report skipped. The OPREP-3 SIR runs without coordination with the safety board. Coordinate with the safety board per MCO 3040.4MCO 3040.4 on mishap events.
- Records retention skipped. The OPREP-3 SIR record is required to be retained per SECNAV M-5210.1. Archive every report in the unit case file.
Decision points
- 30-minute timing window. The voice report is required within 30 minutes of awareness per MCO 3504.2AMCO 3504.2A. Report at the moment of awareness with the information on hand.
- Hazing or sexual assault routing. Route hazing reports per the Enclosure 6 sample and sexual assault reports per the Enclosure 7 sample with the confidentiality rules per the sexual-assault-and-hazing-report-protocol sub-page.
- Supplemental report timing. Submit supplemental reports as facts develop. Do not delay the initial report to consolidate facts.
Authority
This sub-page maps to NAVMC 3500.3E T-R event 0102-OPER-1101 Supervise Operations Event Incident Reporting. The processing workflow sits under MCO 3504.2AMCO 3504.2A Paragraph 4 Execution, Enclosure 4 Message Format, Enclosure 5 Sample Message, DODI 1000.30DODI 1000.30 for the EDIPI rule, MCO 3040.4MCO 3040.4 for mishap coordination, and SECNAV M-5210.1SECNAV M-5210.1 records retention.
Related references
- MCO 3504.2A Operations Event/Incident Report (OPREP-3) Reporting. Primary order.
- CJCSM 3150.03D Joint Reporting Structure Event and Incident Reports (superseded, no direct successor in the 3150 series, current Marine Corps source is MCO 3504.2A).
- DODI 1000.30 Reduction of Social Security Number (SSN) Use Within DoD. EDIPI rule.
- MCO 3040.4 Marine Corps Mishap Investigation Reporting. Mishap coordination.
- SECNAV M-5210.1 DON Records Management Manual.
- NAVMC DIR 5210.11E Marine Corps Records Management Program.
Same topic, other roles
References
- MCO 3504.2A Operations Event/Incident Report (OPREP-3) Reporting
- DODI 1000.30 Reduction of Social Security Number (SSN) Use Within DoD
- SECNAV M-5210.1 DON Records Management Manual
- NAVMC DIR 5210.11E Marine Corps Records Management Program
- MCO 3040.4 Marine Corps Mishap Investigation Reporting
Related Pages
- Admin
Operations Event/Incident Reporting (OPREP-3) - S-1 Procedural Page
same topic - same function - MCO 3504.2A - same T&R event - 5 shared references
- Admin
OPREP-3 PINNACLE and National-Level Interest Reporting
same topic - same function - MCO 3504.2A - same T&R event - 2 shared references
- Admin
Reportable Events and Incidents (Enclosure 2)
same topic - same function - MCO 3504.2A - same T&R event - 2 shared references
- Admin
Sexual Assault and Hazing Report Protocol
same topic - same function - MCO 3504.2A - same T&R event - 2 shared references
- Admin
Sister Service OPREP-3 and WHITE PINNACLE Exercise
same topic - same function - MCO 3504.2A - same T&R event