Deviations and CAPA

A deviation is tied to a batch. QA Manager records its number, title, type, severity, description, opened date and due date. An equipment reference can identify the machine involved. The status follows the investigation from Open through under investigation and root cause identified to capa assigned or Closed; Cancelled remains a separate outcome. These stages give the production and quality teams a common view of what still needs investigation.

A capa actions record captures the corrective or preventive work associated with a deviation. Its action plan, owner name, due date, completion date and effectiveness result let the team follow work beyond the initial root cause. The CAPA status distinguishes Draft, Open, in progress, pending effectiveness check, Effective, Closed and Overdue. The owner name is text, so the team should agree who maintains it and how ownership changes are reviewed.

• Batch exception. Record the lot and the observed problem before describing a proposed remedy.
• Investigation. Add the root cause when the review supports it, and keep severity and due date visible.
• Action and effectiveness. Follow a linked CAPA through completion and the later effectiveness check.

Define which issues require a deviation, how the three severity values are used and who may close an investigation. Agree when a CAPA is needed and who records the action owner. The same batch can have more than one deviation, and one deviation can have several linked actions. Decide how the team will identify the complete set before a release review.

The custom Quality Exceptions & CAPA page brings open deviations, unclosed actions and out-of-calibration equipment into one review surface. Use it during the daily quality discussion, then open the underlying records for decisions and evidence. The page helps organize attention; the deviation and CAPA records hold the details.

During testing of a lot, an analyst records an exception. QA Manager opens a deviation against the batch, marks it Major and describes the event. The manager moves the investigation to under investigation, records the root cause when established and creates a Corrective CAPA linked to the deviation. The action plan names the next work and the owner name identifies the person responsible. After completion, QA Manager records the effectiveness check result and moves the action through pending effectiveness check to Effective when the review supports it.

During release review, open the lot and follow the deviation to its linked action. The reviewer should see the current deviation status, action status and evidence, rather than assuming that a completed action automatically settles the batch decision.

• Open deviations — Batch exceptions still being investigated or assigned to corrective action.
• CAPA effectiveness queue — Actions waiting for an effectiveness judgment.
• CAPA due now — Actions whose due date needs attention.

See testing and exceptions for the initial quality signal and deviation to CAPA for action follow-up.