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
Risk Assessment Plug-and-play starting point Quality Assurance

Risk Assessment: Analytical Method Change Evaluation Against Proven Acceptable Range / MODR

A plug-and-play risk assessment for a proposed analytical method change under ICH Q14: a two-axis decision matrix (parameter boundary status x measurement-principle change) that classifies the change into a handling path, with a filled specimen for a discontinued-column change and the findings it prevents.

Document type: Risk Assessment

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 risk assessment for evaluating a proposed change to a validated analytical procedure against its documented proven acceptable range (PAR) or method operable design region (MODR). It exists because “is the method different” is the wrong question; the question a defensible change decision has to answer is whether the change stays inside understood territory and whether the changed method still meets its Analytical Target Profile (ATP). This assessment is distinct from a generic computerized-system or equipment change risk assessment: it is scoped specifically to the analytical-method-lifecycle boundary question ICH Q14 introduces. 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.

Document control header

FieldEntry
Document titleAnalytical Method Change Evaluation, <<FILL: method/analyte name>>
Document number<<FILL: RA-ID, e.g. RA-AMC-018>>
Version<<FILL: version, e.g. 1.0>>
Effective date<<FILL: effective date>>
Method / ATP reference<<FILL: method ID; ATP document number and version>>
Development report reference<<FILL: analytical procedure development report number, if enhanced approach was used>>
Document owner<<FILL: role, e.g. Method Owner / QC Technical Lead>>
Change description<<FILL: what is proposed to change, e.g. column supplier, instrument platform, detector type, sample preparation step>>

1. Purpose

This assessment evaluates a proposed change to a validated analytical procedure and classifies it into a handling path, verification-only, partial or full revalidation, or treatment as a new procedure, based on whether the change stays inside a documented proven acceptable range or MODR and whether it changes the underlying measurement principle. It exists so the handling decision is traceable to the development understanding rather than to an unstated judgment call about how “big” the change feels.

2. Scope

This assessment covers a single proposed change to the method named above. It does not itself execute the confirmatory testing it may call for; it decides what testing is required and at what depth. It does not set the regulatory reporting category on its own; section 8 feeds that decision but the applicable regional variation or supplement framework and any ICH Q12 established conditions govern the final filing action.

3. Responsibilities

RoleResponsibility
Method owner (QC technical lead)Raises the change, drafts the initial classification, and executes or commissions the confirmatory testing this assessment calls for.
Analytical developmentConfirms whether the proposed change parameter(s) fall inside the studied PAR/MODR from the development report, and whether the change is same-technique or a different measurement principle.
Quality AssuranceReviews and approves the classification and the resulting handling path; confirms the change is documented in the quality system regardless of path.
Regulatory affairsMaps the classification to the applicable reporting category under ICH Q12 established conditions and the regional variation/supplement framework.
Statistician (where available)Confirms the confirmatory testing design (comparative run, revalidation scope) is statistically adequate for the classification reached.

4. Methodology

The classification is a two-axis decision, not a single severity score. Axis 1 asks whether the changed parameter(s) fall inside a range the development report already studied. Axis 2 asks whether the change alters the measurement principle itself (for example, detection chemistry, separation mode, or assay format) rather than a parameter within an unchanged principle. The two axes combine into a handling path in section 6. This mirrors, and gives documented, repeatable structure to, the change-control decision logic in ICH Q14.

A change that fails Axis 1 (outside any studied range) but passes Axis 2 (same technique) still requires confirmatory data; it is not automatically a full revalidation, but the depth of testing is set by how far outside the studied range the change sits and what the ATP’s performance margin can absorb, assessed in section 7.

5. Scoring scale (boundary and principle status)

AxisStatusDefinition
1: Parameter boundaryInside PAR/MODRThe proposed value(s) for the changed parameter(s) fall within a range the development report studied and confirmed meets the ATP
1: Parameter boundaryOutside studied range, same principleThe value(s) fall outside any studied range, but the measurement principle is unchanged
1: Parameter boundaryNo development data existsThe method was validated under the minimal approach; no PAR/MODR was ever established for this parameter
2: Measurement principleUnchangedThe physical or chemical basis of the measurement (e.g., separation mode, detection chemistry, assay format) is the same
2: Measurement principleChangedThe change alters the measurement principle itself (e.g., UV to charged-aerosol detection, chromatographic to spectroscopic, ligand-binding format change)

6. Assessment table: classification and handling path

Parameter boundary (Axis 1)Measurement principle (Axis 2)ClassificationHandling path
Inside PAR/MODRUnchangedUnderstoodManage under the pharmaceutical quality system; document the assessment; verification testing per section 7, typically no revalidation
Outside studied range, same principleUnchangedPartially understoodPartial or full revalidation of the affected performance characteristics per section 7; assess reporting category
No development data existsUnchangedUndetermined (minimal-approach method)Treat as outside studied range by default; scope confirmatory testing conservatively per section 7 until a PAR is established
AnyChangedNew procedureTreat as a new procedure: ATP-driven development, full validation, and very likely a prior-approval submission; this assessment does not close the change, hand off to development

7. Assessment for this change

FieldEntry
Changed parameter(s)<<FILL>>
Proposed value(s)<<FILL>>
Studied range for this parameter (from development report)<<FILL, or "none established">>
Axis 1 status<<FILL: Inside PAR/MODR / Outside studied range, same principle / No development data exists>>
Axis 2 status<<FILL: Unchanged / Changed>>
Classification (from section 6)<<FILL>>
Handling path selected<<FILL>>
Confirmatory testing required<<FILL: e.g. system suitability plus a defined comparative run; partial revalidation of specificity and precision; full revalidation; new development>>
ATP re-confirmation<<FILL: does confirmatory data show the ATP is still met? Yes / No / Pending>>

8. Regulatory reporting implication

FieldEntry
Established conditions (ICH Q12) covering this parameter, if any<<FILL: document reference, or "none defined">>
Change falls within established conditions?<<FILL: Yes / No>>
Proposed reporting category<<FILL: in-PQS change / annual report / prior-approval supplement, per the applicable regional framework>>
Regulatory affairs sign-off<<FILL: name, date>>

9. Mitigations

Gap identifiedMitigationOwnerTarget date
<<FILL, or "none">><<FILL: e.g. establish a PAR for this parameter before future changes rely on this path again>><<FILL>><<FILL>>

10. Residual risk and approval

FieldEntry
Final classification<<FILL>>
Confirmatory testing outcome<<FILL: pass / fail / pending, with reference to the executed protocol>>
Residual risk statement<<FILL: e.g. "acceptable, ATP re-confirmed by comparative testing">>
Completed by (name, role, date)<<FILL>>
QA approval (name, signature, date)<<FILL>>

References

ICH Q14, Analytical Procedure Development (proven acceptable range and MODR concepts). ICH Q2(R2), Validation of Analytical Procedures (scope of revalidation where required). ICH Q12, Lifecycle Management (established conditions and post-approval change management protocols). ICH Q10, Pharmaceutical Quality System (in-PQS change handling).

Confirm the current version of each reference, and the applicable regional variation/supplement framework, before issue.

Revision history

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

Approvals

RoleNameSignatureDate
Author (Method owner)<<FILL>>
Reviewer (Analytical development)<<FILL>>
Reviewer (Regulatory affairs)<<FILL>>
Approver (Quality Assurance)<<FILL>>

Filled specimen

The following shows the assessment completed for an illustrative discontinued-column change on a finished-product assay. Numbers and sources are illustrative; replace them with your own.

FieldEntry
Changed parameter(s)Column, stationary-phase supplier
Proposed value(s)Column C (same stationary-phase chemistry family as the originally validated Column A)
Studied range for this parameterDevelopment report APD-2026-007 studied Columns A and B of the same stationary-phase family; critical-pair resolution held above 2.0 on both
Axis 1 statusInside PAR/MODR (Column C is a third member of the studied column family)
Axis 2 statusUnchanged (same separation mode and detection)
ClassificationUnderstood
Handling path selectedManage under the pharmaceutical quality system
Confirmatory testing requiredSystem suitability on Column C plus a comparative run of 3 batches on Column A and Column C, results within the method’s known intermediate precision
ATP re-confirmationYes: comparative run mean difference 0.4%, within the +/- 2.0% ATP target and the method’s established intermediate precision

Section 8. Established conditions APD-EC-004 define the column stationary-phase family, not a specific supplier part number, as the established condition. Change falls within established conditions: yes. Proposed reporting category: in-PQS change, documented in the quality system, no prior-approval submission required. Regulatory affairs sign-off: T. Reyes, 12 September 2026.

Section 10. Final classification: Understood, in-PQS change. Confirmatory testing outcome: pass (comparative run report CMP-2026-041). Residual risk statement: acceptable, ATP re-confirmed by comparative testing; no further action required beyond routine trending of the new column lot.

Common inspection findings this risk assessment prevents

  • A method change judged “minor” by feel, with no documented check against the studied PAR/MODR, so the classification cannot be defended later.
  • A change that actually alters the measurement principle handled as an in-PQS change because the difference “seemed small,” skipping the development and validation work a new procedure requires.
  • Confirmatory testing scoped without reference to the ATP’s performance margin, so a comparative run passes on a criterion that was never tied to what the ATP actually requires.
  • A reporting-category decision made without checking whether the change is covered by an established condition on file, resulting in either an unnecessary submission or a missed one.
  • A change repeatedly classified “Understood” for a parameter that in fact has no development data behind it, because no one checked whether a PAR was ever actually established.

How to adapt this risk assessment

  1. Set your document number, method, ATP, and development report references in the header.
  2. Confirm the studied ranges you cite in section 7 come directly from the development report, not from memory or an assumption of similarity.
  3. If the method was validated under the minimal approach and no PAR/MODR exists, default to the conservative “no development data exists” row in section 6 until one is established.
  4. Route section 8 to regulatory affairs before implementing the change, not after; established conditions determine the reporting category, and a change implemented ahead of the correct filing action is itself a finding.
  5. Feed a repeated pattern of “outside studied range” classifications for the same parameter back into a future development report; that pattern is a signal the original PAR was set too narrow.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.