These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Quality Management System
- Features
- CAPA and root cause
CAPA and root cause
CAPA holds the corrective and preventive work that follows a serious nonconformance or audit finding. It ties the source issue to an owner, due date, Quality Manager and effectiveness decision. Tasks make the work visible by investigation, action, verification and effectiveness phase.
OverviewCAP as Due This Week×
Quality Management System · CAPA and root cause
New
CAP as Due This Week
CAP as
| CAPA number | Title | Due date | Status | Owner | |
|---|---|---|---|---|---|
| CPS-14317 | Open cps-943 | 12 Oct | Open | ||
| CPS-36905 | In progress cps-657 | 24 Oct | In progress | ||
| CPS-39842 | Implementation cps-431 | 07 Oct | Implementation | ||
| CPS-27502 | Verification cps-974 | 12 Oct | Verification | ||
| CPS-65763 | Effectiveness check cps-540 | 12 Oct | Effectiveness check |
6 of 6 records
Open cps-943CAP as · CPS-14317
OpenDue date12 Oct
What you can do
Investigate before closing the issue
A major or critical nonconformance creates a corrective CAPA once. The CAPA can also refer to an audit finding. When a CAPA moves into progress without an analysis, the start-work workflow creates a Five Whys root cause analysis, scaffold steps and an investigation task. Quality Engineer uses the problem statement, evidence and answers to identify the cause. Fishbone categories are available for a different analysis method.
The analysis moves through in progress, complete, reviewed and approved states. Approval is a human decision by the responsible quality authority. It is distinct from completing a task. CAPA tasks each carry a phase, assignee, due date, status and evidence. Operations Manager can execute assigned corrective work; Quality Manager retains closure and effectiveness authority.
A CAPA moves through implementation, verification and effectiveness check. The result records whether the action worked. If effectiveness is not effective, the reopen workflow sets the CAPA to Reopened and creates fresh corrective and verification tasks. It is guarded against firing again while already reopened. The original tasks and analysis remain part of the case history, so the team can explain the repeated effort.
How the work is organized
- Source and owner. The CAPA identifies the report or finding and names an accountable owner.
- Cause and tasks. Analysis explains why the issue happened; tasks show who changes what.
- Effectiveness decision. The result determines closure or renewed work.
What to agree during setup
Decide who facilitates root cause analysis, how evidence is attached and which Quality Manager approves its conclusion. Set due dates that leave time for implementation and verification. Agree what observation will show the action worked. The team should distinguish verification of task completion from effectiveness of the correction in later operations.
Check the handoff on an actual case
Use a major inspection defect that created a nonconformance report and CAPA. Move the CAPA to in progress and confirm that a single analysis and investigation task appear. Have Quality Engineer record a problem statement, cause chain and supporting evidence. Assign corrective work to Operations Manager and record its completion. Have Quality Manager review verification and enter not effective. Confirm that the CAPA reopens and that new corrective and verification tasks appear once. A later Effective result can support closure after the work is checked.
What your team sees
- Open CAP as — Active and reopened cases with owner, due date and status.
- Pending CAPA Tasks — Work awaiting an assignee’s action.
- Pending RCA Approvals — Reviewed analyses awaiting a quality decision.
Follow the work through
See nonconformance to CAPA and CAPA effectiveness.
What it keeps track of
Data model- CAP as
- Corrective and preventive action header routed from major or critical issues.
- CAPA tasks
- Investigation, corrective, preventive, verification and effectiveness tasks on a CAPA.
- Root cause analysis
- Root cause analysis exercise on a CAPA using Five Whys, Fishbone or other methods.
- Five whys steps
- One row per why in a five whys exercise.
- Fishbone categories
- One row per fishbone category cause cluster.
- Non conformance reports
- Non conformance report header driving containment, disposition and CAPA.
- Audit findings
- Issues found during audits; major findings route into CAP as.
Who uses it
Permissions- Quality Manager
- Owns approval, effectiveness and closure.
- Quality Engineer
- Facilitates analysis.
- Operations Manager
- Carries out assigned CAPA work.
Set up Quality Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.