PWPM Wiki

Organisational Restructuring Scope Statement

This is a practical guide to building a scope statement for an organisational restructuring project — a definition of deliverables, boundaries and acceptance criteria, adapted to the realities of restructuring teams, roles or the operating model.

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 an organisational restructuring project it plays the same role, tuned to this kind of work.

Why it matters for an Organisational Restructuring project

Organisational Restructuring projects live or die on restructuring teams, roles or the operating model. 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 organisational restructuring projects drift into avoidable delay and cost.

What to include

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

Organisational Restructuring-specific considerations

Tailor the scope statement to the risks that most often derail organisational restructuring projects:

  • People and morale impact
  • Consultation requirements
  • Business continuity

Example

On a real organisational restructuring project, the scope statement would be shaped by restructuring teams, roles or the operating model. In particular, it should explicitly account for the project’s biggest risks — people and morale impact, consultation requirements, business continuity — rather than treating them as afterthoughts.