How to Write a Website or Software Scope of Work

Make a project scope useful for decisions and delivery by defining outcomes, boundaries, responsibilities, assumptions, and change handling.

By Aleksej Djokic ยท

Scope is a shared agreement

A good scope gives the client and delivery team a common description of the outcome, work included, and conditions around it. That makes trade-offs discussable before they become surprises.

Include what people otherwise assume

  • Goals and acceptance criteria
  • User roles, key journeys, and supported devices or browsers
  • Content, data, integrations, migration, and third-party responsibilities
  • Accessibility, privacy, security, performance, and launch expectations
  • Client inputs, review windows, approvals, and ownership
  • Explicit exclusions and a process for evaluating changes

Make each deliverable testable

  1. Name the behavior

    Describe what a user or editor can do, rather than only naming a page.

  2. Define done

    State the evidence that shows it works, including empty, error, and permission states.

  3. Surface dependencies

    Mark work that depends on copy, credentials, data cleanup, approvals, or another vendor.

  4. Set the change path

    Assess new requests against time, cost, risk, and the agreed outcome.

Specific does not mean inflexible

Describe a firm outcome while leaving implementation details open to professional judgment. That protects the goal without pretending every detail is known on day one.

Shape a delivery plan