# Project scope statement template: define acceptance before planning

Write in-scope and out-of-scope boundaries, acceptance criteria, assumptions and change authority with a worked example for a small delivery project.

Canonical: https://project.responseshift.academy/scope-statement-template/
Publisher: Response Shift
Updated: 2026-10-31

## Describe an accepted result

A scope statement defines the result the project commits to deliver and the boundary around it. “Implement access control” is too broad to estimate or accept reliably. Name the sites, users, functions and acceptance evidence that matter.

Keep the business objective distinct from the deliverables. The objective might be controlled staff access; the deliverables are configured readers, access rules, test evidence and an operational handover. Activities such as attending a meeting do not themselves prove that result exists.

## Worked example: first-entrance rollout



| Part | Fictional scope |
| --- | --- |
| Objective | Provide controlled staff entry through the main entrance. |
| In scope | One entrance, existing staff list, reader installation, rule configuration, acceptance test and handover. |
| Out of scope | Visitor registration, second entrance and replacement of the existing network. |
| Acceptance | Agreed test cases pass; authorised staff gain access, unauthorised test credentials fail, and facilities accepts handover. |
| Assumptions | Network compatibility and staff list accuracy will be confirmed before configuration. |
| Authority | Sponsor approves material scope/date/cost changes through the agreed process. |

## Test whether a new request changes scope

Ask whether the request is necessary to meet the agreed acceptance condition or introduces a new result. Fixing a configuration defect may be required to deliver the original scope. Adding visitor registration introduces a capability that was explicitly excluded.

The distinction affects forecasting, but it does not justify ignoring a real need. Capture the request, assess options and let the authorised owner decide. Scope control should make trade-offs visible rather than become a blanket refusal.

## Copyable scope brief



```text
Business objective / success evidence:
Deliverables and boundaries:
In scope / explicitly out of scope:
Acceptance criteria / reviewer / evidence:
Constraints / assumptions / validation owner:
Interfaces and dependencies:
Baseline version / approval date:
Change authority and escalation path:
```

- [Download the template (Markdown)](https://project.responseshift.academy/scope-statement-template/scope-statement-template.md)
- [Download the worked example (CSV)](https://project.responseshift.academy/scope-statement-template/scope-statement-example.csv)

## Review it with the people who accept the work

Ask the operational owner to explain what they will do on the first day after handover. This often exposes missing training, support or access requirements. Resolve them before treating the scope as a reliable scheduling input.

Avoid criteria that depend only on opinion, such as “easy to use”, without describing the task or evidence. The right level of detail depends on the project; this is a planning worksheet, not a substitute for contractual drafting.

## Continue

[Project practice week](https://project.responseshift.academy/practice-week/)

- [APM: project controls background](https://www.apm.org.uk/resources/what-is-project-management/what-is-project-controls/)
