Readiness Support Program (RSP) - S-1 Procedural Page

Role and responsibility

The S-1 officer activates and runs the Readiness Support Program (RSP) per MCO 3040.4MCO 3040.4 Chapter 4 Section 7. The S-1 chief coordinates daily RSP touchpoints with survivors and supporting agencies. The CACO continues primary case support while RSP runs in parallel for specific readiness-adjacent needs. The commander assigns RSP responsibility per Section 7 paragraph 3.

Source documents flow from the casualty case file, the survivor's stated readiness needs, the commander's RSP assignment, and the support agency coordination. RSP actions land as touchpoint records, support service referrals, and readiness milestone documentation. Outputs include the RSP roster entry, the touchpoint log, the support agency referrals, and the commander brief on RSP posture.

Per MCO 3040.4MCO 3040.4 Chapter 4 Section 7 paragraph 2 (Readiness Support Program), RSP provides readiness-adjacent support distinct from CACO immediate assistance and LTAP long-term assistance. Per paragraph 3 (Responsibility), the commander assigns RSP responsibility at the unit level.

Trigger events

• Casualty case identifies survivor needs warranting RSP activation.
• Commander assigns RSP responsibility per Chapter 4 Section 7 paragraph 3.
• Readiness milestone (anniversary, deployment cycle, training event) triggers touchpoint.
• Survivor requests RSP support for specific readiness need.
• Coordination required between CACO, LTAP, and unit chain.
• New unit member joins requiring RSP awareness.
• RSP cycle review opens.

Processing workflow

1. Identify RSP-eligible case. Per MCO 3040.4MCO 3040.4 Chapter 4 Section 7 paragraph 1 (General), determine eligibility against the order rules.
2. Activate RSP support. Per MCO 3040.4MCO 3040.4 Chapter 4 Section 7 paragraph 2 (Readiness Support Program), activate the program for the case.
3. Assign RSP responsibility. Per MCO 3040.4MCO 3040.4 Chapter 4 Section 7 paragraph 3 (Responsibility), the commander assigns at the unit level.
4. Coordinate readiness support touchpoints. Schedule touchpoints aligned with milestone events.
5. Document RSP activity. Capture each touchpoint, referral, and support delivered in the casualty case file.
6. Track RSP support against needs. Maintain visibility on outstanding needs and progress.
7. Process RSP escalation. When the case exceeds local RSP scope, escalate per the order rules.
8. Coordinate with LTAP. Where the case has transitioned to LTAP, coordinate ongoing RSP touchpoints with the LTAP representative.
9. Brief command on RSP posture. The S-1 officer briefs the commander on RSP cases on a fixed cycle.
10. Update RSP roster. Refresh on personnel change, case transition, or survivor relocation.

Systems of record and forms

Systems

• Unit RSP roster. Local roster of RSP-eligible cases.
• DCIPS. National-level casualty case tracking integrating RSP.
• HQMC LTAP. Coordinates with RSP for long-term cases.
• Casualty case file. Local record of RSP activity.

Forms

• RSP Assignment Memorandum. Local format signed by the commander per Chapter 4 Section 7 paragraph 3.
• RSP Touchpoint Log. Local log of touchpoints and outcomes.
• RSP Referral Form. Documents referrals to support agencies.

Common pitfalls

• RSP not activated for eligible case. Per MCO 3040.4MCO 3040.4 Chapter 4 Section 7 paragraph 2, RSP applies to specific cases. The S-1 officer assesses eligibility.
• Responsibility assignment not formalized. Per Section 7 paragraph 3, the commander assigns. Capture the assignment in writing.
• Touchpoints handled informally without documentation. The RSP audit trail breaks. Document at every touchpoint.
• Coordination with LTAP broken. The case transitions to LTAP without RSP touchpoint coordination. Coordinate at transition.
• RSP roster stale. The roster lags personnel changes. Refresh on a fixed cycle.

Decision points

• RSP eligibility. Per MCO 3040.4MCO 3040.4 Chapter 4 Section 7 paragraph 1, eligibility runs per the order rules. The S-1 officer determines.
• Responsibility assignment level. Per Section 7 paragraph 3, the commander assigns. The commander selects the responsible billet.
• Escalation threshold. The case exceeds unit-level RSP scope. The S-1 officer routes to HQMC LTAP or other appropriate agency.

Authority

This sub-page sits under MCO 3040.4MCO 3040.4 Chapter 4 Section 7 (Readiness Support Program). Paragraph 1 covers general. Paragraph 2 covers RSP scope. Paragraph 3 covers responsibility. DoD-level policy at DODI 1300.18DODI 1300.18. S-1 responsibilities sit at MCO 5000.14DMCO 5000.14D MCAP enclosure 4. The processing workflow maps to NAVMC 3500.3E T-R event 0102-OPER-1002.

Related references

• MCO 3040.4 Chapter 4 Section 7. Authoritative RSP rules.
• DODI 1300.18 DoD Personnel Casualty Matters. DoD-level policy.
• MCO 5000.14D Marine Corps Administrative Procedures. S-1 RSP responsibilities.
• NAVMC 3500.3E Manpower and Administration T-R Manual. Event 0102-OPER-1002.