Global Force Management - S-1 Procedural Page

Role and responsibility

The unit GFM coordinator runs GFM tasking at the unit per MCO 3120.12AMCO 3120.12A. The S-1 officer supports personnel inputs to GFM feasibility and Force Synchronization. The S-1 chief reconciles personnel readiness with the GFM tasking. MARFOR commands (MARFORCOM, MARFORPAC, MARFORRES, and others) coordinate GFM through HQMC PP&O. HQMC PP&O coordinates with the Joint Staff and OSD on GFMIG and GFMAP.

Source documents flow from the GFM tasking message, the DRRS readiness state per MCO 3000.13BMCO 3000.13B, the unit deployment posture per MCO 3000.18BMCO 3000.18B, the concurrent tasking record, the GFMAP cycle inputs, the Force Synchronization data, and the MARFOR coordination record. Outputs include the sourcing feasibility recommendation, the Force Synchronization conflict identification, the GFMAP input, the approved tasking execution record, the concurrent tasking tracking, and the force return coordination.

Per MCO 3120.12A, GFM coordinates force sourcing across the Joint Force. The SECDEF Forces For directive identifies the standing force allocation. The GFMAP provides the annual force allocation plan. Force Synchronization addresses conflicts when multiple tasking competes for the same forces.

Trigger events

• GFM tasking message arrives at the unit.
• GFMAP cycle opens for unit inputs.
• Concurrent tasking identified for the same forces.
• Joint Staff sourcing inquiry routes through MARFOR.
• Operational planning team (OPT) review of force allocation.
• Force return per GFMAP timing.
• SECDEF Forces For directive change.

Processing workflow

1. Receive GFM tasking. The unit GFM coordinator receives from MARFOR or HQMC PP&O per MCO 3120.12AMCO 3120.12A.
2. Validate the tasking against unit DRRS readiness. Per MCO 3000.13BMCO 3000.13B, the DRRS state supports the feasibility assessment.
3. Coordinate with the MAGTF and the operational chain. The MAGTF commander assesses the tasking within MAGTF capacity.
4. Submit sourcing feasibility recommendation. The unit submits the recommendation through MARFOR to HQMC PP&O.
5. Identify Force Synchronization conflicts. Per MCO 3120.12A, Force Synchronization addresses conflicts when multiple tasking competes for the same forces. The S-1 surfaces personnel conflicts.
6. Support GFMAP input cycle. Per MCO 3120.12A, the GFMAP cycle drives annual force allocation. The unit submits inputs through MARFOR.
7. Coordinate force allocation with MARFOR. MARFOR coordinates the final allocation. The unit executes the approved tasking.
8. Execute the approved tasking through the deployment cycle. Per MCO 3000.18BMCO 3000.18B, the FDP&E Manual drives the execution.
9. Track concurrent taskings. The S-1 maintains the unit tasking record across operational, exercise, and individual augment commitments.
10. Coordinate force return per GFMAP timing. The redeployment timing aligns with the GFMAP cycle.

Systems of record and forms

Systems

• Global Force Management Allocation Plan (GFMAP). Per MCO 3120.12A.
• MARFOR command coordination systems. Per MCO 3000.18B and 3120.12A.
• DRRS. Per MCO 3000.13B for readiness feedback.
• Joint Staff GFM coordination tools. Per CJCS and DoD GFMIG.

Forms

• GFM Tasking Order. Per MCO 3120.12A.
• Sourcing Feasibility Memorandum. Per MARFOR routing.
• Force Synchronization Conflict Notification. Per MCO 3120.12A.
• GFMAP Input Worksheet. Per the annual cycle.
• Force Return Coordination Memorandum. Per redeployment.

Common pitfalls

• GFM tasking accepted without DRRS readiness validation. Per MCO 3000.13BMCO 3000.13B, the readiness state supports feasibility.
• Force Synchronization conflicts not surfaced. Per MCO 3120.12AMCO 3120.12A, concurrent tasking surfaces through Force Synchronization.
• GFMAP inputs late. The annual cycle drives the input timing.
• Concurrent tasking tracking lagged. The S-1 maintains current posture.
• Force return not coordinated with GFMAP. The redeployment aligns with the cycle.

Decision points

• Sourcing feasibility recommendation. Per MCO 3120.12A, the unit's recommendation reflects DRRS state and operational tempo.
• Force Synchronization priority. Per MCO 3120.12A, the higher-priority tasking prevails when conflicts arise.
• GFMAP scope. Annual allocation versus ad-hoc tasking drives the GFMAP input scope.
• Force return timing. Per GFMAP and MCO 3000.18B, the redeployment timing aligns with the cycle.

Authority

This sub-page sits under MCO 3120.12AMCO 3120.12A Marine Corps Global Force Management and Force Synchronization. MCO 3000.18BMCO 3000.18B covers FDP&E. MCO 3000.13BMCO 3000.13B covers readiness reporting. DoD GFMIG and GFMAP set DoD-level frameworks. Joint Staff GFM procedures support the coordination.

Related references

• MCO 3120.12A. GFM and Force Synchronization.
• MCO 3000.18B. FDP&E Manual.
• MCO 3000.13B. Readiness Reporting.
• DoD GFMIG and GFMAP. DoD frameworks.
• NAVMC 3500.3E. T-R event 0170-OPER-2003.