Naga MounikaDrug Product · Validation · CMC
Menu
Working document

Formulation Development Report

A plug-and-play report summarizing a completed formulation development program: results against every stage gate, the presentation decision and its supporting data, deviations, conclusion, and handoff to tech transfer, with a filled specimen.

Document typeReport
Topic areaDrug Product
LevelAdvanced
UpdatedSeptember 2026
How to use this document

Copy the template below into your quality system. Replace every <<FILL: ...>> placeholder with your company, system, and process specifics, then route it through your own document control, review, and approval. The filled specimen shows one worked example; adapt the numbers and scope to your operation and verify each cited regulation or standard against the current source before you rely on it.

This is a generic, originally worded starting point. It contains no confidential, proprietary, or employer material, it is drafted with AI assistance and reviewed, it is not legal or compliance advice, and adopting it does not by itself create or prove compliance. See the Disclaimer and Terms.

This is a ready-to-use report summarizing a completed formulation development program, from failure-mode screening through a locked formulation ready for transfer. It is the closing document for the Formulation Development Plan: the plan states what would be done and why, this report states what was actually found and what was decided. Replace every <<FILL: ...>> placeholder with your own specifics. A filled specimen follows.

Document control header

FieldEntry
Document titleFormulation Development Report for <<FILL: product>>
Document number<<FILL: e.g. FDR-2026-02>>
Version<<FILL>>
Effective date<<FILL>>
Linked formulation development plan<<FILL: document number>>
Modality<<FILL: protein / oligonucleotide (naked or LNP) / cell / viral vector (AAV)>>
Report owner<<FILL: e.g. Formulation Development Lead>>

1. Purpose

This report summarizes the results of formulation development for <<FILL: product>> against the stage gates defined in the linked plan, states the locked formulation and the data supporting it, and documents the basis on which this formulation is considered ready for technology transfer.

2. Scope

DimensionDecision
Program covered<<FILL>>
Development stages summarized<<FILL: e.g. failure-mode screening through confirmation and lock>>
Out of scope<<FILL: e.g. commercial-scale process characterization, covered under the tech transfer report>>

3. Summary of activity against the plan’s stage gates

GatePlan’s exit criterionResultStatus
G1: Failure-mode screeningRisk assessment approved; screening matrix defined<<FILL>><<FILL: met / met with deviation>>
G2: Lead formulation selectionLead candidate(s) selected with documented rationale<<FILL>><<FILL>>
G3: Presentation decisionLiquid-versus-lyophilized decision documented and approved<<FILL>><<FILL>>
G4: Confirmation and lockFormulation and process parameters locked<<FILL>><<FILL>>

4. Dominant degradation mechanism and excipient rationale

<<FILL: state the modality's dominant failure mode as confirmed by development data, and summarize how the locked excipient and buffer system addresses it specifically, referencing the forced degradation and/or cryoformulation study reports behind the claim>>

5. Presentation decision

Question (per the plan’s decision table)AnswerData reference
Cell-based or lyophilization-incompatible naked oligonucleotide?<<FILL>><<FILL>>
Liquid stability supports target shelf life and cold chain?<<FILL>><<FILL>>
A degradation pathway justifies removing the water?<<FILL>><<FILL>>
Viral vector lyophilization, treated as its own development stream?<<FILL: N/A or summary>><<FILL>>
Presentation decided<<FILL: liquid frozen / liquid refrigerated / lyophilized>>

6. Confirmatory study results

StudyResultAcceptance criteria metReport reference
Forced degradation / stress study<<FILL>><<FILL>><<FILL: document number>>
Cryoformulation freeze-thaw study<<FILL: if applicable>><<FILL>><<FILL>>
Lyophilization cycle development (Tg’/Tc or eutectic characterization)<<FILL: if applicable>><<FILL>><<FILL>>
High-concentration / PFS readiness assessment<<FILL: if applicable>><<FILL>><<FILL>>
Scale-down mixing model qualification<<FILL>><<FILL>><<FILL>>

7. Deviations during development

DeviationStudy affectedImpact assessmentResolution
<<FILL>><<FILL>><<FILL>><<FILL>>

State “none” explicitly if no deviations occurred; do not omit this section.

8. Locked formulation

ComponentSpecification
Drug substance concentration<<FILL>>
Buffer / pH<<FILL>>
Stabilizing excipient(s)<<FILL>>
Surfactant / other functional excipient(s)<<FILL>>
Presentation<<FILL: liquid / lyophilized, container type>>
Process-parameter ranges carried to transfer<<FILL: mixing, and, where applicable, cycle parameters>>

9. Conclusion and handoff to tech transfer

<<FILL: explicit statement that the formulation is locked, that every stage gate in section 3 closed met or met-with-documented-deviation, and that the scale-down mixing model (and cycle design, where applicable) is qualified, not just the stability data alone>> See technology transfer for advanced therapies for how this report’s outputs feed the transfer risk assessment and plan.

10. References

ICH Q8(R2), Pharmaceutical Development. ICH Q5C, Quality of Biotechnological Products: Stability Testing. ICH Q9(R1), Quality Risk Management.

Confirm the current version of each reference before issue.

11. Revision history

VersionDateAuthorSummary of change
<<FILL: 1.0>><<FILL>><<FILL>>Initial issue.

12. Approvals

RoleNameSignatureDate
Author (Formulation lead)<<FILL>>
Analytical Development<<FILL>>
Quality Assurance<<FILL>>

Filled specimen

Extract from the closing report for Acme Therapeutics’ ATX-AAV9, continuing the program introduced in the linked Formulation Development Plan’s specimen.

GateResultStatus
G1Risk assessment RA-2026-011 identified capsid rupture and surface adsorption during freeze-thaw as the dominant risk, ahead of aggregation under agitationMet
G2Differential scanning fluorimetry screening across 14 buffer/excipient conditions selected a low-level poloxamer 188 and sucrose lead candidate at reduced buffer concentrationMet
G3Frozen-liquid stability at -70C supported the target shelf life with the qualified dry-vapor shipper; lyophilization not pursuedMet
G4Confirmatory freeze-thaw study passed at 3 cycles; scale-down mixing qualification closed 11 days after the freeze-thaw resultMet with documented delay, no impact

Section 4: the dominant mechanism, capsid rupture and genome leakage from freeze-thaw interfacial stress plus surface adsorption at low concentration, was confirmed by the freeze-thaw study reading free single-stranded DNA and infectious titer, not aggregate level alone. The low-level poloxamer 188 addresses adsorption specifically; sucrose addresses the separate devitrification-exotherm mechanism.

Section 7 deviations: one deviation recorded, DEV-2026-0142, a delay in starting the scale-down mixing qualification against the plan’s original timeline; impact assessment found no effect on the freeze-thaw result or the presentation decision, since the qualification is a separate, independent confirmation; resolution was a schedule adjustment with no protocol change.

Section 9 conclusion: formulation locked 2026-08-19; every stage gate closed met or met-with-no-impact deviation; scale-down mixing model qualification confirmed bench-scale shear exposure predicted full-scale behavior within the pre-defined margin. Ready for transfer; outputs feed the tech transfer risk assessment’s process-parameter section directly.

Common inspection findings this report prevents

  • A formulation declared “locked” in practice, via an email or a meeting decision, with no report tracing the conclusion back to the stage-gate data that supports it.
  • A presentation decision (liquid versus lyophilized) stated as a conclusion with no reference back to the specific stability or thermal-characterization data behind it.
  • A scale-down mixing model qualification omitted from the closing report because it finished after the headline stability result, understating how much of the “lock” decision actually depended on it.
  • A deviation during development left out of the closing report because it was resolved, when its impact assessment is itself part of the traceable record a reviewer expects.

How to adapt this report

  1. Populate section 3 directly from the linked plan’s stage gates; do not summarize activity that does not map to a defined gate.
  2. In section 5, answer every question from the plan’s presentation-decision table in order, with a data reference for each, not a conclusion asserted without its supporting study.
  3. List every confirmatory study in section 6 that the plan called for, marking any not yet applicable to this modality as N/A rather than omitting the row.
  4. State deviations in section 7 explicitly, including “none,” and never let a deviation disappear because it was ultimately judged to have no impact.
  5. Do not declare the formulation ready for transfer in section 9 until both the stability data and the scale-down mixing model qualification (and cycle design, where applicable) are closed.
Add this site to your home screen Full screen, works offline, one tap from your home screen.