eduKateSG · Why Science?
Read a planned AI update as a controlled evidence pathway
Use FDA’s final PCCP guidance through planned modifications, development and validation protocols, impact assessments, datasets, human factors, cybersecurity, implementation, labeling and changes outside the plan.
AI-enabled device software can improve after its first marketing authorization, yet every change can also alter performance and risk. A Predetermined Change Control Plan, or PCCP, gives FDA a way to review specified future changes and their controls in advance.
The plan has three connected parts: a Description of Modifications, a Modification Protocol and an Impact Assessment. Together they explain what may change, how the change will be built and validated, and why risks remain controlled.
Did you know? An authorised PCCP is not permission for unlimited self-learning. A future modification must remain within the plan FDA reviewed; changes outside it may need a new marketing submission.
This guide supports AI lifecycle and regulatory literacy. It does not validate a specific plan or product update.
Chapter index
Chapters 1–9: modification scope, data, validation and risks
- 1. A PCCP is reviewed prospectively
- 2. The Description of Modifications sets scope
- 3. The Modification Protocol explains control
- 4. The Impact Assessment connects change and risk
- 5. The plan belongs to a specific device
- 6. Modification boundaries should be precise
- 7. Data management supports trustworthy change
- 8. Validation must match the modification
- 9. Human factors may need re-evaluation
Chapters 10–17: implementation, transparency, monitoring and boundaries
- 10. Cybersecurity remains connected
- 11. Implementation needs configuration control
- 12. Transparency supports users
- 13. Real-world monitoring can test assumptions
- 14. An authorised plan is not unlimited adaptation
- 15. Changes outside the plan need assessment
- 16. PCCP authorization is part of a marketing decision
- 17. A complete receipt follows each release
A Predetermined Change Control Plan becomes understandable when planned modifications, modification protocol and impact assessment travel together. The sponsor includes the plan in a marketing submission so FDA can evaluate specified future modifications before implementation. This connects adaptive development with prospective evidence and control.
Try this
Evidence question: Which official page, guidance or decision supports the point about a pccp is reviewed prospectively? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for a pccp is reviewed prospectively. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for a pccp is reviewed prospectively, its identifier or version context, and one limit that must remain visible.
CHAPTER 2 OF 17 · Define planned changes
2. The Description of Modifications sets scope
FDA reviews a PCCP inside a marketing submission for an AI-enabled device software function. This section identifies the planned AI-enabled device software changes that the sponsor may make under the plan. It also prevents “self-learning” from becoming an unlimited-change claim.
Try this
Evidence question: Which official page, guidance or decision supports the point about the description of modifications sets scope? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for the description of modifications sets scope. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for the description of modifications sets scope, its identifier or version context, and one limit that must remain visible.
CHAPTER 3 OF 17 · Define planned changes
3. The Modification Protocol explains control
An authorized PCCP can support certain future changes without a new marketing submission when the changes remain within the reviewed plan. The protocol describes how each modification will be developed, validated and implemented. The authorized decision and current labeling anchor the plan.
Try this
Evidence question: Which official page, guidance or decision supports the point about the modification protocol explains control? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for the modification protocol explains control. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for the modification protocol explains control, its identifier or version context, and one limit that must remain visible.
CHAPTER 4 OF 17 · Define planned changes
4. The Impact Assessment connects change and risk
Changes outside the authorized plan still require their own regulatory assessment. The assessment explains benefits, risks, mitigations and how the plan supports continued safety and effectiveness. Version, data and validation records remain essential after implementation.
Try this
Evidence question: Which official page, guidance or decision supports the point about the impact assessment connects change and risk? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for the impact assessment connects change and risk. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for the impact assessment connects change and risk, its identifier or version context, and one limit that must remain visible.
A Predetermined Change Control Plan becomes understandable when planned modifications, modification protocol and impact assessment travel together. An authorised PCCP is tied to the device, intended use, software function and marketing submission in which FDA reviewed it. This connects adaptive development with prospective evidence and control.
Try this
Evidence question: Which official page, guidance or decision supports the point about the plan belongs to a specific device? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for the plan belongs to a specific device. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the plan belongs to a specific device, its identifier or version context, and one limit that must remain visible.
FDA reviews a PCCP inside a marketing submission for an AI-enabled device software function. Data inputs, performance ranges, model retraining, user interface or other planned changes need measurable limits. It also prevents “self-learning” from becoming an unlimited-change claim.
Try this
Evidence question: Which official page, guidance or decision supports the point about modification boundaries should be precise? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for modification boundaries should be precise. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for modification boundaries should be precise, its identifier or version context, and one limit that must remain visible.
An authorized PCCP can support certain future changes without a new marketing submission when the changes remain within the reviewed plan. Collection, curation, representativeness, independence and versioning affect whether later training and testing support the planned modification. The authorized decision and current labeling anchor the plan.
Try this
Evidence question: Which official page, guidance or decision supports the point about data management supports trustworthy change? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for data management supports trustworthy change. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for data management supports trustworthy change, its identifier or version context, and one limit that must remain visible.
Changes outside the authorized plan still require their own regulatory assessment. Performance metrics, acceptance criteria, subgroups, sites and comparison methods should test the change described in the plan. Version, data and validation records remain essential after implementation.
Try this
Evidence question: Which official page, guidance or decision supports the point about validation must match the modification? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for validation must match the modification. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for validation must match the modification, its identifier or version context, and one limit that must remain visible.
A Predetermined Change Control Plan becomes understandable when planned modifications, modification protocol and impact assessment travel together. A model or interface update can change how users interpret outputs, respond to alerts or integrate the device into workflow. This connects adaptive development with prospective evidence and control.
Try this
Evidence question: Which official page, guidance or decision supports the point about human factors may need re-evaluation? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for human factors may need re-evaluation. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for human factors may need re-evaluation, its identifier or version context, and one limit that must remain visible.
FDA reviews a PCCP inside a marketing submission for an AI-enabled device software function. Software changes can alter attack surfaces, dependencies and update mechanisms, so security assessment remains part of lifecycle risk. It also prevents “self-learning” from becoming an unlimited-change claim.
Try this
Evidence question: Which official page, guidance or decision supports the point about cybersecurity remains connected? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for cybersecurity remains connected. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for cybersecurity remains connected, its identifier or version context, and one limit that must remain visible.
An authorized PCCP can support certain future changes without a new marketing submission when the changes remain within the reviewed plan. Version identifiers, release records, traceability and rollback plans help prove which authorised modification reached which device. The authorized decision and current labeling anchor the plan.
Try this
Evidence question: Which official page, guidance or decision supports the point about implementation needs configuration control? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for implementation needs configuration control. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for implementation needs configuration control, its identifier or version context, and one limit that must remain visible.
Changes outside the authorized plan still require their own regulatory assessment. Labeling and communications can explain relevant updates, performance boundaries and how users can identify the current version. Version, data and validation records remain essential after implementation.
Try this
Evidence question: Which official page, guidance or decision supports the point about transparency supports users? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for transparency supports users. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for transparency supports users, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Control each release
13. Real-world monitoring can test assumptions
A Predetermined Change Control Plan becomes understandable when planned modifications, modification protocol and impact assessment travel together. Postmarket data may reveal drift, subgroup performance or new hazards, but methods and denominators must be defined. This connects adaptive development with prospective evidence and control.
Try this
Evidence question: Which official page, guidance or decision supports the point about real-world monitoring can test assumptions? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for real-world monitoring can test assumptions. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for real-world monitoring can test assumptions, its identifier or version context, and one limit that must remain visible.
CHAPTER 14 OF 17 · Control each release
14. An authorised plan is not unlimited adaptation
FDA reviews a PCCP inside a marketing submission for an AI-enabled device software function. Only modifications described and controlled by the authorised PCCP can rely on that prospective review route. It also prevents “self-learning” from becoming an unlimited-change claim.
Try this
Evidence question: Which official page, guidance or decision supports the point about an authorised plan is not unlimited adaptation? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for an authorised plan is not unlimited adaptation. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for an authorised plan is not unlimited adaptation, its identifier or version context, and one limit that must remain visible.
An authorized PCCP can support certain future changes without a new marketing submission when the changes remain within the reviewed plan. A modification beyond the PCCP may require a new marketing submission under the applicable regulations and guidance. The authorized decision and current labeling anchor the plan.
Try this
Evidence question: Which official page, guidance or decision supports the point about changes outside the plan need assessment? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for changes outside the plan need assessment. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for changes outside the plan need assessment, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Control each release
16. PCCP authorization is part of a marketing decision
Changes outside the authorized plan still require their own regulatory assessment. The decision letter, summary and labeling should be checked to determine whether and how a plan was authorised. Version, data and validation records remain essential after implementation.
Try this
Evidence question: Which official page, guidance or decision supports the point about pccp authorization is part of a marketing decision? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for pccp authorization is part of a marketing decision. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for pccp authorization is part of a marketing decision, its identifier or version context, and one limit that must remain visible.
A Predetermined Change Control Plan becomes understandable when planned modifications, modification protocol and impact assessment travel together. Record the authorised plan, modification, protocol version, datasets, validation, impact assessment, implementation date, device version, communication and monitoring. This connects adaptive development with prospective evidence and control.
Try this
Evidence question: Which official page, guidance or decision supports the point about a complete receipt follows each release? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, version and one limit for a complete receipt follows each release. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for a complete receipt follows each release, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A planned AI change becomes trustworthy when scope, validation and implementation remain traceable
PCCPs move some evidence work earlier without removing accountability. The plan only succeeds when each deployed version can be matched to the authorised modification, protocol, validation and monitoring record.
Save the device and submission number, authorised PCCP, modification description, protocol and acceptance criteria, training and test data versions, subgroup analyses, impact assessment, human-factors and cybersecurity checks, implementation and rollback plan, labeling, release date, monitoring and access date.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Description of Modifications | Defines future changes within the plan | Which measurable boundary? |
| Modification Protocol | Controls development, validation and implementation | Which acceptance criteria? |
| Impact Assessment | Evaluates benefits, risks and mitigations | What could change clinically? |
| Release record | Shows what was deployed under the plan | Which version and date? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA PCCP Final Guidance — accessed 25 October 2026.
- FDA Predetermined Change Control Plans — accessed 25 October 2026.
- FDA PCCP Guiding Principles — accessed 25 October 2026.
- FDA AI-Enabled Medical Devices — accessed 25 October 2026.
- FDA Medical Device Cybersecurity — accessed 25 October 2026.