# Project Execution — Acceptances

![Project Execution — Acceptances](/docs-content/93da95bc85-06-acceptances.png.webp)

**Navigation:** Intelligence → Project Execution → Acceptances  
**Primary audience:** project managers, delivery owners, quality roles, contract owners, and authorized customer collaborators

## Purpose

Acceptances records whether deliverables, milestones, changes, and other outcomes were explicitly accepted, conditionally accepted, rejected, or remain pending. It connects the precise accepted statement to authorized evidence and open conditions.

## Scope controls and indicators

Period selects acceptance or request date. Project filters context. State selects Accepted, Pending, Conditional, Rejected, Expired, or Overdue. Evidence Type filters written communication, meeting statement, signed document, system approval, or another permitted source.

Deliverables is total scope. Accepted shows evidenced completed approvals. Pending shows requested decisions awaiting a result. Conditional counts approvals whose stated conditions remain open.

## Acceptance register

Each row shows deliverable, project, state, requested and decided dates, accepting authority, evidence type, conditions, owner, and due date. Selecting a record opens its evidence chain.

## Acceptance evidence chain

The chain presents request, response, conditions, revised deliverable versions, later confirmation, and closure in chronological order. It separates an informal positive statement from formal authority and exposes contradictory sources.

## Supporting analysis

**Acceptance aging** groups pending or overdue items by age. **Evidence strength** distinguishes explicit written, explicit meeting, conditional, indirect, and human-verified evidence. **Acceptance actions** shows escalation, request, closure, and clarification work.

## Actions

- **Record acceptance** captures the exact statement, authority, object, conditions, date, and evidence.
- Request or remind the appropriate authority.
- Open the evidence source and effective deliverable version.
- Add, satisfy, or reopen a condition.
- Escalate an overdue request.
- Close an accepted deliverable when all conditions and completion requirements are met.

## Recommended procedure

Verify the person or mechanism has authority, identify the exact version and scope accepted, and record every condition. Keep project completion separate from acceptance when delivery is finished but customer approval is still pending.

## Interpretation

The screen records evidence of acceptance; it does not determine legal enforceability. Conditional acceptance remains open until its condition has evidenced resolution.

## Related screens

[Scope Changes](/documentation/packages/bnd-scope/screens/intelligence-project-scope-changes), [Decisions & Commitments](/documentation/packages/bnd-work/screens/work-decisions-and-commitments), and [Meeting Files & Versions](/documentation/packages/bnd-evidence/screens/home-meetings-files-and-versions).