Create a bespoke document in minutes, or upload and review your own.
Get your first 2 documents free
Your data doesn't train Genie's AI
You keep IP ownership of your information
Statement of Work
I need a statement of work for a software development project that outlines the scope, deliverables, timeline, and payment terms, with a focus on agile methodologies and regular progress reviews. The document should also include provisions for change management and quality assurance standards.
What is a Statement of Work?
A Statement of Work (SOW) is a formal document that outlines the specific deliverables, timelines, and performance standards for services or projects under contract in accordance with New Zealand's Contract and Commercial Law Act 2017. This detailed agreement serves as a binding component of the master service agreement, precisely defining project scope, methodologies, pricing structures, and success criteria while aligning with requirements set forth by the Commerce Commission and industry-specific regulations.
Under standard commercial practice and the Fair Trading Act 1986, the SOW must clearly articulate key performance indicators, resource allocation, payment terms, and dispute reֱ mechanisms. It functions as a critical risk management tool, protecting both service providers and clients by establishing clear expectations and accountability frameworks. For government contracts, it must additionally comply with the Government Procurement Rules and maintain transparency standards, making it an essential document for project governance and contractual clarity in both public and private sector engagements.
When should you use a Statement of Work?
Consider implementing a Statement of Work when you're engaging external contractors, consultants, or service providers for complex projects where precise scope definition and deliverable tracking are crucial. This document becomes particularly vital when your project involves significant financial commitments, requires strict compliance with the Health and Safety at Work Act 2015, or demands clear accountability frameworks under the Contract and Commercial Law Act 2017.
You should prioritize creating a Statement of Work for situations involving multi-phase projects, technology implementations, or professional services where success criteria need explicit definition. It's especially important when dealing with government contracts subject to procurement rules, projects requiring specific intellectual property arrangements, or services with staged payment structures. The document proves invaluable for risk management by preventing scope creep, setting clear expectations for deliverables and timelines, and establishing concrete performance metrics. For maximum protection, implement it before project commencement to ensure all parties have a shared understanding of objectives, responsibilities, and success criteria.
What are the different types of Statement of Work?
Within New Zealand's commercial and legal landscape, the Statement of Work takes several distinct forms, each tailored to specific industry needs and contractual requirements. These variations differ in their scope, complexity, and focus areas while maintaining compliance with relevant legislation such as the Contract and Commercial Law Act 2017 and industry-specific regulations.
- SOW Statement Of Work: The standard comprehensive template suitable for general business engagements, outlining core deliverables, timelines, and performance metrics.
- Statement Of Work Contract: A more detailed version that incorporates additional contractual elements, particularly suited for complex projects requiring extensive legal protection.
- SOW For Software Development: Specialized version focusing on technology projects, including specific provisions for intellectual property rights, testing requirements, and technical specifications.
- Work Confidentiality Agreement: Incorporates enhanced confidentiality provisions within the SOW framework, crucial for projects involving sensitive information.
- Employment Confidentiality Agreement: Combines work scope definition with comprehensive confidentiality measures for employees working on sensitive projects.
Selecting the appropriate SOW variation depends on your specific project requirements, industry context, and risk management needs. Consider factors such as project complexity, confidentiality requirements, and regulatory compliance obligations when choosing and customizing your template to ensure comprehensive coverage of all crucial aspects.
Who should typically use a Statement of Work?
In the New Zealand business environment, a Statement of Work involves multiple stakeholders who play distinct roles in its creation, execution, and oversight. These parties must understand their responsibilities under the Contract and Commercial Law Act 2017 and relevant industry regulations to ensure effective implementation and compliance.
- Service Provider/Contractor: The party responsible for delivering the specified work or services, typically drafting the initial SOW and ensuring deliverables align with agreed terms and quality standards.
- Client Organization: The entity commissioning the work, responsible for reviewing, negotiating, and approving the SOW terms, while maintaining oversight of project progress and compliance.
- Project Managers: Key representatives from both parties who oversee day-to-day implementation, monitor progress against SOW metrics, and manage change requests.
- Legal Counsel: Internal or external lawyers who review and refine the SOW to ensure legal compliance, risk management, and protection of their respective party's interests.
- Subject Matter Experts: Technical specialists who contribute to defining specifications, quality standards, and acceptance criteria within their domain expertise.
- Procurement Officers: Particularly in government contracts, these officials ensure the SOW aligns with procurement policies and public sector requirements.
Successful execution of an SOW depends on clear communication and coordination among all parties, with each stakeholder understanding their specific obligations and authority within the agreement's framework.
How do you write a Statement of Work?
Successfully creating an effective Statement of Work requires careful attention to both legal requirements and practical implementation considerations under New Zealand law. Utilizing a custom-generated template from a reputable provider like ֱ can significantly simplify the process and minimize the chance of mistakes, ensuring accuracy and compliance with legal requirements.
- Project Scope Definition: Clearly articulate deliverables, timelines, and success criteria using precise, measurable terms that align with the Contract and Commercial Law Act 2017.
- Performance Metrics: Establish specific, quantifiable key performance indicators (KPIs) and quality standards that reflect industry best practices and regulatory requirements.
- Resource Allocation: Detail personnel requirements, equipment needs, and material specifications, including any mandatory certifications or qualifications.
- Payment Terms: Specify pricing structures, payment schedules, and conditions for milestone payments in accordance with the Fair Trading Act 1986.
- Change Management: Include clear procedures for scope modifications, approval processes, and impact assessments on timeline and costs.
- Risk Management: Address potential issues, including dispute reֱ mechanisms, liability limitations, and insurance requirements aligned with local regulations.
Before finalizing, ensure all parties review the document thoroughly, paying particular attention to technical specifications and compliance requirements. Consider having legal counsel review complex or high-value SOWs to ensure enforceability and comprehensive risk protection.
What should be included in a Statement of Work?
A comprehensive Statement of Work must include specific elements to ensure legal validity and enforceability under New Zealand's Contract and Commercial Law Act 2017 and related regulations. ֱ takes the guesswork out of this process by providing legally sound, custom-generated legal documents, ensuring all mandatory elements are correctly included and minimizing drafting errors. The following checklist outlines essential components required for a legally robust SOW:
- Parties and Authorization: Full legal names, registered addresses, and authorized signatories of all involved parties, including ABN/NZBN numbers where applicable.
- Project Overview: Clear statement of purpose, project objectives, and intended outcomes, establishing the foundational context for the agreement.
- Scope Definition: Detailed description of included and excluded work, with specific deliverables, acceptance criteria, and quality standards.
- Timeline and Milestones: Specific dates, deadlines, and project phases, including dependencies and critical path activities.
- Financial Terms: Comprehensive pricing structure, payment schedules, invoicing requirements, and any performance-linked payment conditions.
- Performance Standards: Measurable KPIs, quality metrics, and acceptance criteria aligned with industry standards and regulatory requirements.
- Resource Requirements: Detailed specification of personnel, equipment, materials, and facilities needed for project execution.
- Change Management Process: Formal procedures for scope modifications, including approval protocols and impact assessment requirements.
- Risk Allocation: Clear distribution of responsibilities, liabilities, and indemnification provisions between parties.
- Dispute Reֱ: Specific procedures for handling disagreements, including mediation and arbitration processes under New Zealand law.
- Intellectual Property Rights: Clear ownership and usage rights for project deliverables, existing IP, and newly created materials.
- Confidentiality Provisions: Detailed requirements for handling sensitive information in compliance with the Privacy Act 2020.
- Termination Conditions: Specific circumstances and procedures for contract termination, including notice periods and consequences.
- Governing Law: Express statement of New Zealand law as the governing jurisdiction for the agreement.
Review each element carefully during drafting to ensure comprehensive coverage and alignment with your specific project requirements. Regular internal review and updates maintain the document's effectiveness throughout the project lifecycle.
What's the difference between a Statement of Work and a Method Statement?
A Statement of Work is often confused with a Method Statement in New Zealand's commercial and construction sectors. While both documents play crucial roles in project execution, they serve distinct purposes and contain different elements under New Zealand law. Understanding these differences is essential for proper document selection and compliance with relevant regulations, including the Construction Contracts Act 2002 and Health and Safety at Work Act 2015.
- Primary Purpose: A Statement of Work defines what will be delivered, including specific outcomes, deliverables, and success criteria. In contrast, a Method Statement focuses on how work will be performed, detailing specific procedures and safety protocols.
- Scope and Detail: SOWs encompass broader project elements including timelines, costs, and resource allocation, while Method Statements concentrate on technical execution details and risk mitigation procedures.
- Legal Standing: SOWs form part of the contractual agreement between parties, establishing binding obligations. Method Statements typically serve as operational documents supporting health and safety compliance.
- Timeline Application: An SOW covers the entire project duration and deliverables, whereas a Method Statement might be created for specific tasks or phases within the larger project.
- Stakeholder Focus: SOWs primarily address business and contractual relationships between parties. Method Statements focus on worker safety and operational procedures.
- Modification Requirements: Changes to an SOW usually require formal contract amendments, while Method Statements can be updated more readily to reflect evolving safety needs or procedural improvements.
Understanding these distinctions helps ensure appropriate document selection and proper risk management. While both documents may be required for complex projects, they serve complementary rather than interchangeable functions in project documentation and compliance frameworks.
Download our whitepaper on the future of AI in Legal
ұԾ’s Security Promise
Genie is the safest place to draft. Here’s how we prioritise your privacy and security.
Your documents are private:
We do not train on your data; ұԾ’s AI improves independently
All data stored on Genie is private to your organisation
Your documents are protected:
Your documents are protected by ultra-secure 256-bit encryption
Our bank-grade security infrastructure undergoes regular external audits
We are ISO27001 certified, so your data is secure
Organizational security
You retain IP ownership of your documents
You have full control over your data and who gets to see it
Innovation in privacy:
Genie partnered with the Computational Privacy Department at Imperial College London
Together, we ran a £1 million research project on privacy and anonymity in legal contracts
Want to know more?
Visit our for more details and real-time security updates.
Read our Privacy Policy.