Establishing IPAC Connectivity and Working Relationships

Why This Is Your First Responsibility

Per MCO 5000.14DMCO 5000.14D Enclosure 3 paragraph a, the first listed commander responsibility for personnel administration is establishing command procedures for receiving IPAC support and ensuring connectivity with the IPAC. The MCAP states it directly: "For administration to function efficiently, free and open exchange of information must exist between the unit and the IPAC."

This is not delegated to S-1. You as commander own the relationship. S-1 executes within the procedures you establish.

Why the Relationship Matters

The 1999 consolidation moved most personnel administrative work from operating force units to IPACs in the supporting establishment. Per MCO 5000.14DMCO 5000.14D, this reduced commanders' direct access to personnel information and processes. The IPAC supports you by relieving the burden of higher-level admin functions, but only if the relationship works.

A broken IPAC relationship creates these problems.

• Pay errors take weeks to fix instead of days
• NAVMC 10922NAVMC 10922 packages get rejected without clear reason
• Separation packages stall at PAC routing
• Audit findings pile up at the unit level
• IG complaints against the unit increase
• Marines lose trust in the chain

A working IPAC relationship prevents all of this.

Identifying Your Supporting IPAC

If you do not know which IPAC supports your unit, find out today.

• Geographic alignment is typical (your IPAC is on or near your base).
• Some units have non-standard IPAC alignment (deployed units, training commands, recruiting).
• Marine Corps Bases each have an IPAC. Some have multiple branches.
• Reserve units are supported by I&I staff, not IPACs in the same way.

Your S-1 should know. If they do not, that is your first finding.

Required Points of Contact

Get these names, phone numbers, and emails on file.

Maintain this contact list at S-1. Update quarterly or when IPAC personnel rotate.

Establishing Command Procedures

Per MCO 5000.14DMCO 5000.14D, you establish the procedures. Document them in writing as a unit SOP. Cover these areas.

Routing of Standard Actions

Define which actions route directly from S-1 to PAC vs which require commander review first.

• Routine pay corrections: S-1 routes directly to PAC
• BAH changes from NAVMC 10922NAVMC 10922: S-1 routes directly
• NJP results: Commander signs first, then S-1 to PAC
• Administrative separations: Commander recommendation first, then to PAC
• Awards: Approval routing per command policy, then to PAC

Liaison Personnel

Designate specific Marines who interface with IPAC.

• S-1 Officer or Adjutant (primary)
• Admin Chief (daily working contact)
• Casualty Assistance Officer (when applicable)
• SJA (legal coordination)

Communication Cadence

Establish regular touchpoints.

• Weekly: Admin Chief calls IPAC counterpart on open issues
• Monthly: S-1 Officer meets with IPAC OIC on metrics and trends
• Quarterly: Commander touches base with IPAC OIC on relationship health
• Annually: Joint review of audit findings and process improvements

Escalation Paths

When something stalls, define the path.

1. S-1 admin clerk to PAC counterpart (working level)
2. Admin Chief to PAC Section Head (NCOIC level)
3. S-1 Officer to PAC Personnel Officer (0170)
4. Commander to IPAC OIC
5. Commander up the chain to MCAAT (ask_mcaat@usmc.mil) for policy disputes

Tracking IPAC Performance

Hold IPAC accountable through metrics. Track these monthly.

Share these monthly with your IPAC OIC. Trends going wrong is your early warning.

What You Owe IPAC

The relationship is two-way. Ensure your unit delivers these to IPAC.

• Complete packages with all supporting documents (no incomplete submissions)
• Accurate UMSR submissions via MOL (commander responsibility per MCO 5000.14DMCO 5000.14D)
• Timely Pro/Con marks and counseling Page 11s
• Clear unit diary submissions for promotions, transfers, awards
• LIMDU documents forwarded immediately
• PEB tracking documentation
• Meal card management
• Fitness reports processed on time
• Command payroll review monthly with discrepancies reported

A unit that delivers clean inputs gets faster IPAC service. A unit that submits incomplete packages gets pushed to the bottom of the queue.

Common Relationship Failures

These break the IPAC relationship.

1. Going around IPAC to HQMC or DFAS. This burns relationships. Use IPAC first.
2. Repeated incomplete submissions. PAC clerks remember units that send junk packages.
3. Public criticism of IPAC at command meetings. Address performance privately with IPAC OIC.
4. Skipping the chain on escalations. Going direct to MCAAT without trying IPAC first.
5. No commander engagement. Letting S-1 handle everything without commander interface.

When the Relationship Breaks

If IPAC service fails repeatedly.

1. Document specific incidents with dates, times, and actions.
2. Schedule a face-to-face with IPAC OIC. Bring documentation.
3. Develop a corrective action plan jointly.
4. If unresolved, escalate up your chain to your superior commander.
5. As a last resort, submit through your chain to MCAAT for policy review.

Do not let it fester. Marines pay the price.

Decision Framework

For any IPAC issue, ask these questions.

• Has my S-1 attempted resolution at the working level first?
• Is this a one-time issue or a pattern?
• Does the issue require commander engagement, or can S-1 resolve?
• Have I documented the issue for the IPAC OIC discussion?
• What outcome do I want from the engagement?

Engage personally when the pattern persists, when Marines are being harmed, or when policy clarity is needed.

Related Roles

The IPAC relationship affects everyone in the unit.

• Marines experience the IPAC relationship through their own pay and records actions.
• Leaders route their Marines' concerns through S-1 to IPAC.
• Admin at S-1 lives the relationship daily and is your eyes on IPAC performance.