Comment from Jitendra Pund

Dear Sir/Madam, Please find herewith my comments on Responding to FDA Form 483 Observations at the Conclusion of a Drug CGMP Inspection: Draft Guidance for Industry. 1. To strengthen expectations for documenting investigation scope and rationale during FDA inspections, it helps to frame requirements in a structured way that auditors recognize as proof of compliance and scientific integrity. The draft appropriately recommends an investigation report and, where applicable, a cross functional risk assessment. To strengthen its actionability, the guidance should encourage firms to document not only what was investigated, but also: •Boundary Determination Explain how the scope of the investigation was defined, including the criteria used to set boundaries. •Inclusion/Exclusion Rationale Justify why certain related areas were included or excluded, showing risk-based reasoning rather than convenience. •Information Sources Identify the data and records reviewed to assess recurrence or spread (e.g., trending reports, prior deviations, audit trails). •Scope Sufficiency Rationale Provide a clear rationale for why the investigation scope was sufficient, demonstrating that broader risks were considered and ruled out. 2. Because this draft addresses a longstanding area of variability in industry practice, FDA may wish to strengthen its utility by adding an appendix with a model response framework. A simplified example would help firms not only understand the expectation but also see how to organize a complete, concise, and risk-based response. Such a framework could illustrate how a firm might present: •Observation Summary Concise description of the issue observed. •Significance Assessment Evaluation of product quality, patient safety, and regulatory impact. •Scope & Systemic Review Boundaries defined, related areas considered, and systemic implications assessed. •Root Cause Analysis Scientific rationale for the identified cause, with rejected hypotheses documented. •Interim Actions Immediate containment or mitigation steps taken pending CAPA. •CAPA Plan Corrective and preventive measures, linked to risk assessment outcomes. •Timelines Defined milestones for investigation closure and CAPA implementation. •Effectiveness Checks Verification strategy to confirm CAPA success and prevent recurrence. 3. The draft guidance notes that observations may be grouped by general area or by system, and that repeat observations and trends may reveal systemic issues. This is an important point. The guidance could be strengthened further by explicitly encouraging establishments to classify each observation according to its systemic significance. Specifically, firms should indicate whether the observation is best characterized as: •Isolated event •Recurring issue within a single system •Cross-functional issue affecting multiple systems •Site-wide issue •Multi-site or corporate oversight issue •Issue involving external partners such as contract facilities or suppliers This type of classification would improve the quality of management review and remediation prioritization. It would also help distinguish between local execution failures and broader governance or quality-system weaknesses. That distinction is often critical to determining the adequacy of the response and ensuring that corrective actions are appropriately scaled to the level of risk. Regards Jitendra Pund