A Statement of Work (SOW) is not the same as a contract. It is the document that defines what you are building, which is then referenced by the contract.
Most scope disputes are not contract disputes. They are SOW disputes: situations where the client and the freelancer have different memories of what was agreed because the SOW was not specific enough.
What Makes an SOW Signable Without Argument
The answer is specificity at the right level.
Too vague: "Build a user authentication system." Neither side can agree whether this was delivered.
Too detailed: Three pages of implementation specifications that the client cannot evaluate and will not read. Gets signed without real engagement.
Right level: "User authentication including email/password registration with email verification, login with 30-day session expiry, password reset via email link, and account lockout after five failed attempts. Social login (Google, Apple) is not included."
That description is specific enough that both sides can confirm delivery. It is readable enough that the client actually engages with it before signing.
The Structure of a Signable SOW
Opening paragraph: purpose of this engagement and the problem being solved in plain language.
Deliverables section: numbered list of specific items, described at the readable-specific level above.
Out of scope section: explicit list of related things that are not included. This is the section that prevents "I thought that was included" conversations.
Assumptions section: everything you are assuming to be true when building the estimate. Wrong assumptions become change orders when identified; this section provides the legal and relational basis for that.
Acceptance criteria: how delivery is confirmed. "Client will review and confirm acceptance within five business days of delivery. Silence does not constitute acceptance."
Change order policy: one paragraph stating that work outside this document requires a written change order before proceeding.
The Signing Conversation
When you send the SOW, include a short note: "Please read through the deliverables and out-of-scope sections carefully. If anything looks different from your expectations, I would rather align before we start than discover a gap mid-project."
This framing positions the SOW as a collaborative alignment document, not a legal trap. Most clients engage more carefully with it as a result.
The Solopreneur AI Toolkit includes prompts for writing SOWs, scope documents, and change orders in clear, professional language. EUR 12.
Top comments (0)