CP-1 - Policy and Procedures

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): organization-level; mission/business process-level; system-level] contingency planning policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the contingency planning policy and the associated contingency planning controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the contingency planning policy and procedures; and c. Review and update the current contingency planning: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].


ID: CP-1
Enhancements: 

Space Segment Guidance

Contingency planning for spacecraft should reflect how authority and responsibilities shift across space, ground, launch, and partner segments, and how phase and mode (LEOP, nominal, maintenance, safe, disposal) change what is practical within short contact windows. Consider explicit triggers to declare a contingency (e.g., missed AOS, repeated command rejects, unexpected auth failures, off-nominal power/thermal), how FDIR actions interact with human procedures, and how crypto material is generated, escrowed, rotated, and revoked under stress. Policies that define cross-organization communications, evidence capture (audit/telemetry minima that persist in low-power states), and validation via simulators/flatsats tend to remain usable when timelines are measured in passes, not hours.