This guide covers everything you need to know about the project scope statement in PMBOK 8. The project scope statement is the detailed written description of what the project will and will not deliver — it is the boundary document that defines what is in scope, what is explicitly out of scope, and what constraints and assumptions govern the work.
What Is the Project Scope Statement?
The project scope statement is a detailed description of the project deliverables and the work required to create them. It includes the product scope description (what the deliverables are), the acceptance criteria (how deliverables will be verified), the project exclusions (what is explicitly not included), and the constraints and assumptions that bound the work.
The project scope statement builds on the project charter by providing the level of detail needed to guide planning, execution, and control. While the charter defines the project at a high level and authorizes the project manager, the scope statement defines the work with enough specificity that the team knows what to build and the client knows what to expect.
Once approved, the scope statement becomes the reference for all scope-related decisions. Any proposed addition to the project’s scope requires a change request; the scope statement is the document used to determine whether a request is in scope or out of scope.
Project Scope Statement in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the project scope statement belongs to the Scope Performance Domain and is produced during the Define Scope process. PMBOK 8 maintains the scope statement as a core planning artifact, recognizing that clear scope definition is foundational to all other planning activities — you cannot build a reliable schedule, budget, or risk register without a defined scope.
The project scope statement feeds directly into the WBS development process, the requirements management plan, and the risk register. It is also the reference document for the scope baseline and the primary input for stakeholder scope reviews.
Key Elements of the Project Scope Statement
A well-structured project scope statement typically includes:
- Product Scope Description — detailed description of the deliverables and their characteristics
- Acceptance Criteria — the specific conditions each deliverable must satisfy to be accepted
- Project Deliverables — complete list of all deliverables the project will produce
- Project Exclusions — explicit statement of what the project will not deliver
- Constraints — limiting factors affecting how the project can be executed
- Assumptions — conditions treated as true for planning purposes
Project Scope Statement Example — Project Phoenix
The Project Phoenix Scope Statement defined the project as the design, development, and launch of a new 12-page responsive website for TechCorp, including homepage, product catalog (up to 50 products), checkout flow with Stripe integration, CMS setup using WordPress, hosting on CloudHost Pro, and basic SEO configuration for the 20 target keywords identified during discovery. The acceptance criteria required a Google Lighthouse performance score above 85, page load time under 3 seconds on 4G, and zero critical bugs in the QA report.
The exclusions section was as important as the inclusions: explicitly excluded were mobile app development, social media management, content writing beyond the homepage and product descriptions, email marketing setup, and any ongoing maintenance beyond the 30-day hypercare period. These exclusions prevented five potential scope creep requests during execution, each of which was redirected to the scope statement as the definitive reference.
You can download the complete filled-in example below — it shows exactly how the project scope statement was written for a real project.
Download Free Project Scope Statement Template and Example
We have prepared two free resources to help you write a project scope statement for your own projects:
- Download the Project Scope Statement Template — PMBOK 8 (blank, ready to fill in)
- Download the Project Scope Statement Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Project Scope Statement — Best Practices and Common Mistakes
Write the exclusions section with the same care as the inclusions. A comprehensive exclusions list is one of the most effective scope management tools available — it preemptively addresses the most common sources of stakeholder scope creep requests. Be specific about acceptance criteria: vague criteria create disputes at delivery; specific, measurable criteria create clarity and speed up acceptance.
The project scope statement is most effective when it is reviewed and signed off by the key stakeholders before the WBS is developed and execution begins. Teams that skip or rush this document often spend the entire project debating what is and is not included in the scope.
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.
Free Template & Filled-In Example
Apply what you’ve learned with these two free resources:
- Download the Free Project Scope Statement Template (PMBOK 8) — Ready-to-use blank template for your next project.
- Download the Filled-In Example — Project Phoenix — See exactly how this document was completed for a real $72K website launch project.
Project Management