How to Write a Statement of Work: The 8 Sections You Need

SOW vs contract vs proposal: the differences

A proposal outlines what you could do and why you are the right choice - it is a sales document sent before the client commits. A statement of work defines exactly what you will do once the client has agreed - it is an operational document. A contract sets out the legal terms of the relationship (payment terms, IP ownership, dispute resolution, confidentiality) - it is a legal document. In practice, many freelancers and small agencies combine all three into a single document. What matters is that the scope, deliverables, timeline, and price are unambiguously defined in writing before work begins.

The 8 sections every SOW needs

• Project overview: a brief description of the project, its purpose, and the business objective it serves.
• Scope of work: exactly what you will deliver - in specific, measurable terms.
• Deliverables: the outputs you will hand over - files, reports, designs, code, documents.
• Timeline and milestones: key dates, phases, and dependencies.
• Acceptance criteria: how the client will confirm that each deliverable meets requirements.
• Payment schedule: amounts, triggers, and payment terms.
• Change management: what happens when scope changes are requested.
• Assumptions and exclusions: what you are assuming to be true and what is explicitly not in scope.

How to write the scope of work section

The scope section is the most important part of a SOW and the most commonly written badly. Vague scope leads directly to scope creep - the gradual expansion of work without corresponding payment. Write scope statements in specific, testable language. Not 'design a website' but 'design and develop a five-page marketing website using WordPress, including homepage, about, services, blog, and contact pages, responsive for mobile and desktop, with Google Analytics integration.' Not 'provide marketing support' but 'write and schedule 12 social media posts per month across Instagram and LinkedIn for three months.'

The exclusions section is equally important. State clearly what is not included: 'This scope does not include photography, copywriting, SEO setup, third-party plugin licences, hosting, or ongoing maintenance after launch.' Exclusions prevent the client from assuming anything not explicitly mentioned is excluded - a dangerous assumption that experienced clients will not make, but inexperienced ones often do.

Setting milestones and payment triggers

For projects longer than two weeks, tie payment to milestones rather than the calendar. Common structures: a deposit of 25-50% on contract signing, a mid-project payment on delivery of an agreed milestone, and a final payment on completion. The deposit protects you against a client who disappears after the project starts. The milestone payment protects you against a client who approves work verbally but delays final payment. Never start significant work without a deposit on a new client relationship.

Change management: protecting yourself from scope creep

Every SOW needs a change request clause. When a client asks for something outside the agreed scope, you issue a change request document that describes the additional work, the additional cost, and the impact on the timeline. The client approves in writing before the work begins. Without this clause, you face a choice between doing extra work for free or having an awkward conversation with no contractual backing. With it, the process is professional and expected by both parties.

Common SOW mistakes

• Writing scope in vague, aspirational language - 'deliver a great website' is not scope. Every word in the scope section should be something you can point to and say 'done' or 'not done'.
• No revision limit - 'unlimited revisions' sounds generous but is a professional liability. Specify the number of revision rounds included (typically 2-3) and the hourly rate for additional rounds.
• Missing the acceptance criteria - if you do not define what 'done' looks like, the client decides. Include clear, objective acceptance criteria for each deliverable.
• Skipping the SOW for 'small' projects - scope creep is just as common on a 500 project as a 50,000 one, and the conversation is just as uncomfortable.

Use the Statement of Work Builder

The Statement of Work Builder on this site guides you through all eight sections and generates a professional, printable SOW document. Your business details save automatically for repeat use. Download as a PDF or print to sign. Nothing is stored on a server.