A scope baseline template is the approved version of the project scope statement, Work Breakdown Structure (WBS), and WBS Dictionary, serving as the reference point for measuring and controlling scope performance throughout the project. According to the Project Management Institute (PMI), the scope baseline template is a critical component of the Planning Performance Domain in PMBOK 8, providing the authoritative definition of project scope that can only be changed through formal change control. Every scope performance measurement, deliverable acceptance decision, and change evaluation is made by comparing actual results against the scope baseline template. Without a formally approved and maintained scope baseline, projects cannot objectively assess scope performance or make defensible change control decisions that protect project integrity.

What is a Scope Baseline?

A scope baseline template is the approved, time-phased description of project scope that can only be changed through a formal change control process. It combines the Project Scope Statement, WBS, and WBS Dictionary into a single reference document used to evaluate scope change requests, verify that completed work matches the approved plan, and provide the scope component of earned value calculations. The scope baseline is established when the project sponsor formally approves the scope statement and WBS, typically during the planning phase before execution begins. It remains fixed unless a scope change request is approved, at which point both the scope baseline and any affected cost and schedule baselines are updated together to maintain consistency. In PMBOK 8, the scope baseline template is one of three primary project baselines — alongside the schedule baseline and cost baseline — that together constitute the performance measurement baseline used for earned value analysis.

What's Included in This Scope Baseline Template?

• Scope Statement Summary — Condensed description of project deliverables, product scope, key requirements, exclusions, and constraints drawn from the full project scope statement, providing a concise reference within the baseline document for quick access during execution.
• WBS Hierarchy Table — Visual and tabular decomposition of all project work into work packages, with unique WBS IDs, work package names, brief descriptions, and the parent-child relationships that define the hierarchical structure of the total authorized project scope.
• WBS Dictionary Summary — Key attributes for each work package including the responsible owner, estimated effort, estimated duration, defined acceptance criteria, and any technical or quality standards applicable to that specific work package during execution.
• Baseline Approval Tracking — Component-level record of when each element of the scope baseline was approved, by whom, at what version, and any conditions attached to approval, providing the governance audit trail needed for phase gate reviews and project audits.
• Version Control and Change Log — Complete history of all approved scope baseline changes, including the change request reference, the nature of the change, the date approved, and the approving authority, enabling reconstruction of the scope baseline at any point in the project history.
• Adaptive Scope Mapping — For hybrid projects, the mapping between Epics, Features, and User Stories in the product backlog and their corresponding positions in the WBS hierarchy, enabling integrated performance reporting across predictive and adaptive scope elements.

How to Use This Scope Baseline Template (PMBOK 8)

1. Establish only after formal sponsor approval — The scope baseline template is not established until the sponsor formally signs off on both the scope statement and the WBS. Treating a working draft as a baseline undermines change control integrity and makes performance measurement meaningless.
2. Use the WBS Dictionary for work package estimation — The WBS dictionary attributes provide the detail needed for accurate scheduling and cost estimation. Work packages without sufficient dictionary detail are routinely underestimated because assumptions remain implicit and unvalidated.
3. Compare actual deliverables against this baseline during validation — In deliverable acceptance reviews, explicitly reference the scope baseline to confirm that what was produced matches what was authorized. Undocumented scope additions discovered at acceptance are expensive and damaging to relationships.
4. Process all scope changes through formal change control — No change to the scope baseline should be made without a formally approved change request. Even seemingly minor changes erode baseline integrity over time and make performance measurement unreliable for earned value analysis.
5. Maintain version history throughout the project — Every approved baseline revision must be documented with a new version number, effective date, and summary of changes. This history is valuable for claims management, audit responses, and lessons learned analysis at project closure.

When to Create This Document (PMBOK 8)

The scope baseline template is created during the Planning Performance Domain, after the WBS and WBS dictionary are developed and the project scope statement is formally approved. In PMBOK 8, the scope baseline is a required project artifact for any project subject to formal change control. It serves as the scope component of the performance measurement baseline used for earned value analysis throughout the execution phase and as the primary reference for all scope validation activities.

Related Templates

• Project Scope Statement Template
• Scope Management Plan Template
• Deliverables Acceptance Checklist Template
• Change Request Template
• Requirements Documentation Template