Scope Baseline: Definition, Components & Example [2026]
A. Togay Koralturk, Best-Selling PMP Author
Last updated on October 07, 2026
11 min read
Once a project's scope is agreed, it has to be approved and then locked, so it cannot quietly change. Without that, the scope drifts over time and there is no record of what was originally promised. The scope baseline is that lock: the approved version of the scope that everything else is measured against, so when new work appears, it's obvious whether it was part of the deal or not. This guide explains the scope baseline in full — what it is, its three components, the process it comes from, how it's controlled, and how it appears on the PMP and CAPM exams.
What is a scope baseline?
A scope baseline is the approved version of a project's scope, serving as the reference point against which scope is measured and controlled throughout the project. It's the officially agreed answer to "what is this project going to deliver?" — captured in a set of documents, formally approved, and then held stable so that any later change is visible and deliberate rather than accidental.
The defining word is approved. A scope baseline isn't just a description of scope; it's a controlled, frozen version of it that can only be changed through formal change control, built from three documents covered in the next section.
The 3 components of a scope baseline
The scope baseline is made up of three components, each capturing a different layer of the project's scope. Knowing all three — and that all three, together, form the baseline — is the single most tested fact about it.
- The project scope statement. The narrative definition of scope: the project's deliverables, their acceptance criteria, and — crucially — what's explicitly excluded, along with key assumptions and constraints. It sets the boundaries in words.
- The work breakdown structure (WBS). The hierarchical decomposition of that scope into deliverables and work packages. It turns the narrative into a structured, complete map of everything the project must produce.
- The WBS dictionary. The detailed description behind each WBS element: the work involved, its owner, deliverables, acceptance criteria, and estimates. It supplies the specifics the WBS diagram can't.
The three build on one another: the scope statement defines the boundaries, the WBS structures the work inside those boundaries, and the WBS dictionary details each piece. A scope baseline needs all three, because each answers a different question — what's in and out? (statement), what are all the pieces? (WBS), and what does each piece involve? (dictionary).
Ready to take the next step in project management?
200,000+ Professionals Taught by Our Instructors
What process produces the scope baseline?
The scope baseline is an output of the Develop Scope Structure process — the scope-management activity in which the team decomposes the deliverables into a WBS and documents them in the WBS dictionary. (Develop Scope Structure is the process's name in the current PMBOK® Guide, the Eighth Edition; earlier editions called it Create WBS, and many prep materials still do — same process, current name.) Because the scope statement is created just before (in the Define Scope process) and the WBS and dictionary are produced in Develop Scope Structure, the point at which all three come together and are approved is where the scope baseline is established.
Once created, the scope baseline becomes a component of the project management plan — the overall plan that guides the project. From there it takes on its role as a reference: it feeds into planning the schedule and budget, and it becomes the standard used later to validate deliverables and control changes. This is a common exam detail worth memorizing: if a question asks which process the scope baseline is an output of, the answer is Develop Scope Structure (Create WBS in older materials), and if it asks what the scope baseline is part of, the answer is the project management plan.
The purpose of a scope baseline
The purpose of a scope baseline is to provide a stable, approved reference for measuring and controlling scope, so the project can tell — objectively — whether it's still delivering what was agreed. Without a fixed baseline, scope is whatever each person remembers, and changes cannot be detected.
That reference does several jobs. It enables scope control: by comparing actual work against the baseline, the team spots variance early — work that's missing, or work that's appeared without approval. It's the foundation for the schedule and budget, which are estimated from the baseline's work packages, so a solid scope baseline makes the whole plan more reliable. And it controls scope creep: because the baseline defines exactly what is in scope, any new work is clearly outside it and must be approved and added before it is done.
The scope baseline and change control
Because the scope baseline is the standard everything is measured against, it is a controlled document — it can only be changed through formal integrated change control, never edited informally. A baseline that can be edited without approval is no longer a reliable reference.
In practice, a proposed change to scope follows a defined path: a change request is raised, its impact is analyzed (on scope, schedule, cost, and risk), and it's reviewed and approved or rejected — typically by a change control board. Only if it's approved is the scope baseline updated, and when it is, all three components are revised together (the scope statement, WBS, and WBS dictionary), along with any affected schedule and cost baselines. The baseline is also what two monitoring activities rely on: Validate Scope, where completed deliverables are formally accepted by comparing them to the baseline, and Monitor and Control Scope, where the team monitors scope status and manages changes to the baseline. Scope can change, but only through this documented process, so the baseline always reflects the currently approved scope.
Scope baseline vs. the performance measurement baseline
The scope baseline is one of three project baselines, and it's easy to confuse them. The scope baseline covers scope; the schedule baseline covers the approved timeline; and the cost baseline covers the approved, time-phased budget. Each is the approved, controlled version of its dimension.
Together, these three combine into the performance measurement baseline (PMB) — the integrated baseline used to measure overall project performance, most notably in earned value management. When people loosely say "the project baseline," they usually mean this combined PMB. The relationship is worth keeping straight for the exam: the scope baseline is specifically the scope portion, while the performance measurement baseline is the combination of the scope, schedule, and cost baselines. The scope baseline comes first, because the schedule and cost baselines are estimated from the work packages it defines.
How and when the scope baseline is created
The scope baseline is created by the project manager together with the team, during scope definition — after the requirements have been gathered and the scope has been defined. The sequence is straightforward: the scope statement is written to define the boundaries, the WBS is built to decompose the work, the WBS dictionary is filled in to detail each element, and then the complete set is reviewed and formally approved to become the baseline.
Formal approval is what makes the three documents a baseline. Before approval they are draft planning documents that can be edited freely. After approval, the set becomes the controlled baseline.
The Scope Baseline on the PMP® and CAPM® Exams
The scope baseline is a high-frequency topic in scope management on both the PMP exam and the CAPM, and the facts to lock in are precise. It has three components — the scope statement, the WBS, and the WBS dictionary. It is an output of the Develop Scope Structure process (Create WBS before the PMBOK® Guide's Eighth Edition) and a part of the project management plan. And it is a controlled document that changes only through integrated change control.
Questions frequently test exactly these points: which three documents make up the scope baseline, which process it's an output of, or what a project manager must do before altering it (route the change through formal change control). You may also see it distinguished from the performance measurement baseline. Our PMP Complete Study Guide, the most complete on the market, covers the scope baseline and the wider set of project baselines exactly as the exam frames them. If you're learning project management from the ground up, our Complete Project Management Course teaches scope planning and baselining step by step.
PMP Practice Question: Scope Baseline
During Validate Scope on a facilities project, the customer refuses to formally accept a completed deliverable. The deliverable matches its WBS dictionary entry's description and passes every acceptance criterion in it, but the customer points to the baselined project scope statement, which describes a narrower capability. Investigating, the project manager finds that a change request expanding this deliverable was approved by the change control board four months ago; the WBS and the dictionary entry were updated at the time, but the scope statement was never revised.
What should the project manager do next?
a) Direct the team to rework the deliverable to match the scope statement, since when the baseline's components conflict, the narrative scope statement takes precedence over the WBS and its dictionary.
b) Submit a new change request to expand the scope statement to match the delivered capability, since every edit to a baselined document requires a change control board decision.
c) Retrieve the approved change request, correct the scope statement under that existing approval, and proceed with formal acceptance against the fully updated baseline.
d) Accept the deliverable and log the discrepancy in lessons learned, since the WBS and dictionary — the components that actually define the work — already authorize what was built.
Correct answer: C.
Rationale: The deliverable is right; the baseline record is defective. The board's approval four months ago authorized the change to the scope baseline as a whole, and a baseline update means all three components move together — updating the WBS and dictionary while leaving the scope statement behind was a failure to implement an approved change, not a new scope question. So the fix is administrative: produce the approval record, correct the scope statement under it, and run formal acceptance against the now-consistent baseline. Choice a) invents a precedence among the components that does not exist; the statement, WBS, and dictionary are one baseline and must agree, and "fixing" the deliverable would undo work the board explicitly approved. Choice b) is the subtlest trap, because "every baseline edit needs the board" sounds like discipline — but this edit was already approved; re-routing it treats a documentation correction as a new scope decision and delays acceptance for a change the governance process already made. Choice d) gets the diagnosis half-right and the remedy wrong: informal acceptance bypasses Validate Scope, and leaving the statement uncorrected preserves the exact inconsistency that caused the dispute. Only c) completes the approved change and accepts the deliverable through the formal process. To drill this kind of change-control judgment, work through our PMP practice exams or, at the entry level, our CAPM practice exams.
Ready to take the next step in project management?
200,000+ Professionals Taught by Our Instructors
Frequently asked questions
What is a scope baseline?
A scope baseline is the approved version of a project's scope, used as the fixed reference point the project is measured and controlled against throughout execution. It consists of three documents — the project scope statement, the work breakdown structure, and the WBS dictionary — that are formally approved and then held stable, so any later change is visible and must go through formal change control.
What are the three components of a scope baseline?
The scope baseline has three components: the project scope statement (the narrative definition of deliverables, acceptance criteria, and exclusions), the work breakdown structure or WBS (the hierarchical decomposition of the work), and the WBS dictionary (the detailed description of each WBS element). All three together form the scope baseline; no single one is the baseline on its own.
What process is the scope baseline an output of?
The scope baseline is an output of the Develop Scope Structure process (its name in the PMBOK® Guide, Eighth Edition; earlier editions called it Create WBS), where the team decomposes the deliverables into a WBS and documents them in a WBS dictionary. Because the scope statement is produced just before, the three components come together and are approved at this point. Once created, the scope baseline becomes part of the project management plan.
What is the difference between the scope baseline and the performance measurement baseline?
The scope baseline is the approved version of scope only. The performance measurement baseline (PMB) is the integrated combination of three baselines — the scope baseline, the schedule baseline, and the cost baseline — used to measure overall project performance, especially in earned value management. When people loosely say "the project baseline," they usually mean the PMB.
How does a scope baseline prevent scope creep?
A scope baseline prevents scope creep by defining exactly what is in scope in an approved, controlled form. Because any work not in the baseline is visibly out of scope, new work can't slip in unnoticed — it must be raised as a change request, evaluated, and approved before the baseline is updated and the work is done. The baseline gives the team an approved reference to compare any new work against.
Who creates the scope baseline and when?
The project manager creates the scope baseline together with the team during scope definition, after requirements are gathered and scope is defined. The scope statement, WBS, and WBS dictionary are developed, then the complete set is reviewed and formally approved, which turns those planning documents into the baseline. From that point it's a controlled document, changeable only through change control.
Is the scope baseline on the PMP exam?
Yes. The scope baseline is a high-frequency scope-management topic on the PMP exam. You are expected to know its three components (scope statement, WBS, WBS dictionary), that it's an output of the Develop Scope Structure process (formerly Create WBS) and part of the project management plan, and that it's a controlled document changed only through integrated change control. It may also be distinguished from the performance measurement baseline.
Is the scope baseline on the CAPM exam?
Yes. The CAPM covers the scope baseline as a core part of scope management, usually a little more directly than the PMP — often testing its three components, the process it comes from, or how it's changed. Because the CAPM is scenario-based, you should also be ready to recognize when a change to scope must go through change control against the baseline.
Project Scope Statement: Components & Example [2026]
What a project scope statement is, its six components, a full worked example, a copyable format, and how it anchors the scope baseline — with PMP exam tips.
WBS Dictionary: Components, Example & Template [2026]
A WBS dictionary details every element of a work breakdown structure. What it includes, a worked example, WBS vs. dictionary, how to create one, and exam tips.
Work Breakdown Structure (WBS): Examples & Guide [2026]
A work breakdown structure (WBS) decomposes a project's scope into deliverables and work packages. The 100% rule, types, an example, and PMP exam tips.
