Statement of Work vs Contract: What Freelancers and Agencies Need (and When)
By the xyvora team · Updated · 6 min read
Quick answer
A contract (services agreement) sets the long-term legal terms between you and a client: payment rules, ownership of work, confidentiality, liability and termination. A statement of work (SOW) describes one specific project under that contract: deliverables, milestones, timeline, acceptance criteria and the fee for that project. Sign the contract once, then add a new SOW for each project.
Key takeaways
- The contract is the relationship; the SOW is the project.
- Sign one services agreement per client, then one SOW per project.
- A SOW should define deliverables, milestones, acceptance criteria and fees.
- If the contract and SOW conflict, the contract should say which one wins.
- Small one-off jobs can put the scope inside the contract instead.
What is a statement of work?
A statement of work is a document that describes exactly what will be delivered on one project, how and when. It turns a proposal's promises into measurable commitments both sides can check. Agencies and larger clients often insist on one before any work or invoice is approved.
Statement of work vs contract: the difference
| Contract (services agreement) | Statement of work | |
|---|---|---|
| Covers | The whole relationship | One project |
| How often | Once per client | Once per project |
| Main content | Payment rules, IP, confidentiality, liability, termination, disputes | Deliverables, milestones, timeline, acceptance, project fee |
| Changes | Rarely changed | Changed through a change request |
| Signed by | Both parties | Both parties, referring to the contract |
What goes into a statement of work?
- Reference to the services agreement it falls under, and the project name.
- Objectives: the result the project should achieve.
- Deliverables: each item, its format and how many revision rounds it includes.
- Out of scope: what is not included, to stop scope creep.
- Milestones and timeline: dates, and the client inputs each one depends on.
- Acceptance criteria: how and when the client approves each deliverable, for example "approved if no feedback within 5 working days".
- Fees and invoicing: the project fee and which milestone triggers each invoice.
- Contacts: who approves work on each side.
When do freelancers need a SOW?
- Projects longer than a few weeks or with several deliverables.
- Repeat clients, where each new project gets its own SOW under the same agreement.
- Agency work and corporate clients whose finance teams need approved scopes.
- Fixed-price projects, where a clear scope protects your margin.
For a small one-off job, the scope section of a services agreement is often enough.
SOWs for agencies hiring contractors
Agencies need the same structure on the other side: a contractor agreement with each freelancer they hire, and a contractor SOW for each piece of work. Matching the client SOW's milestones and acceptance criteria to the contractor's SOW keeps deadlines and payments aligned.
Statement of work template
xyvora includes a Statement of Work in the client kit and a Contractor SOW in the agency team kit, alongside the services agreement and change request form. Each fills in your client's details and downloads as PDF or Word. See the client kit.
Frequently asked questions
Is a statement of work legally binding?
A SOW signed by both parties and referring to a signed services agreement is generally binding as part of that agreement. Make sure the contract says which document wins if the two conflict.
Can a statement of work replace a contract?
Not on its own. A SOW usually lacks clauses on ownership of work, confidentiality, liability and termination. Either sign a services agreement first or include those terms.
Who writes the statement of work, freelancer or client?
Either can, but freelancers and agencies usually write it because they know what the work involves. The client reviews and signs it.