Product teams shipping AI medical software quickly hit the same tension: each model, data or performance iteration can reopen a regulatory submission. Predetermined Change Control Plans (PCCPs) address that tension by pre-specifying certain modifications and how they will be validated, without freezing delivery.
This analysis is for SaMD / MDSW manufacturers preparing FDA access (and often a QMS also read under MDSAP). It draws on FDA's August 2025 final guidance: Marketing Submission Recommendations for a Predetermined Change Control Plan for Artificial Intelligence-Enabled Device Software Functions.
What a PCCP is (and is not)
For FDA, a PCCP describes planned modifications to AI-enabled device software functions (AI-DSFs), the methodology to develop, validate and implement them, and an assessment of their impact. FDA reviews the PCCP as part of a marketing submission (510(k), De Novo or PMA) so described modifications can later be implemented without a new submission for each iteration, provided the plan is followed.
A PCCP is not permission to redesign intended use at will, and it is not a substitute for the QMS. It must live inside design control, ISO 13485 change management and the software lifecycle (often IEC 62304), with pre-defined acceptance criteria and audit-ready traceability.
The three building blocks FDA recommends
Description of Modifications
Which modifications are planned (model, data, performance, and so on), with clear bounds.
Modification Protocol
How each modification type will be developed, verified and validated, including acceptance criteria.
Impact Assessment
Which risks/benefits and evidence show the device remains safe and effective after the change.
FDA also recommends presenting the PCCP as a standalone submission section, clearly listed in the table of contents. Intended-use populations and environments should remain coherent as the device evolves.
Anchoring the PCCP in a European QMS
Even though the PCCP is most explicitly formalised on the FDA side, European manufacturers exporting to or preparing for the US should wire it into processes already expected in the EU: change control, clinical/performance evaluation, post-market surveillance and software control. A decorative PCCP outside the eQMS will not survive MDSAP or a design review.
Change control and design control
Every “inside the PCCP” modification still needs the same documentary discipline as an out-of-plan change: requirements, risk, testing, release and implementation decision. The difference is that the protocol was pre-reviewed in the marketing submission.
Monitoring and post-market
Without performance and drift monitoring, the Modification Protocol stays theoretical. Connect the PCCP to PMS indicators, product alerts and the ability to stop a release when criteria are no longer met.
Quick decision grid
- Prioritise a PCCP when the model or data will change often inside a stable intended-use envelope.
- Do not use a PCCP to hide a fuzzy intended use or weak clinical validation.
- Align the FDA PCCP and the CE narrative: same risks, same bounds, shared evidence where relevant.
- Industrialise traceability (protocol, validation runs, criteria) in the eQMS / Qapsule.
For framing and dossier work, see regulatory strategy and CE marking.
FAQ
Does a PCCP remove the need for any new FDA submission?
No. It targets pre-described modifications executed under the protocol cleared/approved in the marketing submission. Outside that envelope, or if you deviate from the protocol, a new submission may be required. Follow FDA guidance and your clearance/approval letter.
Is a PCCP mandatory under the EU MDR?
The FDA-style PCCP is not an identically named MDR formality. MDR already requires change control, clinical evaluation and post-market surveillance. A dual EU/US manufacturer benefits from a pre-specified change plan that is coherent on both sides.
Where should we start?
Stabilise intended use, list truly foreseeable modifications, define protocols and acceptance criteria, then wire everything into change control and monitoring. Without measurable criteria, a PCCP will not convince reviewers.
How does a PCCP relate to the AI Act?
The AI Act emphasises data governance, robustness and monitoring for high-risk systems. A well-run PCCP can support evidence of controlled change, but it does not replace an AI Act / MDR mapping.
Can QARA PULSE help draft a PCCP?
Yes: scoping modifications, validation protocol, QMS/eQMS anchoring, and consistency with the CE file. Contact us for a scoping workshop.
QARA PULSE analysis (June 2026) based on published FDA guidance and field practice. Not personalised regulatory advice. Always validate scope with your counsel and FDA as needed.