Why You Need A Lawyer To Review Your Statement Of Work (2026 Updated)

If you’re about to sign a Statement of Work (SOW), it probably feels like you’re close to the finish line. The scope is agreed, the price is (mostly) agreed, and you just want to get started.

But in practice, the SOW is often where projects succeed or fail - because it’s the document that sets expectations about what “done” looks like, who does what, when it’s delivered, and what happens when something changes.

This 2026 update is simply to reflect how common SOWs have become across modern service relationships (especially tech, marketing, consulting, and outsourced operations), and how much more closely businesses are paying attention to practical contract risk: delays, scope creep, data handling, and responsibility gaps.

A lawyer reviewing your SOW isn’t about making it longer or more complicated. It’s about making it clearer, enforceable, and aligned with your actual business deal - so you’re protected from day one.

What Is A Statement Of Work (And How Is It Different To A Contract)?

A Statement of Work is usually the “project specifics” document. It sets out the operational detail of a job: deliverables, timelines, milestones, assumptions, and pricing.

In New Zealand, SOWs commonly sit underneath (or alongside) a “main contract”, such as:

• a master agreement (the general legal terms that apply to all work);
• a consultancy or service agreement (ongoing services); or
• a contractor engagement (project-based work).

The key point is this: an SOW often becomes legally binding once signed, even if it looks like a “project plan”. If the deal goes sideways, the SOW is one of the first documents anyone will pull out to work out what was actually promised.

So Why Does The “Difference” Matter?

Because businesses often treat the SOW as informal - but it can create (or change) legal obligations in a big way.

Common examples include:

• The SOW conflicts with the main agreement (and it’s unclear which document wins).
• The SOW adds new obligations (like tighter deadlines, additional reporting, or expanded deliverables) without adjusting the fee.
• The SOW quietly shifts risk (for example, making you responsible for third parties, approvals, or outcomes you don’t control).

It’s also worth noting that contracts in NZ are interpreted based on what the documents say and what the parties intended - which is exactly why clarity matters. A lawyer’s role is to make sure the written SOW matches the real commercial deal, and reduces room for argument later.

Why A Lawyer Should Review Your SOW Before You Sign

SOW reviews are basically risk reviews. Your lawyer is checking that the SOW is commercially workable and legally enforceable, and that it doesn’t accidentally put you in a bad position.

Here’s what a good SOW review usually protects you from.

1. Scope Creep (And Getting Stuck Doing “Extras” For Free)

Scope creep is one of the most common causes of disputes - especially in IT builds, digital marketing, creative work, and consulting.

A lawyer will look for:

• vague deliverables (“support as required”, “ongoing optimisation”, “best endeavours”);
• missing exclusions (what’s not included);
• assumptions that aren’t realistic (for example, you relying on the client providing content, approvals, or access quickly); and
• a change control process that actually lets you charge for variations.

If you’re working under a broader agreement like a Master Services Agreement, your SOW also needs to align with how variations, approvals, and acceptance are handled in that main contract.

2. Payment Risk (Milestones, Deposits, And What Triggers An Invoice)

Many SOWs look fine until you ask one simple question: “When exactly do we get paid?”

A lawyer will help you tighten:

• payment triggers (e.g. signing, milestone completion, monthly in arrears);
• acceptance criteria (what counts as “delivered” or “accepted”);
• timeframes for review (so the client can’t sit on feedback for weeks); and
• disputed invoices (what must still be paid, and what happens while you resolve the dispute).

In a lot of industries, it’s not the “rate” that causes trouble - it’s the uncertainty around whether the rate applies to the work that was actually done.

3. Liability Traps (Being Responsible For Things Outside Your Control)

SOWs sometimes include hidden risk transfers, like:

• you guaranteeing an outcome (rather than providing a service);
• you taking responsibility for third-party tools or platforms (that you don’t control);
• client delays being treated as your delays; or
• requirements that are impossible without client cooperation (but the SOW doesn’t say that clearly).

Your lawyer will also check that liability clauses in the main agreement aren’t being overridden accidentally by the SOW - or, if they are, that it’s a change you genuinely meant to make.

4. Compliance Gaps (Privacy, Consumer Law, And Safety)

Depending on what the SOW is for, it may trigger compliance responsibilities that aren’t obvious from the project description.

For example:

• If you’re collecting or accessing personal information, you need to think about the Privacy Act 2020 obligations (and the SOW should clearly state who is doing what, and what security standards apply). A Privacy Policy can be part of the wider compliance picture too, particularly where you’re handling customer data through a service.
• If you’re supplying services to consumers (even indirectly), the Fair Trading Act 1986 and Consumer Guarantees Act 1993 can shape what you can and can’t disclaim, and how “promises” in marketing and proposals can be treated.
• If work is happening on-site or involves operational risk, the Health and Safety at Work Act 2015 may require clearer allocation of health and safety duties, inductions, and incident reporting.

Not every SOW needs a compliance overhaul - but it’s much easier to address these issues before the work starts than after a complaint, breach, or incident.

5. Unclear Exit Rights (What Happens If The Project Needs To Stop?)

Projects pause or change all the time: budgets get cut, priorities shift, stakeholders change, or the relationship just isn’t working.

A lawyer will check that you’re not stuck in an unfair situation, including:

• termination rights (for convenience vs for breach);
• notice periods;
• what fees are payable on termination (including work in progress);
• handover obligations (and whether you’re paid for them); and
• what happens to IP, accounts, data, and access.

If you need a deeper review of the overall agreement stack (not just the SOW pages), a contract review and redraft can be a practical way to make sure everything fits together properly.

The Clauses That Commonly Cause Disputes In A SOW

Most SOW disputes don’t start with anyone acting in bad faith. They start because the document leaves room for different interpretations.

Below are the clauses we most often see causing friction - and what a lawyer is looking for when reviewing them.

Deliverables And Acceptance Criteria

If deliverables are described too loosely, it’s hard to prove you’ve completed the work - or hard to prove the other side is being unreasonable.

Good acceptance terms usually cover:

• what exactly will be delivered (and in what format);
• what “acceptance” means (objective criteria where possible);
• how long the client has to review and request changes; and
• what happens if the client doesn’t respond (deemed acceptance).

Assumptions And Client Responsibilities

This is a big one. Many SOWs list assumptions, but don’t make them enforceable.

For example, if your timelines depend on the client providing:

• access to systems;
• brand assets or copy;
• approvals within a set timeframe; or
• key staff attending workshops,

…then the SOW should say what happens if they don’t. Otherwise, you can end up wearing the delay and the cost.

Change Requests And Variations

A practical change process usually includes:

• what counts as a change request;
• how changes are requested (in writing, via email, in a ticketing system);
• time and cost impacts;
• who can approve changes (to avoid someone junior “approving” extra scope); and
• what happens if you start the change before paperwork is finalised.

If the SOW is vague here, it can become a “you said / we said” argument later.

Service Levels, Support, And Ongoing Maintenance

If the SOW includes ongoing support, response times, or uptime promises, you’ll want those obligations clearly documented and realistic.

Sometimes it’s better handled through a separate Service Level Agreement, particularly where performance standards need to be measurable and updated over time.

Intellectual Property (IP) And Ownership Of Work Product

SOWs often create confusion around IP because they describe “deliverables” without clearly stating who owns what and when ownership transfers.

A lawyer will usually check:

• whether you’re assigning IP to the client, or licensing it;
• whether you’re retaining your pre-existing materials, templates, code, or processes;
• whether third-party materials are involved (and their licence terms); and
• whether payment is a condition for IP transfer.

This matters even for non-tech work - marketing assets, training materials, reports, designs, and documentation can all involve IP rights.

Confidentiality And Data Handling

Many SOWs include a one-liner about confidentiality, but for modern service delivery that may not be enough.

If you’ll be accessing customer lists, employee details, medical information, payment data, or anything sensitive, the SOW and main agreement should clearly address:

• permitted use (what you can do with the data);
• security standards;
• subcontractors and offshore access;
• breach notification; and
• return/deletion at the end of the engagement.

This is one area where getting it wrong can create major exposure, especially if the relationship ends badly or there’s a data incident.

How To Make Your SOW Work With Your Other Documents (MSA, SLA, Purchase Orders, And Policies)

One of the most overlooked issues is document hierarchy: which document wins if there’s a conflict?

In a real-world commercial relationship, you might have:

• a master agreement setting overall legal terms;
• one or more SOWs covering specific projects;
• purchase orders issued by the client;
• an SLA for support/performance;
• policies (privacy, security, acceptable use); and
• emails and proposals that contain key promises.

If these aren’t aligned, you can end up with a contract that says two different things at once - which is a recipe for dispute.

Document Hierarchy: The “Which One Wins?” Clause

A lawyer will often recommend an order of precedence clause so everyone knows where to look first if there’s an inconsistency.

For example, you might want:

• the main agreement to override general inconsistencies; but
• the SOW to override on project specifics (like milestones and deliverables), as long as it explicitly says it’s overriding the main agreement.

There’s no one-size-fits-all answer - it depends on your business model and what you’re trying to protect - but you do want the relationship between documents to be intentional.

Don’t Let A Purchase Order Override Your Deal

Some clients send purchase orders with “standard terms” on the back (or linked online). If you accept them without thinking, you may be agreeing to terms you never negotiated.

A lawyer can help you set up the SOW (and acceptance process) so it’s clear that your agreed terms apply, not random procurement terms.

If You Use Contractors Or Subcontractors, Align The Back-To-Back Terms

If you’re delivering services to a client and using a contractor to help you, your obligations to the client should match what you can actually require from the contractor.

That usually means your contractor agreement should cover things like confidentiality, IP ownership, delivery timeframes, and responsibility for rework - so you’re not left exposed.

Make The SOW Usable (Not Just “Legally Correct”)

The best SOWs are documents your team will actually use.

A good legal review doesn’t just fix technical legal issues. It also helps make the SOW clearer and more practical, for example by:

• tightening definitions (so everyone uses the same language);
• making timelines match real workflow;
• clarifying who signs off deliverables;
• adding a clean variation process; and
• making sure the fee structure matches the scope.

If you want a targeted review specifically on the SOW document, a SOW review is often a quick way to spot the issues that cause the most pain later.

What You Can Do Before Sending Your SOW To A Lawyer (A Practical Checklist)

You don’t need to “perfect” your SOW before legal review - that’s what we’re here for - but you will get a faster and more useful review if you gather a few key details first.

Checklist: The Information That Makes A SOW Review More Effective

• The commercial deal: what you’re delivering, your price, the real deadlines, and any non-negotiables.
• The full document stack: the main agreement (if any), the SOW, and any attachments, proposals, or purchase order terms.
• How you’ll deliver the work: who’s on your team, whether subcontractors are involved, and what dependencies exist.
• Your biggest worry: late payment, endless revisions, IP ownership, delays, or being blamed for things outside your control.
• How you want changes handled: fixed price with strict variations, or time and materials, or a hybrid model.

Even one short email explaining “what’s actually going on in the relationship” helps your lawyer tailor the review so it’s commercially realistic - not just technically correct.

A Quick Reality Check: If You’re Thinking “It’s Just A Small Project…”

Small projects can still create big disputes.

Imagine this: you quote a fixed fee, the client changes direction twice, and you’re now over budget. The client refuses to approve a variation because “it was implied” in the original scope. You finish the work, and they delay payment because they’re not “happy” - but there’s no acceptance criteria.

That’s exactly the situation an SOW review is designed to prevent.

Key Takeaways

• A Statement of Work can be legally binding and is often the document that determines what you actually have to deliver, when, and for what price.
• Lawyer review helps prevent common SOW problems like scope creep, unclear acceptance criteria, risky assumptions, and payment disputes.
• SOWs should align with your wider contract documents (like a Master Services Agreement, Service Level Agreement, purchase orders, and policies) so there’s no confusion about which terms apply.
• Clear variation processes, client responsibilities, and termination mechanics are practical protections that can save you time, money, and stress if the project changes.
• If your SOW involves personal data, consumer-facing services, or on-site work, you should also consider compliance with laws like the Privacy Act 2020, Fair Trading Act 1986, Consumer Guarantees Act 1993, and Health and Safety at Work Act 2015.

If you’d like help reviewing your Statement of Work (or making sure it works properly with your wider contract terms), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.