# Applying proportionate investigation to minor events
> Quality systems may route minor events into the same documentation and investigation process used for more serious deviations. This can consume investigator and reviewer capacity without proportional quality benefit. The challenge is to create risk-based triage criteria that distinguish events requiring full investigation from those appropriate for streamlined assessment, without overlooking recurring or systemic failures.
- Status: Current. Last verified 2026-10-15.
- Applies to: Qualitative synthesis of 17 public practitioner discussions, October 2026. Not facts about AskDona, verified audit findings or prevalence statistics.
- Canonical: https://askdona.com/ai/assessment-challenge-12-proportionate-investigation-minor-events.md
12
**Category: CONTROL | Subcategory: Document**
Assessment area: Quality Assessment
Quality systems may route minor events into the same documentation and investigation process used for more serious deviations. This can consume investigator and reviewer capacity without proportional quality benefit. The challenge is to create risk-based triage criteria that distinguish events requiring full investigation from those appropriate for streamlined assessment, without overlooking recurring or systemic failures.
Deviation and quality-event processes are designed to ensure that manufacturing problems receive appropriate attention, yet a uniform investigation requirement can create a heavy workload when applied to every event regardless of significance. A minor documentation or operational issue may trigger much of the same routing, review, and approval activity as a more consequential deviation.
The practitioner discussion raised the difficulty of deciding when a streamlined assessment is adequate and when a full investigation, deeper root-cause work, or CAPA is warranted. If categories and thresholds are vague, assessors may classify similar cases differently, or default to the most burdensome process to avoid challenge. Over time, an accumulation of low-value investigations can compete with attention to higher-impact quality risks.
The central challenge is to define a proportionate triage mechanism that still captures relevant GMP information, supports defensible escalation, and distinguishes administrative efficiency from an unjustified reduction in quality oversight.
---
## AskDona Assessment — Applying Proportionate Investigation to Minor Events
**Topic ID:** 12
**Category:** CONTROL | **Subcategory:** Document
**Assessment area:** Quality Assessment
**Challenge status:** Current · verified 2026-10-15
**Prepared:** 2026-10-16
> **Evidence and attribution note:** The original challenge in Section 1 is reproduced verbatim from the supplied prompt. The FDA-derived excerpts in Section 2 are reproduced from the **user-supplied analytical summary**, not quoted directly from the FDA Warning Letters. The FDA URLs are provided as copyable Markdown links at the end; **[Outdated — marked 2026-10-16]** source-specific interpretations should be checked against the primary FDA pages before publication. **Updated (16 Oct 2026):** all 24 linked FDA letters were opened and each finding checked; the result is given as a “Fact check” note under each finding. A Warning Letter is case-specific and does not establish a universal investigation threshold. AskDona's output is a *preliminary evidence assessment*, not authorization to close a deviation, reject CAPA, release a batch or waive a required investigation.
### Executive Positioning
**AskDona Assessment helps quality teams apply proportionate investigation rules more consistently by checking whether a proposed minor-event disposition is supported by defined criteria and verifiable records.** It supports evidence gathering and first-pass triage review while qualified Quality Unit staff retain investigation, escalation and closure authority.
### 1. Original Challenge — Verbatim
#### 1.1 Title and classification
**Applying proportionate investigation to minor events**
**Current · verified 2026-10-15 · 12**
**Category:** CONTROL | **Subcategory:** Document
**Assessment area:** Quality Assessment
#### 1.2 Original text
> Quality systems may route minor events into the same documentation and investigation process used for more serious deviations. This can consume investigator and reviewer capacity without proportional quality benefit. The challenge is to create risk-based triage criteria that distinguish events requiring full investigation from those appropriate for streamlined assessment, without overlooking recurring or systemic failures.
>
> Deviation and quality-event processes are designed to ensure that manufacturing problems receive appropriate attention, yet a uniform investigation requirement can create a heavy workload when applied to every event regardless of significance. A minor documentation or operational issue may trigger much of the same routing, review, and approval activity as a more consequential deviation.
>
> The practitioner discussion raised the difficulty of deciding when a streamlined assessment is adequate and when a full investigation, deeper root-cause work, or CAPA is warranted. If categories and thresholds are vague, assessors may classify similar cases differently, or default to the most burdensome process to avoid challenge. Over time, an accumulation of low-value investigations can compete with attention to higher-impact quality risks.
>
> The central challenge is to define a proportionate triage mechanism that still captures relevant GMP information, supports defensible escalation, and distinguishes administrative efficiency from an unjustified reduction in quality oversight.
### 2. FDA Warning Letter–Derived Insights — Original Wording from the Supplied Analysis
The following passages are selections of the supplied analytical text. Bracketed numbers retain that analysis's original reference identifiers. They are **not verbatim FDA quotations**.
#### Finding 01 — Undefined investigation and CAPA escalation thresholds
**② FDA-derived analytical original:**
> Many quality systems suffer from critical gaps where procedures delegate the decision to initiate an investigation or CAPA to quality personnel, but fail to provide any specific criteria or guidelines on *when* a deviation actually warrants such actions [16].
**Regulatory finding / issue:** The same event may be treated as minor at one site and escalated at another. An absence of documented thresholds makes a streamlined pathway hard to defend.
**AskDona Assessment perspective:** Assess whether each triage decision applies an expert-approved SOP rule, records the event-specific rationale and identifies the required approval authority.
**Proposed AskDona solution:** Configure Excel-imported criteria for impact, patient/product risk, recurrence, detectability, status of released batches and SOP escalation triggers. Retrieve the SOP and event evidence with RAG; return a preliminary label, reasoning, quotations and source files. Escalate missing thresholds or ambiguous evidence as Cannot determine.
**Expected benefit:** More consistent triage rationale and earlier recognition of events that require fuller review.
**Related FDA link(s):** [ProRx LLC — 723704](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/prorx-llc-723704-04072026)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Supported.** ProRx (503B outsourcing facility, CDER): the firm's SOP stated that “QA determines if an investigation and/or CAPA is required”, and FDA found the firm “has not established clear criteria for determining when investigations should be initiated”; the revised SOPs still gave no criteria for when a deviation warrants a formal investigation and CAPA. “Delegate” is the analysis's word.
#### Finding 02 — Ticket systems can conceal formal CAPA triggers
**② FDA-derived analytical original:**
> To reduce the burden of formal CAPAs, some firms attempt to narrow their CAPA triggers to focus strictly on "systemic or recurring issues," while routing "individual and sporadic instances" to a simplified "ticket" or "production event" tracking system [14, 21].
**Regulatory finding / issue:** Ticket closure must not be mistaken for adequate evaluation of potential systemic failure or CAPA need.
**AskDona Assessment perspective:** Test whether routing to a ticket was justified and whether the selected path preserves trendability, ownership and escalation criteria.
**Proposed AskDona solution:** Assess ticket narratives, deviation histories, complaint links, CAPA procedures and closure records. Identify instances without disposition rationale, occurrence-history review or a controlled handoff to the QMS.
**Expected benefit:** A lighter workflow for genuinely low-risk events without losing visibility into potential CAPA candidates.
**Related FDA link(s):** [Exactech dba Advita Ortho — 720250](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/exactech-inc-dba-advita-ortho-720250-12192025); [O.N. Diagnostics — 730301](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/diagnostics-llc-730301-09012026)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Partly supported; the two cases are mixed.** The narrowing language belongs to **O.N. Diagnostics [21] only**: its CAPA procedure allowed a (redacted) “ticket” instead of a corrective action, and the revision aimed to “narrow the CAPA triggers and place more emphasis on systemic or recurring issues”, with “individual and sporadic instances” not requiring a CAPA. This is **firm SOP text**; FDA found the threshold had moved “from a safety hazard focus to systemic issues” and lacked clarity based on risk. “Production event” comes from **Exactech / Advita Ortho [14] only**, which had no written procedure for Production Events and did not treat them as quality data. “Simplified” is the analysis's word.
#### Finding 03 — Counterintuitive scoring can downgrade poorly detectable events
**② FDA-derived analytical original:**
> For example, if a firm's "Detectability" rating assigns a lower risk score to events that are "Low to Almost Impossible" to detect, recurring and hidden quality problems may go uninvestigated because they fail to hit the mathematical CAPA trigger [18].
**Regulatory finding / issue:** A documented score may be mathematically valid yet procedurally unsafe when scale direction or trigger logic is inconsistent.
**AskDona Assessment perspective:** Review the existence, version and internal consistency of the approved scoring matrix; distinguish evidence checks from actual risk computation.
**Proposed AskDona solution:** Compare SOP scoring definitions, assessment entries and justification fields; flag conflicting scale descriptions or unsupported scores. Use deterministic spreadsheet formulas or separately validated rules for numerical scoring, not unverified LLM arithmetic.
**Expected benefit:** Reduced false de-escalation risk and clearer documentation of the decision logic.
**Related FDA link(s):** [Phillips Precision — 697119](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/phillips-precision-inc-697119-12092024)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Supported, with a nuance.** Phillips Precision: the firm's “Detectability” rating, with “Low to Almost Impossible” as one definition, “does not associate lower ability to detect a nonconformity with a higher risk”, so “recurring quality problems may not be detected because a CAPA would not be initiated.” The score values are redacted, and “hidden” is the analysis's word.
#### Finding 04 — Minor classification without examination of underlying records
**② FDA-derived analytical original:**
> A common compliance failure involves classifying customer complaints or OOS results as "minor and unjustified" without a thorough investigation [24].
**Regulatory finding / issue:** The term minor cannot substitute for review of relevant batch, laboratory, equipment and prior-event evidence.
**AskDona Assessment perspective:** Define the minimum evidence package required even for abbreviated disposition, with additional review for OOS and product-impact uncertainty.
**Proposed AskDona solution:** Check whether batch and laboratory records, maintenance/cleaning logs, prior deviations and approved closure rationales are available and cited. Flag missing records without automatically asserting a regulatory violation.
**Expected benefit:** More defensible closure of low-impact cases and fewer unsupported no-investigation decisions.
**Related FDA link(s):** [Alchymars ICM SM — 542879](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/alchymars-icm-sm-private-limited-542879-02162018)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Supported, with tighter wording.** Alchymars (API): “minor and unjustified” is the **firm's own** classification of two customer complaints (black spots; out-of-specification moisture), which FDA criticised as made without a thorough review. Both were customer complaints rather than separate OOS results, and the letter does not use “OOS”.
#### Finding 05 — Critical product defects misclassified as minor
**② FDA-derived analytical original:**
> Firms occasionally categorize critical product issues, such as visible particulate contamination, as "minor" defects [2, 17].
**Regulatory finding / issue:** Misclassification can bypass criteria intended for serious contamination or product-quality impact.
**AskDona Assessment perspective:** Evaluate classification against the defect taxonomy and evidence of severity, rather than accepting the label entered by the investigator.
**Proposed AskDona solution:** Use expert-defined defect-code and escalation checklists to compare observations, photographs or text records when available, inspection instructions and applicable limits. Flag incompatibility between the documented defect description and assigned category for QA review.
**Expected benefit:** Fewer high-consequence events passing through low-risk pathways; improved coding consistency.
**Related FDA link(s):** [SCA Pharmaceuticals — 724202](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/sca-pharmaceuticals-llc-724202-09142026); [Pine Pharmaceuticals — 728537](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/pine-pharmaceuticals-llc-728537-08072026)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Pine supported; SCA not.** Pine [17]: an item that “meets the definition of particulate matter” was “classified as a ‘minor’ defect … without scientific justification” (the item's name is redacted, so “visible” is not confirmed). SCA Pharmaceuticals [2] classified particulates as **major**, not minor; FDA says extrinsic particulates “should be classified as critical”. Both are 503B compounding letters from CDER.
#### Finding 06 — Repeated low-impact events treated in isolation
**② FDA-derived analytical original:**
> When a firm experiences multiple repeated minor deviations—such as recurring packaging equipment issues that cause physical defects like broken tablets—treating each event as an individual, isolated occurrence with "no further action required" is an inadequate approach [19].
**Regulatory finding / issue:** Event-level triage is insufficient without a longitudinal look at recurrence and shared root-cause signals.
**AskDona Assessment perspective:** Include a criterion requiring review of comparable events over an approved lookback window and justification for absence of a trend escalation.
**Proposed AskDona solution:** Review historical event summaries or precomputed trend reports supplied to the repository; compare equipment, line, product, error code and event descriptions. Surface possible matches and missing trend assessments to investigators.
**Expected benefit:** Earlier review of recurring patterns while preserving abbreviated handling for isolated, demonstrably low-risk occurrences.
**Related FDA link(s):** [RemedyRepack — 649198](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/remedyrepack-inc-649198-05112023)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Supported, with a misquote corrected.** RemedyRepack (drug repackager): “multiple deviations for numerous broken tablets caused by your packaging equipment” were treated “as individual occurrences”, and the firm “determined no further action was necessary”. “No further action required”, “isolated” and “minor” are not the letter's words.
#### Finding 07 — Production events and alarms missing from consolidated quality evidence
**② FDA-derived analytical original:**
> If these production events are treated as benign and resolved via quick fixes or approved reworks without being consolidated and analyzed as quality data sources, the firm loses visibility of systemic process variability, creating a potential risk to distributed products [14].
**Regulatory finding / issue:** A light event-recording pathway must still feed the governed quality-data inventory and trend analyses.
**AskDona Assessment perspective:** Assess whether event sources and interfaces are defined and whether relevant production/alarm records were considered before minor closure.
**Proposed AskDona solution:** Evaluate exported alarm logs, production-event registers, batch records and quality procedures within the configured RAG evidence scope; report missing cross-references and uncertain coverage.
**Expected benefit:** Better quality-signal visibility and stronger explanations of why a production event did or did not escalate.
**Related FDA link(s):** [Exactech dba Advita Ortho — 720250](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/exactech-inc-dba-advita-ortho-720250-12192025)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Partly supported.** Exactech / Advita Ortho: Production Events “are not analyzed as quality data sources or escalated to CAPAs where appropriate”; “benign in nature” and “approved reworks” were the **firm's** investigation conclusions, which FDA rejected, stating “this does represent a potential risk to distributed product.” The word before “fix” is redacted, so “quick fixes” is not confirmed, and “consolidated” is the analysis's word.
#### Finding 08 — Deviations canceled without product-impact rationale
**② FDA-derived analytical original:**
> Simply cancelling open deviations that are deemed "low impact" without a documented, science-based investigation is a severe data integrity and quality system failure [23].
**Regulatory finding / issue:** Cancellation and closure should themselves be assessed as governed dispositions; neither removes the need for recorded reasoning and authority.
**AskDona Assessment perspective:** Test for a retained original event record, cancellation reason, product-impact evaluation, reviewer and approval evidence.
**Proposed AskDona solution:** Run criteria against deviation history, approval logs, event description, batch disposition evidence and SOP requirements. Return Cannot determine when the necessary authorization or evidence is not accessible.
**Expected benefit:** More reviewable cancellation decisions and reduced loss of accountability for quality events.
**Related FDA link(s):** [Genzyme Ireland — 728681](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/genzyme-ireland-limited-728681-06222026)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Partly supported.** Genzyme Ireland (biologics; issued by CBER): the firm “cancelled numerous deviations without investigating the root cause or assessing product impact”; its own retrospective review of 74 cancelled deviations found 36 required investigation. The letter does not say the deviations were deemed “low impact”, and “science-based” is the analysis's word.
#### Finding 09 — Inconclusive OOS laboratory root cause not escalated to manufacturing review
**② FDA-derived analytical original:**
> If laboratory root cause is inconclusive, the system must trigger a thorough production review—examining batch manufacturing records, raw materials, deviation history, and process capability—to identify potential manufacturing causes [1, 4, 8].
**Regulatory finding / issue:** A rapid disposition must not stop at an unconfirmed laboratory explanation, especially for OOS or atypical events.
**AskDona Assessment perspective:** Separate criteria for laboratory investigation completeness, confirmed assignable cause, manufacturing-impact evaluation and QA approval.
**Proposed AskDona solution:** Search laboratory investigations, manufacturing and material records, SOPs and batch histories; identify missing production review when laboratory causes are unconfirmed.
**Expected benefit:** Earlier identification of potentially insufficient OOS investigation scope.
**Related FDA link(s):** [TG United — 577583](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/tg-united-inc-577583-08012019); [Surmasis Pharmaceutical — 553686](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/surmasis-pharmaceutical-553686-11062018)
**Fact check (16 Oct 2026, against the linked FDA letters):** **Supported for all three.** Surmasis [4] and Signa [8]: when a laboratory root cause is not identified, “a thorough investigation of potential manufacturing causes must be performed”, covering batch manufacturing records, raw materials, process capability, deviation history and batch failure history. TG United [1] frames the same point as a remediation request (“include a thorough review of production”) rather than a stated rule.
### 3. Shared Operating Model — Risk-Proportionate Triage with Human Oversight
1. **Define the event and applicable procedure.** Identify site, product, lot, process step, date, event type and approved SOP revision. The Quality Unit owns applicable criteria and escalation authority.
2. **Collect the minimum evidence set.** Include event narrative, batch/lot status, potential patient/product impact, containment status, repeat history and relevant maintenance, laboratory or complaint records. Restrict the retrieval scope to controlled versions and the appropriate site/product.
3. **Apply a pre-approved criteria checklist.** AskDona checks whether each required element can be found, whether the documentation supports the recorded preliminary classification, and where evidence is missing or inconsistent.
4. **Separate evidence sufficiency from risk disposition.** Use labels such as **Evidence supported**, **Gap identified**, **Not applicable** and **Cannot determine**. Do not interpret **Cannot determine** as either a compliant closure or a confirmed violation.
5. **Require qualified review.** QA/QU personnel verify source quotations, decide streamlined versus formal investigation, determine CAPA applicability and approve the rationale in the QMS.
6. **Preserve event history and revisit trends.** Re-run an assessment at defined intervals or after complaint/trend signals; periodic re-execution is feasible, whereas always-on automated monitoring and cross-platform CAPA triggering require separate integration and validation.
#### 3.1 Illustrative decision pathways (not an automated regulatory determination)
| Possible path | Preconditions to verify | Ownership |
|---|---|---|
| Streamlined assessment | Approved site procedure permits abbreviated handling; specific event impact is justified; no unresolved serious defect, OOS, or significant recurrence signal; minimum records and approval are present | Qualified QA/QU reviewer |
| Full investigation | Product impact uncertain or potentially significant; critical defect; recurring pattern; incomplete preliminary assessment; other applicable escalation rule met | Investigation owner and QA/QU |
| CAPA evaluation | Suspected systemic cause, recurrence, ineffective previous corrections or other SOP-defined triggers | Authorized Quality Unit / CAPA board |
| Cannot determine | Required records, scope, thresholds or authorization cannot be verified | Human evidence request and decision |
### 4. Example AskDona Assessment Criteria for a Pilot
These are **proposed customer-configured checks**, not a claim that AskDona ships with validated GMP triage templates.
| ID | Proposed assessment criterion | Evidence to inspect | Gap / escalation signal |
|---|---|---|---|
| QEV-01 | The applicable SOP and approved classification thresholds are identified. | Deviation SOP; controlled revision | Missing or conflicting version |
| QEV-02 | The event narrative, affected product, lot and processing step are recorded. | Deviation/ticket; batch record | Context insufficient |
| QEV-03 | Product and potential patient impact have an evidence-backed rationale. | Impact assessment; disposition | Unsupported 'no impact' |
| QEV-04 | The defect classification follows the approved defect coding scheme. | SOP; defect log; inspection record | Potential misclassification |
| QEV-05 | Historical comparable events were considered over the defined period. | Trend report; event history | Recurrence not evaluated |
| QEV-06 | Equipment alarms and production events relevant to the case were reviewed. | Alarm log; equipment record; batch record | Signals omitted |
| QEV-07 | OOS/atypical cases satisfy applicable laboratory and production investigation rules. | Laboratory OOS; production records | Unconfirmed cause / missing review |
| QEV-08 | The decision to use a streamlined route is justified against approved triggers. | Triage worksheet; SOP | Unsupported shortened workflow |
| QEV-09 | CAPA applicability is explicitly reviewed, not inferred from a ticket label. | CAPA procedure; CAPA screening | No documented CAPA review |
| QEV-10 | Closure/cancellation includes rationale, approver and record retention. | eQMS history; sign-off | Unauthorized or untraceable closure |
| QEV-11 | Risk-score inputs and methods match the approved procedure. | Risk matrix; raw inputs | Inconsistent scale or formula |
| QEV-12 | Reclassification triggers after new evidence are specified. | SOP; PMS/trend review | No reassessment mechanism |
**Illustrative first-pass result**
```text
Criterion: QEV-05
Preliminary label: Cannot determine
Comment: The proposed minor-event closure references an isolated occurrence,
but the uploaded evidence does not include the required 12-month
similar-event trend review.
Evidence: No supporting trend record identified in the scoped repository.
Reference: Event E-1042; SOP DEV-07, revision 5 (illustrative only)
Human action: Obtain the controlled trend report; QA determines whether
an investigation or CAPA evaluation is required.
```
### 5. AskDona Capability Boundaries
| Function | Status supported by supplied materials | Safe customer-facing statement |
|---|---|---|
| Import existing criteria and evaluation templates from Excel | Documented current capability | Set up expert-defined triage checklists efficiently |
| Retrieve relevant passages from a selected RAG document repository | Documented current capability | Find supporting records for each configured check |
| Produce preliminary result, reason, quotation and source file | Documented current capability | Give reviewers an evidence-linked first-pass assessment |
| Prior questions, metadata filtering and conditional item exclusion | Documented current capability | Scope checks by facility, product, workflow or event category when configured |
| Preserve execution history and export assessed Excel file | Documented current capability | Create a review-ready initial evidence package |
| Apply an FDA-/GMP-approved universal minor-event classification | **Not established** | Quality experts define local procedure-specific thresholds |
| Automatically calculate validated risk scores / infer product safety | **Not established** | Use validated deterministic calculations and expert judgment |
| Continuously detect trends across live MES, LIMS, QMS, complaint databases | **Concept / integration-dependent** | Could be piloted with curated exports; live sync requires integration |
| Auto-open or close CAPA, deviations, batch disposition or electronic approvals | **Not established** | Final governed workflow stays in the authoritative QMS |
| Fully deterministic commercial assessments | **Not established generally**; separately demonstrated in controlled research conditions | Do not claim zero output variation across production contexts |
**Specific regulatory limitation:** Documenting a minor classification does not establish that the classification is correct. Also, absence of a relevant file in the scoped RAG repository is an evidence gap, not proof that the organization failed to create a record. For use in a regulated QMS, intended use, computerized-system assurance, controls for electronic records and reviewer procedures must be validated/qualified as applicable.
### 6. Proposed Pilot and Expected Adoption Impact
**Pilot scope:** One manufacturing site and one deviation category; sample 60–100 historical cases including true low-impact events, recurring low-severity cases, OOS investigations, production alarms, cancelled deviations and CAPA escalations. Prepare an independently adjudicated QA/QU reference set before testing.
**Test process:** Map SOP rules to 12 configured criteria; upload controlled event packages and supporting trend data; run assessments; have reviewers independently check citations, classification gaps and proposed escalations; record corrections. Include deliberately missing or contradictory evidence and test repeated runs.
| Measure | Definition / evaluation | Expected organizational effect (to validate) |
|---|---|---|
| Reviewer time | Median minutes spent retrieving and assessing evidence per case | Less administrative effort for low-risk events |
| Evidence coverage | Share of reviewed cases with complete minimum triage records | Stronger rationale for streamlined paths |
| Escalation sensitivity | Share of reference 'needs full investigation' cases not falsely marked clear | Minimize unsafe de-escalation |
| False escalation | Share of reference minor cases needlessly routed to full review | Fewer low-value full investigations |
| Trend review coverage | Share of cases with appropriate comparable-event review | Better systemic signal detection |
| Citation validity | Correct source passages and current document versions | More reviewable, audit-ready rationale |
| Human override rate | Frequency and reasons for QA disagreement with AI first pass | Feedback for criteria and prompt refinement |
| Output stability | Agreement in label, source file and quotation across repeated fixed-input runs | Detect reliability/validation concerns |
**Expected adoption benefits:** reduced manual evidence searching, better harmonization of triage rationales, fewer unjustified 'minor' dispositions, more consistent QA escalation, improved visibility into recurring production signals, and more investigator time for substantive root-cause analysis. These are prospective outcomes, **not measured GMP performance claims**. A previously shared security assessment PoC reported 91%+ answer accuracy and 45% workload reduction in its own context; those figures must not be transferred to deviation/CAPA work without validation.
### 7. FDA URLs — Full Copyable Markdown Links
The URLs below are carried over from the supplied FDA-derived analysis, with the same numbered references. Some entries are FDA inspection guidance rather than Warning Letters; all are **contextual references**, not proof that a specific FDA observation is universally applicable. **[Outdated — marked 2026-10-16]** The exact meaning of each case should be verified against the linked primary page before external distribution. **Updated (16 Oct 2026):** all 24 linked FDA letters were opened and each finding checked; the result is given as a “Fact check” note under each finding. Firm names, letter numbers and dates match; all 24 are Warning Letters (none is an inspection guide). Most are drug, API or compounding letters from CDER; [11], [12], [14], [18], [20], [21] and [22] are CDRH device letters, [23] is from CBER, and [10] concerns OTC drugs rather than cosmetics. [3], [5]–[7], [9]–[13], [15], [20] and [22] are listed but not cited in the text.
* [1] [TG United, Inc. - 577583 - 08/01/2019 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/tg-united-inc-577583-08012019)
* [2] [SCA Pharmaceuticals, LLC - 724202 - 09/14/2026 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/sca-pharmaceuticals-llc-724202-09142026)
* [3] [Sanofi - 690604 - 01/15/2025 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/sanofi-690604-01152025)
* [4] [Surmasis Pharmaceutical - 553686 - 11/06/2018 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/surmasis-pharmaceutical-553686-11062018)
* [5] [ALI Pharmaceutical Manufacturing, LLC - 645781 - 03/30/2023 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/ali-pharmaceutical-manufacturing-llc-645781-03302023)
* [6] [Pharmathen International S.A. - 723680 - 05/27/2026 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/pharmathen-international-sa-723680-05272026)
* [7] [Intas Pharmaceuticals Limited - 652067 - 07/28/2023 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/intas-pharmaceuticals-limited-652067-07282023)
* [8] [Signa SA de CV - 605219 - 07/14/2020 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/signa-sa-de-cv-605219-07142020)
* [9] [Abraxis Bioscience LLC - 633713 - 10/31/2022 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/abraxis-bioscience-llc-633713-10312022)
* [10] [Advanced Cosmetic Research Laboratories Inc. - 635176 - 09/26/2022 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/advanced-cosmetic-research-laboratories-inc-635176-09262022)
* [11] [Nipro Renal Solutions USA, Corporation - 732874 - 07/24/2026 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/nipro-renal-solutions-usa-corporation-732874-07242026)
* [12] [Medline Industries, LP - 677545 - 03/18/2024 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/medline-industries-lp-677545-03182024)
* [13] [Chemical Services Group, Inc./Royal Chemical Company - 648378 - 04/05/2023 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/chemical-services-group-incroyal-chemical-company-648378-04052023)
* [14] [Exactech, Inc. dba Advita Ortho - 720250 - 12/19/2025 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/exactech-inc-dba-advita-ortho-720250-12192025)
* [15] [Morton Grove Pharmaceuticals, Inc. - 505993 - 02/17/2017 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/morton-grove-pharmaceuticals-inc-505993-02172017)
* [16] [ProRx LLC - 723704 - 04/07/2026 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/prorx-llc-723704-04072026)
* [17] [Pine Pharmaceuticals, LLC - 728537 - 08/07/2026 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/pine-pharmaceuticals-llc-728537-08072026)
* [18] [Phillips Precision, Inc. - 697119 - 12/09/2024 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/phillips-precision-inc-697119-12092024)
* [19] [RemedyRepack, Inc. - 649198 - 05/11/2023 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/remedyrepack-inc-649198-05112023)
* [20] [ITL Asia Pacific Sdn Bhd - 590380 - 09/25/2019 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/itl-asia-pacific-sdn-bhd-590380-09252019)
* [21] [O.N. Diagnostics, LLC - 730301 - 09/01/2026 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/diagnostics-llc-730301-09012026)
* [22] [Medtronic, Inc. - 617539 - 12/09/2021 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/medtronic-inc-617539-12092021)
* [23] [Genzyme Ireland Limited - 728681 - 06/22/2026 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/genzyme-ireland-limited-728681-06222026)
* [24] [Alchymars ICM SM Private Limited - 542879 - 02/16/2018 | FDA](https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/alchymars-icm-sm-private-limited-542879-02162018)
---
**Positioning statement:** *AskDona Assessment can make proportionate investigation more defensible by checking whether expert-defined escalation rules, minimum case evidence, prior-event review and quality approvals are documented and consistent. It supports the first-pass evidence review; it does not make the final deviation, CAPA or batch disposition decision.*