On this page
How do you write pharmaceutical development in CTD P.2?
Explain why the proposed formulation, process, package and conditions of use were selected, using the actual development evidence. Connect important material attributes and changes to product performance. P.2 should make the design rationale understandable; a chronological list of experiments or a claim that all components pass specifications is not that rationale.
Before you begin
Marketing-application P.2 under M4Q(R1)/Q8(R2). Q8 does not prescribe clinical-research-stage submission contents; applicability to other product classes needs assessment.
What you will prepare: A reasoned development narrative linking design decisions to studies and the proposed control strategy.
P.2.1: explain the components and their interactions
Start from P.1 and the intended route and use. For the drug substance, discuss characteristics that can affect performance, such as relevant solubility, solid state or particle attributes, using actual development evidence. Explain substance–excipient compatibility and, for a product containing multiple active substances, relevant interactions between them.
For excipients, explain the selected function, concentration and performance-relevant characteristics. Use the development studies and supplier/material knowledge supporting the choice. “Commonly used” is not a complete rationale for an unstudied route or interaction. If an excipient identity, grade or material attribute is unknown, obtain it before claiming compatibility. The deeper M4Q narrative topics for substance and excipients sit within this FDA v4 electronic heading.
P.2.2: connect formulation history to the proposed product
Describe the important formulation changes and their reasons, distinguishing clinical formulations from the composition proposed in P.1. Link relevant comparative in-vitro or in-vivo evidence where appropriate; do not imply equivalence solely because the active ingredient is unchanged.
Address any overage and its justification explicitly. Explain the physicochemical or biological properties that determine product performance for the actual dosage form, for example reconstitution, dissolution, aggregation or potency when relevant. A record of development experiments should lead to a clear explanation of the final design, including unresolved limitations. Do not invent an overage percentage or a numerical target to fill a template.
P.2.3–P.2.4: justify the process and packaging choices
For P.2.3, explain selection and optimization of the manufacturing process, focusing on aspects affecting quality and performance. Reconcile the narrative with P.3.3 and describe meaningful differences between pivotal clinical-batch manufacture and the proposed process. Where relevant, explain the sterilization approach and its rationale; identify the evidence needed from manufacturing and microbiology specialists.
For P.2.4, evaluate the container system for storage, transport and use. Explain relevant protection, compatibility, material safety and delivery performance using packaging studies. Keep the suitability argument here and the component description/specifications in P.7. A material certificate does not by itself demonstrate dose delivery, low sorption or adequate barrier performance for this product.
P.2.5–P.2.6: support the conditions of use
For P.2.5, discuss the dosage form's applicable microbiological attributes. A decision not to perform a microbial-limits test on a nonsterile product needs a rationale, not an empty row. Where a preservative system is used, address selection and effectiveness. For sterile products, address the container system's role in preventing microbial contamination. Distinguish these development questions from an isolated passing release test.
For P.2.6, connect the product's compatibility with diluents and administration devices to the proposed instructions. Identify tested materials, concentrations, contact periods and conditions; describe relevant precipitation, sorption or stability observations. If proposed use extends beyond what was studied, flag the gap and obtain the appropriate technical assessment before asserting support for the labeling.
Worked review: the administration set was never evaluated
Fictional exercise: a solution was studied in one administration set, while a draft instruction permits any set for a longer infusion. The P.2 narrative says compatibility is established.
Map the study's actual conditions to each proposed instruction. Ask the formulation and clinical/regulatory owners to evaluate the unsupported materials and exposure time, then obtain evidence or revise the proposal as appropriate. Review P.8 in-use stability and the labeling together. Do not replace the missing compatibility assessment with a statement that all components meet their individual specifications.
Write from decisions, not a chronology of experiments
Use this editorial decision record to turn development history into an explanation of the proposed product.
| Decision | Supporting evidence to identify | Link to the final proposal |
|---|---|---|
| Material or grade selection | Relevant attributes, compatibility and performance work | Composition and excipient controls |
| Formulation choice | Options studied, important results and reasons for selection | P.1 and the clinical formulation relationship |
| Process selection | Development findings affecting quality and performance | P.3 process and controls |
| Package selection | Protection, compatibility, safety and delivery evidence | P.7 components and P.8 stability |
| Use conditions | Tested diluents, devices, duration and handling | Proposed instructions and in-use claims |
A rejected option can be useful evidence when it explains the selected design. Include the reason it was rejected and the relevant observation rather than a long narrative of every unsuccessful experiment. Separate measured results from a development hypothesis still requiring confirmation.
Writing exercise: “The process was optimized” does not tell a reviewer what was learned. Replace it with the attribute or performance question considered, the evidence supporting the selected conditions, and the boundary of that conclusion. Do not invent ranges or a design-space claim when the development record supports only a narrower operating proposal.
Check the clinical biopharmaceutic summary when formulation changes affect the clinical bridge. Reconcile P.8 stability when proposed use includes opening, dilution or a different administration system. A conclusion is only as broad as the product and conditions its evidence supports.
Your preparation checklist
0/3 checkedUse this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.
Frequently asked questions
How is P.2 different from the product manufacturing section?
P.2 explains the development rationale and choices affecting product quality and performance. P.3 describes the proposed manufacturing process and its controls. The two should agree about the selected process, while P.2 explains why it was selected rather than duplicating the operating narrative.
Does pharmaceutical development require a design-space claim?
Do not invent a design-space claim merely to make the section appear sophisticated. Explain the development approach and knowledge actually supported by the program. Any proposed design space needs its own scientific basis and appropriate regulatory treatment; routine process ranges are not automatically a design space.
Does meeting component specifications prove product compatibility?
No. Specifications address defined component characteristics, while compatibility concerns the product, materials and actual conditions of storage or use. Connect the claim to relevant development studies and limitations. Individually acceptable components can still require an assessment of their interaction in the proposed system.
Can instructions permit any administration device after testing one device?
Do not generalize without a supported assessment. Identify the tested materials, conditions and duration, compare them with the proposed instructions, and obtain the relevant technical conclusion. Keep any gap explicit or revise the proposal rather than extending the study’s scope through broad wording.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Guidance
ICH M4Q(R1): CTD Quality ↗Step 4, September 12, 2002; Module 3, printed pages 5–18. Organization/content guidance, not a universal list of required studies. Checked September 22, 2026. Guide-specific passages: 3.2.P.2.1–3.2.P.2.6 and internal narrative subdivisions, printed pages 12–13.
Guidance
FDA Q8(R2): Pharmaceutical Development ↗Final, November 2009, revision 2; Part I introduction/scope and pharmaceutical development. PDF and current FDA status page inspected. Checked September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 3.2.P.2. A heading identifies placement, not mandatory applicability.

