> 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/acceptance-and-sign-off.md).

# Acceptance and Sign-Off

### Purpose

Acceptance confirms that a deliverable has met agreed criteria.

Acceptance must be evidence-based and commercially traceable.

### Acceptance Inputs

Acceptance should be based on:

* agreed deliverable definition
* agreed acceptance criteria
* submitted evidence
* customer review
* defect or exception status
* approval record

### Acceptance Outcomes

Possible outcomes:

* accepted
* accepted with minor observations
* rejected with reasons
* deferred pending customer dependency
* withdrawn due to change control

### Rejection Standard

A rejection must:

* identify the failed acceptance criterion
* explain the issue
* provide evidence
* define required remediation
* confirm review timescale

### Acceptance Record

Acceptance records should include:

* deliverable name
* version
* submission date
* acceptance criteria
* evidence provided
* review outcome
* approver
* approval date
* comments