Project Scope Statement
Clearly define boundaries, deliverables, and exclusions to prevent scope creep with this master template and worked example.
§1 Purpose of the Scope Statement
The Project Scope Statement is the definitive agreement on what the project will—and crucially, will not—deliver.
While the Project Charter authorizes the project's existence, the Scope Statement establishes its detailed boundaries. It acts as the primary mechanism for controlling scope creep. By explicitly listing deliverables, defining hard acceptance criteria, and detailing project exclusions, the project manager creates a strict baseline against which all future Change Requests must be evaluated.
§2 Blank Template
A standardized framework for defining the boundaries, outputs, and constraints of a new project.
This document should be drafted during the Planning phase, reviewed with key subject matter experts, and formally signed off by the Project Sponsor before execution begins.
PROJECT SCOPE STATEMENT
Project Scope Description
Project Deliverables
Product Acceptance Criteria
Project Exclusions
Project Constraints
Project Assumptions
§3 Worked Example: Mary's Consulting
A completed example demonstrating how to define strict parameters for a mid-sized digital implementation project.
Notice how the project manager uses Australian spelling conventions (e.g., catalogue, colour, optimised) and translates broad business desires into highly specific deliverables and exclusions.
PROJECT SCOPE STATEMENT
Project Scope Description
Project Deliverables
- Approved brand and visual design system - brand guidelines, colour palette, typography, component library.
- Information architecture and wireframes - sitemap, page templates, interaction flows.
- Content set - home, services, case studies (≥ 20), consultant directory entries, blog seed content (≥ 10 posts), legal pages.
- CMS-driven website - fully developed responsive site with editor workflow.
- CRM integration - contact and RFP forms routed to the company CRM via API with logging and retry.
- Hosting environment - production hosting, DNS, SSL, CDN, monitoring, and backup.
- Test & QA artifacts - test plan, executed test cases, performance report, third-party WCAG 2.1 AA audit report.
- Production launch - Go-Live event, post-launch support transition.
- Project management documents - charter, plans, logs, status reports, lessons learned, formal acceptance.
Product Acceptance Criteria
- All Must-priority requirements verified and validated as documented in the Requirements Traceability Matrix.
- 75th-percentile Largest Contentful Paint (LCP) < 2.5 seconds in the pre-launch performance test.
- Third-party WCAG 2.1 AA audit returns zero Severity-1 findings.
- User Acceptance Testing completed with no open Severity-1 or Severity-2 defects.
- CEO (Mary) signs off on brand/visual fit.
- Marketing Lead signs off on content and CMS workflow.
- Legal/Compliance signs off on GDPR and accessibility.
- Production hosting documented and handed off to IT/Hosting Operations.
Project Exclusions
- Internal consultant portal (extranet, time tracking, client workspaces).
- Client project delivery tools, dashboards, or collaboration spaces.
- Billing, invoicing, or financial-system integration.
- Paid advertising campaigns, SEO content production beyond launch seed, and ongoing marketing operations.
- Multi-language translation of consultant bios at launch (deferred to a future phase).
- Mobile native applications (iOS / Android).
- Migration of historical blog content older than 24 months.
Project Constraints
- Budget: Total project cost capped at $150,000 USD. Any expenditure beyond this requires sponsor approval.
- Schedule: Production launch must occur on or before the November 2026 Go-Live milestone.
- Resources: Core team is fixed at the Project Manager (Andrew) plus three team members (Bob, Bill, Christine). Functional manager approval is required to add resources.
- Brand approval: Final brand and visual direction must be approved personally by the CEO (Mary). No delegation of this approval is permitted.
- Quality: Site must meet WCAG 2.1 AA, GDPR, and the firm's IT security standards. These are non-negotiable.
- Technology: CMS selection must be from the firm's approved technology list; hosting must use the firm's approved cloud provider.
- PM Authority: The PM may approve expenditures up to $5,000 per item and reallocate up to 10% within budget categories. Anything beyond requires sponsor approval.
Project Assumptions
- The three core team members will be available at planned allocations through project close.
- Mary will be available for design reviews at agreed checkpoints; turnaround on brand decisions ≤ 5 business days.
- The existing CRM offers a supported integration method (API or vendor connector) for lead capture.
- Consultants worldwide will provide updated bios and case-study content within agreed deadlines.
- WCAG 2.1 AA is the accepted accessibility standard for the project.
- Marketing will execute SEO and content campaigns post-launch to drive traffic; the project itself does not include those activities.
- The hosting/CMS vendor's standard SLA (≥ 99.5% uptime) is acceptable to IT Operations.
- No major change in the firm's service offerings during the project timeline.
Quantify the Criteria
Avoid vague terms like "fast" or "user-friendly" in acceptance criteria. Notice how the PM quantified performance as an LCP of < 2.5 seconds, creating an objective target.
Define Authority
The constraints section explicitly caps the PM's financial authority ($5,000 variance limit). This clarifies exactly when a change must be escalated to the sponsor.
Assumptions = Risk
Every assumption listed here (e.g., "CRM offers a supported API") must immediately be transferred to the project's Risk Register to track the likelihood of it proving false.
