Alex is Sprintlaw's co-founder and a legal technology leader. He holds law and media degrees from the University of Sydney and has been recognized by Australasian Lawyer, Lawyers Weekly and the Sydney Young Entrepreneur Awards for his work building Sprintlaw and improving access to business legal support.
A statement of work is the project document that says exactly what you'll do, what the client will provide, when work is due, how much the client will pay and how changes will be handled.
That sounds simple, but the detail matters. A vague statement of work can turn a profitable project into weeks of unpaid extras, delayed approvals and uncomfortable invoice conversations.
If you run a consulting, agency, software, design, marketing or other services business, a good statement of work template can save you a lot of back and forth. The trick is to treat it as more than an admin form. It should be a practical project plan that also fits neatly with your broader services agreement.
What Is A Statement Of Work?
A statement of work is a project-specific document that sets out the agreed scope, deliverables, timeline and fees for a client engagement.
You might also hear people call it an SOW, a scope of work, a work order or a project brief. The names can overlap, but the useful idea is the same: your services agreement gives the legal framework, and the statement of work fills in the project details.
For example, your main services agreement might cover:
- Payment terms
- Intellectual property ownership and licensing
- Confidentiality
- Liability limits
- Termination rights
- Dispute processes
Your statement of work then says:
- Which services you'll provide for this client
- What the final deliverables will be
- What is out of scope
- What the client needs to give you
- Key dates and milestones
- How acceptance, revisions and change requests will work
Say Maya runs a small brand strategy agency. Her main services agreement stays the same for most clients. For a $12,000 rebrand, her statement of work lists the brand workshop, two concept directions, one selected logo suite, brand guidelines, two rounds of revisions and a 6-week timeline. If the client later asks for packaging design, Maya can point to the SOW and treat that as extra work.
Is A Statement Of Work A Contract?
Yes, it can be part of a contract if it's accepted by both sides and is intended to create binding obligations.
In practice, a statement of work often works together with a master services agreement or standard terms. The legal position depends on the wording, how it's signed or accepted, and the contract law of the state that governs the deal.
For most service businesses, federal law won't tell you exactly what an SOW must say. General contract principles are mostly state law. That said, federal laws can still matter depending on what you're delivering. For example:
- The Copyright Act can affect ownership and work for hire treatment of creative work, software code, copy, designs and other copyright materials.
- The Lanham Act can matter if you're creating brand names, logos or advertising that uses trademarks.
- The Defend Trade Secrets Act can support protection for confidential business information, especially when your agreement includes clear confidentiality obligations.
- The Federal Trade Commission Act and FTC guidance can matter if your marketing services involve advertising claims, endorsements or promotional materials.
If your project includes goods as well as services, the Uniform Commercial Code may also affect some sales terms. That can change how acceptance, rejection and remedies work, so it's worth getting tailored advice for mixed goods and services projects.
Electronic signatures are commonly used for SOWs, and the federal E-SIGN Act generally supports the validity of electronic signatures in many business contracts. Your process still needs to show clear acceptance, such as signing, clicking to accept or written approval by email where your contract allows it.
How Do You Write A Statement Of Work?
You write a statement of work by turning the commercial deal into clear, testable project terms.
A helpful statement of work template should leave very little room for guessing. If there's a dispute later, you want the document to answer practical questions like: Was this included? Who had to approve it? When was it due? What happens if the client delays?
A Fill-In Outline For Your Statement Of Work
You can use the outline below as a drafting checklist. It isn't a finished legal document, and a lawyer should tailor it before you use it with clients.
- Parties And Project Name: identify your business, the client and the project in plain terms.
- Background: briefly explain why the client is engaging you and what the project is meant to achieve.
- Services: describe the work you'll perform, with enough detail for someone else to understand it.
- Deliverables: list the actual outputs, such as reports, designs, code, training sessions or campaign assets.
- Out-Of-Scope Items: state what isn't included, especially common extras clients may assume are included.
- Assumptions: record the facts you're relying on, such as client access, data quality, system availability or team participation.
- Dependencies: list what the client or third parties must do before you can complete your work.
- Milestones And Timeline: set out dates, review points and what each milestone requires.
- Fees And Expenses: explain fixed fees, hourly rates, retainers, deposits, taxes and reimbursable expenses.
- Acceptance And Revisions: say how the client approves deliverables and how many revision rounds are included.
- Change Requests: explain how new work, timeline changes and extra fees will be agreed.
- Special Terms: add project-specific confidentiality, intellectual property, data, security or compliance requirements.
- Order Of Priority: say whether the services agreement or SOW controls if the documents conflict.
A common mistake is to write deliverables as tasks only. For example, prepare website content is less clear than five website pages of up to 800 words each, plus one round of client revisions, delivered in editable document format.
What Should Go In Your Scope, Assumptions And Dependencies?
Your scope should explain exactly what is included, while assumptions and dependencies explain what must be true for you to deliver it.
This is where many client projects get messy. You may know what you meant during the sales call, but your client may remember the conversation differently. A clear scope section gives both sides a shared reference point.
Scope
Your scope should describe the work in business-friendly detail. If you provide services in stages, break the scope into phases.
For example, a website project scope might include:
- Discovery meeting of up to 90 minutes
- Homepage wireframe
- Design of 5 core page templates
- Build of up to 10 website pages
- Basic search engine optimization setup
- One training session of up to 60 minutes
It should also say what isn't included. That might include copywriting, photography, logo design, hosting, custom integrations, paid advertising setup or ongoing maintenance.
Assumptions
Assumptions are the things you're relying on when pricing and scheduling the project. They might be about the client, the information provided or the technical environment.
For example:
- The client will provide final copy before design starts.
- The client has the right to use all images and brand assets it supplies.
- The client will give access to required systems within 2 business days.
- No custom software development is required unless agreed in a change request.
Dependencies
Dependencies are the actions or inputs that sit outside your control. If a client dependency is late, your SOW should say the timeline moves and extra costs may apply.
This matters because delays often look like your problem unless the SOW says otherwise. If the client takes 12 days to approve a draft that needed approval within 3 business days, your delivery date shouldn't stay frozen unless you agreed to that risk.
How Should You Handle Milestones, Fees And Acceptance?
You should tie milestones, fees and acceptance together so the client knows what they're paying for and when a deliverable is considered complete.
A milestone isn't just a calendar date. It should describe the work to be delivered and what has to happen next. This makes invoicing easier and helps you avoid endless review loops.
A Worked Example
Let us say Jordan runs a video production studio and agrees to produce a 90-second product video for $8,000.
A clear SOW might break the project down like this:
- Milestone 1: concept and script outline, due 7 business days after kickoff, with a $2,000 invoice on approval.
- Milestone 2: filming day and raw footage capture, scheduled after the client approves the script, with a $3,000 invoice on completion of filming.
- Milestone 3: first edited cut, due 10 business days after filming, with one consolidated round of client revisions included.
- Milestone 4: final video file delivered within 5 business days after revision comments, with the final $3,000 invoice due on delivery.
The SOW should also say how acceptance works. For example, the client must give written feedback or approval within 5 business days of receiving a deliverable. If the client doesn't respond within that period, the deliverable is deemed accepted, unless your broader agreement says something different.
That kind of acceptance process is especially useful for agencies and consultants. Without it, you may finish the work but struggle to close the project, issue the final invoice or start the next phase.
Your fees section should cover:
- Fixed fees, hourly fees or a mix of both
- Deposits and payment milestones
- When invoices are issued and when they're due
- Whether expenses need pre-approval
- What happens if the client pauses the project
- Whether fees are exclusive or inclusive of applicable taxes
If payment timing is critical to your cash flow, don't leave it to a vague phrase like payment on completion. Say what completion means.
What Happens If The Client Changes The Scope?
If the client changes the scope, your statement of work should require a written change request before you do extra work.
This doesn't have to be awkward. In fact, a clear change process can make you look more professional. It helps you say yes to extra work while protecting your time and margins.
Your change request process should cover:
- Who can request changes
- How the request must be made
- How you'll price extra work
- Whether timelines will move
- When the change becomes binding
- What happens if the parties don't agree
For smaller projects, an approved email may be enough if your contract allows that. For larger projects, you may want a signed change order that attaches to the SOW.
Here is a practical way to think about it. If a client asks for a change that affects price, timing, deliverables, legal risk or your team capacity, pause and document it before you start. If it's a tiny clarification that doesn't affect any of those things, you may not need a formal change order.
A good SOW also separates revisions from changes. Revisions are edits to work already included in the scope. Changes are new work or a different direction. For example, changing the wording on a brochure may be a revision. Asking for a new landing page, extra photoshoot or additional software feature is usually a change.
If you start doing extra work without approval, you may struggle to recover the extra fees later. A written change process gives you a calm way to protect the project relationship and your bottom line.
Frequently Asked Questions
Can I Use The Same Statement Of Work Template For Every Client?
You can start with the same template, but you should tailor it for each project. The risky parts are usually the details: deliverables, timelines, assumptions, client responsibilities, data access, IP rights and acceptance.
Should The Client Sign The Statement Of Work?
Yes, signing is usually the cleanest option. You may also be able to rely on electronic acceptance, but your process should clearly show that the client agreed to the SOW and any linked terms.
What Is The Difference Between A Scope Of Work And A Statement Of Work?
A scope of work usually describes what work is included. A statement of work is often broader because it also covers milestones, fees, acceptance, assumptions, dependencies and change requests.
Do I Need A New SOW For Each Project?
Usually, yes. If each project has different deliverables, timing or fees, a new SOW helps keep the main services agreement in place while updating the commercial details.
Key Takeaways
- A statement of work should clearly set out the scope, deliverables, timeline, fees, assumptions, dependencies and acceptance process for a client project.
- Your SOW usually works with a broader services agreement, rather than replacing it.
- Be specific about what is out of scope, because that's often where unpaid extra work begins.
- Milestones should link deliverables, approvals and payment points so you can manage the project and your cash flow.
- A written change request process helps you handle extra client requests without damaging the relationship.
- Templates are useful starting points, but your SOW should be tailored to your services, clients and risk profile.
If you'd like help with your statement of work, services agreement, change request process or client project terms, you can reach our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they're provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.
Drafted by Taylor, Sprintlaw's AI, and overseen by Alex Solo. How we write








