This is a ready-to-use analytical procedure development report for the ICH Q14 enhanced approach. It is the document a reviewer, an assessor, or an inspector reads to follow the whole development chain in one place: the ATP, the parameter risk assessment, the screening and optimization work, the resulting proven acceptable ranges and method operable design region (MODR), and the control strategy those ranges support, without having to reassemble the story from separate raw-data 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
| Field | Entry |
|---|---|
| Report title | Analytical Procedure Development Report, <<FILL: method/analyte name>> |
| Report number | <<FILL: RPT-ID, e.g. APD-2026-007>> |
| Version | <<FILL: version, e.g. 1.0>> |
| Product / method | <<FILL: product name, method purpose>> |
| Development approach | Enhanced (ICH Q14) |
| Role | Name | Signature | Date |
|---|---|---|---|
| Author (Analytical development) | <<FILL>> | ||
| Reviewer (Statistician / DoE specialist) | <<FILL>> | ||
| Reviewer (Method owner / QC) | <<FILL>> | ||
| Approver (Quality Assurance) | <<FILL>> |
1. Purpose and scope
This report summarizes the enhanced analytical procedure development program for <<FILL: method>>, from the Analytical Target Profile through the finished control strategy, and states whether the program met its predefined acceptance basis. It draws on, and references without repeating in full, the ATP form <<FILL: document number>> and the underlying risk assessment and design-of-experiments raw data held under <<FILL: document number(s)>>. It does not replace those underlying records; it is the roll-up a reviewer reads first, with pointers to the source data.
2. Method and development summary
| Field | Entry |
|---|---|
| ATP reference | <<FILL: document number, version>> |
| Method class | <<FILL: e.g. HPLC assay, impurity method, chemometric/spectroscopic, relative potency bioassay>> |
| Development stage at report issue | <<FILL: e.g. pre-validation, post-approval change>> |
| Risk assessment reference(s) | <<FILL: document number(s), version(s)>> |
| Design of experiments reference(s) | <<FILL: document number(s), version(s), design types used>> |
3. Parameter risk assessment summary
State the number of candidate parameters assessed, the high-risk parameters carried into experimental study, and the parameters screened out with their rationale, with a pointer to the full assessment rather than reproducing its tables.
| Field | Entry |
|---|---|
| Candidate parameters assessed | <<FILL>> |
| High-risk parameters carried into study | <<FILL: list>> |
| Parameters screened out (with rationale) | <<FILL: list, or "none">> |
| Risk tool used | <<FILL: e.g. cause-and-effect analysis feeding a failure-mode assessment>> |
4. Screening and optimization summary
| Study | Design type | Parameters studied | Key finding | Attribute affected |
|---|---|---|---|---|
<<FILL>> | <<FILL: fractional factorial / definitive screening / response surface>> | <<FILL>> | <<FILL>> | <<FILL: e.g. critical-pair resolution, RSD>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
5. Proven acceptable ranges and MODR
| Parameter | Studied range | Proven acceptable range | Interacts with other parameters? | Included in a claimed MODR? |
|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | Yes / No: <<FILL>> | Yes / No: <<FILL>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
| Field | Entry |
|---|---|
| MODR claimed? | Yes / No: <<FILL>> |
| MODR statement | <<FILL: the joint region across the interacting parameters shown to keep the method within its ATP, or "not applicable, no interacting parameters identified">> |
| Basis | <<FILL: fitted response-surface model(s), reference to the DoE report(s) in section 4>> |
6. Attributes achieved against the ATP
| ATP element | ATP target | Achieved result | How confirmed |
|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL: worst-case DoE run, confirmation run>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
7. Control strategy (system suitability and procedural controls)
| Control | Derived from | Limit | Acceptance |
|---|---|---|---|
<<FILL: e.g. critical-pair resolution>> | <<FILL: worst-case corner of the studied range>> | <<FILL>> | <<FILL>> |
<<FILL: e.g. replicate-injection RSD>> | <<FILL>> | <<FILL>> | <<FILL>> |
<<FILL: e.g. tailing factor>> | <<FILL>> | <<FILL>> | <<FILL>> |
<<FILL: e.g. sensitivity / signal-to-noise at reporting level>> | <<FILL>> | <<FILL>> | <<FILL>> |
State plainly that every system suitability limit in this table traces to observed data at or near the worst-case edge of a studied range, not to a generic template.
8. Deviations during development
Every deviation that occurred across the risk assessment, screening, optimization, or range-confirmation 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.
| Reference | Phase (risk assessment/screening/optimization/confirmation) | Description | Impact 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 ATP element is met at every studied condition within the claimed proven acceptable ranges/MODR, and every system suitability limit traces to studied data">>. Against that basis: <<FILL: met / partially met with justification, referencing sections 5, 6, and 7>>.
10. Conclusion
<<FILL: The enhanced development program for [METHOD] demonstrates [summary]. The proven acceptable ranges/MODR ARE / ARE NOT sufficiently supported by studied data. The control strategy IS / IS NOT ready to support validation and routine use of this procedure.>>
11. References
ICH Q14, Analytical Procedure Development. ICH Q2(R2), Validation of Analytical Procedures (the deliverable that follows this report). ICH Q9(R1), Quality Risk Management. ICH Q12, Lifecycle Management (established conditions carried forward from the proven acceptable ranges/MODR claimed here).
Confirm the current version of each reference before issue.
12. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
Filled specimen (excerpt)
The following shows the report completed for an illustrative reverse-phase gradient finished-product assay, the same running example used in the ICH Q14/Q2(R2) article this report accompanies. Numbers are illustrative; replace them with your own.
Section 2. ATP reference ATP-2026-011 v1.0. Method class: HPLC assay. Development stage: pre-validation. Risk assessment RA-AD-014 v1.0. DoE references DOE-AD-021 v1.0 (definitive screening) and DOE-AD-027 v1.0 (response surface, optimization).
Section 3. 8 candidate parameters assessed in RA-AD-014. High-risk parameters carried into study: gradient slope, mobile-phase pH, column temperature. Screened out: flow rate and injection volume (medium risk, prior platform knowledge sufficient), detector wavelength (low risk, analyte has a broad absorbance plateau). Risk tool: cause-and-effect analysis feeding a failure-mode assessment.
Section 4 (excerpt).
| Study | Design type | Parameters studied | Key finding | Attribute affected |
|---|---|---|---|---|
| DOE-AD-021 | Definitive screening | Gradient slope, mobile-phase pH, column temperature | pH and temperature interact; slope has an independent main effect | Critical-pair (D2/main) resolution |
| DOE-AD-027 | Response surface | Mobile-phase pH, column temperature | Resolution greater than 2.0 across pH 2.4-2.8 and temperature 33-37 C | Critical-pair resolution, RSD |
Section 5. Column temperature: studied 30-40 C, proven acceptable range 33-37 C, interacts with pH: yes, included in claimed MODR: yes. Mobile-phase pH: studied 2.2-3.0, proven acceptable range 2.4-2.8, interacts with temperature: yes, included in MODR: yes. Gradient slope: studied +/- 10% of nominal, proven acceptable range +/- 5% of nominal, interacts with others: no, included in MODR: no (independent range). MODR claimed: yes. Statement: critical-pair resolution remains above 2.0 across the joint region of mobile-phase pH 2.4 to 2.8 and column temperature 33 to 37 C. Basis: response-surface model fitted from DOE-AD-027.
Section 6 (excerpt).
| ATP element | Target | Achieved | How confirmed |
|---|---|---|---|
| Accuracy and precision (combined) | +/- 2.0% of true value, 95% probability | +/- 1.4% observed across the MODR corners | Confirmation runs at 4 MODR corner points |
| Specificity | Baseline resolution from D1-D3 and excipients | Resolution 2.1-2.6 across studied conditions, worst case 2.1 | Worst-case corner of DOE-AD-027 |
Section 7 (excerpt). Critical-pair resolution, derived from the worst-case MODR corner (resolution 2.1 observed), limit not less than 2.0, acceptance: pass. Replicate-injection RSD, derived from repeatability data across the MODR, limit not more than 1.0%, acceptance: pass.
Section 8. DEV-2026-0287: one response-surface run in DOE-AD-027 was aborted mid-sequence by a column oven fault; investigated, re-executed at the same randomized design point with no impact on the fitted model. Impact on conclusion: none.
Section 9. Acceptance basis: every ATP element is met at every studied condition within the claimed MODR, and every system suitability limit traces to studied data. Met: yes, per sections 5, 6, and 7.
Section 10 (conclusion, specimen): the enhanced development program for this assay demonstrates that critical-pair resolution, accuracy, and precision all meet their ATP targets across the claimed MODR (mobile-phase pH 2.4-2.8, column temperature 33-37 C) and the independent proven acceptable range for gradient slope, confirmed at four MODR corner points. The MODR is sufficiently supported by studied data. The control strategy is ready to support validation of this procedure.
Common inspection observations this report prevents
- A proven acceptable range or MODR asserted in a filing with no reference to the design-of-experiments data that support it, an “enhanced label, minimal data” gap.
- System suitability limits presented with no stated derivation, so a reviewer cannot tell whether they trace to studied data or to a generic template.
- A deviation that occurred during development, such as an aborted DoE run, omitted from the development record.
- ATP elements listed as “achieved” with no stated method of confirmation.
- A claimed MODR that does not actually capture parameter interaction, because independent ranges were studied and then presented as if they were a joint region.
How to adapt this report
- Set your report number, method, and development stage on the approval page.
- Populate sections 3 through 7 by pulling confirmed results from your actual risk assessment and DoE data; do not restate the full raw dataset, reference the document numbers.
- List every deviation across the whole development program in section 8, not only DoE-phase deviations.
- 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.
- If a claimed MODR has not been confirmed at its corner points with real data, say so plainly in section 5 and reflect that limitation in the conclusion.
- Confirm every regulation in section 11 against the current published version before issue.