When you need it
Use this statement when the project needs an agreed description of what it will deliver and what falls outside its boundary, before detailed planning, procurement, or baseline approval proceeds.
DOCX /
AI tools and documents for engineering and project management.
Project Scope Statement
Describe the project deliverables, inclusions, exclusions and acceptance boundaries.
How to use this templateThis Word template contains prepared headings, tables, project fields and completion notes. Add your information, review the completed document and remove the notes before issue.
The form prepares a separate brief; it does not fill the Word or Excel file.
Read product descriptions in your language. The Word and Excel template files are in English.
Only selected pages are shown. This is not the complete template. The full editable Word or Excel file is supplied with purchase.
Learning
How to use this template
What it helps you decide
It gives sponsors and delivery teams a common reference for deliverables, acceptance, exclusions, assumptions, and responsibilities, making later discussions about completion or proposed additions more precise and easier to evidence.
How to complete it
- Describe Purpose and product description from the approved objectives, then define Deliverables and boundaries with enough specificity to distinguish adjacent packages or services.
- State Acceptance requirements and Exclusions and responsibilities using actual agreements, preserving assumptions and constraints that materially influence what the project can deliver.
- Review Assumptions and constraints with responsible contributors, then record Baseline status and open decisions so readers know which boundaries are agreed or pending.
Who prepares and reviews it
The project manager typically drafts it with the sponsor, users, engineers, and package owners. Commercial and planning contributors assess boundaries, while the designated governance authority approves its baseline status and unresolved decisions.
A mistake to avoid
Using broad phrases such as complete facility without defined boundaries can unintentionally absorb adjacent infrastructure, services, or documentation that the project never planned to provide.
Illustrative example
Illustrative example: a distribution-centre project includes the building and internal yard but excludes the public-road upgrade. The statement records that boundary and the required handover outputs. A later request for external junction design is assessed as a scope question against this agreed reference.
Document contents
- Purpose and product description
- Deliverables and boundaries
- Acceptance requirements
- Exclusions and responsibilities
- Assumptions and constraints
- Baseline status and open decisions
Required inputs
- Project name, location, company, document number and revision
- Actual project scope, source records and responsible roles
Practical tools.
Professional judgment.
Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.
Prepare project brief