DELIVERABLE ACCEPTANCE DOCUMENT
Project Name/Number:
Prepared by:
Date:
Customer/End User Group:
Contact Name:
Project Type (S/M/L):
Business Unit:
Project Manager:
Project Sponsor:
The document is used to formalize the acceptance of the deliverables of the project by the Project Sponsor, Buyer,
Customer, or End user. Approval by the appropriate approval authority constitutes acceptance of the deliverable and
will allow the Project Manager to move on to the closing of the project (e.g., Archiving, Lessons Learned, etc.).
Requirements for formal deliverable acceptance, and how to address non-conforming deliverables, are usually
defined in the contract.1
APPROVAL
Comments:

Make required revisions to transition plan.

Sign this approval form below.

Bring product documentation up to date.
REVISE AND RESUBMIT – the approvers require significant change in the plan and wish to reassess
before final decision.
Comments:

Make required revisions to the transition plan.

Make required product/deliverable changes.

Resubmit for approval.
REJECT DELIVERABLE AND PROJECT

Archive documents.

Close the project.
APPROVAL AUTHORITY
Estimated date:
Comments:
DATE
(Project Sponsor, Buyer, Customer, or End User)
PROJECT MANAGER
DATE
1A
Guide to the Project Management Body of Knowledge (PMBOK® Guide) Fifth Edition. This content is copyrighted material of, and
owned by, the Project Management Institute, Inc. (PMI), copyright 2013. This content has been reproduced with the permission of
PMI. Unauthorized reproduction of this material is strictly prohibited.
©2013 UPMM™ templates are owned and copyrighted by International Institute for Learning, Inc. (IIL). Templates are used with the permission of IIL.
1