Redundancy Review - S-1 Procedural Page

Role and responsibility

The Command Reports Manager runs the redundancy review per SECNAVINST 5210.16SECNAVINST 5210.16 paragraph 7d-f before establishing any new information collection at the unit. The S-1 chief supports inventory cross-reference. The S-1 officer signs by direction on the redundancy review documentation. The staff section proposing the new collection provides the purpose, the audience, the questions or data elements, and the expected use. The HQMC AR (ARDB) program manager supports the review when the scope crosses unit boundaries or when the redundancy is unclear.

Source documents flow from the staff section's proposed information collection package, the unit Reports Inventory, the NAVMC form catalog, the DD form catalog, the SF form catalog, the higher headquarters reporting requirements, and the AR Reports Management SharePoint site resources. Redundancy review outputs include the documented review record, the determination of higher-level form availability, the routing to an existing form when applicable, the case file initiation per MCO 5214.2GMCO 5214.2G Chapter 2 paragraph 7a when no higher-level form exists, and the audit trail.

Per SECNAVINST 5210.16 paragraph 7d-f, local forms shall not be used if a higher-level form and report (NAVMC, DD, SF, etc.) already exists for the information being collected. The Command Reports Manager confirms no higher-level form exists before supporting a local collection. The redundancy review protects against duplicate collections and reduces administrative burden across the unit.

Trigger events

• Staff section proposes a new information collection (form, data call, survey, system).
• Existing local report under 3-year review surfaces possible redundancy.
• Higher headquarters publishes a new form covering content the unit collects locally.
• New MCO or SECNAVINST issuance affects existing local reports.
• IGMC Reports Management FA inspection covers the redundancy review.

Processing workflow

1. Receive proposed new information collection. The staff section forwards a package documenting the purpose, the audience, the questions or data elements, the expected use, and the frequency.
2. Search the existing Reports Inventory. Per MCO 5214.2GMCO 5214.2G Chapter 3 paragraph 1, search the unit inventory for an existing report covering the same purpose. Existing valid reports preclude a new collection.
3. Search NAVMC, DD, and SF form catalogs. Per SECNAVINST 5210.16SECNAVINST 5210.16 paragraph 7d-f, search the standard form catalogs for a matching form. Common sources include the Marine Corps NAVMC catalog, the DoD DD catalog, and the GSA Standard Form catalog.
4. Search higher headquarters reporting requirements. Pull MCOs, MARADMINs, and MARFOR directives for overlapping requirements. The HQMC AR (ARDB) Reports Inventory holds Marine Corps-wide records.
5. Coordinate with MARFOR or HQMC AR. Where the scope is unclear or the unit lacks visibility on higher-authority forms, coordinate with the MARFOR Reports Manager or the HQMC AR (ARDB) program sponsor.
6. Document the redundancy review. Per SECNAVINST 5210.16 paragraph 7d-f, the review captures the search performed, the sources checked, the result (higher-level form found or not), and the routing decision.
7. Route to existing form when one exists. If a higher-level form (NAVMC, DD, SF) covers the information being collected, the staff section routes to the existing form. The local proposal closes.
8. Support local establishment when no higher-level form exists. If no higher-level form covers the information, the Command Reports Manager supports the local report establishment per MCO 5214.2G Chapter 2 paragraph 7a.
9. Build the case file. Per MCO 5214.2G Chapter 2 paragraph 7a and Appendix A, the local report establishment runs through case file creation documenting the directive requiring the report, the date required, a sample, and the assigned RCS.
10. Brief the commander. The Command Reports Manager briefs the commander on the redundancy review outcome and the new collection (if supported).

Systems of record and forms

Systems

• Unit Reports Inventory. Per MCO 5214.2G Chapter 3 paragraph 1.
• NAVMC Forms Catalog. Marine Corps form repository.
• DD Forms Catalog. DoD form repository.
• Standard Form (SF) Catalog. GSA form repository.
• Marine Corps AR (ARDB) Reports Inventory. Marine Corps-wide inventory.
• AR Reports Management SharePoint Site. Holds review templates and resources.

Forms

• Redundancy Review Memorandum. Local format documenting the review per SECNAVINST 5210.16 paragraph 7d-f.
• Information Collection Proposal Package. Local format submitted by the staff section.
• Routing-to-Existing-Form Memorandum. Local format when a higher-level form exists.

Common pitfalls

• Redundancy review skipped before establishing a new collection. Per SECNAVINST 5210.16SECNAVINST 5210.16 paragraph 7d-f, the review runs before establishment.
• Search limited to the unit inventory. The review searches NAVMC, DD, SF, and higher headquarters reporting requirements.
• Local form created where a NAVMC or DD form exists. Per SECNAVINST 5210.16 paragraph 7d-f, the higher-level form applies when one exists for the information being collected.
• Redundancy review documentation absent. The review record supports the audit trail.
• Coordination with MARFOR or HQMC AR skipped on cross-unit scope. The HQMC AR program sponsor holds Marine Corps-wide visibility.
• Case file initiation skipped after the review supports local establishment. Per MCO 5214.2GMCO 5214.2G Chapter 2 paragraph 7a, the case file follows the redundancy review.
• 3-year review surfaces a higher-level form covering an existing local report without cancellation. Per Chapter 5 paragraph 1, the local report cancels when a higher-level form covers the same information.

Decision points

• Higher-level form scope. Per SECNAVINST 5210.16 paragraph 7d-f, the higher-level form's purpose drives the determination. Partial overlap supports a local extension rather than full replacement.
• Coordination versus unilateral decision. When the scope is clear, the Command Reports Manager decides at the unit level. When the scope crosses MARFOR or HQMC visibility, coordination flows.
• Modification of existing form versus new local form. Per Chapter 1 paragraph 3a, the Reports Management Program supports modification over new collection where the existing form covers the purpose with adjustment.
• Cancellation of existing local report. The 3-year review per Chapter 5 paragraph 1 surfaces local reports duplicated by higher-level forms.

Authority

This sub-page sits under SECNAVINST 5210.16SECNAVINST 5210.16 paragraph 7d-f (Redundancy Review) and MCO 5214.2GMCO 5214.2G Chapter 1 paragraph 3a (Reports Management Program Scope) and Chapter 2 paragraph 7a (Case File Establishment). 5 CFR Part 1320 and 44 U.S.C. Chapter 35 cover the federal Paperwork Reduction Act framework. The IGMC Reports Management FA Checklist item 0105 audits the redundancy review.

Related references

• SECNAVINST 5210.16 paragraph 7d-f. Redundancy review rule.
• MCO 5214.2G Chapter 1 paragraph 3a and Chapter 2 paragraph 7a. Program scope and case file.
• 5 CFR Part 1320 and 44 U.S.C. Chapter 35. Paperwork Reduction Act.
• IGMC Reports Management FA Checklist item 0105. Audit baseline.