Most project disputes come down to one thing: different assumptions about what was included. A statement of work (SOW), a document that specifies the scope, deliverables, timeline, and terms of a project, is the most effective way to prevent those disputes. It doesn’t need to be long or legal; it needs to be clear.
What to include
Scope: what you will do and, explicitly, what you won’t. “This includes one round of stakeholder interviews, a written strategy document, and a one-hour presentation to the leadership team. It does not include implementation support or ongoing advisory.”
Deliverables: the specific outputs, what format, what length, what standard. Vague deliverables (“a strategy document”) leave too much room for interpretation.
Timeline: key dates for drafts, feedback, and final delivery. Include how long the client has to review and provide feedback at each stage.
Revisions: how many rounds of revisions are included, and what counts as a revision vs a change in scope.
Fees and payment terms: the total fee, payment schedule, and what happens if the scope changes.
Keep it readable
An SOW doesn’t need to be written in legal language. Plain English is better, it’s more likely to be read, and if there’s ever a dispute, it’s more likely to be understood by both parties. Structure it as a short document, not a contract, though it should be attached to or referenced in your contract.
The statement of work template below gives you a ready-to-use structure covering all the key sections, with guidance notes for each.
Related articles
- How to write a freelance contract that protects you
- How to handle scope creep in a comms project
- How to onboard a new comms client properly
Put it into practice
This article comes with a free Statement of work template. Download it, open it in Google Sheets or Excel, and use it alongside what you have just read.