PWPM Wiki
Facility RelocationScope Statement

Facility Relocation Scope Statement

This is a practical guide to building a scope statement for a facility relocation project — a definition of deliverables, boundaries and acceptance criteria, adapted to the realities of relocating a facility or operation to a new site.

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

Why it matters for a Facility Relocation project

Facility Relocation projects live or die on relocating a facility or operation to a new site. 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 facility relocation projects drift into avoidable delay and cost.

What to include

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

Facility Relocation-specific considerations

Tailor the scope statement to the risks that most often derail facility relocation projects:

  • Downtime minimisation
  • Logistics
  • Staff and equipment moves

Example

On a real facility relocation project, the scope statement would be shaped by relocating a facility or operation to a new site. In particular, it should explicitly account for the project’s biggest risks — downtime minimisation, logistics, staff and equipment moves — rather than treating them as afterthoughts.