The Corrective Action Request Process


Corrective Action Request (CAR) Process.
A change request may be inquired by an employee as a result of customer finding, internal finding or supplier issues. Corrective Action Requests are normally determined during quality assurance auditing where Quality assurance project manager decides the criteria for reviewing and communicating non conformance and when the corrective action is required, (Romero & Putz, 2018). Request for corrective action from the employee can stem from non-conformance reported by the client, or from employee's direct observation when a significant problem threatens the production schedule. The significance of CAR is to inspect the problem which already occurred and requires root cause analysis and resolution to prevent its recurrence.

The process starts with the supplier forming a cross-functional root cause and corrective action team where the team size vary based on the nonconformance activity being performed relative to root cause corrective action process.

The process of corrective action request is as follows:

  • Initiation of the corrective action request: The CAR can be generated as a result of internal audit process or management review process where the details regarding the issue are recorded on the corrective /preventive action request form. The quality assurance project manager determines time frame requirements related to the steps of the process relative to the severity of encountered non-conformance.
  • Investigating a request for corrective action: Causes of conformance are determined by the investigator who designs the implementation plan to resolve the same issue. The investigator is accountable for finding the root cause and determining the short term containment and required corrective actions.
  • Implementing corrective actions: An individual is assigned to implement the required actions. The person is responsible for overseeing the implementation of actions to be taken and the summary of actions is documented in CAR form.
  • Verifying a corrective action: The quality assurance manager assigns a schedule to follow up where the responsible person records the results of actions taken to determine their effectiveness. In case the actions become ineffective, the new corrective action request may be issued, otherwise, the request is forwarded to a quality assurance project manager for closure.
  • Closing corrective action requests and periodic review of data: The CAR is closed upon final review. The records of previously issued CARs are periodically reviewed in order to summarize any trends and implement further action as required.
Guidelines and Instructions for Documenting Nonconformity for Corrective Action Requests (CAR).
  • Clearly stating the weakness and problem: The adverse event is clearly defined and proper assessment of events carried out to understand conditions that lead to a problem. The mitigation procedures to be applied are then stated.
  • List the accountable individuals for the results of corrective actions: The responsible individuals should be listed, trained on how to carry out their expected duties, and how to report the issues.
  • Create simple solutions to address the root cause: Define the regulatory requirements and resources which can be used to reduce or eliminate the root causes.
  • Set achievable deadlines: Determine a reasonable time frame for implementing the corrective actions on the system.

Each CAR should be understandable by the client and management staff and should contain sufficient and concise information to verify the nonconformity identified during the edit. When the client’s procedural requirements are not satisfied, those requirements should be identified and recorded.

In conclusion, the appropriate Corrective Action Request should be conducted in a systematic approach in order to identify the real root cause essential for the improvement of the quality management system. Effective containment and corrective actions corresponding to the identified root cause should be provided.


  • Ershadi, M. J., Aiasi, R., & Kazemi, S. (2018). Root cause analysis in quality problem solving of research information systems: a case study. International Journal of Productivity and Quality Management, 24(2), 284-299.
  • Sawant, M. A., Yadav, O. P., & Rokke, C. (2018). A practical quality management system implementation framework for small-sized companies. International Journal of Intelligent Enterprise, 5(1-2), 173-193.
  • Romero, C., & Putz, F. E. (2018). Analysis of corrective action requests from Forest Stewardship Council audits of natural forest management in Indonesia. Forest Policy and Economics, 96, 28-37.


What is Downtime?

Downtime is another way of saying a system is not available to the users. It is also referred to as an outage. While downtime can be planned months in advance, it is typically not and is often a surprise.


5 Reasons Multitasking is Bad for IT Productivity

When it comes to IT operations, multitasking seems to be a prerequisite. Quite often it's even written into the job posting. However, research is revealing that multitasking may do more damage than good.

It's the Process, Stupid!

The greatest invention in the last 200 years isn't a product, but rather the scientific method, the process which has been used to create millions of products. Today, when change is exponential, a focus on process over products is even more important.



Downtime is a term used to describe when a service is unavailable to its intended recipients. While downtime can be planned months in advance, it is typically not and is often a surprise.

Most downtime events are unplanned and caused by a failure or are triggered on short notice and occur as a result of an attempt to fix a service that is not performing at its optimal level.

Signs & Symptoms
Downtime is the number one cause of financial harm yet most IT leaders don't understand the signs and symptoms of an environment that experiences too much unplanned downtime.

Sure it's easy to surmise that the systems are offline more than they should be especially when management is enraged but there are legitimate signs and symptoms which will allow you to reduce the frequency and impact of unplanned outages.

  • Unauthorized Changes
  • High amounts of Unplanned Work
  • Low Throughput of Effective Change
  • Server to Administrator Rations < 100:1
  • Lack of Indicator Measurements
  • SLA Commitment Breaches
Related Conditions

Low Throughput of Effective Change

More Videos You May Like
Downtime Video Image.png

Calculate Your Downtime Today!

Top 3 Ways To Prevent Downtime

1. Implement Preventive Maintenance Schedules

2. Execute Pre Business System Checks

3. Implement Measurements & Indicators

Implement Preventive Maintenance Schedules

Take care of your IT assets and they will take care of you. Implement a consistent, high quality preventive maintenance schedule. Let Allari do the chore based tasks while you focus on the important stuff!