Naval Messages and GENADMINs - S-1 Procedural Page

Role and responsibility

The unit message drafter prepares the naval message per SECNAV M-5216.5SECNAV M-5216.5 Chapter 10 (Naval Messages and GENADMIN). The S-1 chief or adjutant runs format review. The unit security manager classifies the message content before release. The message release authority (designated officer per command policy) signs the release line. The unit message account operator submits the released message into the messaging system (Defense Messaging System, NIPR, or SIPR per classification). The S-1 clerk files the released message in the unit records system. The commander or designated release authority approves the release.

Source documents flow from the operational tasking, the reportable event, the personnel action affecting multiple commands, or the policy issuance routing through message traffic. Naval message outputs include the formatted message with the proper MSGID, SUBJ, REF, GENTEXT, and POC lines per Chapter 10, the classified content reviewed by the security manager, the release authority signature, the released message in the messaging system, the unit message account log entry, and the filed copy per SECNAV M 5210.1.

Per SECNAV M-5216.5 Chapter 10, naval messages cover GENADMIN (general administrative), NAVADMIN (Navy-wide administrative), MARADMIN (Marine Corps-wide administrative), and operational message traffic. Each message type follows defined format rules. The release authority signs the release line authorizing transmission.

Trigger events

• Operational tasking requires message traffic notification.
• Reportable event triggers a casualty, serious incident, or unit status report.
• Policy issuance to subordinate commands triggers MARADMIN format.
• Personnel action affecting multiple commands routes via message.
• Higher headquarters tasks a message response.
• Annual review of unit message account access.
• Unit message release authority change.

Processing workflow

1. Identify the message type. Per SECNAV M-5216.5SECNAV M-5216.5 Chapter 10, message types include GENADMIN (general admin), NAVADMIN (Navy-wide), MARADMIN (Marine Corps-wide), and operational traffic.
2. Draft the message. Per Chapter 10, the message carries the standard heading lines:
   • MSGID line identifying the originator.
   • SUBJ line stating the subject (all caps).
   • REF lines listing every referenced document.
   • GENTEXT or remarks per the message type.
   • POC line identifying the point of contact.
3. Apply the MSGID line. The MSGID identifies the originating activity, the precedence, and the date-time group.
4. Apply the SUBJ line. The SUBJ runs in all caps stating the subject clearly.
5. Apply REF lines. Per Chapter 10, every referenced document carries a REF letter (REF A, REF B, etc.) with the document identifier.
6. Apply GENTEXT or remarks. The GENTEXT block carries the message substance organized in numbered paragraphs.
7. Apply POC line. Per Chapter 10, the POC line identifies the responsible officer with name, rank, phone, and email.
8. Coordinate classification. Per Chapter 10, classified content routes through the security manager. The security manager reviews and authorizes the classification.
9. Route through the release authority. Per Chapter 10, the release authority (commander or designated officer) signs the release line authorizing transmission.
10. Submit through the unit message account. The unit message account operator submits the released message via Defense Messaging System or appropriate transmission channel.
11. File the released message. Per SECNAV M 5210.1 and MCO 5210.11F, file the released message in the unit records system per the SSIC retention schedule.

Systems of record and forms

Systems

• Defense Messaging System (DMS) and successor systems. Holds released naval messages.
• Unit Message Account. Holds inbound and outbound message traffic.
• Unit Records System. Holds the released message copy per SECNAV M 5210.1.
• Security Manager Classification Records. Holds the classification review record.

Forms

• Naval Message Format. Per SECNAV M-5216.5 Chapter 10.
• GENADMIN Message. Per Chapter 10.
• NAVADMIN Message Format. Navy-wide administrative format.
• MARADMIN Message Format. Marine Corps-wide administrative format per MCO 5216.20BMCO 5216.20.
• Release Authority Designation Letter. Local format per Chapter 10.

Common pitfalls

• Message released without classification review. Per SECNAV M-5216.5SECNAV M-5216.5 Chapter 10, classified content routes through the security manager.
• MSGID line incomplete. Per Chapter 10, the MSGID identifies the originator, precedence, and date-time group.
• SUBJ line not in all caps. Per Chapter 10, the SUBJ runs in all caps.
• REF letters out of sequence or missing. Per Chapter 10, REF letters run sequentially (REF A, REF B, etc.) with every referenced document listed.
• POC line missing. Per Chapter 10, the POC line identifies the responsible officer.
• Release authority signature missing on release line. Per Chapter 10, the release authority signs to authorize transmission.
• Message released over the wrong system (NIPR vs SIPR). The classification drives the system. The security manager confirms before release.
• Released message not filed in the records system. Per SECNAV M 5210.1, the released message retains per the SSIC schedule.

Decision points

• Message type selection. Per Chapter 10, the audience and the action drive the type. GENADMIN routes general administrative content. NAVADMIN routes Navy-wide content. MARADMIN routes Marine Corps-wide content. Operational messages route through the operational chain.
• Precedence selection. Routine, Priority, Immediate, Flash. The operational urgency drives the precedence.
• Classification level. The security manager reviews the content and applies the appropriate classification.
• Release authority assignment. Per Chapter 10, the commander designates release authority in writing. Different message types and classification levels route to different release authorities.

Authority

This sub-page sits under SECNAV M-5216.5SECNAV M-5216.5 Chapter 10 (Naval Messages and GENADMIN) with Chapter 7 (SSIC) and Chapter 8 (Signing and Authenticating) cross-referenced. MCO 5216.20BMCO 5216.20 applies Marine Corps-specific message format adjustments and MARADMIN handling. SECNAV M-5210.2SECNAV M-5210.2 sets the SSIC system. The processing workflow maps to NAVMC 3500.3E T-R events 0111-GENA-2002 (Prepare naval messages) and 0111-GENA-2102 (Review naval messages).

Related references

• SECNAV M-5216.5 Chapter 10. Naval messages and GENADMIN format.
• MCO 5216.20B. Marine Corps supplement.
• SECNAV M-5210.2. SSIC system.
• NAVMC 3500.3E. T-R events 0111-GENA-2002 and 0111-GENA-2102.