> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Use the Management of Change Process

> Submit change requests, complete the MOC screening checklist, assess risk impacts, and track changes through approval and post-review.

By following this guide, you will submit change requests, complete the MOC screening checklist, assess risk impacts, and track changes through approval and post-implementation review.

<Info>
  **Who should read this:** Anyone proposing a change to operations,
  equipment, procedures, or organizational structure. Safety managers
  review and approve MOC requests. Admins configure MOC workflows.

  **Prerequisites:** Any workspace member can submit a change request.
  Safety manager or admin role is required to review, approve, or
  reject requests.
</Info>

## MOC Workflow Overview

| Status          | Description                                                                |
| --------------- | -------------------------------------------------------------------------- |
| Draft           | Change request created. Basic details captured.                            |
| Screening       | Change is being evaluated against the 8-question screening checklist.      |
| Risk Assessment | Change has been screened and requires a formal risk assessment.            |
| Approval        | Risk assessment complete. Change awaiting management approval.             |
| Implementation  | Change approved and being implemented.                                     |
| Post-Review     | Change has been implemented. Effectiveness and safety impact under review. |
| Closed          | MOC process complete. Record is immutable.                                 |

## Submit a Change Request

<Steps>
  ### Step 1: Open the MOC form

  In the Safety sidebar, navigate to **Management of Change** and create a new change request. You can also use `Cmd+K` and select "New Change Request."

  ### Step 2: Select the change category

  Choose the category that best describes the change (Operational, Organizational, Technical, Regulatory, or Process). For the full category reference, see [MOC Workflow](/en/reference/moc-workflow).

  ### Step 3: Enter the change title and description

  Use a clear title that summarizes the proposed change. Include what is changing and why, the current vs. proposed state, affected systems and personnel, and expected timeline.

  ### Step 4: Classify the timeline

  Select **Standard** or **Emergency**. If you need to select Emergency, only do so when delay would create a greater safety risk than proceeding.

  <Warning>
    Emergency changes bypass the standard screening timeline but still require a complete risk
    assessment and post-implementation review.
  </Warning>

  ### Step 5: Submit the request

  Submit the change request. It moves to **Submitted** status and is queued for safety manager review.
</Steps>

## Complete the MOC Screening

<Steps>
  ### Step 1: Open the screening checklist

  Open the submitted change request and navigate to the **Screening** tab.

  ### Step 2: Answer each screening question

  The checklist includes 8 questions evaluating whether the change could affect operations, maintenance, personnel, equipment, compliance, hazards, risk controls, or external interfaces. For the full screening checklist, see [MOC Workflow](/en/reference/moc-workflow).

  ### Step 3: Determine the screening result

  If any question is answered **Yes**, the change requires a full risk assessment. If all answers are **No**, the change may proceed with documentation only.

  <Tip>
    When in doubt, answer Yes. It is better to perform an unnecessary risk assessment than to miss a
    hazard introduced by a change.
  </Tip>
</Steps>

## Perform the Risk Assessment

If the screening determines a risk assessment is needed:

<Steps>
  ### Step 1: Identify hazards

  Document each hazard that could result from implementing the proposed change.

  ### Step 2: Assess risk

  For each identified hazard, rate severity and likelihood using the ICAO 5x5 risk matrix. See [Conduct a Risk Assessment](/en/how-to/sms/conduct-risk-assessment) for detailed guidance.

  ### Step 3: Define risk controls

  For hazards in the yellow (ALARP) or red (Unacceptable) zone, define controls to reduce the risk before the change is implemented.

  ### Step 4: Assess residual risk

  Rate the expected risk level after controls are in place. Document any residual risk that will be accepted.
</Steps>

## Approve or Reject the Change

Review the complete MOC package -- change description, screening results, risk assessment, and residual risk levels -- then make your decision:

* If you want to authorize the change, approve it with any conditions or monitoring requirements.
* If you want to reject, document the reasons and return to the requestor.
* If you need more information, request changes before making a decision.

## Conduct Post-Review (PIR)

After an approved change has been implemented:

<Steps>
  ### Step 1: Schedule the PIR

  Set a review date -- typically 30 to 90 days after implementation.

  ### Step 2: Evaluate effectiveness

  Assess whether the change was implemented as planned, risk controls are functioning, no new hazards have emerged, and safety performance has not degraded.

  ### Step 3: Document the PIR findings

  Record the review results and any additional actions needed.

  ### Step 4: Close the MOC

  Once the PIR is satisfactory, close the MOC record. The complete package is retained per 14 CFR 5.97.
</Steps>

## Related

<CardGroup cols={2}>
  <Card title="MOC Workflow" href="/reference/moc-workflow">
    Complete reference for MOC statuses, screening questions, and approval rules.
  </Card>

  <Card title="Conduct a Risk Assessment" href="/how-to/sms/conduct-risk-assessment">
    Detailed guidance on the 5x5 risk matrix used during MOC risk assessment.
  </Card>

  <Card title="Create a CPA" href="/how-to/sms/create-cpa">
    Creating corrective actions from MOC findings.
  </Card>

  <Card title="Track Compliance" href="/how-to/sms/track-compliance">
    How MOC records contribute to Part 5 compliance.
  </Card>
</CardGroup>