> 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/delivery-assurance.md).

# Delivery Assurance

### Purpose

Delivery assurance gives confidence that work is progressing, risks are managed, and outputs are fit for purpose.

### Assurance Areas

Delivery assurance covers:

* scope
* schedule
* cost
* quality
* security
* technical architecture
* commercial obligations
* supplier delivery
* acceptance evidence
* customer readiness

### Assurance Questions

A delivery review should ask:

* Are we delivering the agreed scope?
* Are milestones on track?
* Are risks and issues visible?
* Are blockers being resolved?
* Are decisions being made at the right level?
* Is the customer fulfilling dependencies?
* Is quality being built in?
* Are security obligations being met?
* Is acceptance evidence being captured?
* Are changes being controlled?

### Assurance Evidence

Evidence may include:

* signed Statement of Work
* approved delivery plan
* sprint reports
* backlog reports
* test evidence
* architecture decisions
* security review records
* code review records
* acceptance certificates
* customer approvals