This Scope Baseline example shows how Alex Morgan, PMP, established and controlled the approved scope reference for Project Phoenix — a $72,250 website launch managed using the PMBOK Guide 8th Edition. The Scope Baseline is the anchor against which all scope decisions are measured throughout execution, and this example shows what a solid, well-integrated scope baseline looks like for a real digital project.

What Is a Scope Baseline?

The Scope Baseline is the approved version of the project scope, comprising three integrated components: the Project Scope Statement (describing what is and is not in scope), the Work Breakdown Structure (decomposing the scope into manageable work packages), and the WBS Dictionary (providing detailed descriptions for each work package). In PMBOK 8, the Scope Baseline is an output of the Create WBS process within the Planning Performance Domain. It is formally approved by the project sponsor and can only be modified through the Integrated Change Control process. The Scope Baseline is the reference point for Validate Scope (confirming completed deliverables meet requirements) and Control Scope (identifying and preventing scope creep).

What's Inside This Scope Baseline Example

This Scope Baseline example for Project Phoenix includes:

• Scope statement summary: a 12-page responsive corporate website for MCG with CRM integration (Mautic), technical SEO setup, and WCAG 2.1 AA accessibility compliance — delivered by June 13, 2025
• WBS: a three-level decomposition — Level 0 (Website Launch Project), Level 1 (6 packages: Project Management, Requirements & Design, Development, Infrastructure, Testing & QA, Launch & Transition), Level 2 (28 work packages with WBS codes 1.1.1 through 1.6.4)
• WBS Dictionary: detailed description, deliverable definition, acceptance criteria, assigned owner, and budget allocation for each of the 28 work packages
• Scope component tracking: all 28 work packages approved at baseline; 0 work packages deferred; 2 scope requests rejected during execution (live chat module and multilingual content — both documented as out-of-scope in the Scope Statement)
• Baseline approval: Scope Baseline formally approved by Riley Park on March 17, 2025 (kickoff day); no formal re-baseline was required during the project's 13-week lifecycle

How Alex Morgan Used This Scope Baseline

Alex Morgan used the Scope Baseline as the primary reference in every scope conversation throughout Project Phoenix. When Riley Park suggested adding live chat in Week 5, Alex pulled up the Scope Baseline on screen during the meeting and confirmed in real time that live chat was documented as out-of-scope — not as a judgment call, but as an approved, sponsor-signed decision made during planning. When CR-003 (advanced analytics dashboard) was submitted, it was evaluated against the Scope Baseline to confirm it was a net-new scope addition requiring formal change control — which led to its deferral to Phase 2 rather than being absorbed into existing work packages. The Scope Baseline made "no" a documented fact rather than a PM opinion.

Download and Customize

This Scope Baseline example is available as a free download. Use it as a reference to build your own scope baseline, or start with the blank template and fill it in for your project.

• Download the Scope Baseline Template — PMBOK 8 (blank, ready to use)
• Read the article: Scope Baseline in PMBOK 8 — Guide and Best Practices

Scope Baseline Example: Key Takeaways

The standout lesson from this Scope Baseline example is that the three components of the scope baseline work as a system — the Scope Statement defines the boundaries, the WBS provides the structure, and the WBS Dictionary provides the detail. Any one of them in isolation is insufficient; together, they create a scope definition that is complete, unambiguous, and verifiable. Project Phoenix maintained a zero uncontrolled scope change record throughout 13 weeks — a result of having a complete, approved scope baseline from Day 1 and the discipline to reference it consistently whenever a scope question arose.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.