> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/manual/capa/adding-a-capa.md).
# Adding a CAPA
Add CAPA form
**CAPA Name**
The individual name given for the CAPA.
**Status**
The term status refers to the current condition or state of a Corrective and Preventive Actions (CAPA).
* **Open -** This status indicates that a CAPA has been identified and is under investigation. At this stage, further investigation or analysis may be required to determine the appropriate action to take.
* **Closed -** This status indicates that the CAPA has been implemented and the corrective or preventive action has been completed. At this stage, the results of the action taken may be evaluated to determine if the issue has been resolved satisfactorily.
**Rating**
* **Minor -** This CAPA is seen as a minor improvement to be made to the organisation.
* **Major -** This CAPA is seen as a major improvement or correction that must be made by the organisation.
**CAPA Owner**
The CAPA Owner section refers to the person responsible for implementing and managing the corrective and preventive actions identified as part of the ISMS.
**Identified By**
The person responsible for identifying this CAPA.
**Asset Affected**
Select an asset from the asset list which is most effected by the CAPA.
**CAPA Description**
The description section offers a detailed and complete summary of the CAPA, providing the reader with a clear understanding of what it entails.
**Date Identified**
The specific date on which the CAPA was raised.
**Date Completed**
The specific date on which the CAPA was actioned. If ongoing then leave section blank.
**What Investigation was carried out?**
Provide a detailed explanation of what investigation was carried out.
**Root Cause Analysis**
A root cause analysis (RCA) for a Corrective and Preventive Action (CAPA) in an Information Security Management System (ISMS) is a process of identifying the underlying cause(s) of an issue or problem in the organisation's security controls, processes, or procedures.
The purpose of conducting an RCA is to determine the source of the problem and prevent its recurrence in the future. The RCA process involves identifying the problem, analysing the problem's symptoms, identifying the contributing factors, and identifying the root cause(s) of the issue.
**Corrective Action**
Describe what actions have been identified as needed and how they have been put in place.
**Have you verified that the actions are effective?**
If the corrective actions have been verified to be effective in solving the problem.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://manual.harpe.io/start/manual/capa/adding-a-capa.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
