Corrective Actions

A Corrective Action belongs to a Nonconformance and has a named owner. The record captures root cause, the planned action, due date, completion date and its progress through planned, approved, implementing, effectiveness review and closed states. The quality manager can read the action beside the inspection issue that prompted it, preserving the reason for the work.

The correction workflow starts from the owner’s implementation submission. It retains the root cause and approved action, moves the work into effectiveness review, tests whether the action worked and closes both the action and linked issue only when every related action is accepted. Effectiveness is a separate decision from reporting that implementation is finished.

• Assign ownership. Quality Manager links the action to the nonconformance and names a Corrective Action Owner with a due date.
• Approve the action. Quality Manager reviews the proposed remedy before the owner implements it.
• Verify the effect. Corrective Action Owner submits implementation details, and Quality Manager checks the result before accepting closure.

My Corrective Actions gives an owner a focused list of assigned work. Effectiveness Review gives the manager a queue of actions awaiting the outcome decision. The owner and manager should read the linked nonconformance before changing the action, especially when several actions address one issue.

Agree what constitutes a useful root-cause statement and how the action should refer to that cause. Decide the evidence needed to show implementation and the observation needed to judge effectiveness. Set due dates that allow the check to occur after the action has had a chance to work. The manager should know who can approve the action plan and who can accept the effectiveness result.

For a recurring production defect, the corrective action might revise an inspection practice or work instruction. The record can describe that action, while any actual document revision belongs with controlled documents. Decide how the team will link those operating steps during a pilot case.

Start with a rejected inspection and its linked nonconformance. The owner writes a root cause, proposes an action and sets a due date. The quality manager reviews and approves the plan. After implementation, the owner submits implementation details. The workflow moves the action to effectiveness review; the manager tests the result against the original issue before closing the action.

Add a second action to the same nonconformance. Complete the first and leave the second under review. The nonconformance must stay open. Once the manager accepts every linked action, close the issue from disposition. This rehearsal checks that completion of one task cannot hide unfinished corrective work on the same quality case.

• Corrective Action Queue — Planned through review work with owner and due date.
• My Corrective Actions — Work assigned to the current action owner.
• Effectiveness Review — Implemented actions waiting for the manager’s decision.

Use nonconformance and correction to rehearse approval, effectiveness and issue closure.