Statement of Work Example: How to Draft a SOW to Protect Your Business

If you sell services, you’ve probably felt the pain of vague briefs, sliding deadlines and scope creep. A clear Statement of Work (SOW) is one of the simplest ways to set expectations, control scope and get paid on time.

In this guide, we’ll walk through a practical statement of work example, the key clauses to include, and how a SOW fits with your broader service contract. Our aim is to help you lock in deliverables, timelines and pricing in plain English, while keeping you compliant with Australian law.

Whether you’re a digital agency, IT services provider, consultant, construction contractor, designer or professional services firm, a strong SOW can make all the difference to your cash flow and client relationships. Let’s dive in.

What Is A Statement Of Work (SOW)?

A Statement of Work is a document that describes exactly what you’ll deliver, when you’ll deliver it, how it will be delivered, and how much it will cost. Think of it as the “project manual” for a particular engagement.

Most businesses attach a SOW to a broader service contract, such as a Master Services Agreement (MSA) or a Goods and Services Agreement. The master agreement handles the “legal infrastructure” (liability, IP ownership, confidentiality, dispute resolution), while the SOW sets the project-specific scope.

Used well, a SOW reduces ambiguity. It gives your team a concrete plan to follow and gives your client clear acceptance criteria so you can sign off and invoice without fuss.

When Should Your Business Use A SOW?

Use a SOW whenever you have a project or phase of work with defined deliverables or milestones. Common examples include:

• Website design or development projects with specified features
• IT migrations, integrations, audits or rollouts
• Marketing campaigns, content packages or media buys
• Consulting engagements with reports, workshops or training outputs
• Construction, fit-out or installation jobs with staged works

Even for ongoing retainers, a quarterly or annual SOW can reset expectations and align on deliverables for that period.

Importantly, a SOW should never sit alone. It should be read with your master contract (for example, a Master Services Agreement) so there’s no doubt about payment terms, risk allocation and other boilerplate.

Statement Of Work Example (Template-Style Headings)

Below is a practical statement of work example you can adapt. The headings double as a checklist. Keep the language clear, specific and measurable wherever possible.

1. Project Overview

Short summary of the project and objective.

Example: “This Statement of Work (SOW) sets out ACME Agency’s services to redesign ClientCo’s ecommerce website to improve conversion and implement a new checkout flow.”

2. Scope Of Services (Deliverables)

List each deliverable and what it includes. If helpful, add what it doesn’t include, to prevent scope creep.

• UX wireframes for 10 unique page templates
• Responsive UI design for desktop and mobile
• Front-end development and integration with existing CMS
• Checkout redesign compliant with PCI-DSS

Out Of Scope (examples): Ongoing hosting, brand refresh, copywriting, product photography.

3. Milestones, Timeline And Dependencies

Break the project into milestones with target dates. Note any dependencies (e.g. client approvals, access to systems).

• M1: Discovery workshop and brief (by 15 May) - dependency: ClientCo team attendance
• M2: Wireframes delivered (by 31 May) - dependency: approval of brief
• M3: UI designs delivered (by 21 June) - dependency: wireframe sign-off
• M4: Build complete and UAT (by 19 July) - dependency: content provision

4. Client Responsibilities

Spell out what the client must do to keep the project on track.

• Provide brand assets and content within five business days of request
• Nominate a single project contact who can approve deliverables
• Grant access to staging environment and relevant tools

5. Assumptions

Assumptions help you price fairly and manage risk. State them clearly.

Example: “This quote assumes one round of consolidated feedback per milestone. Additional revisions will be charged at the rates in Section 7.”

6. Acceptance Criteria And Sign-Off

Define what “done” means and the process for acceptance.

Example: “A deliverable is accepted when it meets the documented requirements for that milestone and is approved in writing by ClientCo’s project contact within five business days of delivery.”

7. Fees, Rates And Payment Schedule

Choose a pricing model (fixed fee, time-and-materials, or hybrid) and specify when invoices are issued.

• Fixed fee: $45,000 + GST across four milestones
• Payment: 30% on SOW signature, then 20% on M2, 30% on M3, 20% on M4
• Out-of-scope work: $180 + GST per hour
• Expenses: Pre-approved third-party costs billed at cost + 10%

8. Change Control

Explain how scope changes are handled.

Example: “New features or material changes will be assessed and approved via a written change request detailing impact on timeline and fees.”

9. Intellectual Property

Confirm how IP will be handled, usually referencing your master contract.

Example: “Ownership of final deliverables and licence terms are governed by the Master Services Agreement dated 1 May 2025.”

10. Confidentiality And Data

Reference confidentiality, privacy and data security expectations (often covered by your master contract and policies).

11. Warranties And Support (If Any)

Define warranty periods or post-launch support clearly (e.g. 30 days bug-fix warranty, capped support hours).

12. Special Terms (Optional)

Capture anything unique to this project that doesn’t fit elsewhere (e.g., brand approvals, third-party licences, performance targets).

13. Signatures

Include a signature block for both parties, with date, name and title. If you’re a company, ensure execution follows the Corporations Act requirements (or keep it simple by using your standard signing process).

How To Draft A Strong SOW Step By Step

Step 1: Start From Your Master Contract

Your master contract carries the legal weight-liability limits, IP ownership, indemnities, confidentiality, termination and dispute resolution. The SOW should say, “This SOW forms part of the Master Services Agreement” and adopt the same definitions. If you don’t yet have a master contract, consider putting one in place before issuing your next SOW.

Step 2: Write The Scope Like A Checklist

Replace vague phrases (“help improve SEO”) with measurable outputs (“deliver 10 optimised landing pages and a 12-month content calendar”). If a deliverable can be misunderstood, add a short description or acceptance test so there’s no ambiguity on sign-off.

Step 3: Tie Milestones To Payments

Milestone-based billing reduces cash flow risk and keeps both sides aligned. Match invoices to clear deliverables that can be approved quickly. If you invoice monthly for time-and-materials, include timesheet approval and rate cards in the SOW.

Step 4: Lock Down Client Responsibilities

Delays often come from slow approvals or missing inputs. A SOW that requires consolidated feedback within a set timeframe and nominates a single approver will save weeks of back-and-forth.

Step 5: Add A Simple Change Control Process

You don’t need a complex system. A one-page change request template and a rule that no work proceeds without a signed change order is enough for many small businesses.

Step 6: Review Legal Alignment And Formatting

Make sure the SOW doesn’t contradict your master contract. Keep formatting consistent, number your sections, and use plain English. A quick SOW review can help you catch gaps before the project starts.

Key Legal Clauses To Include In Or Alongside Your SOW

While your SOW does the “what and when,” your master agreement handles the “what if.” Below are key areas to cover-either directly in the SOW or by referencing your master contract.

• Scope And Acceptance: Clear acceptance criteria reduce arguments at handover and support your right to invoice.
• Payment Terms: Include due dates, late payment processes and any admin fees. If you use late fees, ensure they comply with Australian law-this guide on charging late fees on invoices explains the limits.
• Liability And Risk Allocation: Your master agreement should include a balanced limitation of liability clause. If you don’t have one, read up on limitation of liability clauses and update your terms.
• Intellectual Property: Be explicit about who owns what. Often, you’ll assign IP in final deliverables once paid in full, while retaining ownership of your tools and know‑how.
• Unfair Contract Terms (UCT): The Australian Consumer Law’s UCT regime applies to many standard-form small business contracts. It’s wise to get a UCT review and redraft to avoid clauses that could be void or expose you to penalties.
• Privacy And Data: If you handle client or customer data, align your SOW with your Privacy Policy and security practices, and identify any data handling responsibilities.
• Change Control: A simple process for variations helps you bill fairly when scope grows.
• Dispute Resolution: A staged process (good faith negotiations, mediation, then litigation) helps prevent minor issues from escalating.

Common Mistakes (And How To Avoid Disputes)

Mistake 1: Vague Deliverables

Fix it by naming each deliverable, version, format and quantity. If you say “templates,” how many? Which file types? What resolutions?

Mistake 2: No Acceptance Process

Fix it with a simple approval window (e.g. five business days) after delivery. If no response, deem the deliverable accepted. This keeps projects moving.

Mistake 3: Pricing That Doesn’t Match Scope

Fix it by separating included work from optional extras and setting rates for out-of-scope tasks. Use change requests for new features or “nice to haves.”

Mistake 4: Forgetting Client Duties

Fix it by listing what you need from the client with deadlines. If the client’s delay pauses the project, reserve the right to adjust timelines and fees.

Mistake 5: Conflicting Documents

Fix it by stating a “order of precedence.” For example: “If there is a conflict, the Master Services Agreement prevails over this SOW.” If you need to update terms later, follow a proper variation process-this guide to making amendments to contracts explains how to do it cleanly.

Mistake 6: Boilerplate That Breaches UCT

Fix it by avoiding heavy-handed unilateral rights, broad indemnities without limits, or termination-at-will in standard-form contracts. A tailored UCT-friendly approach is safer and often more persuasive to clients.

How A SOW Works With Your Contracts In Practice

Most small businesses work with a simple stack:

• Master contract (e.g., Master Services Agreement or Goods and Services Agreement) - signed once, governs the relationship
• Individual SOWs - signed per project or phase, detailing the scope and price
• Change requests - signed as needed when the scope changes mid‑project

This structure keeps your legal terms consistent while giving you flexibility to spin up new projects quickly. As you grow, it’s common to create SOW templates for different service lines so your team can generate clear scopes in minutes.

Practical Tips To Make Your SOWs Faster And Safer

• Use numbered headings and version control so it’s easy to refer to “Section 3.2” in emails.
• Build a library of standard deliverables with pre-written acceptance criteria (e.g. “Landing page v1 meets Figma spec X and Lighthouse score Y”).
• Link timeframes to client approval windows. If approval is late, the schedule shifts automatically.
• Price by milestone. It creates natural checkpoints and reduces invoice disputes.
• Keep support and warranty terms short and separate from new scopes, so you can update them without rewriting everything.
• Schedule a quick internal legal check before sending larger SOWs-15 minutes can prevent costly rework.

FAQ: Short Answers To Common SOW Questions

Can a SOW stand alone without a contract?

It can, but it’s risky. Without a master contract, you may lack core protections (liability limits, IP and confidentiality). Attach the SOW to your master terms wherever possible.

Is a SOW legally binding?

Yes-if it’s signed and contains the essential terms (scope, price, timeframes) or is incorporated into a binding master agreement. Make sure signatures and authority are in order.

Fixed fee or time-and-materials-which is better?

Fixed fees suit well-defined scopes with clear acceptance. Time-and-materials suits iterative projects where effort is uncertain. You can also do a hybrid: fixed discovery, then time-based build.

What if the client keeps changing their mind?

Use your change control clause. Pause work until a written change request is approved with adjusted fees and timeline. Your SOW should make this standard practice.

How detailed should acceptance criteria be?

Enough to be objective. If two reasonable people can apply the criteria and reach the same pass/fail outcome, you’ve done it right.

Key Takeaways

• A Statement of Work turns vague goals into specific deliverables, timelines and pricing, which reduces scope creep and invoice disputes.
• Pair each SOW with a strong master contract (such as a Master Services Agreement) that handles liability, IP, confidentiality and dispute resolution.
• Write scope like a checklist, set objective acceptance criteria, and tie milestone payments to sign‑offs.
• Include client responsibilities, assumptions and a simple change control process to keep projects on track.
• Make sure your clauses align with Australian Consumer Law, including the unfair contract terms regime-consider a UCT-friendly redraft if you use standard form contracts.
• Before sending, run a quick legal check for conflicts, gaps and risky wording; a targeted SOW review can save time and protect your business.

If you’d like a consultation on drafting or reviewing a Statement of Work for your business, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no‑obligations chat.