Statement of work (SOW) template for agencies and studios

A statement of work is where a good agency relationship is won or lost. It is the document that turns a vague brief and an enthusiastic kick-off call into something both sides can actually be held to. A tight SOW protects your margin, protects the client from surprises, and gives you a shared reference the moment anyone says "I thought that was included". Here is what a strong statement of work contains — and why getting it signed before work begins matters as much as what is in it.

What a tight SOW contains

A statement of work sits underneath your master services agreement or contract and describes one specific engagement. It should leave no room for interpretation on the things that cause disputes:

• Objectives. What this engagement is trying to achieve, in business terms. Not "a new website" but "a site that lets the sales team generate quotes without engineering support".
• Scope and deliverables. The specific things you will produce, listed clearly enough to tick off — pages, features, assets, documents, quantities.
• Out of scope. Just as important as scope. Explicitly name what you are not doing, so assumptions do not quietly become obligations.
• Milestones and timeline. Phases, key dates and dependencies, with a note that dates assume timely client feedback and sign-off.
• Acceptance criteria. How a deliverable is judged complete and approved — who signs off, against what, and within what window before it is deemed accepted.
• Fees and payment schedule. The total, how it breaks down across milestones, invoicing points, and payment terms.
• Assumptions. The conditions your plan and price depend on — access, staging environments, third-party licences, a named point of contact.
• Change control. How new requests are handled: raised in writing, scoped, priced, and approved before work on them starts.

The three sections that protect your margin

If time is short, get these three right and you will avoid most of the pain.

Out of scope is the section teams skip and later wish they had not. A short bulleted list of exclusions does more to prevent scope creep than any amount of carefully worded scope. Name the tempting extras — extra languages, ongoing maintenance, content population — and put them clearly on the other side of the line.

Acceptance criteria stop projects from drifting. Without a defined way to call something "done", deliverables get reopened indefinitely. State who approves, against what standard, and add a deemed-acceptance window — for example, "approved if no feedback is received within five working days".

Change control is what turns scope creep into revenue. When a client asks for something new, you do not refuse and you do not silently absorb it — you raise a change request, scope it, price it, and get it approved. A clause that names this process makes those conversations routine rather than awkward.

This is general information, not legal advice — have important agreements reviewed by a solicitor, particularly the interaction between your SOW and your master services agreement.

Get sign-off before the work starts

Here is the mistake even experienced studios make: they start work on the strength of a "yes, looks great" email while the SOW itself sits unsigned. Then scope drifts, an invoice is queried, and the one document that would have settled it was never actually executed.

Signed sign-off before day one does three things:

1. It confirms the client has genuinely read and agreed the scope, not just skimmed it.
2. It gives you a dated, provable record to point to when change requests arise.
3. It sets a professional tone — this is a studio that operates on clear agreements, not vibes.

The blocker is almost always friction. Chasing a signature through print-sign-scan, or asking a busy client contact to create an account on a signing portal, is exactly what turns a five-minute task into a two-week delay while the project slips. Electronic signatures remove that, and they are legally binding under ESIGN, UETA and eIDAS.

Sending the SOW for signature

• Finalise the SOW as a clean PDF with a signature block for the client's authorised signatory.
• Send it for signature the same day you present it, while intent is high.
• Let the client sign in one tap — no account, no login, no reason to put it off.
• Keep the executed SOW with its audit trail alongside your master agreement.

Signet is designed for exactly this handover moment. Your client signs without creating an account, and every signed SOW comes with a tamper-evident audit trail, a certificate of completion, and a publicly verifiable seal — so when a scope question surfaces three months in, you can prove precisely what was agreed and when. Our UK and EU data residency means client documents stay in-region and are never used to train AI. If proposals are part of your pipeline too, the same approach applies — see how to send a proposal for signature, and compare plans on our pricing page.

Write a SOW that names what is out of scope, defines acceptance, and builds in change control — then get it signed before the first hour is billed. That single habit is the difference between a project that holds its shape and one that quietly erodes your margin.

Signet is in private beta, request early access and send your first sealed agreement free.