This guide covers everything you need to know about the scope baseline in PMBOK 8. The scope baseline is the approved, frozen definition of the project’s scope — it consists of the project scope statement, the WBS, and the WBS dictionary, and it is the official reference for all scope control decisions.
What Is the Scope Baseline?
The scope baseline is the approved version of the project scope statement, WBS, and WBS dictionary, which can only be changed through formal change control procedures. It defines the complete scope of work the project will deliver and serves as the reference against which scope performance is measured throughout execution.
Any work not included in the scope baseline is not part of the project. Any request to add work to the project is a scope change that requires a change request and CCB approval before the scope baseline is updated. The scope baseline is the project’s boundary definition — it determines what is in and what is out.
The scope baseline is also the foundation for the cost and schedule baselines: the cost baseline is derived by estimating the cost of everything in the scope baseline; the schedule baseline is derived by scheduling all the activities required to complete the scope baseline. If the scope baseline changes, the other baselines must be reviewed and potentially revised.
Scope Baseline in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the scope baseline belongs to the Scope Performance Domain and is produced during the Develop Scope Structure process. The scope baseline is one of the three project baselines (scope, schedule, and cost) that together form the performance measurement baseline.
The scope baseline feeds into earned value management (EV is calculated based on the value of baseline scope completed), scope verification (comparing completed deliverables to baseline scope), and scope change control (determining whether proposed changes are in or out of baseline scope).
Key Elements of the Scope Baseline
A well-structured scope baseline consists of three integrated components:
- Project Scope Statement — description of project deliverables, acceptance criteria, exclusions, constraints, and assumptions
- Work Breakdown Structure (WBS) — hierarchical decomposition of the total scope into manageable work packages
- WBS Dictionary — detailed descriptions of each WBS element, including deliverable descriptions, acceptance criteria, and responsible party
- Baseline Approval Record — documentation of sponsor approval with date and version
Scope Baseline Example — Project Phoenix
The Project Phoenix scope baseline was approved by Riley Park on January 20, 2024. The scope statement defined a 12-page website with specific technology stack and performance requirements; the WBS decomposed the scope into six Level 2 packages with 23 Level 3 work packages; and the WBS dictionary provided detailed descriptions and acceptance criteria for each work package. The scope baseline was referenced 12 times during execution to adjudicate scope boundary questions.
Five proposed additions were declined as out-of-scope; one addition (the mobile-responsive product page redesign from CR-001) was approved and the scope baseline was formally updated. When Sarah Chen asked in week 14 whether the project could also set up their email newsletter, Alex referenced the scope statement’s exclusions section — email marketing setup was explicitly excluded — and the request was redirected to a future project. This clear, documented boundary prevented significant scope creep.
You can download the complete filled-in example below — it shows exactly how the scope baseline was documented and used in a real project.
Download Free Scope Baseline Template and Example
We have prepared two free resources to help you establish a scope baseline for your own projects:
- Download the Scope Baseline Template — PMBOK 8 (blank, ready to fill in)
- Download the Scope Baseline Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Scope Baseline — Best Practices and Common Mistakes
Treat the scope baseline as a governance tool, not just a document. Every scope dispute during execution should be resolved by referencing the approved scope baseline — not by negotiation or intuition. Get formal written sponsor approval before freezing the baseline. Keep the WBS dictionary current; an outdated dictionary undermines the scope baseline’s usefulness for adjudicating boundary questions.
The scope baseline is most effective when it is specific enough to answer “is this in scope?” unambiguously for 95% of questions that arise during execution. Teams that skip or rush baseline documentation spend the project fighting scope creep because they have no authoritative reference to consult.
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 Scope Baseline 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