This is a ready-to-use decision aid for classifying inspection findings. Replace every <<FILL: ...>> placeholder with your own specifics and align it to your quality system. A worked set of examples follows. This is educational guidance to adapt and verify, not a substitute for your quality unit’s judgment or legal and regulatory advice.
Knowing how a finding will be graded lets you read your own observations the way an inspector reads them, prioritize the response, and predict escalation. The EU and the wider PIC/S membership grade each deficiency, while FDA does not print a grade on the Form 483, yet the investigator’s internal weighting and the order of observations follow the same logic, and escalation to a Warning Letter is the real measure of severity.
Document control header
| Field | Entry |
|---|---|
| Document title | FDA and EU Deficiency Classification Decision Aid |
| Document number | <<FILL: DOC-ID, e.g. QP-INS-006>> |
| Version | <<FILL: version>> |
| Owner | <<FILL: role, e.g. Head of Compliance>> |
1. The two systems, in brief
- EU and PIC/S: each deficiency is classified. PIC/S guidance PI 040 formally uses Critical, Major, and Other, with the third category commonly reported as Minor in EU practice. The classification drives the consequence, and a single Critical or a stack of Majors can hold up a GMP certificate.
- FDA: the Form 483 lists inspectional observations without a printed Critical/Major/Minor grade. The investigator’s internal severity language and the order of observations carry the signal, and whether the matter escalates to a Warning Letter after the Establishment Inspection Report is reviewed is the true measure of weight.
The grading logic is broadly shared, so classifying your finding by the EU logic also tells you which FDA observations are most likely to escalate.
2. The classification logic
| Class | Broad meaning | Typical triggers |
|---|---|---|
| Critical | Has caused or could cause real patient harm, or involves data falsification or fraud | Data manipulation or deletion affecting release; a sterility assurance breach on a released product; a hazard reaching the patient |
| Major | A serious GMP shortfall short of critical, or a significant breakdown in following procedures | A required control not consistently performed; a system that could allow undetected manipulation, with no harm shown yet |
| Minor (Other) | A lesser gap that does not on its own put patients at risk | An isolated documentation gap; a procedural inconsistency with no quality impact |
The escalators that push a finding up a class: it touches batch disposition or release; it involves data integrity or falsification; it is systemic rather than isolated; it recurs after a prior commitment to fix it; or it shows the quality system did not detect it.
3. The decision path
4. Worked examples
The same underlying subject, audit trail control on a release-testing system, seen at three severities:
| Observed fact | Class | Why |
|---|---|---|
| Audit trail disabled on the release-testing CDS, and a deleted failing result is found | Critical | Falsification or manipulation risk that directly touches batch disposition |
| Audit trail review procedure exists but is not consistently performed across instruments | Major | Substantial GMP departure that could allow undetected manipulation, no harm shown yet |
| Audit trail review is performed but the review record does not always capture the reviewer’s signature date | Minor | A documentation gap with no patient risk on its own |
On an FDA 483 the same three facts would appear as observations with no printed grade, but the investigator’s weighting tracks the same logic, and the first is the kind that escalates to a Warning Letter.
5. Response priority guide
| Class | Response posture |
|---|---|
| Critical | Immediate containment (quarantine or hold affected product), notify leadership, correction started during or immediately after the inspection, full root cause and systemic CAPA, network-wide assessment; treat as likely to escalate |
| Major | Prompt correction, documented root cause, systemic CAPA with an effectiveness check, network read-across |
| Minor | Corrected through routine CAPA, grouped where several relate, with realistic dates |
Across all classes, a response holds when each finding has a real root cause (not “human error” alone), corrections already in place with evidence, systemic CAPA beyond the cited instance, an effectiveness check with a metric and date, and a network-wide assessment so the same gap is not open at a sister site.
6. Acceptance criteria for using this aid
- Every finding is classified against the same logic before the response is drafted.
- Classification considers the escalators (disposition impact, data integrity, systemic, recurring, detection failure), not just the surface fact.
- The response posture matches the class.
- FDA observations are triaged for escalation risk even though they carry no printed grade.
7. References
PIC/S PI 040, classification of deficiencies (referenced by number and title; described, not reproduced). EU GMP framework and EudraGMDP for the certificate consequences of classified deficiencies. FDA Form 483 and Warning Letter process; the Establishment Inspection Report review that drives escalation.
Confirm the current version of each reference before issue.
Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author | <<FILL>> | ||
| Approver (QA / Compliance) | <<FILL>> |
Filled specimen
The following shows the aid applied to one real-shaped finding, so you can see how the classification drives the response. The details are illustrative.
| Field | Entry |
|---|---|
| Finding | On the release-testing CDS, the audit trail for result deletion had been switched off at system level, and a deleted out-of-specification result was recovered from the instrument for a batch that was later released |
| Escalators present | Data integrity and possible falsification; directly touches batch disposition; suggests the quality system did not detect it |
| Class | Critical |
| FDA read | Would appear as a 483 observation with no grade, but is the kind that escalates to a Warning Letter |
| Response posture | Quarantine the affected batches, notify leadership, lock the audit trail configuration and remove the ability to disable it, full root cause including how the setting was changed and by whom, network-wide check of the same setting on every CDS, effectiveness check after the fix |
In this example the finding is Critical because it combines a data integrity or falsification risk with a direct link to batch release, so the response is containment first, not a documentation fix. Classifying it correctly before writing the response is what sets the right urgency and scope.
Common mistakes this aid prevents
- Under-grading a data integrity finding because “no patient was harmed,” missing that falsification is Critical on its own.
- Treating an FDA 483 observation as low priority because it has no printed grade, then being surprised by a Warning Letter.
- A response posture that does not match the severity, for example a documentation fix for a Critical finding.
- Fixing only the cited instance and leaving the same gap open across the network.
How to adapt this aid
- Align the class definitions and response postures to your own quality system and SOPs.
- Use it during the inspection to anticipate how observations will land, and after to prioritize the response.
- Feed the classification into your CAPA prioritization and your network read-across.
- Keep the underlying regulatory references current, since classification guidance is periodically revised.