Inspections Lifecycle
CGIP Directive Setup
Stand up your Commanding General's Inspection Program. Publish a unit-level directive. Designate your CIG and TAIGs in writing. Hold subordinate units to a 36-month inspection cycle.
Command Actions
- Designate the Command Inspector General (CIG) in writing
- Publish the unit-level CGIP directive
- Designate Team Assistant Inspectors General (TAIGs) in writing
- Map every applicable CoRE and CoRE Plus Functional Area to a subordinate unit or to a covering relationship
- Build a 3-year fiscal year inspection plan and coordinate with IGMC
- Inspect every subordinate unit at least once every 36 months
Authority
10 USC 8020 and MCO 5040.6K, Enclosure 1, Chapter 5, Section 2 require every commander at the appropriate echelon to operate a Commanding General's Inspection Program. The CIG works directly for you. Your CGIP inspects subordinate commands on your behalf and reports back to you.
What you sign
- The unit-level CGIP directive itself. This directive names the CIG, names the TAIGs in writing, sets the inspection cadence, and identifies your applicable Functional Areas.
- The written designation of your CIG and each TAIG. Designations include qualifications, clearance eligibility for classified and sensitive information at the level required by their inspection duties, and training completion.
- A waiver request to IGMC, using the Appendix E template, when geographic distance, budget constraints, or a CIG capability gap blocks the 36-month subordinate inspection requirement.
Standing requirements
- Every subordinate unit you command receives a CGIP inspection at least once every 36 months.
- Your CGIP maintains a 3-year fiscal year inspection plan. Coordinate the plan with IGMC for deconfliction.
- Deploying subordinate units receive a CGIP inspection prior to deployment when scheduling permits.
- Your CIG inspects all CoRE Functional Areas. Your CIG inspects CoRE Plus and Non-CoRE Functional Areas at your direction.
Exception path
Waivers route to IGMC for the 36-month inspection cycle when conditions block compliance. Use the Appendix E template in MCO 5040.6K. Document the cause, the workaround, and the date the unit returns to the standard cycle. Geographic distance, budget cuts, and an unbroken CIG capability gap are the recognized waiver grounds.
Same topic, other roles
References
- MCO 5040.6K
- 10 USC 8020
- SECNAVINST 5040.3B
Related Pages
- Commander
Inspections Lifecycle Overview
same topic - MCO 5040.6K - 3 shared references
- Commander
Corrective Action Report Submission
same topic - MCO 5040.6K
- Commander
Final Inspection Report Receipt
same topic - MCO 5040.6K
- Commander
Inspection Records Retention
same topic - MCO 5040.6K
- Admin
CGIP Inspection Staff Support
MCO 5040.6K Ch Enclosure 1, Chapter 5