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.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Project Scope Statement. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Project Scope Statement as a decision instrument rather than an administrative form. The subject terms—scope, statement, template, example, worked—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Name the decision. Write the decision, approval, handover or control activity the completed template must support.
- Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
- Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
- Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
- Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Filling every box even when a field is not applicable instead of recording why.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Writing vague statements without an owner, measure, date or evidence source.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Copying a previous project without revalidating assumptions and stakeholders.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Using the document as a private worksheet when it is meant to support a shared decision.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Creating an approved baseline but failing to define who maintains it and when.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Is the purpose and intended decision clear to a reader outside the team?
- Are owners, dates, measures and sources complete and internally consistent?
- Which fields are assumptions and how will they be validated?
- What event, threshold or review date causes this document to change?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Project Scope Statement?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about scope would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- Risk Management in Portfolios, Programs, and Projects: A Practice Guide — Project Management Institute. Used for risk practices across portfolios, programs and projects. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.