> For the complete documentation index, see [llms.txt](https://framework.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.aic.io/company-operating-manual/commercial-and-contracting-model/change-control.md).

# Change Control

### Purpose

Change control protects delivery, commercial position, timelines, and customer expectations.

Any material change to scope, deliverables, milestones, responsibilities, assumptions, pricing, or acceptance criteria must be controlled.

### What Counts as Change

A change may include:

* new deliverables
* removed deliverables
* altered acceptance criteria
* additional environments
* additional integrations
* revised timeline
* change in customer dependencies
* change in security requirements
* new reporting requirement
* new supplier requirement
* expanded support requirement

### Change Request Requirements

A change request must include:

* change title
* change description
* reason for change
* impact on scope
* impact on timeline
* impact on cost
* impact on risk
* impact on IP
* impact on security
* impact on acceptance
* approval status
* effective date

### Operating Rule

No material change is implemented until approved through the agreed change control process.