Caesar AI Atlas
RegulatoryAdvanced

Substantial Modification vs Intended Purpose

A side-by-side comparison of Substantial Modification and Intended Purpose. Understand how a post-market change differs from the declared use that defines system scope and compliance expectations.

Quick Verdict: Use Intended Purpose to define the system’s approved use baseline; use Substantial Modification when a later change affects compliance or changes that purpose.

At a Glance

Substantial Modification

Substantial Modification defines change to an AI system after market placement or service deployment that affects compliance or changes the system’s intended purpose.

Key Characteristics
  • Refers to a change after market placement or service deployment
  • Can affect compliance or change the system's intended purpose
  • May create new assessment or responsibility obligations
Watch Out For
  • A change may be substantial even if the product name remains the same
  • Post-deployment changes should be assessed against compliance and purpose impacts

Context: Most relevant when evaluating releases, redesigns, new uses, or deployment changes after an AI system is already on the market or in service.

VS
Intended Purpose

Intended Purpose defines use for which an AI system is designed, marketed, or deployed by its provider.

Key Characteristics
  • Defines the use for which an AI system is designed, marketed, or deployed
  • Covers expected context, users, functions, outputs, and limitations
  • Supports risk classification, compliance, and accountability
Watch Out For
  • Purpose statements should be specific enough to guide classification and controls
  • Actual deployment should not silently exceed the documented purpose

Context: Most relevant when setting the baseline for what the system is supposed to do and how it should be governed.

Key Differences

AspectSubstantial ModificationIntended Purpose
Regulatory purposeSubstantial Modification identifies whether a later change creates new compliance or responsibility consequences.Intended Purpose defines the original or current approved use scope for the AI system.
Trigger pointIt is assessed after placing on the market or putting into service when the system changes.It is defined during design, marketing, deployment, and documentation of the system.
Required evidenceEvidence includes change records, impact analysis, test results, conformity assessment implications, and updated documentation.Evidence includes purpose statements, user instructions, functional descriptions, output descriptions, and limitations.
Responsible actorThe actor making or controlling the change may need to evaluate whether new obligations arise.The provider is central because the provider defines how the system is designed, marketed, and documented.
Audit implicationAuditors look for traceable decisions showing whether a change affected compliance or intended purpose.Auditors compare declared purpose with design documents, marketing, user instructions, and actual use.
Operational questionThe key question is whether the system has changed enough to alter obligations.The key question is what the system is supposed to do and under which conditions.
Caesar AI Note

In practice, substantial modification is difficult to manage when the intended purpose was vague at the beginning. A precise purpose statement makes later change-control decisions more defensible.

Notes

Common Mistakes

1

Treating all product updates as non-substantial without documenting the analysis.

2

Changing the practical use of a system without updating the intended purpose.

3

Assuming only technical model changes can be substantial.

4

Failing to link release management with compliance documentation.

When to Use Each

substantial-modification

Use Substantial Modification when assessing a change to an AI system after it has been placed on the market or put into service. It is the right concept for release governance, change control, and deciding whether new assessment or responsibility obligations may apply.

intended-purpose

Use Intended Purpose when documenting the system’s approved function, users, context, outputs, and limits. It provides the baseline against which later changes and compliance impacts can be assessed.

Compliance Note

Under the EU AI Act, intended purpose helps determine classification and obligations, while substantial modification can reopen assessment and responsibility questions after deployment. ISO/IEC 42001-style governance should connect change management records to purpose and compliance impact analysis.

FAQ

Can a change in intended purpose be a substantial modification?+

Yes. A change that alters the system's intended purpose can be a substantial modification in regulatory contexts and may create new assessment or responsibility obligations.

Is substantial modification only about code changes?+

No. The concept concerns changes that affect compliance or intended purpose, which may include technical, functional, deployment, or use-context changes.

Why should intended purpose be documented before deployment?+

A documented intended purpose creates the baseline for classification, accountability, and later change assessment. Without it, teams struggle to determine whether a change is material.

Recently Viewed

No recently viewed comparisons yet.