The 10-Point SOW Review Checklist Before You Sign
A Statement of Work usually gets reviewed by whoever needs the project started, not a lawyer -- this checklist covers the ten places risk most often hides.
July 20, 2026 · By ScopeWise Team
Scope and deliverables (points 1-3)
1. Are deliverables concrete and testable -- "a responsive site with these 12 named pages" rather than "a modern website"? Vague deliverable language is the single biggest source of scope creep. 2. Does every deliverable have defined acceptance criteria -- a stated process for how it gets reviewed and signed off? Without this, "done" is a matter of opinion. 3. Are exclusions stated explicitly -- what is NOT included -- rather than left to be inferred from what is?
Timeline and process (points 4-6)
4. Is there a change-control clause requiring any scope addition to go through a written, priced amendment before work starts on it? Without one, "just one more thing" additions have no friction. 5. Are milestones and dependencies dated, with clear ownership of who delivers what by when? 6. Are assumptions and client-side dependencies (approvals, access, third-party data) explicitly listed, since a SOW timeline that assumes instant client turnaround rarely survives contact with reality.
Commercial and legal terms (points 7-9)
7. Is there a liability cap, and does it have a defined amount and carve-out list -- or is liability left unbounded? 8. Are payment terms and milestones tied to deliverables rather than calendar dates alone, so payment and delivery stay linked? 9. Does the SOW reference an MSA correctly, or does it quietly restate (and possibly contradict) terms the MSA already covers -- see our companion piece on SOW vs. MSA for how that relationship should work.
The final check (point 10)
10. Read it as the other side would. A SOW written entirely from the vendor's perspective, or entirely from the client's, tends to have gaps the other party will surface later -- during the project, not before it starts. Reviewing under time pressure is normal; reviewing without a structured pass through the terms above is where risk slips through. This is the exact ten-point pass a fast SOW turnaround usually skips.