How to write the Quality Overall Summary in CTD 2.3

How do you write a quality overall summary for CTD 2.3?

Write the quality overall summary by explaining the quality argument already supported in Module 3: what the substance and product are, how they are made and controlled, and how the proposed stability position is justified. Preserve distinctions between manufacturers and presentations, and do not introduce an unsupported conclusion while shortening the dossier.

Before you begin

M4Q(R1) organization of a marketing-application QOS. Product-specific expectations and regional applicability require separate assessment. M4Q(R2) draft content is not substituted for the R1 baseline.

What you will prepare: A source-mapped QOS whose conclusions can be reconciled with Module 3 and relevant nonclinical or clinical evidence.

Choose the baseline and establish the evidence map

This guide follows M4Q(R1). The FDA M4Q(R2) file checked for this draft is explicitly a draft, carrying the ICH May 14, 2025 Step 2 endorsement. A newer draft date does not establish regional implementation. Before a real filing, the regulatory owner should confirm the applicable structure and supported electronic format.

The QOS explains the quality package; it is not the place to introduce a new justification absent from the underlying dossier. Obtain the controlled Module 3 sections, development history, specification versions, batch tables and stability conclusions. Create an editorial evidence map with a row for each material conclusion, its source location, version, owner and unresolved dependency.

In 2.3.I, identify the actual product and proposed use. Compare substance, dosage form, strengths and route with the application identity. Make the scope of each substance/manufacturer or product presentation clear before summarizing it. An unexplained switch between manufacturers can invalidate an otherwise correct paragraph.

2.3.S: explain how substance quality is established

Build the substance narrative from its Module 3 evidence rather than a list of document titles. Explain what is made, how the process and controls support consistent material, which structural or impurity questions matter, and how the specification and stability position follow from the submitted evidence.

Use a review matrix such as: proposed impurity conclusion → characterization/qualification evidence → applicable specification version → relevant nonclinical reference. For process changes, identify which material supported the nonclinical and clinical program and where the comparability or bridging discussion can be found. Do not imply that all development batches represent the proposed commercial process.

Reconcile the reference material and container descriptions with the actual analytical and stability packages. If the source includes a proposed retest period, distinguish that proposal from the observed study duration. Never create a missing limit or commitment while shortening the source text.

2.3.P: connect formulation, manufacture, controls and shelf life

Start with the composition and the presentation being proposed. Explain development choices using the submitted formulation and performance evidence. Where the clinical formulation differs, show the reader where the bridge to the proposed product is addressed. Separate different strengths or containers when their supporting evidence differs.

Summarize manufacturing and excipient controls in relation to their role in product quality. For the product specification, use the approved drafting source rather than copying numbers from a historical batch certificate. Keep analytical capability, batch results and the rationale for the criteria connected without treating them as interchangeable evidence.

For stability, reconcile the studied batch, package, condition, timepoints and proposed storage/shelf-life statement. Identify any in-use claim separately. The author’s job is to represent the scientific conclusion and its basis accurately; an attractive summary cannot repair a missing stability justification.

2.3.A and 2.3.R: resolve the conditional material

Treat 2.3.A as the appendix family, not an extra universal report. In 2.3.A.1, summarize relevant facility and equipment information for the applicable biotechnology context and point to the supporting facility description. Do not apply a biologic facility narrative indiscriminately to every product.

For 2.3.A.2, explain the submitted adventitious-agent control argument using the actual materials, process and supporting evaluation. Check that any clearance statement preserves the study conditions and limitations; adding individual reduction values without the source’s justification can imply unsupported overall clearance.

For 2.3.A.3, establish whether a relevant excipient appendix exists and what it supports. Coordinate any novel-excipient safety issue with its underlying quality and safety assessments. A heading labeled “Excipients” does not mean every familiar excipient needs a new standalone dossier.

For 2.3.R, summarize applicable regional material actually included in 3.2.R. Record the authority and reason for inclusion. If the product or regional condition is unknown, mark the decision undetermined in the preparation record; neither an empty heading nor a template default establishes non-applicability.

Worked example: one shelf-life sentence hides two packages

Fictional editorial exercise: a product has bottle and blister presentations. The draft QOS assigns one proposed shelf life to both, but the supporting analysis distinguishes the packages.

Create two evidence-map rows. Compare each container description, stability dataset and approved scientific conclusion. Ask the stability owner to resolve the proposed statement for each presentation, then align the QOS and relevant labeling proposal. Do not extrapolate a number from one package merely to finish the paragraph.

The same method catches a specification limit copied from an earlier version: identify the exact record, confirm whether the change is supported in Module 3, and update every affected summary statement. Keep the final unresolved-item list with the review package.

Build the QOS from a claim-to-evidence table

Before drafting, ask the quality lead to agree the scientific conclusions and unresolved issues for each substance and product instance. The author can organize the reasoning, but should not choose a specification or shelf life simply to complete the narrative.

This is an editorial evidence map, not an additional submission form. Use exact Module 3 section and document identifiers in its working version. Replace a vague “see Module 3” with a reference that lets a reviewer locate the relevant argument.

Review exercise: the QOS claims one specification applies to two manufacturing sites. One site's batch results use an earlier method. The correct first action is to identify the versions and ask the analytical and manufacturing owners what comparison is supported. Do not harmonize the table by overwriting either set of results. Once the issue is resolved, update the QOS, substance control package and affected stability discussion together.

A useful completion test is to remove the QOS conclusion and ask another reviewer to reconstruct it from its references. If they can locate the data but not the rationale, the link is incomplete. If they find a different conclusion, return the disagreement to the scientific owner.

Frequently asked questions

Sources and revisions

Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.

Related guides