SOW (Statement of Work)

The SOW is the operational document translating a master agreement into a single engagement. It typically includes: project objectives, expected deliverables with acceptance criteria, team and roles, timeline with milestones, pricing model (T&M or Fixed Price), billing terms and specific clauses (assumptions, exclusions, change management).

A well-written SOW is the first defense against scope creep and commercial disputes. Mature firms use standardized templates in the PSA that pre-populate SOWs from pipeline and capacity data, cutting drafting time by 50-70% and improving consistency between quote and contract.

Exclusions do more work than inclusions in practice. A scope section that lists what the engagement delivers leaves everything unmentioned open to interpretation, and interpretation always drifts toward the client's expectation. Naming the adjacent things the project explicitly does not cover — data migration, training, third-party coordination — prevents most of the disagreements that later look like bad faith on one side or the other.

Assumptions deserve the same treatment, because they are the part of the SOW that quietly transfers risk. A commitment to a timeline that depends on the client providing environments in week one is only defensible if that dependency is written down along with what happens if it slips. Firms that state the consequence, not merely the assumption, renegotiate from a document rather than from memory.