> ## 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.
# Track Your First CPA
> Walk through the full lifecycle of a Corrective and Preventive Action -- from creation through assignment, progress tracking, verification, and closure.
In this tutorial, you will create a Corrective and Preventive Action (CPA), assign it to an owner, track its progress through the lifecycle, and close it after verification.
By the end of this tutorial, you will have a CPA that has moved through its full lifecycle -- from Open to Closed -- with evidence attached and effectiveness verified.
**Who should do this tutorial?** Safety Managers who create and oversee CPAs, and anyone who may
be assigned as a CPA owner or verifier. You will need Safety Manager or Admin permissions to
create CPAs. Any workspace member can be assigned as an owner.
## Before you start
Make sure you have:
* An active PlaneConnection account with **Safety Manager** or **Admin** role
* At least one completed investigation with recommendations (see [Run Your First Investigation](/en/tutorials/first-investigation)), or an identified hazard that needs corrective action
* Familiarity with the SMS module navigation (see the [Quickstart](/en/tutorials/quickstart))
A **Corrective** action fixes an existing problem. A **Preventive** action prevents a potential
one. See [CPA Lifecycle](/en/reference/cpa-lifecycle) for full definitions and business rules.
## Creating and tracking the CPA
### Create a CPA from an investigation
The most common path is to create a CPA directly from an investigation recommendation.
1. In the Safety module sidebar, click **Investigations**.
2. Open a completed investigation that has recommendations.
3. In the **Recommendations** section, find the recommendation you want to act on.
4. Click the **Create CPA** button next to the recommendation.
PlaneConnection creates a new CPA linked to the investigation and pre-fills the title and description from the recommendation. You are taken to the CPA detail page.
The CPA receives an auto-generated number (e.g., CPA-2026-00018) and starts with a status of **Open**.
You can also create a standalone CPA by navigating to **CPAs** in the sidebar and clicking **New
CPA**. This is useful for actions arising from safety meetings, audit findings, or management of
change reviews that are not tied to a specific investigation.
### Set the type, priority, and due date
On the CPA detail page, configure the key fields:
1. **Type:** Select **Corrective** or **Preventive** based on whether you are fixing an existing problem or preventing a future one.
2. **Priority:** Set the **Priority** based on urgency. PlaneConnection auto-calculates a due date from the priority level. See [CPA Lifecycle](/en/reference/cpa-lifecycle) for priority definitions and default response times.
3. **Due date:** You can adjust the auto-calculated due date if needed, but document the reason if you extend beyond the default.
### Assign an owner
Every CPA needs an owner -- the person responsible for completing the action.
1. Click the **Owner** field and select a workspace member from the list.
2. The owner receives a notification with the CPA details, priority, and due date.
3. Optionally add a **description** with implementation guidance or context the owner may need.
Choose an owner who has the authority and resources to complete the action. For procedural
changes, this is often a department lead. For training actions, this may be the training manager.
For equipment changes, this may be the maintenance director.
### Confirm the CPA is Open
Once the type, priority, owner, and due date are set, the CPA is in **Open** status. This signals that the CPA is approved and ready for work. The owner is notified that the CPA is now active.
The CPA lifecycle follows this sequence:
```
Open --> In Progress --> Implemented --> Verification --> Closed
```
### Track progress
As the owner works on the CPA, they update its status and add progress notes.
1. The owner changes status to **In Progress** when work begins.
2. Progress notes can be added in the **Activity** section -- for example, "Updated SOP draft submitted to safety manager for review" or "Ordered replacement parts, expected delivery Feb 25."
3. PlaneConnection sends reminder notifications as the due date approaches:
* 7 days before due date
* 3 days before due date
* On the due date
* Overdue notifications daily
Overdue CPAs appear in red on the CPA dashboard and in the safety manager's notification feed.
Consistently overdue CPAs can indicate resource issues or unrealistic timelines -- address them
proactively rather than letting them accumulate.
### Attach evidence
Before submitting for verification, the owner must attach evidence demonstrating that the action was completed.
1. In the **Evidence** section of the CPA detail page, click **Upload Evidence**.
2. Attach relevant files such as:
* Updated procedure documents or SOPs
* Training completion records
* Maintenance work order confirmations
* Photos of physical changes
* Meeting minutes where changes were approved
3. Add a note describing what each piece of evidence demonstrates.
Evidence is stored in your organization's secure file storage and becomes part of the permanent SMS record.
### Submit for verification
Once the action is complete and evidence is attached, the owner submits the CPA for verification.
1. Change the status to **Implemented**.
2. Select a **Verifier** from the list of workspace members.
The verifier must be a different person than the CPA owner. This separation of duties is required
by 14 CFR 5.73 -- the person who implemented the action cannot verify its own effectiveness.{" "}
PlaneConnection enforces this rule and will not allow the owner to be selected as verifier.
### Verify effectiveness
The verifier reviews the CPA to determine whether the action actually resolved the root cause or mitigated the risk.
1. The verifier receives a notification and opens the CPA detail page.
2. Review the following:
* **Original recommendation:** Does the completed action align with what was recommended?
* **Evidence:** Is the evidence sufficient to demonstrate completion?
* **Effectiveness:** Has the action resolved the underlying issue? Check for any recurrence since implementation.
3. The verifier records their assessment in the **Verification** section:
* **Verification notes:** Document what was reviewed and the conclusion.
* **Decision:** Select **Verified** (effective) or **Rejected** (not effective or incomplete).
If rejected, the CPA returns to **In Progress** with the verifier's notes explaining what needs to be addressed. The owner must take additional action and resubmit.
If verified, the status changes to **Verification** and the CPA is ready for closure.
### Close the CPA
After verification, a Safety Manager closes the CPA.
1. Review the verified CPA one final time.
2. Change the status to **Closed**.
3. The CPA becomes **read-only** -- no further edits are permitted.
Closed CPAs cannot be reopened or modified. Per 14 CFR 5.97, CPA records must be maintained as
long as the associated risk control remains relevant. If the same issue recurs, create a new CPA
rather than modifying the closed one.
## What happens next
After a CPA is closed, it becomes part of your organization's safety performance record:
1. **Dashboard metrics update.** The CPA dashboard reflects the closure, and on-time completion rates are recalculated.
2. **Linked records update.** The originating investigation and any linked risk assessments reflect the completed action.
3. **Trend analysis.** CPA data feeds into your Safety Performance Indicators -- metrics like average time to close, overdue rates, and recurrence rates help you assess SMS effectiveness.
4. **Audit evidence.** Closed CPAs with attached evidence serve as compliance documentation during FAA surveillance.
## Next steps
Detailed reference for all CPA fields, statuses, and workflows.
Full reference for CPA statuses, transitions, and business rules.
See how CPA metrics feed into your safety performance indicators.
Learn how closed CPAs serve as evidence during FAA audits.