Black Friday10% off any legal service

Statement Of Work Template For NZ Software Projects

byAlex Solo10 min read

A statement of work template for a New Zealand software project should clearly set out the project scope, milestones, deliverables, responsibilities, fees and change control process before anyone starts work.

The slightly more nuanced answer is that a SOW usually works best when it sits under a master services agreement. The master agreement covers the legal foundations, while each SOW deals with the practical details of a particular software build, implementation, integration or support project.

If you get this right early, your project has a much better chance of staying on track. If you leave it vague, you may end up with scope creep, delayed sign-off or arguments about whether an invoice should be paid.

What Is A Statement Of Work In A Software Project?

A statement of work is the project-specific document that explains what will be done, when it will be done, what it will cost and how completion will be measured.

For software projects, a SOW can cover work like:

  • building a new app, portal or platform
  • configuring an existing SaaS product for a client
  • implementing an ERP, CRM or payments system
  • integrating software with third-party tools
  • migrating data from one system to another
  • providing development sprints, testing, training or support and maintenance

A software statement of work is different from a general proposal. A proposal often sells the idea. A SOW should lock in the agreed scope, assumptions, deliverables and commercial terms.

For example, saying we'll build a customer dashboard is usually too loose. A clearer SOW might say the dashboard will include a login page, account overview, invoice download function, admin reporting page and integration with Xero, with a maximum of two rounds of revisions before acceptance testing.

That level of detail may feel a bit dry, but it gives both sides something practical to point to if the project starts drifting.

How Does A SOW Sit Under A Master Services Agreement?

A SOW sits under a master services agreement by dealing with the project details, while the master agreement deals with the ongoing legal relationship.

This structure is common for software providers because you might do several projects for the same client over time. Instead of renegotiating the legal terms every time, you sign one master services agreement, then attach a new SOW for each project.

The Master Services Agreement Usually Covers

  • general payment terms and invoicing rules
  • liability limits and exclusions
  • confidentiality obligations
  • intellectual property ownership and licensing
  • privacy and data handling obligations
  • termination rights
  • how notices are given
  • which document wins if there's an inconsistency

The SOW Usually Covers

  • the specific project scope
  • deliverables and milestones
  • project timeline
  • client inputs and dependencies
  • fees, payment triggers and expenses
  • acceptance testing
  • project-specific assumptions and exclusions

A good master agreement should say that each SOW forms part of the agreement. It should also include an order of precedence clause. For example, the master agreement might control the legal terms, but the SOW might control project-specific details like delivery dates and pricing.

Without that structure, you can end up with mixed messages across your proposal, email thread, invoice terms and project brief.

What Should A Statement Of Work Template Include?

A statement of work template should include enough detail for someone outside the project to understand what has been agreed, without needing to read every email that came before it.

Here is a practical fill-in outline you can use as a starting point. It isn't a finished legal document, and it should be tailored before you use it for a real project.

  1. Parties: Name the software provider and the client, using the correct company names and NZBNs where relevant.
  2. Master Agreement: State which master services agreement the SOW sits under and what happens if the documents conflict.
  3. Project Background: Briefly explain the business problem, system or implementation the project relates to.
  4. Scope Of Work: Describe the exact services to be provided, including any phases or workstreams.
  5. Out Of Scope: List what isn't included, such as custom features, third-party licence fees, extra integrations or data cleansing.
  6. Deliverables: Set out the tangible outputs, such as configured software, source code, documentation, training sessions or test reports.
  7. Milestones And Timeline: Include target dates, milestone descriptions and any dependencies that may move those dates.
  8. Responsibilities: Explain what each side must provide, including access to systems, content, approvals, data and key staff.
  9. Acceptance Criteria: Describe how deliverables will be reviewed, tested, accepted or rejected.
  10. Fees And Payment: State whether pricing is fixed, time and materials, milestone-based or a combination.
  11. Change Control: Set out how scope changes are requested, priced, approved and documented.
  12. Intellectual Property: Confirm whether IP is owned, assigned or licensed, and whether pre-existing tools are excluded.
  13. Privacy And Security: Include project-specific handling of personal information, access controls and data migration requirements.
  14. Assumptions And Dependencies: List anything the price or timeline depends on, such as API access, client sign-off or vendor availability.
  15. Signatures Or Approval: Make it clear who can approve the SOW and any later change requests.

The most useful SOWs are specific. If a term can be measured, tested or evidenced, write it that way.

How Detailed Should The Scope Of Work Be?

Your scope of work should be detailed enough to prevent reasonable confusion, but not so detailed that it becomes impossible to manage normal project changes.

For software work, vague language causes the most trouble. Words like simple, standard, user-friendly or integration can mean very different things to different people.

A better approach is to describe the scope in practical terms:

  • what screens, modules, workflows or user roles are included
  • which systems, APIs or third-party tools the software will connect to
  • what data will be migrated, cleansed or mapped
  • how many rounds of revisions are included
  • which browsers, devices or operating systems are supported
  • what testing is included and what testing sits with the client
  • what training, documentation or handover will be provided

Say Talia runs a Wellington software studio. Her client asks for a fixed-price implementation of a booking platform for $28,000 plus GST, split across four milestones. The SOW says the project includes setup for three locations, five user roles, Stripe payment integration, email notifications and one data import of up to 2,000 customer records.

Halfway through, the client asks to add loyalty points, SMS reminders and a second payment gateway. Because the original SOW clearly listed what was included, Talia can explain that these are new features. She can then issue a change request with extra fees and timing, rather than absorbing the work for free.

That's the real value of a clear scope of work template in New Zealand software projects. It gives you a calm way to manage change without making the relationship feel adversarial.

What Should An Implementation Statement Of Work Cover?

An implementation statement of work should cover not just the software being configured, but also the client inputs and dependencies that make the implementation possible.

Implementation projects often go off track because the provider can't do everything alone. You may need the client to provide access, content, data, technical contacts, internal approvals or third-party vendor support.

Your implementation SOW should be clear on:

  • Discovery: workshops, current system review, requirements gathering and process mapping
  • Configuration: settings, user roles, workflows, permissions and business rules
  • Data Migration: what data will be moved, who cleans it, who checks it and what happens to rejected records
  • Integrations: named third-party platforms, APIs, authentication steps and vendor responsibilities
  • Testing: provider testing, user acceptance testing, defect categories and retesting
  • Training: number of sessions, format, attendees and training materials
  • Go-Live: cutover plan, launch support and any blackout periods
  • Post-Launch Support: support hours, response targets and what is treated as a new request

It's also worth separating defects from enhancements. A defect is usually something that doesn't meet the agreed acceptance criteria. An enhancement is new or changed functionality. If your SOW doesn't draw that line, clients may treat every preference or improvement as a bug to be fixed at no extra cost.

For NZ projects involving personal information, think about the Privacy Act 2020 as well. If you're migrating customer records, employee information or patient data, your SOW should line up with the privacy, security and cybersecurity terms in your main agreement.

The legal terms behind a software SOW should cover contract risk, IP, privacy, consumer and fair trading issues, usually in the master services agreement.

In New Zealand, software projects often touch several legal areas at once.

Intellectual Property

Copyright in software, code, documentation and creative materials is dealt with under the Copyright Act 1994. Your contract should say who owns new materials created for the project, who owns pre-existing tools, and what licence the client receives to use the final product.

This matters because a software provider will often reuse frameworks, libraries or know-how across clients. If the wording accidentally assigns everything to one client, that can create real problems for future projects.

Privacy And Data

If personal information is collected, accessed, migrated or hosted, the Privacy Act 2020 matters. Your documents should address how information is handled, who can access it, what security steps are required and what happens if there's a privacy breach.

If the client is overseas or data is stored offshore, you may also need to think about cross-border disclosure rules under the Privacy Act 2020.

Fair Trading And Consumer Guarantees

The Fair Trading Act 1986 prohibits misleading or deceptive conduct. For software providers, that means your SOW and sales materials shouldn't overpromise features, timelines or performance.

The Consumer Guarantees Act 1993 may also be relevant, especially where services are supplied to consumers or small organisations in circumstances where the Act applies. In many business-to-business contracts, parties can contract out of certain Consumer Guarantees Act guarantees if it's fair and reasonable to do so. The wording needs care.

Standard form small trade contracts can also be affected by the unfair contract terms regime under the Fair Trading Act. If you use the same master agreement and SOW structure across many clients, make sure your terms are balanced and commercially sensible.

Can I Use A Free SOW Template For A NZ Software Project?

Yes, you can use a free SOW template as a starting point, but you should be careful before you rely on it for a paid software project.

Free templates often miss the parts that matter most in real life. They may not match New Zealand law, may not sit properly under your master services agreement, or may use overseas concepts that don't fit your business.

Before using a template, check whether it answers these questions:

  • Does it clearly connect to your master services agreement?
  • Does it say which document wins if there's an inconsistency?
  • Does it define scope, deliverables and exclusions in practical detail?
  • Does it include a proper change control process?
  • Does it deal with acceptance testing and deemed acceptance?
  • Does it match how you actually charge, such as fixed fee, time and materials or milestones?
  • Does it address IP ownership and licensing in a way that protects your reusable tools?
  • Does it cover privacy and security where personal information is involved?
  • Does it fit with New Zealand laws like the Privacy Act 2020, Fair Trading Act 1986 and Consumer Guarantees Act 1993?

Templates work best when they're tailored to your project model. A SaaS implementation SOW will look different from a custom software development SOW, and both will look different from an ongoing support or managed services SOW.

If the project is high value, technically complex or business-critical for either side, getting a statement of work review before work begins is usually far cheaper than trying to fix unclear terms later.

How Do You Manage Scope Changes Without Derailing The Project?

You manage scope changes by requiring written approval before extra work starts, with clear consequences for pricing, milestones and delivery dates.

Scope change is normal in software projects. The issue isn't that changes happen. The issue is whether your SOW gives you a simple process for dealing with them.

A practical change control process usually looks like this:

  1. Request: The client or provider identifies the proposed change in writing.
  2. Impact Assessment: The provider explains the likely effect on fees, timing, deliverables, assumptions and risks.
  3. Approval: An authorised person approves the change before work starts.
  4. Updated Documents: The change is recorded in a change request, variation or updated SOW.
  5. Delivery: The project plan, invoices and milestones are adjusted to match the approved change.

Your SOW should also say what happens if the client delays approvals or doesn't provide required information. For example, if a client takes 10 business days to approve designs when the SOW allowed 3 business days, the delivery date may need to move.

Keep a clear record of decisions. Project management tools, signed change requests and email approvals can all help, as long as the SOW says what counts as approval and who has authority to give it.

Without that discipline, small extras can quietly become unpaid work. That's where scope creep usually starts.

Key Takeaways

  • A statement of work template should define scope, deliverables, milestones, fees, responsibilities and change control before software work begins.
  • A SOW usually works best under a master services agreement, with the master agreement covering the main legal terms.
  • For software projects, be specific about inclusions, exclusions, integrations, data migration, testing and acceptance criteria.
  • NZ laws like the Privacy Act 2020, Fair Trading Act 1986, Consumer Guarantees Act 1993 and Copyright Act 1994 may affect how your SOW and master agreement are drafted.
  • Free templates can be useful starting points, but they often need tailoring to your business model, project type and New Zealand legal context.
  • A clear change control process helps you manage new requests without giving away extra work for free.

If you'd like help with your software statement of work, master services agreement, implementation project terms or change control process, 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.

Alex Solo
Alex SoloCo-Founder

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.

Lock in the contract

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.