Published on 22/12/2025
Knowing When to Seek Clarification from Regulatory Authorities
Introduction: The High Stakes of Misinterpreting Regulatory Queries
During the lifecycle of drug or device development, regulatory agencies such as the U.S. FDA, European Medicines Agency (EMA), and Japan’s PMDA often send communications that include questions, comments, or observations. These queries may arise in response to:
- Clinical Trial Applications (e.g., IND, CTA)
- Marketing Authorizations (e.g., NDA, BLA, MAA)
- Post-approval changes (e.g., CBE, PAS)
- Annual reports and risk management plans
Misinterpreting a regulatory query can have severe consequences—ranging from incomplete responses and prolonged review timelines to outright rejection. That’s why requesting clarification is not just acceptable, but often necessary. However, the timing, content, and tone of such requests must be handled with utmost professionalism.
Scenarios Where Clarification Should Be Requested
There are several circumstances under which sponsors should consider seeking clarification:
- Ambiguous Language: The query contains undefined or vague terms, such as “adequate justification” or “compliance gap.”
- Incomplete Context: The agency’s comment references a section or table that is not clearly identifiable in the sponsor’s submission.
- Contradictory Statements:
Agency Guidelines on Communication for Clarification
Most agencies offer formal or informal mechanisms for clarification. Here’s how it works across major regulators:
- FDA: Sponsors may submit a formal Information Request Clarification under Module 1.1.2 of eCTD. Informal communication may be routed via RPM (Regulatory Project Manager).
- EMA: Clarification questions must be submitted during the “clock-stop” period. Communication goes through the Rapporteur or Coordinator via the Common Repository.
- PMDA: Clarifications are often addressed during face-to-face consultations or by letter exchange. English-language queries are accepted with Japanese translation.
Many agencies recommend sponsors first attempt to interpret queries internally, involving cross-functional experts before reaching out.
Continue with How to Structure a Clarification Request, Examples, and Risk Management
How to Properly Structure a Clarification Request
A well-written clarification request increases the chance of timely and useful feedback. Follow this structure:
- Header: Include application number, product name, and correspondence ID
- Reference to Agency Query: Restate the exact query or comment, including section and page numbers
- Observed Ambiguity: Clearly identify the ambiguity or point of confusion
- Request for Clarification: Politely frame your clarification question, e.g., “Could the agency confirm whether a reanalysis of Arm B data alone is sufficient?”
- Proposed Action (Optional): If applicable, suggest a course of action for approval
Example Clarification Request Letter
Here is a simplified example from a real FDA IND submission:
| Agency Comment | The sponsor is requested to justify the sample size considering dropout rates observed in prior studies. |
|---|---|
| Clarification Request | We request clarification on whether the agency refers to the dropout rate observed in Study 102 or 103. Both studies report different discontinuation rates (Study 102: 18%; Study 103: 9%). Kindly confirm the preferred comparator for our sample size justification. |
When NOT to Request Clarification
Not all confusion warrants regulator engagement. Avoid sending a clarification request in the following cases:
- Minor Typos: If the question is clear despite minor grammatical issues
- Readily Researchable Items: When a simple literature or guidance review resolves the issue
- Scope Creep: Using the clarification request to sneak in new data or arguments
- Time Constraints: If clarification may delay submission beyond review window
Managing Timelines and Follow-Up
Regulatory clock-stop or response periods are typically tight—30 days (FDA), 90 days (EMA) for major submissions. Therefore:
- Send clarification requests within the first 20% of your allowed window
- Set internal timelines for agency reply and response preparation
- Escalate internally if no agency feedback is received within 5–7 business days
Use document management tools (e.g., Veeva Vault, MasterControl) to log outgoing clarification letters and inbound responses.
Real-World Case Example: EMA Clarification on Clinical Endpoint Definition
A sponsor received an EMA question on “clinically meaningful improvement” in their asthma trial but lacked clarity on the agency’s preferred definition. The sponsor submitted a clarification:
“The sponsor seeks clarification whether EMA’s definition of ‘clinically meaningful improvement’ aligns with a ≥12% change in FEV1, or if an alternative endpoint (e.g., ACT score ≥3) is acceptable.”
EMA responded via the Rapporteur that either endpoint would be acceptable if supported by a literature-based rationale. This prevented the sponsor from running unnecessary analyses.
Public Registries and Communication Transparency
While many clarification requests remain confidential, some agencies document summaries of back-and-forth correspondence:
- PMDA RCT Portal: Annotated regulatory feedback summaries
- ClinicalTrials.gov: May contain sponsor notes on agency interactions
These resources provide learning opportunities for crafting better clarification requests.
Conclusion: Asking Smart Questions Shows Regulatory Maturity
Sponsors must not fear requesting clarification from agencies—when done correctly, it demonstrates diligence, respect for the process, and commitment to quality. A concise, respectful clarification request can prevent misunderstandings, reduce risk of rejection, and accelerate review.
Build SOPs around clarification workflows, train regulatory teams to identify when engagement is warranted, and maintain transparent records of all interactions. In regulatory affairs, sometimes the smartest move is asking the right question.