21 CFR 211.192
Production record review
Unexplained discrepancies are investigated, the investigation reaches other batches that may be involved, and the conclusion and follow-up are written on the record.
Corpex-eQMS handles a deviation from the first report to the closure review: classification by NCR level, an impact questionnaire, a structured root cause investigation, batch and product impact, a CAPA gate at final approval, and e-signed submissions, approvals and rejections.
The standard workflow. A second workflow adds first and second review steps; a record can also end as rejected or cancelled.
The originator reports what happened and proposes nothing more. The quality assessor then sets the initial non-conformance level, the impact classification and the detection mode, and cannot approve the assessment without a level.

The investigator writes the plan and the summary, chooses a method and records the root cause and the correction. The investigation cannot be submitted while the plan, summary, root cause or correction is missing. Where your investigation policy sets a minimum depth per level, final approval is refused while the investigation is shallower than the confirmed level asks for, and the record goes back to the investigator.

A deviation rarely stops at one batch. The record carries the impacted batches and links the products, materials and equipment involved, each with its own notes, so the quality approver decides product disposition with the scope in front of them.
The investigator answers whether a CAPA is required, and a "yes" means a CAPA is raised from the deviation, or an open one linked, before the investigation is submitted. QA confirms that decision at final approval. While the deviation awaits CAPA execution, a closure request is refused until the linked work is really finished.

A deviation management system is the controlled record of every departure from an approved procedure, specification or batch record, from the first report to a trended, closed CAPA. GMP deviation software earns its place when the steps below cannot be skipped, because a spreadsheet or a shared folder lets every one of them be skipped. This is the path a record takes in Corpex-eQMS and what the software checks at each point.
| Step | What the record holds | What the software enforces |
|---|---|---|
| 1. Report | What happened, when, where and how it was detected, written by the originator. | The originator reports; the assessor, not the originator, sets the level. |
| 2. Classification | NCR level (critical, major, minor), impact classification and detection mode. | The assessment cannot be approved without a level; the level sets the target days for the due date. |
| 3. Impact assessment | The impact questionnaire (product quality, patient safety, regulatory, validation, other batches, data integrity) and the impacted batches, products, materials and equipment. | The quality approver writes the product disposition and confirms the final level before final approval. |
| 4. Investigation | Plan, summary, team, method and correction, signed by the investigator. | Submission is refused while the plan, summary, root cause or correction is missing, and the chosen method must carry its minimum content. Team members are checked against training requirements. |
| 5. Root cause | 5 Whys, fishbone by 6M, root cause map, process-flow gap analysis or free text. | A 5 Whys needs at least three answered whys. Where the recurrence check is switched on, it runs a second time at investigation and asks for the root cause first. |
| 6. CAPA link | The CAPA decision, the linked CAPAs and any similar CAPA. | The investigator answers "Is a CAPA required?" before submitting: a "yes" needs a CAPA raised or an open one linked, a "no" needs a written reason. QA confirms at final approval, and a changed answer needs its own reason. |
| 7. Effectiveness | The planned effectiveness check and its result. | Closure is refused until every linked CAPA has ended and each planned check is verified with an e-signature or waived with a signed reason. |
| 8. Trending | Recurrence flag with a link to the previous deviation; management review figures. | The review window counts deviations opened, closed and cancelled, by defect category and by NCR level, with median and mean cycle time in total and per stage. |
The trending figures feed management review, and the CAPA half of the loop is described under CAPA and effectiveness checks. A laboratory out-of-specification result starts in LIMS software and reaches this record by a person or through the signed integration API.
Six questions that come up in nearly every deviation review, the rule behind each, and where the answer sits in the record.
EU GMP Chapter 1, point 1.4(xiv) asks for an appropriate level of root cause analysis, the most likely root cause where the true one cannot be found, and a formal case for human error only after process, procedure and system causes have been ruled out. In Corpex-eQMS the method, the root cause and the correction are fields of the investigation, and where your investigation policy sets a minimum depth, final approval is refused while the investigation is shallower than the confirmed level asks for.Source: EudraLex Volume 4, Chapter 1; Chapter 8, points 8.16 and 8.17 say the same for quality defects.
21 CFR 211.192 says the investigation shall extend to other batches of the same drug product and other drug products that may have been associated with the failure. The record carries the impacted batches, the linked products, materials and equipment, and an impact question about other batches, so the scope is on the page when the approver decides disposition.Source: 21 CFR 211.192; EU GMP Chapter 8, point 8.11.
The same section requires a written record of the investigation that includes the conclusions and follow-up. One deviation record holds the assessment, the investigation, the decisions, the CAPA links and the closure review, and every GMP write is in the audit trail with who, when, old value and new value.Source: 21 CFR 211.192.
Chapter 8 expects an investigation to review previous reports for specific or recurring problems (point 8.12) and records to be trended regularly (point 8.19). The record flags recurrence and links the previous deviation, and the management review counts deviations by defect category so a repeating cause shows as a repeating bar.Source: EudraLex Volume 4, Chapter 8. The chapter is written for quality defects; most sites apply it to deviations too.
Chapter 1, point 1.4(xiv) asks for appropriate CAPAs to be identified and taken, with their effectiveness monitored and assessed. The investigator's CAPA decision and QA's confirmation are both recorded, with a written reason for a "no" or a change, the deviation cannot close while a linked CAPA is open, and a planned effectiveness check needs a verified result or a signed waiver.Source: EudraLex Volume 4, Chapter 1; Chapter 8, point 8.18.
The assessor, investigator, reviewers and approver are different people, nobody who acted earlier signs later, and each decision asks for the password again and records what the signature means. An overdue record cannot move until the step owner records who, when and why.Your validation and quality unit decide how these controls meet your own procedures.
The same workflow serves different events, but the right record is not always a deviation.
Something went wrong on the floor: a parameter out of range, a missing signature, an excursion. This is the everyday deviation, classified by NCR level and investigated for root cause.
Tag the record planned when it is a pre-approved, time-limited departure. Where your policy sends temporary changes to change control, raise a change request instead and keep the deviation for the unplanned event.
The OOS investigation runs in CORPEX LIMS, and an open OOS on the same product and batch blocks technical approval there. A deviation on the same event is raised in the eQMS by hand, or by an external system through the signed integration API.
These are checks the system makes before a record moves, not guidance in a manual.
Assessor, investigator, reviewers and approver cannot be the same person, and nobody who acted earlier signs later.
A record past its due date cannot move forward until the step owner records who, when and why.
Submission, each approval and each rejection ask for the password again and record what the signature means.
A rejected deviation keeps its reason on the record, and a repeated return for rework alerts the closure reviewers.
Reopening a closed record and cancelling one raised in error each need a signature and a reason. Neither deletes anything.
Every GMP write is logged with who, when, old and new value, in a trail that is chained so a missing entry shows.
Each card names the control in the software that answers it.
Production record review
Unexplained discrepancies are investigated, the investigation reaches other batches that may be involved, and the conclusion and follow-up are written on the record.
Quality system, quality defects
Deviations are recorded, investigated for root cause and followed by corrective and preventive action; customer complaints are recorded and classified in the complaints module.
Pharmaceutical quality system
CAPA with an effectiveness check, quality-approver decisions and a closure review that is independent of the investigation.
Quality risk management
The NCR level drives the due date; an optional policy sets the root-cause depth required for each level.
Records and signatures
Password re-entry at each signature, role-based rights, session lockout and an audit trail on every GMP write.
This page describes software controls. It is not legal advice; your validation and quality unit decide how they meet each rule.
Short answers, based on what the software does today.
A deviation management system is the controlled record of every departure from an approved procedure, specification or batch record, from the first report through classification, impact assessment, investigation and root cause to a linked CAPA, an effectiveness check and trending. In Corpex-eQMS each step has its own owner, signature and audit trail entry, and the record cannot close while the CAPA work is unfinished.
It should refuse a step that has not been earned, not just record that it happened. In Corpex-eQMS that means no assessment approval without an NCR level, no investigation submission without a plan, a summary and a root cause, no closure while a linked CAPA is open, signatures that re-ask for the password and carry their meaning, and an audit trail chained so a missing entry shows.
An OOS result is a laboratory finding that fails a specification; it is investigated in the laboratory first. A deviation is a departure from an approved procedure, specification or batch record anywhere on site. In Corpex the OOS investigation is held in the LIMS, and an open OOS on the same product and batch blocks technical approval there. The eQMS holds the site-level deviation, which a person raises or an external system reports through the signed integration API.
Yes, but it has to be decided and justified. The investigator answers "Is a CAPA required?" when submitting the investigation, and a "no" needs a written reason. QA confirms the answer at final approval, and changing it needs its own reason. If the answer is "yes", the deviation cannot be closed until at least one linked CAPA is closed, every linked CAPA has ended, and any planned effectiveness check has a result or a signed waiver.
The assessor, investigator, reviewers and approver must be different people, and nobody who created the record or acted on an earlier step can sign a later one. Every step that decides something asks for the password again and records the meaning of the signature. The closure reviewer must also be independent of the people who worked on the record.
The due date comes from the NCR level (30, 15 or 7 days for critical, major and minor by default, set by your administrator) and can be moved only with a reason where a due-date policy applies. An overdue deviation cannot move forward until the step owner records a justification, which is kept with the name, time and text.
You can classify a record as planned or unplanned, alongside quality, health and safety or environment. A planned departure is pre-approved and time-limited, and many inspectorates expect a temporary change to a validated process to go through change control instead. If that is your policy, raise it as a change request and keep the deviation for the unplanned event.
A closed deviation can be reopened with an e-signature and a reason; the version number goes up and the cycle restarts. A deviation raised in error can be cancelled, with an e-signature and a reason from your own list, at any working stage up to closure approval, provided its CAPA work is finished. A cancelled record is locked and counted apart from the closed ones. Nothing is deleted.
Book a demo and we will take one deviation through assessment, investigation, CAPA and closure with you.
Request a Demo