A scope baseline template is the approved version of the project's formal scope documents — consisting of the project scope statement, the work breakdown structure (WBS), and the WBS dictionary — that serves as the reference baseline for scope measurement and change control throughout the project. According to the Project Management Institute (PMI), the scope baseline is a component of the project management plan in PMBOK 8 and can only be changed through formal change control procedures. It provides the definitive answer to the question "what is this project supposed to deliver?" at any point during execution.

What is a Scope Baseline?

A scope baseline template consolidates the three scope documents that together define the complete, authorized scope of the project: (1) the project scope statement, which describes the project scope, major deliverables, assumptions, and constraints; (2) the WBS, which provides the hierarchical decomposition of all work to be performed; and (3) the WBS dictionary, which provides detailed information for each WBS component. In PMBOK 8, the scope baseline is the foundation for the cost baseline and the schedule baseline — no meaningful performance measurement is possible without a clearly defined scope baseline.

What's Included in This Scope Baseline Template?

• Project Scope Statement - The detailed description of the project scope, including the product scope description, key deliverables list, acceptance criteria, project exclusions, and any constraints or assumptions that bound the project work.
• Work Breakdown Structure (WBS) - The hierarchical decomposition of the total project scope into work packages, structured by deliverable or phase, with each node identified by a unique WBS code.
• WBS Dictionary Entries - For each work package in the WBS: description, responsible party, deliverable, acceptance criteria, schedule constraints, budget, quality requirements, and scope inclusions/exclusions.
• Assumptions Log Reference - A reference to the assumptions log entries that underpin the scope baseline, making explicit the conditions under which the scope statement is valid.
• Baseline Approval Record - The date the scope baseline was approved, the names and roles of those who approved it, and the version number, creating a clear audit trail for scope baseline changes.
• Change History - A log of all approved changes to the scope baseline, including the change request ID, description of the change, approval date, and the version of the baseline that superseded.

How to Use This Scope Baseline Template (PMBOK 8)

1. Establish the scope baseline before any execution work begins - Executing work before the scope baseline is approved means performing work against an undefined scope. Changes discovered after execution starts are far more expensive to incorporate.
2. Use the baseline as the reference for all scope change decisions - When a change request is submitted, evaluate it against the approved scope baseline, not against informal understandings. The baseline is the contractual reference point for scope.
3. Maintain version control on the scope baseline - Every approved change that modifies the scope baseline must result in a new baseline version. Without version control, it is impossible to know what scope was approved at any given point in the project.
4. Link the cost and schedule baselines to the scope baseline - The cost and schedule baselines are meaningless without the scope baseline they are built on. Ensure all three baselines are approved at the same time and reference each other explicitly.
5. Use the WBS dictionary for contract statement of work - When work packages are contracted externally, the WBS dictionary entry provides the starting point for the statement of work, ensuring contractual scope aligns precisely with the project scope baseline.
6. Validate scope against the baseline at each phase gate - Before transitioning to the next phase, confirm that all deliverables completed in the current phase are aligned with the scope baseline. Scope validation at phase gates prevents undetected drift.

When to Create This Document (PMBOK 8)

The scope baseline is established during the planning focus area after the scope statement, WBS, and WBS dictionary have been developed and formally approved. In PMBOK 8, the scope baseline is a component of the project management plan and must be in place before work begins on the cost baseline and schedule baseline. Changes to the scope baseline after approval require formal change control through the Assess and Implement Changes process.

Related Templates

• Scope Management Plan Template
• Work Breakdown Structure Template
• WBS Dictionary Template
• Cost Baseline Template
• Schedule Baseline Template

Complete Guide & Filled-In Example

Get the most out of this template with the two companion resources below:

• Scope Baseline in PMBOK 8 - Complete Guide - Understand the purpose, key elements, and best practices before filling in the template.
• Download the Filled-In Example - Project Phoenix - See exactly how this document was completed for a real $72K website launch project.