Skip to content

Stockertim Dictionary · Project management

Scope statement

Also called project scope statement, statement of scope

In short

A written description of what a project will deliver, its boundaries, main deliverables, acceptance criteria, assumptions and exclusions.

  • Beginner
  • Document
  • Checked

In detail

The scope statement defines the edges of the project. It describes the product or result, lists the deliverables, states how each will be accepted, and, just as importantly, records what is not included. A line such as "staff training is out of scope and will be handled by the HR team" can prevent months of later dispute.

It builds on the charter but goes into more detail. Assumptions are written down so that if they prove false the team can raise a change, and constraints, such as a fixed launch date or a regulatory requirement, are recorded because they shape every later plan. The statement becomes part of the scope baseline together with the work breakdown structure.

Once approved, the scope statement is controlled. Requests to add or remove work go through change control, where their effect on time, cost and risk is assessed before a decision. This is the main defence against scope creep.

In practice

Contracts for outsourced projects often attach a scope statement or statement of work, so that the supplier's obligations and the client's responsibilities are clear and change requests can be priced.

Watch out

  • Exclusions matter as much as inclusions; leaving them out invites assumptions.
  • A scope statement that lists activities rather than deliverables is hard to accept against.

Learn it properly

Official sources

Facts last checked on 3 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English