Metrics and Accountability - S-1 Procedural Page

Role and responsibility

The SC builds the unit utilization metrics report per MCO 1320.11HMCO 1320.11H Enclosure (3) (Sample Sponsorship Program Utilization Metrics). The unit commanding officer reviews and signs the metrics report per paragraph 4.b.(6) (Unit Commanding Officers). The installation commander rolls up unit metrics for installation-level accountability per paragraph 4.b.(5). HQMC MF Director per paragraph 4.b.(2) aggregates strategic-level metrics. The S-1 chief reconciles unit metrics against MCTFS inbound data.

Source documents flow from MCTFS inbound assignments, sponsor assignment letters per Enclosure (7), welcome aboard letter issuance records, eAOC touchpoint records, inbound brief attendance logs, IR&R handoff records, and Page 11 documentation completion records. Metrics outputs include the unit utilization metrics report per Enclosure (3), the rolled-up installation metrics, the HQMC MF data submission, and the unit commander metrics brief.

Per MCO 1320.11H paragraph 4.b.(6), unit commanding officers maintain unit-level program execution. Per paragraph 4.b.(5), installation commanders oversee installation-level execution. Per paragraph 4.b.(2), MF Director oversees strategic-level program execution. Per Enclosure (3), the standard metrics cover coverage, timeliness, letter issuance, brief completion, and Page 11 documentation.

Trigger events

• Monthly metrics cycle opens.
• Quarterly commander brief due.
• HQMC MF data call.
• Installation-level metrics roll-up due to installation commander.
• IGMC Sponsorship Program FA inspection notice arrives.
• Annual sponsorship program audit cycle.

Processing workflow

1. Pull inbound and assignment data from MCTFS. The SC pulls the inbound roster, the sponsor assignment letters, the welcome aboard letters, the eAOC records, and the inbound brief attendance.
2. Compute coverage rate. Per MCO 1320.11HMCO 1320.11H Enclosure (3), coverage equals sponsors assigned divided by total inbound. Target is 100 percent coverage.
3. Compute timeliness metrics. Compute days from inbound notification to sponsor assignment, days from sponsor assignment to welcome aboard letter issuance, and days from arrival to inbound brief.
4. Compute welcome aboard letter issuance rate. Per Enclosures (2) and (4)-(6), compute the issuance rate by letter type (CONUS, Accompanied OCONUS, Unaccompanied OCONUS).
5. Compute inbound brief completion rate. Per paragraph 4.b.(9), compute the rate of inbound brief attendance.
6. Compute Page 11 documentation rate. Per MCO P1070.12K paragraph 4006, compute the rate of Page 11 entries documenting sponsorship completion.
7. Build the unit metrics report. Per Enclosure (3) as the template, build the unit-specific report.
8. Brief the commander. The S-1 officer briefs the commander on the metrics cycle, the coverage gaps, and the corrective actions.
9. Submit data to HQMC MF. Per paragraph 4.b.(2), the unit submits data per the MF data call cadence.
10. Apply records retention. Per paragraph 5.b and MCO 5210.11FMCO 5210.11F, retain the metrics file per the records schedule.

Systems of record and forms

Systems

• MCTFS. Source of inbound and assignment data.
• Unit Sponsorship Roster. Aggregates the metrics inputs.
• Marine Corps Total Force Information Management System (MCTIMS). Per Appendix A acronyms.
• HQMC MF Reporting Channel. Per paragraph 4.b.(2).
• Installation Commander Reporting Channel. Per paragraph 4.b.(5).

Forms

• Sponsorship Program Utilization Metrics Report. Per Enclosure (3).
• Unit Sponsorship Roster Export. Local format.
• Commander Brief Slide Deck. Local format.
• HQMC MF Data Submission. Per paragraph 4.b.(2).

Common pitfalls

• Coverage rate computed without sponsor assignment validation. Per MCO 1320.11HMCO 1320.11H Enclosure (3), the sponsor assignment counts only when the assignment letter is signed and delivered. Verbal designation does not count.
• Timeliness metrics not benchmarked against the inbound notification date. Pull the notification date from MCTFS. Without the baseline, timeliness analysis is invalid.
• Letter issuance rate aggregated across types. Per Enclosures (4)-(6), the type-specific rates surface gaps in accompanied OCONUS or unaccompanied OCONUS coverage.
• Inbound brief attendance not tied to Page 11. Per MCO P1070.12K paragraph 4006, the Page 11 documents the brief. A missed Page 11 invalidates the brief attendance metric.
• HQMC MF submission missed. Per paragraph 4.b.(2), the strategic-level visibility breaks. Submit per the cadence.

Decision points

• Metrics cycle cadence. Per MCO 1320.11HMCO 1320.11H Enclosure (3), the unit cycle is typically monthly with a quarterly commander brief. The installation cycle is quarterly. The HQMC MF cadence is annual or per data call.
• Coverage gap response. The unit identifies a coverage gap. Per paragraph 4.b.(6), the unit commanding officer routes corrective action to the SC.
• Metrics format. Per Enclosure (3) as the sample, units adapt the format to local context without dropping the core metrics.

Authority

This sub-page sits under MCO 1320.11HMCO 1320.11H paragraph 4.b.(2) (Marine and Family Programs Director), paragraph 4.b.(5) (Installation Commanders), paragraph 4.b.(6) (Unit Commanding Officers), and Enclosure (3) (Sample Sponsorship Program Utilization Metrics). Paragraph 5.b covers records management with MCO 5210.11FMCO 5210.11F and SECNAV M-5210.1SECNAV M-5210.1. 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-MPMN-2103.

Related references

• MCO 1320.11H paragraphs 4.b.(2), 4.b.(5), 4.b.(6). Authoritative metrics oversight rules.
• MCO 1320.11H Enclosure (3). Sample metrics format.
• MCO 5210.11F and SECNAV M-5210.1. Records retention.
• MCO 5000.14D MCAP enclosure 4. S-1 sponsorship responsibilities.
• NAVMC 3500.3E. T-R event 0102-MPMN-2103.