# 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 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://framework.aic.io/company-operating-manual/delivery-governance/acceptance-and-sign-off.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.