On this page
How should CTD 3.2.S.2 describe drug substance manufacturing?
Connect the actual sites and process sequence with material controls, critical steps, relevant validation or evaluation, and development history. Show which process version produced the supporting material. The narrative, flow diagram and evidence should describe the same manufacturing proposal, including transfers, storage and significant changes.
Before you begin
Chemical and biotech substance manufacturing narratives under M4Q(R1); scientific evidence and validation expectations remain product- and process-specific.
What you will prepare: A process narrative and control map traceable to the proposed manufacturing process and executed development evidence.
Sections covered in this guide (7)
S.2.1–S.2.2: follow the process across real sites
For S.2.1, obtain the controlled site roster and state each manufacturer's name, address and responsibility, including contractors and testing sites. Distinguish legal entity from physical facility; a headquarters address cannot identify an unlisted manufacturing operation.
For S.2.2, reconcile a process flow diagram with a sequential narrative at the proposed scale. Chemical routes need the relevant materials, transformations, operating conditions, intermediates and controls; explain alternate routes and reprocessing rather than hiding them in a footnote. For biotech manufacture, follow the cell-bank vial through culture, harvest, purification/modification, filling, storage and transport. Explain batch definition, pooling and transfers. A reader should locate every material entry and control point in both the drawing and narrative. Missing ranges go back to the process owner; do not fill them from an example dossier.
S.2.3–S.2.4: explain materials and critical decisions
In S.2.3, map each starting/raw material, reagent, solvent and other relevant input to the step where it is used and the quality control that supports its intended use. For biological materials, obtain origin and safety records; for cell substrates, include the applicable source/history, construct and cell-bank control information. Cross-reference the detailed adventitious-agent assessment in A.2.
In S.2.4, take each critical step identified in S.2.2 and state its test or control, criterion, evidence supporting the choice, and treatment of isolated intermediates. For biotech intermediate storage, connect the proposed conditions to stability evidence. Do not call a step noncritical merely because its limit is missing. Record that gap, obtain the risk/scientific assessment, and reconcile the process diagram after resolution.
S.2.5–S.2.6: distinguish demonstrated capability from process history
Use S.2.5 for the applicable validation/evaluation plans, executed results, interpretation and conclusions. Identify what process version and scale the work supports. M4Q specifically addresses aseptic processing/sterilization and provides additional biotech process-evaluation detail. Route viral removal/inactivation study evidence to A.2 with clear references; use current Q5A(R2) when its product scope applies.
Use S.2.6 to explain significant manufacturing or site changes during development, why they occurred and how their quality impact was assessed. Link nonclinical, clinical, stability and commercial-representative batches to their process versions. For biotech changes, present the comparative evidence and its scientific interpretation; do not equate passing release tests with a complete comparability conclusion. If the bridge is missing, identify the affected studies and assign the assessment before claiming representativeness.
Worked review: a hold time changed between evidence and narrative
Fictional exercise: S.2.2 proposes an overnight intermediate hold, but S.2.4 and the supporting evaluation cover only a shorter hold. The discrepancy is a scope problem, not a typographical choice.
Compare the proposed process to the executed study conditions, obtain the technical owner's assessment, and either support the proposed hold or revise the proposal through change control. Review downstream impurity, stability and batch-representativeness claims. Record the resolved evidence link in S.2.5/S.2.6 as appropriate. Never invent a time limit to make the three sections agree.
Create a process-to-control crosswalk
Review the process horizontally before reviewing each S.2 subsection in isolation. Use the process diagram as the row order for this editorial crosswalk.
| Process step | Required working context | Adjacent record to reconcile |
|---|---|---|
| Material entry | Identity, supplier/source and intended function | S.2.3 control and qualification records |
| Transformation or unit operation | Site, equipment context and proposed conditions | S.2.2 narrative and development evidence |
| Critical control or intermediate | Test, criterion and scientific basis | S.2.4 and the applicable evaluation |
| Hold or transfer | Container, duration and conditions proposed | Supporting stability or process assessment |
| Final material | Process version, batch identity and use | S.3/S.4 results and clinical/nonclinical representativeness |
“Required working context” describes what the author needs for the comparison; it is not a universal mandated submission table. The technical owner determines the relevant process details and scientific conclusions.
Review exercise: the flow diagram shows purification at site A and final storage at site B, but only A is listed. Identify the operation and responsibility at B, then inspect transfer conditions and the evidence supporting the receiving process. Adding an address without evaluating the transfer would repair only the directory.
Keep development history connected to the process actually proposed. A historical batch can support a useful conclusion without representing every later process condition. Carry that distinction into characterization, substance stability and any adventitious-agent assessment.
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 do S.2.5 process evaluation and S.2.6 development history differ?
S.2.5 addresses the relevant validation or evaluation and what it demonstrates. S.2.6 explains significant development changes and their quality implications. Identify the versions and batches connecting them; describing the history of a change does not itself demonstrate that the changed process is supported.
Can passing release tests establish complete comparability after a process change?
Not by themselves. Release tests describe selected attributes under their specified methods. The relevant comparability assessment may need broader evidence about the change and its consequences. Preserve the technical experts’ supported conclusion rather than inferring equivalence from a set of passing certificates.
Where should viral clearance evidence be discussed?
Cross-reference the applicable adventitious-agent evaluation in A.2 and explain how it relates to the manufacturing process and version described in S.2. Use current viral-safety guidance within its product scope. Do not represent an older evaluated process as the proposed process without a supported relationship.
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.S.2.1–3.2.S.2.6, printed pages 6–9.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 3.2.S.2. A heading identifies placement, not mandatory applicability.

