OMPF Submission Procedures (MARADMIN 015/20)

What MARADMIN 015/20 Established

MARADMIN 015/20MARADMIN 015/20 updated OMPF document submission requirements to reflect the modern processing environment. Key changes from prior policy.

• Required metadata standardization for all submissions
• Document quality standards (legibility, completeness, format)
• Routing requirements for specific document types
• Rejection criteria for non-compliant submissions
• Tracking requirements for processed submissions

PAC must comply with MARADMIN 015/20MARADMIN 015/20 on every OMPF submission. Audits surface non-compliance.

Required Metadata for All Submissions

Per MARADMIN 015/20MARADMIN 015/20, every OMPF submission requires.

Member Identification

• Full name (last, first, middle initial) matching MCTFS
• Social Security Number (verified against MCTFS)
• Rank and pay grade at time of document
• MOS at time of document
• Unit at time of document

Document Identification

• Document type per MCO P1070.12MCO P1070.12 categories
• Document subject (specific topic)
• Document date (date signed, not date submitted)
• Originating authority (who signed it)
• Effective date if different from document date

Submission Tracking

• Submitting unit
• Submitter name and contact
• Date submitted to PAC
• Tracking number for follow-up

Without complete metadata, the submission gets rejected.

Document Quality Standards

Per MARADMIN 015/20MARADMIN 015/20, documents must meet quality standards for OMPF inclusion.

Legibility

• All text clearly readable
• All signatures visible and identifiable
• All dates clearly written or printed
• Scanned documents at 300 DPI minimum
• No handwritten content that obscures printed text

Completeness

• All required signature blocks signed
• All required date blocks dated
• All attachments included
• All applicable sections completed
• Member acknowledgment where required

Format

• Standard 8.5 x 11 page size
• Single-sided when possible
• Clean copies (no marginalia or stray marks)
• Original or certified copy when required
• Digital format when submitted electronically

Routing Requirements

Different document types route differently per MARADMIN 015/20MARADMIN 015/20.

Direct PAC Submission

• Routine pay actions
• BAH and BAS changes
• Travel claims
• Administrative updates

Through S-1 to PAC

• Performance documents (Page 11, fitness reports)
• Awards
• Promotion warrants
• NJP results
• School certificates

Through Command Chain

• Administrative separations
• Letters of Reprimand
• Special qualification certifications

Direct from Issuing Authority

• HQMC promotion warrants
• Awards from external commands
• Foreign award documents

Knowing the routing prevents misdirected submissions.

Performance Steps

Step 1 - Receive Submission

PAC receives the document.

• Log receipt with date and time
• Identify source (S-1, member, external)
• Identify document type
• Verify routing was correct

Step 2 - Validate Per MARADMIN 015/20

Check the document against requirements.

• Metadata complete?
• Quality standards met?
• Required signatures present?
• Originating authority appropriate?
• Member identification verified?

If any item fails, reject and request corrected version.

Step 3 - Apply OMPF Categorization

Per MCO P1070.12MCO P1070.12.

• Major category identified
• Sub-category identified
• Document type code applied
• Indexing tags prepared

Step 4 - Upload Through O-RMA

Per MARADMIN 412/23MARADMIN 412/23, submit through the OMPF Records Management Application (O-RMA), the OMPF system of record since 5 September 2023. MMRP reviews and approves all documents per the IRAM.

• Scan document if hard copy (300 DPI minimum)
• Apply member identification and document type in the upload interface
• Submit for MMRP review
• Verify submission completion

Step 5 - Verify Indexing

After upload.

• Confirm document appears in member's OMPF
• Verify indexing tags applied correctly
• Test retrieval from OMPF view
• Document any indexing issues

Step 6 - Notify and Track

Close the loop.

• Notify submitting S-1 or member
• Update tracking system with completion
• File working copy per local PAC policy

Common Rejection Reasons

These get documents rejected back to S-1 or member.

1. Missing member SSN or wrong SSN. Critical metadata. Fix before resubmission.
2. Photocopy when original required. Marriage certificates, birth certificates, divorce decrees require original or certified copy. Photocopies not accepted.
3. Missing signature. Document signature block empty or signature not legible. Return to originator.
4. Wrong routing. Document submitted directly to PAC when should have routed through command. Redirect.
5. Stale document. Document over 30 days old at submission without explanation. Documents should submit within 10 working days of signing.
6. Unclear scan quality. Scanned document too low resolution or too dark to read. Re-scan at higher quality.

Tracking and Audit

Per MARADMIN 015/20MARADMIN 015/20, PAC tracks submissions for audit.

• Submission log with all required metadata
• Processing time per submission
• Rejection log with reasons
• Re-submission tracking

Audit findings surface from inadequate tracking.

Submission SLAs

Per MARADMIN 015/20MARADMIN 015/20, processing time targets.

• Routine submissions: 5 business days
• Time-sensitive submissions (NJP, separations): 2 business days
• Re-submissions after rejection: 5 business days from receipt
• Complex submissions: 10 business days with status updates to submitter

PAC tracks adherence and reports to MARFORRES or installation command.

Common Submission Errors at S-1 Level

These prevent successful submission.

1. S-1 forwards incomplete package. Missing supporting documents. PAC rejects, S-1 must rework.
2. Wrong document type identified. S-1 calls a Page 11 a fitness report. Reroute and reprocess.
3. Member SSN wrong on S-1 cover sheet. PAC must verify against MCTFS. Discrepancies cause delays.
4. Original requested but copy submitted. S-1 sends copy when original required. PAC rejects, requires original.
5. Routing skipped command. S-1 sends directly when document needed command endorsement. Reroute through command.

Quality Control Before Submission

S-1 should verify before forwarding to PAC.

• All metadata complete
• All signatures present
• Document quality acceptable
• Original or certified copy as required
• Routing through correct chain

This pre-flight check prevents PAC rejections and rework.

Related Roles

OMPF submission is everyone's problem in the chain.

• Marines submit life event documents and personal records updates.
• Leaders at S-1 process and route documents to PAC with proper metadata.
• Commanders sign documents flowing to OMPF and approve routing per MARADMIN 015/20MARADMIN 015/20.