Start With the Decision, Not the Meeting Name
A model-related regulatory question can concern a specific development decision, the scientific approach supporting that decision, or whether a method may be suitable for use beyond one development program. Those are different questions, even when the same model or analysis is involved. Choosing an interaction pathway therefore starts with clarifying what answer is needed, not with choosing the most familiar meeting label.
This tutorial uses four broad pathway categories: formal meetings, scientific advice, qualification procedures, and written consultations. Their names, availability, and procedures differ across regulatory authorities. The categories are a practical way to reason about the kind of interaction sought; they do not imply that every authority offers an identical route or that a particular route guarantees a particular regulatory outcome.
The earlier material on binding decisions, scientific advice, and nonbinding feedback distinguishes the status of regulatory statements. Here the emphasis is different: given a defined model question, how should a development team select a suitable way to raise it?
Classify the Question Before Selecting a Route
First identify the object being assessed. A question about whether a particular model supports a dose-selection decision in a particular development program is project-specific. A question about whether a modeling method is suitable for a defined type of use across products or programs is method- or tool-focused. A question can contain both elements; in that case, separate them rather than assuming one interaction can resolve both.
Next state the answer needed. The team may need an exchange to clarify a complex scientific issue, advice about a proposed development strategy, assessment of a method for a defined intended use, or a focused response to a narrow question. These aims are not interchangeable. For example, a response about a general method’s suitability does not automatically decide whether a specific model is adequate for a particular product decision.
| Question feature | Likely pathway emphasis | Reasoning |
|---|---|---|
| A project-specific issue needs structured, interactive discussion | Formal meeting | Useful when the team needs to present context, hear responses, and discuss linked questions. |
| The team seeks the authority’s scientific view on a development question | Scientific advice | Frames the request around advice on a proposed scientific or development approach. |
| A method’s suitability for a defined intended use is the central issue | Qualification procedure | Focuses on the method or tool and the scope of its intended use, rather than deciding one product’s full application. |
| A narrow, clearly specified issue may be handled through a document-based exchange | Written consultation | May suit a focused request when an interactive discussion is not necessary and the authority’s procedures permit it. |
These are not universal eligibility rules. Authorities may use different terms, combine stages, or require particular submission and scheduling procedures. The team should check the relevant authority’s current process before relying on a pathway. The table helps frame the substantive choice; it does not replace procedural requirements.
A Practical Matching Logic
A useful selection follows from the relationship between the unit of the question and the unit of the answer. If the question concerns one development program, the desired answer should address the proposed use in that program. If the question concerns a method intended for repeated use, the answer sought must address that method within a specified context of use. A mismatch—such as seeking broad recognition of a method through a narrowly framed product question—risks an answer that does not resolve the actual need.
Then consider whether the question benefits from live interaction. Multiple linked questions, important assumptions to explain, or uncertainty that may require clarification can support seeking a formal meeting or scientific advice, depending on the authority’s routes and the purpose of the request. A narrow question with a complete written rationale may be suitable for written consultation if available. For a method-focused qualification question, a document-based submission may still involve formal review and interaction; “qualification” describes the assessment purpose, not necessarily a single communication format.
Write one sentence describing what the team needs the authority to clarify, advise on, or assess. Avoid starting with a preferred meeting label.
Decide whether the issue is specific to a product or program, concerns a method’s intended use, or contains separable questions at both levels.
Consider whether discussion and clarification are important, or whether a focused written response could address the question adequately under the authority’s procedures.
Ask when the answer is needed to inform development, what evidence is available, and whether the chosen route is available at that stage.
Make clear the proposed use, evidence limits, and remaining decisions. Do not treat advice or a method-focused assessment as an automatic product-level conclusion.
This logic is justified by the consequences of an ill-matched request. If the requested answer is broader than the question and evidence presented, the authority may be unable to address it. If the requested interaction is more elaborate than needed, the team may spend time preparing for a format that does not improve the answer. Matching scope and format to the decision keeps the request answerable and the eventual response interpretable.
Worked Example: A Project-Specific Dose Question
Hypothetical scenario. A team developing an oral medicine has a population pharmacokinetic model and exposure-response analysis. Before a planned clinical study, it wants regulatory input on whether its proposed model-based dose-selection strategy is scientifically justified for the study population. The team expects to explain assumptions about adherence, covariates, and the target exposure.
Classify the question. The object is a proposed strategy in one development program, not a method intended for general use. The desired answer concerns the scientific acceptability of the planned approach in the stated context.
Match the pathway. If the authority’s process permits it, scientific advice is a natural fit when the primary aim is the authority’s scientific view on the proposed development approach. A formal meeting may be preferable where the issue involves several linked questions and the team needs interactive discussion. A written consultation may be considered if the question is narrow and the authority provides a suitable route, but it may offer less opportunity to clarify assumptions in real time.
Check timing and limits. The interaction should occur early enough for the answer to inform the study plan. The request should present the model’s intended role, key evidence, uncertainties that could affect the decision, and the exact question. Even a favorable scientific view would not, by itself, guarantee acceptance of every later model application or a particular regulatory decision.
Worked Example: A Method Intended for Broader Use
Hypothetical scenario. A research group has developed a model-based method for estimating a renal-function-related dose adjustment. It hopes the method could be used across multiple products in a defined class of situations. Its main question is whether the method is suitable for that intended use, given a specified evidence package and applicability limits.
Classify the question. The primary object is a method and its proposed intended use, rather than one product’s immediate development decision. The request must define where the method is meant to apply and where it is not.
Match the pathway. A qualification procedure is the most directly aligned category when the aim is an authority assessment of a method’s suitability for a defined intended use. The request should not imply that qualification would establish suitability in every population, product, or decision context. If a separate product-specific decision is also pending, that issue should be stated separately and may require a different interaction.
Check evidence and scope. The group should show how the supporting evidence relates to the proposed use and identify limitations that could change its applicability. If evidence supports use only in a narrower setting, the intended use should be narrowed accordingly rather than claiming broader suitability than the evidence supports.
Worked Example: A Narrow Question About an Analysis Plan
Hypothetical scenario. Before analyzing data from a planned study, a sponsor wants to ask whether a proposed simulation-based sensitivity analysis addresses a specified uncertainty in the model used for a particular development decision. The question is tightly bounded, the analysis plan is short, and no related issues require discussion.
Classify the question. This is project-specific and focused on one planned analysis. The sponsor is not seeking broad assessment of the simulation method or a decision on the full development program.
Match the pathway. A written consultation may be efficient if the relevant authority offers that option and the question can be answered from the written material. The request should define the uncertainty, explain how the analysis varies the relevant assumption, and state how different outcomes could affect the decision. If the issue is entangled with other scientific questions or requires iterative explanation, a more interactive route may be more suitable.
Check what remains unresolved. A response about the analysis plan would not automatically endorse the underlying model or the final decision. Those are distinct questions and should not be inferred unless they were explicitly within the request and supported by the evidence reviewed.
Development Stage, Evidence, and Failure Modes
The development stage matters because it determines what decision is approaching and what evidence is available. Early interaction can inform plans for data collection, model evaluation, and study design; later interaction may address a more specific application supported by additional evidence. The best timing is not simply “as early as possible”: the question must be mature enough to answer, while the answer must arrive in time to influence the decision.
The request should make the model’s intended role and limitations clear. Earlier material on context of use and decision-focused evidence is directly relevant: the authority needs to understand which decision the model informs, what evidence supports that use, and which uncertainties could alter the conclusion. A route cannot compensate for an unclear question or an evidence package that does not address the proposed use.
- Choosing a format before defining the question. “We need a meeting” does not say whether the issue is project-specific advice, a method assessment, or a narrow written question. State the question first.
- Treating qualification as a product endorsement. Assessment of a method for a defined use does not automatically decide whether a particular product should receive a particular dose or label.
- Assuming written means informal or non-substantive. A written process may still be a structured regulatory interaction. Its status and implications depend on the authority and procedure.
- Assuming a meeting guarantees resolution. A meeting can enable discussion, but the authority may identify evidence gaps, qualify its response, or leave the final decision for a later review.
- Combining unrelated questions. A request that mixes a method’s broad suitability with a product-specific decision can obscure what answer is being sought. Separate the questions and explain their relationship.
- Ignoring procedural availability. A substantively sensible route may not be available in the desired form or at the desired stage. Verify current authority procedures before planning the interaction.
Comparing the Main Alternatives
There is no universal ranking in which one pathway is always “stronger.” The appropriate comparison is functional: which route best aligns the requested answer, question scope, interaction needs, and timing? A formal meeting emphasizes structured discussion; scientific advice emphasizes obtaining the authority’s scientific view on a development issue; qualification emphasizes assessment of a method for a defined intended use; written consultation emphasizes a document-based response to a focused question, where available.
These categories can overlap in practice. A method-focused assessment can include meetings or written exchanges, and a scientific advice process may involve structured documentation. The distinction is the principal purpose of the request, not necessarily the number of communications. Where a question spans categories, identify the primary question and avoid implying that one response will settle decisions outside its scope.
Check Your Understanding
For each scenario, identify a suitable pathway emphasis and explain the key limitation. Solutions follow each question.
- A team needs advice on a proposed model-informed study design for one product and has several linked assumptions it wants to discuss. What pathway emphasis fits best, and why?
Solution: Scientific advice or a formal meeting is the appropriate emphasis, subject to the authority’s procedures. The question is project-specific, and linked assumptions make interaction useful. A formal meeting may fit when structured discussion is especially important; scientific advice frames the request around the authority’s scientific view. Neither route guarantees that the proposed design will be accepted. - A consortium wants an authority assessment of whether a modeling method is suitable for a narrowly defined intended use across programs. Which pathway is most directly aligned?
Solution: A qualification procedure is most directly aligned because the object is the method and its defined intended use. The consortium must not present the result as blanket endorsement for settings outside that use or as a decision on every product that might apply the method. - A sponsor has one concise, well-supported question about a planned sensitivity analysis and does not need live clarification. What route could be considered, and what must be checked?
Solution: A written consultation could be considered if the authority offers a suitable process. The sponsor should verify procedural availability and provide enough context for the question to be answered. The response should not be interpreted as approval of the entire model or development strategy unless those matters were explicitly assessed. - A team asks for qualification of a method but mainly wants a decision about the dose for one product. What is the mismatch, and how should it be corrected?
Solution: The requested route and the actual decision are mismatched: qualification concerns a method’s suitability for a defined intended use, whereas the immediate question is product-specific. The team should clarify whether it seeks product-specific scientific advice or a formal discussion, and separately state whether broader method qualification is also needed. The evidence and intended use should be scoped to each question.