| Document Control | |
|---|---|
| Document Title | Corrective Action Request Form SOP |
| Document ID | HWB-QMS-FORM-005 |
| Version | 1.1 |
| Status | APPROVED |
| Author | George (Systems Architect) |
| Approved By | Humberto Dominguez, CEO |
| Date | 09/21/2026 |
Corrective Action Request Form
1.0 Purpose
The purpose of this form is to document and manage the resolution of nonconformities identified within the QMS, ensuring that root causes are addressed and preventive actions are implemented.
2.0 Scope
This form is used for all corrective actions resulting from audits, complaints, or process failures.
3.0 Prerequisites
- Identification of a nonconformity.
- Authorization to initiate a Corrective Action Request (CAR).
4.0 Procedure (Form Layout)
4.1 Identification of Nonconformity
- CAR Number: _____
- Date Identified: _____
- Source of Nonconformity:
- [ ] Internal Audit
- [ ] External Audit
- [ ] Client Complaint
- [ ] Management Review
- [ ] Process/Service Nonconformity
- [ ] Other: _____
- Description of Nonconformity: ______________ ______________
4.2 Immediate Correction (Containment Action)
- Action Taken: ________________
- Responsible Person: __ Completion Date: __
4.3 Root Cause Analysis
- Root Cause(s) Identified: __________ ______________
4.4 Corrective Action Plan (Preventive Action)
- Action(s) to Prevent Recurrence: _________ ______________
- Responsible Person: __ Target Completion Date: __
4.5 Implementation and Verification
- Verification of Effectiveness: _____________
- Verified By: __ Verification Date: __
4.6 Closure
- Final Approval (Sign/Date): _______
5.0 Verification
The effectiveness of the corrective action is verified by the QMS manager or designated auditor before closure.
6.0 Notes and Cautions
- Ensure the root cause analysis goes beyond the surface symptom (use "5 Whys" if necessary).
- Records must be retained according to section 7.5 of the Quality Manual.
7.0 Revision History
| Version | Date | Author | Description of Change |
|---|---|---|---|
| 1.0 | 2026-02-21 | Gemini | Initial Release |
| 1.1 | 2026-02-21 | Gemini | Updated to full HWB-QMS SOP standard format. |
| 2.0.0 | 09/21/2026 | George (Systems Architect) | Modernized and upgraded to post-May 1st, 2026 baseline. Standardized under HWB-QMS-1.0 v2.0 (Everyday Words) and approved by Humberto Dominguez, CEO. |
8.0 Document Conventions
- All fields marked with "_____" must be completed or marked N/A.
- Checkboxes "[ ]" should be marked with an "X" where applicable.