What a written project scope should include

A written scope is the shared description of what will be built. It protects both sides, because it turns a conversation into something that can be checked.

Deliverables. A list of what will exist at the end: pages, features, integrations. If something is not on the list, it is not included unless the scope is changed.

What is out of scope. Naming what is excluded prevents assumptions. Content writing, photography or third-party subscriptions are common examples to state either way.

Milestones. For larger projects, work can be split into agreed milestones, each with defined deliverables. This lets progress be reviewed in stages.

Revisions. How feedback is handled and what counts as a revision. Revisions usually apply to the agreed deliverables; new features or major changes may need a separate estimate.

What you provide. Content, access to accounts, and a named person for approvals, with an indication of when each is needed.

Handover. What you receive when the work is complete, and who holds the accounts the project depends on.

Read the scope against your own one-sentence goal for the project. If the goal cannot be reached with the listed deliverables, raise it before work begins.

Have a similar product challenge? Explore Opplexify’s software development services, review starting project prices, or tell us what you need.