Stockertim Dictionary · Project management
Formal acceptance
Also called acceptance sign-off, customer acceptance, sign-off
In short
Written confirmation from the customer or sponsor that a deliverable meets its agreed criteria, transferring it from the project to its owner.
- Beginner
- Process
- Checked
In detail
Formal acceptance is the moment a deliverable stops being the project's responsibility. The customer or sponsor checks it against the acceptance criteria agreed earlier, and, if it passes, signs to say so. Ownership, and often warranty periods and payment obligations, move from the project team or supplier to the receiving organisation.
Acceptance works best when it is planned from the start. Criteria are set in the scope statement or contract, tests are designed to prove each criterion, and the people who will sign are involved early so there are no surprises. Where criteria were vague, acceptance becomes a negotiation, and projects can drift for months in a state of nearly finished.
Acceptance may be conditional, with a list of minor defects to fix by an agreed date, or staged, with each deliverable accepted separately. Either way it should be recorded, because later disputes about whether the project delivered what was asked usually turn on what was signed.
In practice
Contracts often tie a final payment to formal acceptance, and project closure cannot begin until the main deliverables have been accepted.
Watch out
- Using a deliverable is not the same as accepting it; get the signature.
- Acceptance confirms outputs, not that the benefits will follow.
Learn it properly
Official sources
- Government Functional Standard GovS 002: Project Delivery · UK Government (Cabinet Office)
- Project management: an overview · NHS England (Quality, Service Improvement and Redesign tools)
Facts last checked on 3 November 2026.
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.