Service agreement vs. statement of work — which one do you need?
By Contracts Specialist
Updated: May 16, 2026
They're not the same thing. Here's when to use each, and which clauses change.
These two documents sound similar, but they serve different purposes. Using the wrong one — or using one when you need both — can leave gaps in your legal protection that cost you money, time, and client relationships. Understanding the difference is essential for freelancers who work with repeat clients, multi-phase projects, or any engagement where the scope might evolve over time.
A Service Agreement (also called a master services agreement or MSA) is the overarching contract. It covers the general relationship between you and the client — payment terms, confidentiality, IP ownership, termination, and liability. Think of it as the constitution for your working relationship. A Statement of Work (SOW) is project-specific. It defines the exact deliverables, timeline, milestones, and budget for one particular project. An SOW is usually attached to or referenced by the service agreement. One MSA can have many SOWs over months or years.
Step 1: When to use just a service agreement
For simple, one-off projects where the scope, timeline, and payment are straightforward enough to include in a single document. Most freelance projects fall into this category. Example: a £2,000 logo design with a 2-week timeline, 50% deposit, and 2 revision rounds. All terms fit comfortably in 2–3 pages. A separate SOW would be overkill. The service agreement covers everything: parties, scope, payment, timeline, IP, revisions, and termination. Send it, sign it, start work.
Step 2: When to use both
For ongoing client relationships where you'll do multiple projects over time. The service agreement sets the ground rules; each project gets its own SOW with specific details. Example: a marketing agency that hires you monthly for blog posts, landing pages, and email campaigns. The MSA covers payment terms (net-14, late penalties), confidentiality, IP ownership (transfer on payment), and termination (30-day notice). Each month's SOW specifies exact deliverables: '4 blog posts, 1 landing page, 2 email sequences, due by the 15th, £3,500 total.' This separation is cleaner: you sign the MSA once, then add SOWs as needed without renegotiating the relationship terms.
Step 3: Key clause differences
Service agreement clauses are broad and relationship-level: IP transfers upon full payment (applies to all work under the agreement), confidentiality covers all information shared during the relationship, termination requires 30 days notice (not project-specific). SOW clauses are narrow and project-level: scope defines exactly what this project includes ('website redesign, 5 pages, delivered by March 15'), timeline has specific milestone dates, budget is the exact amount for this project only (£5,000), deliverables list precise outputs ('responsive HTML/CSS, Figma source files, style guide'). The service agreement says 'how we work together.' The SOW says 'what we are doing right now.'
Step 4: Common mistakes to avoid
Mistake 1: Using an SOW without an MSA for repeat clients. You end up renegotiating payment terms, confidentiality, and IP ownership for every project. Mistake 2: Putting project-specific details in the MSA. The MSA should not mention 'the website redesign' because that locks you into renegotiating the MSA for every new project. Mistake 3: Not referencing the MSA in the SOW. Every SOW should state: 'This SOW is governed by the Master Service Agreement dated [Date] between [Parties].' This ensures the MSA protections apply to the SOW. Mistake 4: Using the same document for both. A 10-page contract that tries to be both MSA and SOW becomes confusing and hard to enforce.
Key difference in clauses: A service agreement has broad, relationship-level clauses ("IP transfers upon full payment"). An SOW has project-level specifics ("Website redesign, 5 pages, delivered by March 15, £5,000 total"). Both are necessary for ongoing relationships; only the service agreement is needed for one-off projects.
Our recommendation: Start with a service agreement for every client. Add SOWs only when the relationship involves multiple projects. Our freelance service agreement template works great as a standalone for most projects, and our Pro retainer agreement includes MSA-style language for ongoing relationships.
Protect yourself with the right contract
Download free, lawyer-reviewed templates or upgrade to Pro for all clauses.