Monthly FPC and Commander Standing Notification Events

What This Page Covers

This page is the steady-state monthly procedure for the FPC, the urinalysis approval, the DRRS-MC submission, and the Commander Standing Notification Events (CSNEs) driving out-of-cycle Readiness Boards.

For the deeper FPC framework (council role, attendance, SOP requirements, CIRRAS access rules), see the dedicated Force Preservation Council topic. This page is the recurring monthly procedure.

The Monthly FPC in Steady-State

The first FPC happens within 30 days of CoC. The 12 to 24 FPCs in the period afterward follow the same shape.

The standing checklist

A FPC where the new-join list is read without substantive discussion is procedural compliance with no effect. The MCO assumes substance.

Recurring outputs

• CIRRAS profile updates for every Marine reviewed
• Council minutes
• MfR if CO did not chair
• Updated action item tracker

Recurring inputs

• Marines briefed at last council for follow-up
• New joins since last council
• DoDI 6490.08 notifications received from providers since last council
• Open SAPR cases from CMG with FPC overlap
• Incidents since last council from Incident Playbook responses

Random Urinalysis Schedule

You approve the monthly random urinalysis schedule per MCO 5300.17 and DoDI 1010.01. The unit SACO or UPL drafts the schedule. You review and approve.

What approval covers

• Number of Marines tested
• Selection method (random per SACO procedures)
• Date and time blocks
• Special-population coverage if applicable

Documentation

Signed schedule retained per local SOP. Test results documented in CIRRAS profile for any flagged Marine for the next FPC.

Failure mode

The schedule is treated as a SACO-only document. CO signs without review. Selection methodology drifts. Inspector finding at IGMC FAC #31.

DRRS-MC Reporting

You submit the monthly DRRS-MC readiness report with required commander's remarks per MCO 3000.13B.

The report covers

• C-Level (overall capability)
• P-Level (personnel)
• S-Level (supply)
• R-Level (training)
• T-Level (equipment condition)

Commander's remarks

Required when:

• Any subjective override applied to a category
• Trend change from prior month
• Specific issues affecting readiness (open FLIPLs, supply discrepancies, training shortfalls)
• New CSNE triggered or resolved

Remarks are not optional when an override is applied. The MCO requires rationale.

Submission discipline

The DRRS-MC report is monthly. Submission window is set by higher headquarters. Late or missing submission is visible at HHQ level.

CIRRAS Audit

Each monthly FPC audits CIRRAS for currency. The Force Preservation page details the discipline. The monthly version of the audit is:

• Every elevated or high profile reviewed for staleness (no update in 90 days = stale)
• Every new join confirmed at ELEVATED for the 90-day window
• Every profile-level access user confirmed as uniformed (quarterly full audit)
• Every FPC decision from the council carried into the affected profile within 5 days

A monthly cadence where CIRRAS is touched only at the FPC misses real-time event-driven updates. Profiles are updated when events happen, not waited for the monthly review.

Commander Standing Notification Events (CSNEs)

Per the Commanders Readiness Handbook, CSNEs are predetermined readiness triggers requiring an out-of-cycle Readiness Board, regardless of the monthly cadence.

Typical CSNEs

What CSNE Triggers

When a CSNE fires, you convene an out-of-cycle Readiness Board within the timeline set in your published FPC SOP and Readiness Board SOP. The board reviews the trigger, documents impact, and adjusts DRRS-MC reporting as needed.

The next monthly DRRS-MC report annotates the CSNE in commander's remarks.

Documentation

Each CSNE generates:

• Memorandum for Record on the trigger
• Out-of-cycle Readiness Board minutes
• DRRS-MC annotation
• Adjustment to monthly FPC agenda if force-preservation implications

Monthly Pattern Worth Establishing

A workable cadence the first 90 days after assumption:

• Week 1: SACO drafts urinalysis schedule. CO reviews and approves.
• Week 2: DRRS-MC report drafted by S-3 with commander's remarks reviewed by CO. Submitted.
• Week 3: FPC convened. CMG runs same day or back-to-back where possible.
• Week 4: CIRRAS audit. Action items from FPC tracked to completion.

Adjust to fit local rhythm. The constraint is: each item happens monthly.

Common Failures

1. CO approves urinalysis schedule without review. SACO drift in methodology. Findings on IGMC FAC #31.
2. DRRS-MC commander remarks left blank. Subjective override applied without rationale. MCO 3000.13B violation.
3. FPC and CMG scheduled to conflict. Both monthly, both non-delegable. Coordinate the calendar.
4. CIRRAS profiles updated only at FPC. Misses event-driven updates between councils.
5. CSNE-triggered Readiness Board not convened. Trigger fired but cadence not adjusted. DRRS-MC report continues without addressing the trigger.
6. MfR retained less than 3 years. Filed and lost. MCO 1500.60A Para 4.b.(3)(l) violation.
7. DRRS-MC submission late. HHQ visibility on the deviation. Recurring lateness is documented.

Related Pages

• Battle Rhythm Overview (this topic, order 1) - the lookup index
• Monthly CMG (this topic, order 2) - the parallel non-delegable forum
• Quarterly CMR and Readiness (this topic, order 4) - the quarterly extension
• FPC Overview (Force Preservation topic) - council role and SOP requirements
• CIRRAS Commander Role (Force Preservation topic) - profile discipline
• New Join Elevated Risk (Force Preservation topic) - the 90-day rule