Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics -> Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
Report Plug-and-play starting point Quality Assurance

Report: QbD Development and Control Strategy Summary

A plug-and-play roll-up report that ties the QTPP, the CQA/CPP/CMA criticality risk assessment, the DoE program, the verified design space, and the finished control strategy into one reviewable document, with results against acceptance, deviations during development, a filled specimen, and the regulations it satisfies.

Document type: Report

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

This is a ready-to-use QbD development and control strategy summary report. It is the document a reviewer or an inspector reads to follow the whole chain in one place: the Quality Target Product Profile, the criticality risk assessment, the DoE program, the verified design space, and the resulting control strategy, without having to reassemble it from separate files. Replace every <<FILL: ...>> placeholder with your own specifics. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it. This is general educational reference, not regulatory or professional advice.

Approval page

FieldEntry
Report titleQbD Development and Control Strategy Summary, <<FILL: product name>>
Report number<<FILL: RPT-ID, e.g. QBD-SUM-009>>
Version<<FILL: version, e.g. 1.0>>
Product<<FILL: product name, dosage form, strength(s)>>
Development stage covered<<FILL: e.g. pre-BLA/NDA>>
RoleNameSignatureDate
Author (Process development)<<FILL>>
Reviewer (Statistician / DoE specialist)<<FILL>>
Reviewer (Regulatory affairs)<<FILL>>
Approver (Quality Assurance)<<FILL>>

1. Purpose and scope

This report summarizes the QbD development program for <<FILL: product>>, from the Quality Target Product Profile through the finished control strategy, and states whether the program’s predefined acceptance basis was met. It draws on, and references without repeating in full, the QTPP form <<FILL: document number>>, the CQA/CPP/CMA criticality risk assessment <<FILL: document number>>, and the DoE study protocol(s) and reports <<FILL: document numbers>> executed for this product. It does not replace any of those underlying records; it is the roll-up a reviewer reads first, with pointers to the source documents for the full data.

2. Product and development summary

FieldEntry
QTPP reference<<FILL: document number, version>>
Development stage at report issue<<FILL>>
Unit operations in scope<<FILL>>
Criticality risk assessment reference(s)<<FILL: document number(s), version(s)>>
DoE study reference(s)<<FILL: document number(s), version(s), design types used>>

3. CQAs achieved

CQAQTPP-derived targetAchieved resultHow confirmed
<<FILL>><<FILL>><<FILL>><<FILL: DoE confirmation run, PPQ batch, stability data>>
<<FILL>><<FILL>><<FILL>><<FILL>>
<<FILL>><<FILL>><<FILL>><<FILL>>

4. Criticality risk assessment summary

State the number of candidate attributes assessed, the CQAs designated, and the CPPs/CMAs designated, with a pointer to the full assessment rather than reproducing its tables.

FieldEntry
Candidate attributes assessed<<FILL>>
CQAs designated<<FILL: list>>
CPPs designated<<FILL: list>>
CMAs designated<<FILL: list>>
Items where the override rule applied (high severity retained despite a lower RPN)<<FILL, or "none">>

5. DoE program summary

DoE studyDesign typeFactors studiedKey findingCPP/CMA implication
<<FILL>><<FILL: factorial/CCD/BBD/mixture>><<FILL>><<FILL>><<FILL>>
<<FILL>><<FILL>><<FILL>><<FILL>><<FILL>>

6. Design space

FieldEntry
Design space defined?Yes / No: <<FILL>>
Design space statement<<FILL: the multivariate region across the studied CPPs/CMAs shown to deliver acceptable CQAs>>
Basis<<FILL: fitted response-surface model(s), reference to DoE report(s)>>
Verified at commercial scale?Yes / No / Not yet reached: <<FILL>>
Normal operating range (NOR)<<FILL>>

7. Control strategy (final)

CQAControl layerSpecific controlAcceptance
<<FILL>>Material<<FILL>><<FILL>>
<<FILL>>Parameter<<FILL>><<FILL>>
<<FILL>>In-process<<FILL>><<FILL>>
<<FILL>>Process Analytical Technology / RTRT (if used)<<FILL>><<FILL>>
<<FILL>>End product<<FILL>><<FILL>>

8. Deviations during development

Every deviation that occurred across the QTPP, risk assessment, DoE, or design-space verification work is listed here with its impact on the conclusions of this report. Omitting a deviation that occurred is a serious integrity finding, not a shortcut.

ReferencePhase (QTPP/risk assessment/DoE/design space)DescriptionImpact on conclusion
<<FILL, or "none">><<FILL>><<FILL>><<FILL>>

9. Results against the predefined acceptance basis

<<FILL: state the acceptance basis defined before the program started, for example "every CQA achieves its QTPP target with a design space verified at commercial scale and a control strategy that traces every CPP/CMA to a control">>. Against that basis: <<FILL: met / partially met with justification, referencing sections 3, 6, and 7>>.

10. Conclusion

<<FILL: The QbD development program for [PRODUCT] demonstrates [summary]. The design space IS / IS NOT verified at commercial scale. The control strategy IS / IS NOT ready to support the filing / commercial control strategy for this product.>>

11. References

ICH Q8(R2), Pharmaceutical Development. ICH Q9(R1), Quality Risk Management. ICH Q10, Pharmaceutical Quality System. ICH Q11, Development and Manufacture of Drug Substances. ICH Q12, Lifecycle Management (Established Conditions carried from the design space). FDA Guidance, Process Validation: General Principles and Practices, 2011.

Confirm the current version of each reference before issue.

12. Revision history

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

Filled specimen (excerpt)

The following shows the report completed for an illustrative 50 mg immediate-release tablet, the same product used as the running example in the QbD and DoE article this report accompanies. Numbers are illustrative; replace them with your own.

Section 2. QTPP reference QTPP-2026-014 v1.0. Development stage: pre-NDA. Unit operations in scope: granulation, blending, compression. Criticality risk assessment RA-PD-022 v1.0. DoE references DOE-PD-041 v1.0 (2^3 factorial, screening) and DOE-PD-052 v1.0 (CCD, optimization).

Section 3 (excerpt).

CQATargetAchievedHow confirmed
DissolutionNot less than 80 percent (Q) at 30 minutes30-minute release 88 to 94 percent across the design space, 91 percent at commercial-scale confirmationDoE confirmation runs plus 3 commercial-scale verification batches
Content uniformityMeets compendial uniformity-of-dosage-units chapterAcceptance value within limit across all confirmation and verification batchesDoE confirmation runs plus commercial-scale verification batches

Section 4. 12 candidate attributes assessed in RA-PD-022; 5 CQAs designated (assay, content uniformity, dissolution, degradation products, water content). CPPs designated: granulation water, main compression force, blend time. CMA designated: API particle size (D90). No item required the override rule.

Section 6. Design space defined: yes. Statement: acceptable dissolution, content uniformity, and assay are assured when granulation water is 28 to 36 percent, main compression force is 8 to 14 kN, and blend time is 12 to 18 minutes, with API D90 not more than the specified limit. Verified at commercial scale: yes, three verification batches run at the NOR (water 30 to 34 percent, force 9 to 12 kN, blend time 14 to 16 minutes) all met every CQA.

Section 8. DEV-2026-0311: one DoE run in DOE-PD-052 fell outside the randomized order due to an equipment scheduling conflict; investigated, no impact on the fitted model since the run was re-executed at the correct randomized position and the discarded attempt excluded from the dataset with documented rationale. Impact on conclusion: none.

Section 9. Acceptance basis: every CQA achieves its QTPP target, with a design space verified at commercial scale and a control strategy tracing every CPP and CMA to a documented control. Met: yes, per sections 3, 6, and 7.

Section 10 (conclusion, specimen): the QbD development program for this product demonstrates that dissolution, content uniformity, assay, degradation products, and water content all meet their QTPP-derived targets across the verified design space, confirmed at commercial scale on three verification batches. The design space is verified at commercial scale. The control strategy is ready to support the commercial control strategy filed for this product.

Common inspection observations this report prevents

  • A control strategy presented with no traceable chain back to the QTPP and the criticality risk assessment that justified it.
  • A design space asserted in a filing with no reference to the DoE report and confirmation-run data that support it.
  • A deviation that occurred during development, such as an out-of-sequence DoE run, omitted from the development record.
  • CQAs listed as “achieved” with no stated method of confirmation (DoE run, PPQ batch, stability data).
  • No statement of whether the design space was verified at the intended commercial scale, leaving a lab-scale claim standing unqualified.

How to adapt this report

  1. Set your report number, product, and development stage on the approval page.
  2. Populate sections 3 through 7 by pulling the confirmed results from your actual QTPP, criticality risk assessment, and DoE reports; do not restate their full tables, reference the document numbers.
  3. List every deviation across the whole development program in section 8, not only DoE deviations.
  4. State the acceptance basis in section 9 as it was defined before the program started; a basis written after the fact to match the results is not defensible.
  5. If the design space has not yet been verified at commercial scale, say so plainly in section 6 and reflect that limitation in the conclusion.
  6. Confirm every regulation in section 11 against the current published version before issue.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.