This guide covers everything you need to know about deliverables in PMBOK 8. Deliverables are the tangible or intangible outputs produced during project execution that must meet agreed acceptance criteria before the project can close. Managing deliverables rigorously is the difference between a project that ends with satisfied stakeholders and one that ends in disputes.
What Are Deliverables?
A deliverable is any unique, verifiable product, result, or capability produced to complete a process, phase, or project. Deliverables can be external (the website, the report, the software release delivered to the client) or internal (the project management plan, the test results, the training materials). In PMBOK 8, deliverables are central to the execution and monitoring of project work.
Each deliverable must have documented acceptance criteria — the specific, measurable conditions it must satisfy for the sponsor or client to formally accept it. Without clear acceptance criteria, what counts as “done” is subjective and disputes are inevitable. Acceptance criteria should be defined during scope planning, not during the acceptance conversation.
PMBOK 8 emphasizes that deliverables are inspected and formally accepted through a verification process. Accepted deliverables are then handed over or transitioned to the sponsor, client, or operations team as part of project closure.
Deliverables in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, deliverables belong to the Governance Performance Domain and are produced during the Manage Project Execution process. PMBOK 8 treats deliverable acceptance as an integrated activity connecting scope verification, quality control, and formal closure.
Accepted deliverables feed directly into the Close Project or Phase process. Any deliverable that fails acceptance criteria generates a defect repair change request, creating a formal feedback loop between execution and change control.
Key Elements of Deliverables Tracking
A well-structured deliverables acceptance document typically includes:
- Deliverable ID and Name — unique identifier and descriptive name for each output
- Acceptance Criteria — specific, measurable conditions the deliverable must meet
- Verification Method — how the deliverable will be tested or inspected
- Acceptance Status — pending, accepted, rejected, or conditionally accepted
- Signoff — authorized stakeholder signature and date confirming acceptance
Deliverables Example — Project Phoenix
Project Phoenix produced seven major deliverables: the Project Management Plan, the Website Design Mockups, the Developed Website (frontend and backend), the Hosting Infrastructure Setup, the QA Test Report, the Launch Checklist, and the Final Project Report. Each deliverable had documented acceptance criteria established during the Define Scope process and reviewed with Sarah Chen before execution began.
The most scrutinized deliverable was the Developed Website. Its acceptance criteria included page load time under 3 seconds on 4G, a Google Lighthouse performance score above 85, zero critical bugs in the QA report, and mobile responsiveness verified across iOS and Android. The website passed all criteria on first submission, and Sarah Chen signed the acceptance form on April 28, 2024 — two days ahead of schedule.
You can download the complete filled-in example below — it shows exactly how deliverables acceptance was managed in a real project context.
Download Free Deliverables Template and Example
We have prepared two free resources to help you apply deliverables management on your own projects:
- Download the Deliverables Acceptance Checklist Template — PMBOK 8 (blank, ready to fill in)
- Download the Deliverables Acceptance Checklist Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Deliverables — Best Practices and Common Mistakes
Define acceptance criteria during scope planning, get them approved in writing by the client or sponsor, and never start work on a deliverable without agreed acceptance criteria. Use a formal acceptance checklist for every major deliverable — verbal acceptance does not create an audit trail. Document conditional acceptances clearly, specifying exactly what must be corrected and by when.
The deliverables process is most effective when acceptance criteria are specific, measurable, and agreed upon before work begins. Teams that skip or rush this step often find themselves in end-of-project disputes where the client claims deliverables do not meet unstated expectations.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Project Management