Sample scope document · fullstack.sg

Template. This shows the structure of a scope document. Everything in square brackets is a placeholder. It is not taken from a client project.

1. Summary

Project: [Project name] Prepared for: [Agency or team] on behalf of [client, if applicable] Date and version: [YYYY-MM-DD], v[1]

[Two or three sentences: what is being built, for whom, and what it needs to achieve.]

2. In scope

[Page templates or screens, listed individually]
[Components, including the states they need: default, loading, error, empty]
[Integrations, each naming the system and the direction of data]
[Content or data migration, with source and approximate volume]
[Environments: staging and production]
[Documentation and handover]

3. Out of scope

[Visual design, copywriting, imagery]
[Ongoing maintenance after handover, unless agreed separately]
[Third-party subscriptions and hosting costs]
[Anything else discussed but not included]

4. Assumptions

Each assumption is something the estimate depends on. If one turns out to be wrong, the estimate is revisited.

[Approved designs cover desktop and mobile for every template]
[The CRM provides a documented API and a sandbox account]
[Content is supplied in final form by (date)]
[One point of contact makes scope decisions]

5. Dependencies

Dependency	Owner	Needed by
[Repository access]	[Agency]	[Kickoff]
[Hosting account]	[Client]	[Week 1]
[API credentials, test and live]	[Client]	[Week 2]
[Final content]	[Client]	[Week 4]

6. Delivery plan

Stage	Output	Review
[Foundations]	[Project setup, environments, design tokens]	[Preview URL]
[Components]	[Component library with all states]	[Preview URL]
[Templates and integrations]	[Pages assembled; integrations connected]	[Preview URL]
[Launch]	[Production release, monitoring set up]	[Launch checklist]
[Handover]	[Documentation and access transfer]	[Walkthrough call]

7. Acceptance

The work is accepted when [each item in section 2 works as described on the staging environment / on the agreed browsers and devices], reviewed by [name or role].

8. Changes to scope

Requests outside section 2 are estimated in writing and only started once approved by [name or role].

9. Estimate

[Fixed price for the scope above, or a time-based estimate with a range.] [Payment schedule, if applicable.] [What the estimate excludes.]