MARADMIN 427/23 - Unit Punishment Book Policy Update for Officer Nonjudicial Punishment OMPF Filing

Scope

MARADMIN 427/23 updates Unit Punishment Book policy for officer Nonjudicial Punishment. When an officer receives NJP, the UPB entry, the acknowledgment of the opportunity to submit matters, and any response provide to the local personnel administration center for inclusion into the officer's Official Military Personnel File (OMPF). The message closes the gap between unit-level UPB completion and permanent OMPF filing for officer cases.

Audience

• Commanding officers imposing NJP on officers.
• S-1 officers, S-1 chiefs, and legal clerks preparing the officer UPB package.
• IPAC personnel receiving the package for OMPF inclusion.

Required action

• Complete the officer UPB entry under the standard NJP UPB rules.
• Route the officer NJP UPB entry to the local personnel administration center (IPAC) for OMPF inclusion.
• Route the officer acknowledgment of the opportunity to submit matters with the entry.
• Route any officer response with the package.
• IPAC includes the package in the officer's OMPF. The OMPF entry is the primary action. The unit legal file retains a copy.

Connection to higher policy

• Manual for Courts-Martial 2024 Part V. Parent NJP procedures.
• MCO P1070.12K paragraph 4007. OMPF adverse material rules.

Connection to Marine Corps doctrine

• MCO 5800.16 Volume 14 paragraph 011105. Officer UPB completion follows the standard NJP UPB rules.
• MCO 5800.16 Volume 15. Officer Misconduct and Substandard Performance of Duty framework. Officer misconduct routes through procedures distinct from enlisted procedures.
• IGMC Legal Administration Functional Area checklist. Cites this message as an audit reference for NJP and UPB execution.
• NAVMC 3500.3E T-R events 0102-GENA-1011 and 0111-GENA-2009. Map the NJP processing workflow in the portal's admin pages.

Status

Signed 2023-08-28 per the HQMC message index. Active. Date settled from the message header, released 2023-08-28, confirmed against the archived message on 2026-07-16.