Deviation Management and CAPA: When to Escalate
A practical pharmaceutical guide to triaging deviations, recognizing urgent quality risks, involving the right decision-makers, and deciding when investigation findings should move into formal CAPA.
When should a pharmaceutical deviation be escalated?
Escalate a deviation promptly when it may affect patient safety, product quality, data integrity, a released batch, a regulatory commitment, or the state of control; when containment is uncertain; or when similar events suggest a systemic problem. Notify the designated Quality Unit under the site procedure, assess scope and risk, preserve evidence, and decide whether formal CAPA, management action, product action, or regulatory reporting is needed.
Start with clear terms
Deviation management, escalation, and CAPA: key definitions
Organizations use different labels across quality systems. Define the terms in the site procedure and keep the practical distinctions clear.
| Term | Practical meaning | Example |
|---|---|---|
| Deviation | A departure from an approved instruction, procedure, specification, process condition, or expected state that the quality system requires to be recorded and assessed. | A manufacturing parameter moves outside its approved range or a controlled step is performed in a different sequence. |
| Escalation | Promptly raising an event or risk to the role or level with the authority and expertise to make the next decision. | Notifying Quality and site leadership about a possible mix-up involving product already released. |
| Correction / immediate action | An action that addresses the detected condition or protects the process now; it may not remove the underlying cause. | Stopping a line and segregating material while affected scope is checked. |
| Corrective action | An action intended to eliminate or control a cause of an identified nonconformity or problem and reduce recurrence risk. | Changing an equipment control so a known failure condition cannot occur without detection. |
| CAPA | The governed system that links investigation findings to proportionate corrective and, where appropriate, preventive actions, ownership, verification, effectiveness review, and closure. | A recurring deviation with a confirmed system cause is routed into formal action and follow-up. |
| External notification / reporting | A separate decision governed by product-specific regulations, authorizations, contracts, and local procedures. | Assessing whether a market quality defect or reportable event requires contact with an authority or customer. |
Regulations set principles; SOPs set routes
What GMP and quality-system guidance say about deviations and escalation
The exact obligations depend on the market and product. Major frameworks expect deviations and failures to be recorded, investigated, risk-assessed, and followed through with suitable actions. Escalation levels and internal response times should be defined in the company’s quality system rather than assumed to be universal.
Record and justify procedural deviations
For US drug CGMP, 21 CFR 211.100(b) requires written production and process-control procedures to be followed and deviations from written procedures to be recorded and justified.
Thoroughly investigate specified failures
Unexplained discrepancies and batch or component specification failures require thorough investigation, whether or not a batch has been distributed; the investigation can extend to associated batches and products.
Provide timely communication and escalation
ICH Q10 describes management responsibility for a timely, effective process to raise quality issues to appropriate management levels. It connects deviation signals, CAPA, performance monitoring, and management review.
Investigate causes and scale effort to risk
EU GMP Chapter 1 addresses appropriate root-cause analysis and CAPA effectiveness. ICH Q9(R1) says risk-management effort, formality, and documentation should be commensurate with risk, uncertainty, importance, and complexity.
More than sending an email
What escalation means in a deviation process
Escalation moves a quality issue to a decision-maker who can assign resources, control affected product, approve a risk response, resolve a cross-functional barrier, or determine whether additional authorities need to be involved. It should bring the relevant facts, uncertainty, potential impact, containment status, and next decision together.
Local operational notification
Promptly tell the responsible supervisor and Quality contact so process conditions can be stabilized, evidence protected, and the initial deviation recorded.
Quality and technical escalation
Bring in the Quality Unit and relevant process experts to assess risk, scope, investigation depth, batch impact, and whether a formal CAPA or change is needed.
Senior or external escalation
Raise significant, uncertain, recurring, broad, or potentially reportable issues to senior site or corporate leaders and Regulatory Affairs, Medical, or other functions under defined procedures.
Escalation is not a conclusion that the product is defective, that a recall is required, or that a regulation has been breached. It is a controlled request for timely assessment by the people responsible for those determinations.
Recognize urgent signals
Deviation escalation triggers in pharmaceutical manufacturing
Use the site’s defined severity criteria. The following are common indicators for immediate or prompt Quality escalation because they may involve high consequence, broad exposure, weak detection, or regulatory commitments.
Potential patient or product-quality impact
Suspected wrong product, strength, identity, purity, potency, contamination, mix-up, compromised sterile assurance, incorrect packaging or label, or any condition that may make product unsuitable for use.
Specification or critical process failure
Out-of-specification or unexplained results, critical process parameter excursions, yield discrepancies requiring investigation, failed in-process controls, or evidence that approved limits were not followed.
Data integrity or record reliability concern
Missing, altered, unattributable, backdated, deleted, or inconsistent data; unapproved overrides; unexplained audit-trail activity; or uncertainty about whether release decisions relied on complete records.
Material may be released or distributed
Affected product is in final review, released, distributed, exported, or used in another process, or batch traceability is incomplete and the potential scope is not yet bounded.
Containment is absent or unreliable
Product cannot be segregated, process controls are not functioning, temporary checks are not verified, the event is continuing, or an immediate action may itself affect other quality attributes.
Repeat, systemic, or cross-site pattern
Similar deviations recur, several products or locations share a mechanism, a supplier or outsourced activity is involved, or the quality system may not be detecting or correcting the trend.
Prioritize with a documented rationale
Risk factors to consider before deciding escalation level
Do not classify an event by its label alone. Consider what could happen, how much product or process may be affected, what is known, whether controls are working, and how quickly a decision is required.
| Risk factor | Questions to ask | Escalation implication |
|---|---|---|
| Potential consequence | Could the event affect patient safety, identity, strength, purity, quality, sterility, labeling, efficacy, or reliable product supply? | High potential consequence requires prompt Quality triage and a documented protection decision. |
| Product and process scope | Which batches, materials, products, lines, methods, sites, markets, or time periods may be involved? | Unbounded or multi-product scope may require broader technical and senior review. |
| Current control | Has the event stopped? Is product held or traceable? Are temporary controls verified and effective? | Failed, missing, or uncertain containment increases urgency. |
| Detectability | Would routine testing, review, monitoring, or distribution traceability reliably detect the issue? | Weak detection or possible escape beyond the site calls for stronger escalation. |
| Recurrence and trend | Have related deviations, complaints, OOS results, audits, or near misses occurred before? | Repeated events may indicate a systemic cause and need for formal CAPA or management review. |
| Uncertainty and evidence | Are facts incomplete, records unreliable, scope unknown, or competing causes unresolved? | Uncertainty can justify more formal assessment and temporary controls; do not treat “unknown” as “low.” |
| Commitments and reporting | Could a filing, permit, customer agreement, supply obligation, or reporting time limit be affected? | Involve Regulatory Affairs or the accountable function promptly under local procedures. |
Translate risk into action
Deviation escalation levels: an illustrative decision matrix
Severity labels and response times must be defined by the site quality system. This example shows the kind of distinctions an SOP can make; it is not a universal classification or deadline schedule.
| Illustrative level | Typical indicators | Who to involve | Expected response path |
|---|---|---|---|
| Immediate / potentially critical | Uncontrolled risk; possible wrong product or label; suspected contamination or sterility concern; unreliable release data; product possibly distributed; containment failure; serious uncertainty about affected scope. | Quality Unit immediately through the approved urgent route; area leadership; relevant technical experts; Regulatory Affairs, Medical, or senior management as procedure requires. | Stabilize process, protect or hold potentially affected product where authorized, preserve evidence, document initial facts, and make a prompt risk and reporting assessment. |
| Major / prompt escalation | Potential batch nonconformance; significant process or utility excursion; repeated event; multi-batch or cross-site scope; supplier issue; important commitment at risk; cause or containment not yet clear. | Quality, responsible department manager, subject-matter experts, and other impacted functions. | Assign a risk-based investigation, define interim controls and decision milestones, and escalate further if scope, impact, or control changes. |
| Trend / system-level | Several individually bounded deviations share a cause, weak procedure, recurring equipment fault, training-system weakness, or repeated overdue investigation pattern. | Quality systems owner, department leaders, process owners, and management review forum. | Analyze aggregate trends, identify a systemic owner, assess formal CAPA, and monitor whether the pattern changes. |
| Routine / locally controlled | Isolated, low-consequence, immediately corrected event with evidence that the affected scope is known and no significant product or data concern is present. | Local supervisor and designated Quality reviewer under site procedure. | Record, investigate, document correction and rationale, trend as required, and upgrade the level if new information changes risk. |
Connect investigation to improvement
When should a deviation escalate into formal CAPA?
Deviation handling records and resolves a specific event. CAPA is the structured improvement route for addressing supported causes and preventing recurrence or occurrence elsewhere. A deviation may be escalated immediately even before the investigation can determine whether formal CAPA is warranted.
Formal CAPA is often warranted when…
- Evidence indicates a systemic or recurring cause.
- The event has significant potential product or patient impact.
- Multiple batches, products, sites, suppliers, or systems may share the mechanism.
- An audit, inspection, complaint trend, or management review identifies a quality-system weakness.
- A previous action failed or effectiveness criteria were not met.
- Durable changes to process design, equipment, software, training system, or governance are needed.
A separate CAPA may not always be needed when…
- The event is isolated and its scope is clear.
- It is promptly corrected with supported evidence of no broader cause or continued risk.
- The approved procedure permits event-level actions and trend monitoring.
- The investigation documents why a systemic action is not proportionate or useful.
- Trend thresholds and future escalation triggers are retained.
Keep product and authority decisions distinct
Deviation escalation versus batch disposition and regulatory reporting
Internal escalation gives responsible functions the information and authority to decide what to do. Batch release, rejection, reprocessing, recall, market notification, authority reporting, and customer communication each follow applicable procedures and legal requirements. Opening a deviation or CAPA does not automatically determine any of those outcomes.
Assess product and batch status
Identify whether material is in process, awaiting release, released, distributed, exported, or used downstream. Apply the responsible Quality Unit’s approved disposition and escalation procedures.
Assess market exposure
Use traceability and distribution records to establish affected markets and recipients when potentially nonconforming product may have left the site. Involve Regulatory Affairs and other authorized roles.
Check reporting duties and deadlines
Assess the applicable country rules, product authorization, contract terms, and commitments. Do not wait for a CAPA to close before making a time-sensitive reporting decision.
Make accountability explicit
Deviation escalation roles and responsibilities
| Role | Core responsibility | Escalation contribution |
|---|---|---|
| Person discovering the event | Stop or stabilize the activity when safe and authorized; report facts promptly; preserve records and samples. | Do not self-classify as harmless or wait for a complete investigation before raising a potential risk. |
| Area supervisor / process owner | Coordinate immediate response, determine affected operation, maintain traceability, and ensure a deviation is recorded. | Notify designated Quality contacts and escalate if product, process, evidence, or containment is uncertain. |
| Quality Unit / QA | Provide independent oversight of classification, investigation scope, risk, record quality, CAPA decision, and closure under applicable rules. | Escalate significant quality issues, challenge unsupported conclusions, and ensure required actions and follow-up occur. |
| Technical subject-matter experts | Assess process, laboratory, engineering, validation, microbiology, computerized-system, material, or supplier evidence within expertise. | Explain potential mechanisms, technical limits, controls, and whether the event could affect other processes. |
| Regulatory Affairs / Medical / Safety | Assess regulatory commitments, market obligations, health impact, product communication, and required notifications as applicable. | Advise on external communication timelines and decision pathways using current jurisdiction-specific requirements. |
| Site or senior management | Provide authority, resources, cross-functional decisions, and oversight for significant or systemic quality issues. | Resolve barriers, review trends, and ensure the escalation system is timely and effective. |
Specific titles and authority vary by jurisdiction and organization. Procedures should identify primary contacts, after-hours backups, who can place or release a hold, who approves classification changes, and how unresolved risk reaches senior management.
A practical response sequence
Step-by-step deviation escalation and CAPA workflow
This sequence gives teams a common route from discovery through learning. Adapt approval authority, time limits, and external reporting to the site’s controlled procedures.
Make the situation safe and contain risk
Stop or stabilize the affected activity when appropriate, segregate potentially affected material, and apply approved temporary controls.
Output: immediate protection actionsNotify the supervisor and Quality
Use the required channel and escalation route. Report what is known, what is uncertain, whether the event is continuing, and what action has already been taken.
Output: accountable initial notificationRecord the initial event facts
Capture time, place, process state, product or material identifiers, people or systems involved, observations, and source records without adding unsupported conclusions.
Output: traceable deviation entryAssign a provisional risk level
Assess possible consequence, scope, containment, detection, recurrence, uncertainty, and commitments. Mark the category provisional where facts are incomplete.
Output: documented triage decisionIdentify affected product and process scope
Map batches, components, methods, equipment, lines, systems, sites, suppliers, markets, and time periods that could share the event mechanism.
Output: preliminary scope mapPreserve evidence and protect data integrity
Retain source records, raw data, audit trails, samples, images, equipment status, system configuration, and time stamps under controlled procedures.
Output: secured evidence setSet investigation depth and team
Scale investigation effort and expertise to risk, uncertainty, and complexity. Bring in technical functions that can test potential causes and scope.
Output: approved investigation planAssess batch, distribution, and reporting decisions
Follow separate approved routes for release, rejection, reprocessing, recall, market exposure, customer communication, and authority reporting as applicable.
Output: recorded product and reporting assessmentInvestigate cause and related events
Build a chronology, test causal hypotheses, review similar deviations and trends, and extend scope to associated batches or products where the evidence supports it.
Output: evidence-based cause and scopeDecide whether formal CAPA is warranted
Link the cause and risk to the response. Document whether event-level correction is enough or whether systemic action, change control, supplier action, or management oversight is needed.
Output: justified CAPA pathwayAssign actions, owners, and criteria
Set interim and durable actions, accountable owners, resources, milestones, risk controls, and prospective verification or effectiveness criteria.
Output: approved action planVerify, trend, and close with approval
Confirm actions were implemented, effectiveness evidence meets defined criteria, remaining risk is addressed, and closure approval is documented. Use trends to identify wider lessons.
Output: documented quality decisionMake escalation reconstructable
What to document when escalating a deviation
A good escalation record allows the next decision-maker to understand the event without rebuilding the facts from scattered messages. Include concise, time-stamped facts and distinguish confirmed information from assumptions.
- Event identifier, date and time discovered, location, process step, product, and reporter.
- What happened and what should have happened, described without premature cause conclusions.
- Potential severity, product and process scope, affected batch status, markets, and uncertainty.
- Immediate actions, holds, segregation, checks, monitoring, containment owner, and verification.
- Notification time, recipients, communication route, decisions, approvals, and next update point.
- Evidence sources, record references, samples, raw data, audit trails, system settings, and chain of custody where applicable.
- Risk assessment assumptions, alternatives, classification changes, and rationale for decisions.
- Related deviations, complaints, OOS results, audit observations, supplier events, or prior CAPAs.
- Batch disposition, distribution assessment, regulatory or customer reporting decision and accountable function.
- Investigation owner, due dates, milestones, CAPA decision, effectiveness criteria, and closure authority.
Build a usable escalation route
What a deviation escalation SOP should define
An SOP should help staff act quickly when the facts are incomplete. It should make the first notification, interim controls, decision authority, and route for unresolved concerns explicit.
| SOP element | What to define | Why it matters |
|---|---|---|
| Trigger criteria | Events involving possible product or patient risk, critical process limits, contamination, identity or labeling, data integrity, uncontrolled scope, recurrence, or external commitments. | Staff can recognize an escalation trigger before the investigation is complete. |
| Who to notify and when | Primary supervisor and Quality contacts, expected notification timing by event level, contact method, after-hours backup, and acknowledgement route. | A report reaches an accountable decision-maker even when normal channels are unavailable. |
| Authority and interim controls | Who may stop work, segregate material, place a hold, secure records, and authorize any change to temporary controls. | Actions are prompt, controlled, and traceable while product impact is assessed. |
| Risk classification and reclassification | Site categories, assessment factors, required approvals, escalation thresholds, and how to record a changed category. | Risk decisions remain consistent as new evidence changes the picture. |
| Escalation beyond the first contact | What to do if the assigned contact is unavailable, does not acknowledge the concern, or a material risk remains unresolved. | Concerns do not stall in a single inbox or reporting line. |
| Separate quality decisions | Cross-references for batch disposition, market assessment, complaint handling, regulatory reporting, change control, and CAPA. | Opening a deviation does not replace other required decision pathways. |
| Review and trend oversight | Periodic review of escalations, repeat causes, delayed notifications, classification changes, overdue investigations, and management actions. | The site can see whether its escalation process works across departments and shifts. |
Apply the principles to real decisions
Examples of when to escalate a deviation
These examples show how the initial response can differ by risk and uncertainty. The final classification and disposition must follow the site procedure and the evidence for the specific event.
Possible label mix-up during packaging
Initial response: stop or secure the operation under authorized procedures, identify the last verified correct check, segregate potentially affected materials, and notify Quality promptly. Preserve line-clearance and reconciliation records.
Escalation question: could incorrect labeling have reached other units, batches, or the market? Extend scope and involve Regulatory Affairs or other accountable functions if product may have been released or distributed.
Process or storage excursion
Initial response: record the time range, equipment and sensor status, process conditions, product exposure, alarms, and any recovery action. Maintain appropriate controls while technical experts assess the affected window.
Escalation question: are limits, duration, product impact, or scope uncertain? Bring in Quality and relevant engineering or technical experts; reassess severity when validated evidence becomes available.
Documentation omission found during review
Initial response: notify the responsible reviewer and Quality under the applicable procedure; preserve the original record and make any correction only through an authorized, attributable method.
Escalation question: is the missing entry isolated and independently supported, or does it obscure a process step, test, approval, or data trail? The answer determines investigation depth; do not infer low risk from the appearance of a clerical error.
Protect the decision process
Common mistakes in deviation escalation
Waiting for the full investigation
Initial notification and containment should not wait for confirmed root cause when the event may carry meaningful risk.
Treating unknown as low risk
Incomplete scope or uncertain evidence can require closer controls and a provisional higher level until facts are established.
Using a score without context
A risk score supports judgment; it does not replace assessment of patient impact, actual exposure, control strength, or reporting duties.
Sending one message and stopping
Procedures should identify acknowledgement and backup routes so an urgent concern reaches someone authorized to act.
Equating escalation with recall
Escalation prompts assessment. Product disposition, field action, and external communication require their own authorized evidence-based decisions.
Closing when the correction is done
Correction may resolve the immediate condition; investigation, cause assessment, CAPA decision, and effectiveness review may still be needed.
Failing to revisit the initial level
New evidence can expand scope or reduce uncertainty. Reassess and record changes instead of keeping the first classification by default.
Handling repeat events one by one
Trend related records, complaints, laboratory results, and prior actions to identify a shared system issue or ineffective CAPA.
Check whether the system is working
Deviation escalation metrics and management review
Use a small set of measures that help leaders remove delays and identify recurring risk. Define each measure, its data source, exclusions, review frequency, and owner before setting targets. A metric is a prompt for investigation, not proof that an individual event was handled well.
| Measure | Useful definition | Question it can answer |
|---|---|---|
| Time from discovery to notification | Elapsed time between recorded discovery and required first notification, grouped by event level and shift. | Are urgent events reaching the right people within the site’s defined timeframe? |
| Time to initial Quality triage | Elapsed time from notification or record creation to documented Quality risk review. | Are the right reviewers available, including after hours? |
| Containment verification | Share of applicable events with a recorded check that the interim control was implemented and remains effective. | Did the assigned hold, segregation, stop, or monitoring control actually work? |
| Repeat-event rate | Related events within a defined period, normalized to an appropriate production, test, or activity denominator where useful. | Are causes recurring by process, equipment, product, supplier, or site? |
| Escalation and reclassification pattern | Count or share of records escalated, downgraded, or expanded after new facts, with reason and category. | Are initial criteria clear and are teams updating decisions as evidence develops? |
| CAPA referral and effectiveness | CAPA referrals by cause or risk category, plus due-date status and effectiveness outcomes. | Are systemic problems receiving durable actions that prevent recurrence? |
| Overdue investigations and extensions | Open records past due date, extension frequency, age, and stated reason by event level. | Are important risks waiting too long for investigation or decision? |
Quick initial triage
Deviation escalation triage aid
Use these prompts to prepare an initial discussion with Quality. This aid is educational; the approved site SOP, authorized decision-makers, and applicable regulatory obligations govern each event.
Before handing off the concern
Deviation escalation checklist
- Have I described what happened, when, where, and what is still uncertain?
- Have I followed the immediate stop, hold, segregation, or safety procedure that applies?
- Has the designated Quality contact been notified through the required route?
- Are affected products, batches, systems, records, time ranges, and markets identified or clearly marked unknown?
- Are source documents, raw data, samples, audit trails, and equipment status protected?
- Is there a named owner for interim containment and a way to verify it?
- Has the risk level been recorded as provisional where evidence is incomplete?
- Have repeat events, related complaints, test failures, audit findings, and prior CAPAs been considered?
- Are batch disposition, distribution exposure, and reporting decisions routed to authorized functions?
- Are the next update, investigator, due date, CAPA decision, and approval path clear?
Quick answers for quality teams
Frequently asked questions
When should a pharmaceutical deviation be escalated?
Escalate promptly when there may be patient or product risk, a significant process or specification failure, contamination, labeling or identity concern, data-integrity issue, uncontrolled scope, failed containment, repeat pattern, or time-sensitive commitment. Notify the roles and timing defined in the approved procedure; do not wait for root cause when immediate risk may exist.
Who should be notified first about a deviation?
Follow the site procedure, which commonly identifies the area supervisor and designated Quality Unit or QA contact. For an urgent event, use the approved urgent or after-hours route and notify additional authorized functions when the trigger criteria require them.
Does every deviation need to be escalated to senior management?
No. A tiered escalation system directs routine events to designated local and Quality reviewers and raises significant, systemic, unresolved, or cross-functional risks to the appropriate management level. The site SOP should define those thresholds and the route when a concern is not acknowledged.
Does every deviation require a formal CAPA?
No. Every event should be handled under the applicable deviation procedure, but the need for a separate formal CAPA depends on risk, evidence, cause, recurrence, and the site’s criteria. Document why event-level correction is sufficient or why broader action is required.
What types of deviation usually need immediate escalation?
Potentially serious patient or product risks, suspected contamination or sterility concerns, possible wrong identity or labeling, unreliable release data, uncontrolled or expanding scope, a failed containment, or product that may have been distributed generally warrant use of the approved urgent route. The site procedure and evidence determine the exact level.
How soon should QA be informed?
Use the timing in the approved site procedure. An event that may involve immediate product risk, data integrity, uncontrolled scope, or a reporting deadline should be raised through the urgent route promptly; there is no single internal time limit that applies to every event in every organization.
What should a team do when the impact is unknown?
Record the uncertainty, maintain appropriate temporary controls, notify Quality, define the affected scope, and gather evidence. Treat the initial classification as provisional and reassess it as facts emerge; unknown impact should not automatically be recorded as low risk.
What is the difference between deviation escalation and CAPA?
Escalation is the communication and decision path used to bring an event and its risk to people with the authority and expertise to respond. CAPA is the structured system for correcting supported causes and preventing recurrence or occurrence elsewhere. A deviation can be escalated before the CAPA decision is known.
Does a repeated deviation prove that the previous CAPA failed?
Not by itself. Investigate whether the new event shares the same cause, process, control, or scope, then review the prior action and its effectiveness criteria. A related recurrence may show ineffective action or an incomplete cause assessment and should be evaluated accordingly.
Should a potentially affected batch be placed on hold?
Apply the site’s authorized control and disposition procedure to prevent unintended use or release while Quality assesses the event. The appropriate status depends on product stage, scope, evidence, and authority; escalation alone does not decide final batch disposition.
When does a deviation need regulatory reporting?
Reporting duties depend on jurisdiction, product status, event type, marketing authorization, and other commitments. Route the assessment promptly to Regulatory Affairs or the designated accountable function, and track any time-sensitive obligation separately from the CAPA closure date.
What should be documented when a deviation is escalated?
Document the event facts, discovery and notification times, affected scope, known and unknown risk, containment, evidence references, recipients, decisions, approvals, classification rationale, related records, assigned owners, and next milestones. Preserve original records and make corrections only through controlled, attributable methods.
How should repeated deviations be escalated?
Link and trend related deviations, complaints, test failures, audits, and prior CAPAs. Assess whether they share a cause or weak control, expand the scope if evidence supports it, and refer a systemic pattern to the Quality Systems owner and management review route defined in the procedure.
What does 21 CFR 211.100(b) require for procedural deviations?
It requires written production and process-control procedures to be followed and deviations from those procedures to be recorded and justified. Applicable requirements and the organization’s approved procedures should be checked for the specific event.
What does 21 CFR 211.192 require when a discrepancy is found?
It requires a thorough investigation of an unexplained discrepancy or a batch or component failure to meet specifications, whether or not the batch has already been distributed, with the investigation documented in writing. The Quality Control Unit reviews production and control records as specified by the regulation.
Which factors determine the escalation level?
Consider potential consequence, affected scope, product status, containment, detectability, recurrence, uncertainty, evidence quality, cross-site impact, and external commitments. Apply the approved risk method and document the reasoning, approver, and any later reclassification.
Primary regulatory and quality references
Guidance and regulations to consult
Use the current applicable text, local requirements, product authorization, and controlled site procedures when making decisions. Guidance supports a quality system and does not replace binding regulations.
.webp)
