> 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/delivery-governance/project-controls.md).

# Project Controls

### Purpose

Project controls ensure that delivery is planned, tracked, and governed.

### Required Controls

Each project should maintain:

* approved Statement of Work
* delivery plan
* project initiation document
* governance cadence
* RAID log
* change log
* decision log
* dependency log
* milestone tracker
* acceptance register
* financial tracker
* resourcing plan

### Control Reviews

Controls should be reviewed:

* at mobilisation
* before each milestone
* during weekly delivery reviews
* before customer governance meetings
* when a major risk or change occurs
* before acceptance
* at closure

### Control Ownership

The Delivery Lead owns project controls.

The Commercial Lead owns commercial controls.

The Technical Lead owns technical controls.

The Security Lead owns security controls.