PWPM Wiki
Website RedesignScope Statement

Website Redesign Scope Statement

This is a practical guide to building a scope statement for a website redesign project — a definition of deliverables, boundaries and acceptance criteria, adapted to the realities of redesigning an existing website.

What a Scope Statement is

A scope statement is a definition of deliverables, boundaries and acceptance criteria. For the full concept and how it works in general, see Scope Statement. On a website redesign project it plays the same role, tuned to this kind of work.

Why it matters for a Website Redesign project

Website Redesign projects live or die on redesigning an existing website. A well-built scope statement gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how website redesign projects drift into avoidable delay and cost.

What to include

  • Deliverables
  • In scope
  • Explicitly out of scope
  • Acceptance criteria
  • Constraints and assumptions

Website Redesign-specific considerations

Tailor the scope statement to the risks that most often derail website redesign projects:

  • Scope creep
  • Content migration
  • SEO preservation

Example

On a real website redesign project, the scope statement would be shaped by redesigning an existing website. In particular, it should explicitly account for the project’s biggest risks — scope creep, content migration, SEO preservation — rather than treating them as afterthoughts.