BW-301b · Module 2

Scope Precision

6 min read

Scope creep does not start when the client asks for something extra. It starts when the statement of work does not define what "extra" means. Every boundary the SOW fails to draw is a boundary the client will eventually test — not out of bad faith, but because ambiguous scope naturally expands in the direction of what the client needs.

The discipline of scope writing is the discipline of drawing boundaries that are clear, defensible, and honest — clear enough that the client understands what they are getting, defensible enough that you can point to the language when scope expands, and honest enough that you are actually delivering what you wrote.

Do This

  • "This engagement includes configuration of up to 50 user accounts in the specified system. Account migration from legacy systems is excluded."
  • Define scope by what is included and what is explicitly excluded for each major workstream
  • Name the specific systems, data sets, locations, and user populations the engagement covers
  • State assumptions explicitly: "This scope assumes client will provide API access to [system] within 5 business days of contract execution"

Avoid This

  • "We will configure user accounts as needed" — "as needed" has no boundary
  • Define scope only by what is included without explicitly excluding adjacent work the client will expect
  • "System integration" without naming the specific systems and integration patterns
  • Leave assumptions unstated and address scope disputes reactively when they arise
## Scope of Work: Data Migration Services

### Included in This Engagement
- Migration of customer records from [Legacy CRM] to [Target CRM],
  limited to accounts created between January 1, 2020 and the contract
  execution date
- Data cleaning and deduplication for migrated records, using the
  deduplication rules defined in Appendix B
- Up to 3 rounds of client-requested data validation against the
  post-migration dataset
- Training for up to 10 designated system administrators (4-hour
  session, remote delivery)

### Explicitly Excluded from This Engagement
- Migration of records created before January 1, 2020
- Migration of financial transaction history or invoice records
- Custom field mapping not included in the field mapping document
  (Appendix C)
- Integration with third-party systems other than those named in
  Appendix D
- Ongoing data maintenance or system administration after go-live

### Scope Change Process
Any work outside this scope requires a written change order signed
by both parties before work begins. VENDOR will provide a change
order estimate within 5 business days of a written scope change request.