intended purpose; or what documentation is required for a constrained packaging change. Poor CC topics include: sweeping policy proposals, broad “advise us on our development plan,” or during-cycle issues unrelated to PSG teleconferences or Covered Product Authorizations. FDA’s guidance also explains that if a BE protocol merits a formal protocol review outside the CC process, it should be submitted via the CDER NextGen Collaboration Portal under the appropriate pathway; when the issue is a specific question not covered by a PSG, FDA recommends using CC instead of protocol review.

Finally, align expectations with GDUFA III performance goals. FDA aims to respond to Level 1 CCs within 60 days, Level 2 (more complex/multidisciplinary) CCs within 120 days, and to clarify ambiguities in a CC response within 21 days once such a clarification request is submitted. Those timeframes guide planning and vendor contracts around BE, CMC, and labeling workstreams.

Choosing the Right Track: CC vs. Pre-ANDA Meetings, PSGs, and EU Scientific Advice

Regulatory friction often comes from picking the wrong channel. Use CC when one specific, document-citable answer will unblock progress. For multi-question, interconnected issues—e.g., a complex locally acting product with device, Q1/Q2, and modeling elements—request a pre-ANDA meeting instead. FDA’s guidance distinguishes CC from meetings: meeting requests serve a different purpose, include different materials, and are treated separately by the Agency. For PSG-covered products, first read the PSG end-to-end; then decide if your issue is (1) a precision question that CC can resolve (e.g., a small schema deviation), or (2) a broader design discussion better handled in a meeting.

Remember there is no one-to-one EU equivalent to US CC. In the EU/UK, sponsors typically pursue scientific advice with the EMA/CHMP (or nationally) for development questions. If your global plan needs alignment, use CC to nail US-specific points and EMA scientific advice to handle EU expectations and comparators; reconcile outputs in your global development protocol and your Module 2.3/2.5 narratives.

Decision tree for US generics teams:

• Single, narrow question whose answer can be implemented quickly → Controlled Correspondence.
• Multiple interdependent questions (especially for complex products) or need for back-and-forth → pre-ANDA meeting.
• PSG exists but you propose a justified alternative → CC to evaluate the alternative; keep justification concise and data-anchored.
• Formal BE protocol review (outside CC) is warranted → submit via CDER NextGen under the protocol-review pathway noted in FDA’s guidance.

What to Ask—and How to Frame It: Question Design That Yields Actionable Answers

FDA can answer faster and more decisively when your submission presents a decision-ready question with the minimum information needed to assess it. In practice, that means your CC should be on corporate letterhead (dated within ~7 days of submission), identify the authorized requester/agent (attach a Letter of Authorization when an agent files on your behalf), and include contact information and a clear, one-paragraph ask that cites the specific strength, RLD, and module context. The guidance lays out these content expectations and notes FDA will not treat submissions lacking proper authorization as CC under GDUFA III.

Draft your question against a short evidence pack, not a data dump. For example:

• Inactive ingredient level: state the proposed level by strength, justify with safety/precedent data (e.g., IID, literature), and ask whether FDA agrees the level is acceptable for the proposed product. Do not ask FDA to search the IID for you or to opine without a strength-specific proposal.
• Analytical approach: present the intended use (release vs. characterization), key parameters (range, sensitivity), and why the method is fit for purpose. Ask whether FDA agrees this approach is adequate for the intended control.
• BE design nuance: if the deviation from PSG is narrow (e.g., sampling windows, fed/fasted rationale, analyte handling), summarize the deviation and justification, then pose a yes/no-style question. For broader departures, prefer pre-ANDA engagement.

Structure every CC around a single verifiable conclusion you want FDA to confirm (“Does FDA agree that…”). If you truly have multiple unrelated questions, split them—FDA may triage across disciplines, and mixing orthogonal topics can slow assessment. Reserve narrative detail for appendices with tight figure/table labels; your main text should remain a one-page brief with an unambiguous, numbered question and an itemized list of attachments.

Submission Mechanics: CDER NextGen Portal, Event IDs, and Attachments

Submit CCs electronically via the CDER Direct NextGen Collaboration Portal using a corporate email. The portal routes requests to OGD/OPQ disciplines, issues status notifications, and returns written responses through the same account. FDA strongly discourages sending CC to individual staff or duplicating via courier/fax; if you cannot use the portal, email to the generic-drugs mailbox is permitted, but all communications will then occur via email and won’t be captured in the portal workflow.

Operational tips to prevent “tech-rejection” friction:

• Identity & authority: ensure the submitter is the manufacturer/related industry (or authorized agent) and include the LOA in the CC package; otherwise FDA will not treat the inquiry as a CC under GDUFA III.
• Evidence hygiene: anchor every attachment (tables/figures) with IDs that will later become named destinations when you cite them in an ANDA. Avoid scans; submit searchable, font-embedded PDFs.
• Right mailbox for IID: don’t send IID questions to the CC mailbox; engage the IID appropriately and provide only the inactive ingredients you want FDA to evaluate in the CC.
• NextGen benefits: the portal provides real-time status and notifications around CC submissions—use it to synchronize internal timelines with GDUFA goal dates.

Finally, “publish” your CC internally like a mini-submission: a cover memo (ask + rationale), numbered attachments, and a log of file hashes. If the CC informs a protocol or specification, mirror the same language in your Module 2.3/3/5 drafts to avoid later inconsistencies.

Timelines & Tracking Under GDUFA III: Level 1 vs. Level 2, Clarifications, and Planning Buffers

Time is money in generics, so plan your buffers around FDA’s performance goals. Under GDUFA III, FDA will review and respond to 90% of Level 1 CCs within 60 days of submission and to 90% of Level 2 CCs within 120 days. When FDA’s written response contains an ambiguity—defined in the commitment letter as a response (or critical portion of it) that merits further clarification—FDA will respond to 90% of clarification requests within 21 days of receipt. Submit your clarification request within seven calendar days of the original response and under the same event ID; submit later and it becomes a new CC with a new clock. Use these clocks to stage BE vendor starts, PPQ runs, or labeling redlines.

Working with Level 2 topics. Expect Level 2 timelines for questions that are inherently more complex or multidisciplinary (e.g., complex products, device-drug interfaces, significant deviations from PSG design). Where feasible, narrow the ask to fit Level 1—e.g., break apart a multi-facet inquiry into sequenced, specific questions that FDA can answer definitively without cross-consults.

Internal SLAs. Build a house SLA that matches the GDUFA clocks: a 48-hour completeness check on any FDA request for additional information (which can pause the clock while outstanding), a seven-day window for clarification requests, and a two-click evidence rule (your team must be able to map every claim in the ask to a table/figure in your attachments in ≤2 clicks). Treat the CC package as inspection-ready—your ANDA will quote it.

Discipline-Specific Patterns: CMC, BE, and Labeling Questions That Land

CMC (Module 3): Target attribute-level questions that FDA can confirm without re-reviewing your entire control strategy. Examples: “Does FDA agree that x% of [excipient] is acceptable for the 10-mg strength of [RLD], given the attached IID precedent and safety literature?” or “Is the proposed dissolution apparatus/speed acceptable for an IR tablet where the PSG is silent, based on the attached discrimination data?” Provide attribute tables, method capability snippets, and, if relevant, comparability outlines. Avoid asking FDA to endorse an entire validation package—ask about the sufficiency of a specific approach for a stated purpose.

Bioequivalence: When a PSG exists, quote the relevant section and specify the exact deviation (e.g., sampling windows, fed vs fasted). When a PSG does not exist or is silent, present literature/RLD rationale and ask whether FDA agrees your design meets the intent of BE demonstration. The guidance clarifies when CC is suitable versus when a formal BE protocol review or pre-ANDA engagement is preferable; use that to choose the right lane.

Labeling: CC can help resolve discrete cross-references (e.g., whether a specific carved-out statement remains accurate given RLD changes) or SPL formatting specifics with regulatory impact. Keep labeling CCs surgical; broader PI alignment belongs in assessment-cycle communications, not CC.

Facilities/DMF touchpoints: CC is not a forum for DMF assessment discussions, but it can clarify submission mechanics (e.g., how to reference a DMF or how a particular change should be filed). Include LOAs and precise identifiers. For changes that hinge on DMF assessment, expect FDA to steer you to the standard DMF processes and timelines referenced in the GDUFA III letter.

Templates & Evidence: Attachments, LOAs, and “Just Enough” Context

One-page core + smart appendices. Your main page should carry: (1) the Ask (one paragraph, yes/no-style when possible); (2) Context (RLD, strengths, PSG citations if any); (3) Why Now (decision you’re trying to make: start BE, lock specs, trigger vendor); and (4) Attachment index (tables/figures with IDs). Place data in numbered appendices. Don’t bury your ask under narrative; reviewers should see the question within 10 seconds of opening the file.

Authority & identity. If an agent files the CC, include a Letter of Authorization (LOA) with each submission; without it, FDA will not treat the filing as CC under GDUFA III. Use a corporate email in the portal; general/personal accounts may not be accepted as CC submissions.

Right level of detail. Provide just enough to support a decision: a discrimination plot, a side-by-side excipient precedent table, a succinct BE schematic. Omit full protocols unless the guidance indicates protocol review is the correct path. Where your question intersects the Inactive Ingredient Database (IID), present your exact proposed level(s) and the specific RLD/strength—do not ask FDA to conduct a general IID search.

After the response. If an answer contains an ambiguity, submit a single clarification request within 7 calendar days under the same event ID; FDA’s goal is to respond to 90% of such requests within 21 days. Mirror FDA’s position in your internal specifications, protocols, or label drafts immediately so your ANDA reflects the same language and logic.