SOP: Quality Event Classification, Risk Ranking, and Escalation

This is a ready-to-use SOP for classifying and escalating quality events. It pairs with the Quality Event Triage and Classification Record (the form you fill per event) and the Quality Event Escalation and Notification Matrix (who is told and how fast). Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it.

Document control header

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> assigns a severity tier (critical, major, minor) to a quality event, ranks its risk, screens it for regulatory reportability, and escalates it, so that investigation depth, timelines, notification, and product disposition are proportionate to patient and product risk.

2. Scope

This procedure applies to all quality events at the sites in the header: deviations and nonconformances, out-of-specification and out-of-trend results, complaints, audit and inspection findings, environmental excursions, equipment failures, and data integrity events. For combination products it applies to events affecting either the drug/biologic or the device constituent part. It does not replace the investigation procedure (<<FILL: SOP-ID for deviations/investigations>>) or the CAPA procedure (<<FILL: SOP-ID for CAPA>>); it sizes them.

3. Responsibilities

4. Definitions

• Quality event: any departure from an approved standard, expectation, or commitment that touches product quality, patient safety, or data integrity.
• SISPQ: safety, identity, strength, purity, and quality of the product as registered.
• Critical / Major / Minor: the three severity tiers defined in section 5.5.
• Reportability screen: the check, done at classification, of whether the event trips a regulatory reporting threshold.

5. Procedure

5.1 Contain before you classify

Secure the situation first: quarantine affected product, stop the line if needed, isolate the suspect system, and preserve original records and failing samples. Containment buys time to classify correctly without product moving.

5.2 Capture the facts

Record the objective description (what, where, when, who, which lot/system) with no root cause, blame, or speculation. Pull the underlying records (batch record, audit trail, chromatogram, EM data) before they can be overwritten. For data integrity events, freeze the audit trail and metadata.

5.3 Define the affected scope

Ask what else this could touch: other units in the batch, other batches on the same equipment, other products on a shared line, other results from the same instrument or analyst, other time periods. Scope is where minor events become major. Default the question on shared lines to “what is the next product on this equipment.”

5.4 Assess potential patient impact

Run the patient-impact questions; the honest answer anchors the tier:

1. Does the event affect SISPQ? If yes, it is at least major and likely critical.
2. Could affected product reach a patient (distributed, in finished goods, or still containable)?
3. What is the harm if it does (negligible, minor, serious, life-threatening)?
4. What population is exposed (pediatric, immunocompromised, single-source life-sustaining)?
5. Is the data supporting disposition trustworthy? A data integrity failure defaults the event high.

If the honest answer to “could this reach a patient and cause harm” is yes or unknown, you are at critical until proven otherwise.

5.5 Assign the tier

Two anchoring rules: classify on potential, not only outcome (a near-miss caught by luck is still serious), and systemic beats isolated (recurrence escalates severity because it signals a CAPA failure).

5.6 Score the risk drivers (for non-obvious tiers)

Where the tier is not obvious, score severity (S), probability/occurrence (P), and detectability (D). Map the S-by-P band to a tier, then let poor detectability (the control that should have caught it was the control that failed) bump one band higher.

5.7 Run the reportability screen

At classification, screen the event against reporting thresholds so the regulatory clock starts on day zero, not after the investigation. Record the outcome on the triage form. Common triggers:

• US field alert report, 21 CFR 314.81, within 3 working days for specified NDA/ANDA problems.
• Biological product deviation report, 21 CFR 600.14 / 21 CFR 1271.350, generally within 45 calendar days for distributed biologics or HCT/Ps.
• Recall / field action assessment for distributed product.
• GCP serious breach reporting under ICH E6(R3) and regional rules.
• For a combination product, device-side postmarket reporting in addition to the drug/biologic obligations.

5.8 Assign and justify

State the tier and the specific drivers, and document why you did not go one level higher. “Classified major, not critical, because the impact assessment confirmed no SISPQ effect on released product; isolated; no patient exposure” is defensible. “Minor” with no reasoning is a finding.

5.9 Escalate

Notify per the Escalation and Notification Matrix: critical reaches the head of quality (and often regulatory affairs) the same day; major within 1 to 2 business days; minor is logged. Open the CAPA if warranted.

5.10 Re-classify on evidence only

Classification is provisional until the investigation closes. Escalate the tier if scope or patient exposure grows; downgrade only on evidence. Never silently overwrite the first classification; the original rationale and the change must both remain visible. Operating rule: classify high at open, refine on evidence.

6. Acceptance criteria

• Every event has a tier with a written justification within the SOP-defined time of opening.
• Each event has an explicit patient-impact statement and a completed reportability screen.
• Investigation depth visibly matches the tier; over-investigating a minor and under-investigating a critical are both defects.
• Re-classifications are evidence-based with the history preserved.
• Escalation happened on time for critical and major events, with notification records.
• QA’s authority over the final tier is documented and independent of production.

7. Records generated

• Quality event triage and classification record (per event).
• Reportability screen outcome.
• Escalation / notification record.
• Re-classification record where applicable.

8. References

21 CFR 211.192 (investigation of discrepancies and failures), 211.100(b) (deviations recorded and justified), 314.81 (field alert reports), 600.14 / 1271.350 (biological product deviation reports). EU GMP Chapter 1 (Pharmaceutical Quality System); EU GMP Annex 16 (QP certification and unresolved deviations). ICH Q9(R1), Quality Risk Management (2023 revision), on proportionality and reducing subjectivity. ICH Q10, Pharmaceutical Quality System, on effort commensurate with risk. ICH E6(R3), Good Clinical Practice (serious breach reporting), where clinical. 21 CFR Part 4 (combination products), where applicable.

Confirm the current version and clause numbers before issue.

9. Revision history

10. Approvals

Filled specimen

Illustrative triage of one event. Replace with your own.

Event. A fill-line in-process check finds a single under-filled vial of a sterile injectable; the upstream checkweigher is later found to have drifted out of calibration for an unknown period.

• Contain. Line stopped, affected units quarantined, checkweigher locked out, retained units secured.
• Scope. All units filled since the last good checkweigher calibration are potentially affected; the window is open.
• Patient impact. Under-dose affects strength (SISPQ); product is parenteral; the failed control was the automated detection control, so detectability is poor.
• Risk ranking. Severity medium-high, probability medium-high (window open), detectability poor. Band maps to critical; poor detectability holds it there.
• Reportability screen. If the affected NDA/ANDA product were distributed and the strength failure confirmed, a field alert screen trips; here product is contained, screen documented and monitored.
• Tier. Critical at open. Why not lower: the affected window is unbounded and the primary control failed.
• Re-classification. After the impact assessment bounds the window (last good calibration, statistical sampling of retained units) and finds no further under-fills in a small contained quantity, re-classified to major with documented justification; calibration program gets a CAPA.

This shows “classify high at open, refine on evidence” in practice: a defensible critical that was justified down to major on evidence, with the history preserved.

Common inspection findings this SOP prevents

• Classifying down to dodge work, so a real quality impact gets a shallow investigation.
• Inconsistent classification of the same event type across shifts or months.
• A tier assigned with no justification and no “why not higher.”
• Investigating one batch when 211.192 required extending to other associated batches.
• Late or missing regulatory reporting because the reportability screen was done after the investigation, not at classification.
• Data integrity events treated as low severity.

How to adapt this SOP

1. Set your document number, owner, and effective date.
2. Align the tier names in 5.5 to your QMS terminology if different (for example major/minor/no-impact, or a 1 to 5 scale).
3. Point the cross-references to your real investigation, CAPA, and complaint procedures.
4. Attach your escalation matrix and triage form as controlled annexes.
5. Confirm every regulation in section 8 against the current published version before issue.