Alex is a co-founder of Sprintlaw. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
- What Is The Difference Between An SLA And A Statement Of Work?
- Do You Need An SLA, A SOW Or A Master Services Agreement?
- When Should You Use A Standalone SLA?
- When Should You Use A Statement Of Work?
- What Should Go In An SLA?
- What Should Go In A Statement Of Work?
- How Do SLAs And SOWs Work Together In Practice?
- Common Drafting Mistakes To Avoid
- Key Takeaways
Mia runs a small IT support business in Auckland. A new client wants monthly help desk support, a one-off migration project, and a guarantee that urgent tickets will be answered within two hours. Mia is ready to send a proposal, but she is stuck on the paperwork: does she need an SLA, a Statement of Work, or a bigger services contract?
If that sounds familiar, you aren't overthinking it. The document you choose can change how you get paid, what you're responsible for, and how easy it is to manage scope changes later.
The good news is that the structure doesn't have to be complicated. Once you know what each document is meant to do, you can match it to the way your service is actually delivered.
What Is The Difference Between An SLA And A Statement Of Work?
An SLA sets service performance standards, while a Statement of Work sets out the work you'll do for a particular job or phase. They can work together, but they aren't the same document.
A Service Level Agreement, often called an SLA, is usually about ongoing performance. It answers questions like:
- How quickly will you respond to support requests?
- What uptime or availability target applies?
- When is support available?
- What happens if you miss a service level?
- What is excluded from the service level commitment?
A Statement of Work, often called a SOW, is usually about a defined piece of work. It answers questions like:
- What exactly are you delivering?
- What milestones and dates apply?
- What information or access must the client provide?
- What fees apply to that work?
- How will changes be approved?
For example, if you're building a new website, the SOW might cover design, development, testing and launch. If you then provide hosting or support after launch, the SLA might cover uptime, support hours and response times.
The main risk is using one document to do the other document's job. A SOW with vague service levels can create unrealistic expectations. An SLA without a clear scope can make it look like you promised to fix everything, even work you never priced.
Do You Need An SLA, A SOW Or A Master Services Agreement?
It depends on whether you're doing one defined project, recurring services, or a mix of both. The right service agreement structure should match the commercial relationship, not just the document name your client asks for.
Here is a practical way to choose:
- Use a SOW when you're delivering a specific project, milestone or piece of work.
- Use an SLA when service quality, response times or availability are a key part of the deal.
- Use a Master Services Agreement, or MSA, when you expect to do multiple projects or ongoing work for the same client.
An MSA is the umbrella contract. It usually covers the legal and commercial rules that apply across the relationship, such as payment terms, liability limits, confidentiality, intellectual property, privacy, termination and dispute escalation.
Then each SOW sits under the MSA and sets out the details for a particular job. An SLA can sit inside the MSA, inside a SOW, or as a schedule, depending on how central the service levels are.
Say Mia's IT business charges a client $3,000 plus GST per month for help desk support, plus $8,000 plus GST for a Microsoft 365 migration. A sensible structure could be:
- An MSA for the overall relationship and legal terms.
- A SOW for the migration project, including milestones and acceptance testing.
- An SLA schedule for help desk response times, support hours and service credits.
That way, Mia doesn't need to renegotiate the main legal terms every time the client adds a new project.
When Should You Use A Standalone SLA?
You should usually use a standalone SLA when the main value of your service is reliable, ongoing performance rather than a one-off deliverable. This is common for managed services, software support, hosting, maintenance services and outsourced operations.
A standalone SLA can work well where you already have trading terms or an IT services agreement in place, but you need a clear service schedule for a particular service tier.
For example, a software provider might offer three support packages:
- Standard: email support during business hours, response within 2 business days.
- Priority: email and phone support, response within 1 business day.
- Premium: urgent support response within 2 hours during support hours.
The SLA should be careful about the difference between response time and resolution time. If you promise to respond within 2 hours, that doesn't mean you promise to fix the issue within 2 hours unless the SLA clearly says so.
You should also define what counts as an incident, when the clock starts, and what happens if the client doesn't provide information you need. Without those details, a service level can become hard to measure and harder to defend commercially.
If your SLA includes service credits, keep them realistic. For example, a missed monthly uptime target might give the client a 5% credit for that month's recurring service fee. It's usually safer to make service credits the client's agreed remedy for that particular service level failure, instead of leaving the consequences open-ended.
When Should You Use A Statement Of Work?
You should use a Statement of Work when you need to describe a particular project, deliverable, phase or retainer in detail. A SOW is especially useful when the scope, timing and price need to be pinned down before work starts.
A good SOW doesn't need to be long, but it does need to be specific enough for a practical statement of work review. If you're providing marketing services, for example, a SOW that says monthly marketing support for $2,000 plus GST is probably too vague. Does that include strategy, copywriting, design, social media scheduling, ad management, reporting, meetings, or all of the above?
A clearer SOW might say that you'll provide up to 10 social media posts per month, 1 monthly content calendar, 1 performance report, and 1 strategy meeting. It might also say that paid advertising spend, video production and urgent campaign work are excluded unless agreed in writing.
This level of detail helps both sides. Your client understands what they're buying, and you have a clear basis for saying when something is out of scope. It also makes invoicing easier because you can tie payment to deliverables, milestones or time periods.
A SOW is also useful where you use the same legal terms across many clients, but the actual work changes each time. For example, a consultant might have a standard services agreement, then use a different SOW for each client project.
What Should Go In An SLA?
An SLA should be practical, measurable and linked to the way you actually deliver the service. It's better to promise fewer things clearly than to include ambitious service levels you can't consistently meet.
Key SLA terms usually include:
- Service description: what service the SLA applies to, and any services it doesn't cover.
- Support hours: whether support is 24/7, business hours only, or limited to certain days.
- Priority levels: how issues are classified, such as critical, high, medium or low.
- Response times: how quickly you'll acknowledge or start working on an issue.
- Resolution targets: if you offer them, when you aim to fix or work around an issue.
- Uptime or availability: how availability is measured, and what downtime is excluded.
- Client responsibilities: what the client must do, such as provide access, logs, approvals or information.
- Remedies: whether service credits, fee reductions or escalation rights apply.
It's also important to deal with planned maintenance, third party outages, force majeure events, misuse of the service, and issues caused by the client's systems. If you rely on another provider, such as a cloud hosting platform, you should avoid promising a higher service level than you can control.
For many small businesses, the SLA can be a schedule to your services agreement rather than a separate document. That keeps the legal terms in one place and makes it easier to update service levels when your packages change.
What Should Go In A Statement Of Work?
A SOW should give the project team enough clarity to get started without needing a long chain of emails to fill in the blanks. It should also give you a clean process for dealing with changes.
Common SOW terms include:
- Background and purpose: a short explanation of the project and its goals.
- Scope of work: the tasks, services or deliverables you'll provide.
- Out of scope items: work that isn't included in the price.
- Milestones and timeline: key dates, phases and dependencies.
- Fees and payment: fixed fees, hourly rates, deposits, milestone payments or retainers.
- Client inputs: content, data, approvals, access or personnel the client must provide.
- Acceptance process: how the client reviews deliverables and raises defects or change requests.
- Change control: how extra work is quoted, approved and billed.
For creative, consulting and technology projects, the acceptance process is often where disputes arise. If the client has 5 business days to review a deliverable and must give specific feedback, everyone knows what happens next. If feedback is late or unclear, the SOW can say that the timeline moves out or the deliverable is treated as accepted.
You should also think carefully about intellectual property. The MSA or services agreement might say who owns pre-existing materials, project deliverables, templates, code, designs or reports. The SOW can then add any project-specific IP terms, such as a licence to use a particular tool or a transfer of final deliverables after payment.
How Do SLAs And SOWs Work Together In Practice?
In many service businesses, you won't choose between an SLA and a SOW. You'll use both, but for different purposes.
Think of it this way: the SOW tells the client what work is being done, and the SLA tells the client the standard to which certain ongoing services will be performed. The MSA or main services agreement then sets the legal rules that support both documents.
Going back to Mia's IT business, her migration SOW might include:
- Project planning and discovery.
- User account setup and data migration.
- Testing and go live support.
- A fixed project fee and milestone dates.
- Client responsibilities, such as providing admin access and user lists.
Her SLA for ongoing support might include:
- Support available from 8:30am to 5:30pm on business days.
- Critical issues responded to within 2 hours during support hours.
- Low priority requests responded to within 2 business days.
- Exclusions for third party outages and issues caused by unauthorised changes.
- A service credit process if agreed service levels are missed.
If the migration is delayed because the client hasn't provided access, the SOW should deal with the timeline impact. If the help desk misses a response time after the support arrangement begins, the SLA should deal with the remedy. Separating those issues makes the contract easier to manage.
Common Drafting Mistakes To Avoid
The most common mistake is being too broad. Phrases like all IT support, unlimited revisions or full marketing services sound helpful in a proposal, but they can create a much bigger obligation than you intended.
Another mistake is copying service levels from a larger provider without checking whether they suit your business. A small team may not be able to offer 24/7 support, a 99.99% uptime commitment, or same day resolution for every issue. It's usually better to be transparent about what you can provide and price accordingly.
You should also avoid burying important terms in email chains. If the price, scope, service levels or timeline changes, record the change properly. That might be a signed change order, an updated SOW, or written approval under the change control process in your contract.
Finally, make sure your documents don't contradict each other. If your MSA says payment is due in 7 days but your SOW says 30 days, or your SLA says support is business hours only but your proposal says 24/7, it can be unclear which term wins. A simple order of priority clause can help, especially where you use an MSA with schedules and SOWs.
Key Takeaways
- An SLA sets measurable service standards, such as response times, uptime, support hours and service credits.
- A SOW sets out the scope, deliverables, timing, fees and change process for a specific project or phase.
- An MSA can sit above both documents and cover the main legal terms for an ongoing client relationship.
- Use clear definitions, exclusions and client responsibilities so you don't accidentally promise more than you can deliver.
- If you provide both project work and ongoing support, you may need a SOW for the project and an SLA for the support service.
If you'd like help with preparing SLAs, drafting Statements of Work, structuring your MSA or reviewing your services contract, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.
Drafted by Taylor, Sprintlaw's AI, and overseen by Alex Solo. How we write
Lock in the contract
Turning the information into a usable contract
Once money, deliverables or customer obligations are involved, the next step is usually a clear contract that matches how the business actually works.







