An Australian Statement of Work (SOW) is a project-specific scope document that defines in precise terms the work a service provider agrees to perform for a client in connection with a particular project or engagement. Unlike a general service agreement, which establishes the ongoing commercial relationship and standard terms, a SOW is project-focused: it specifies what will be done, what will be delivered, by when, and for how much, for a specific body of work.

In Australian business practice, SOWs are most commonly issued under a master services agreement (MSA) or framework contract. The MSA sets out the overarching commercial terms — intellectual property ownership, limitation of liability, confidentiality, dispute resolution, governing law, and insurance — while each SOW references the MSA and adds only the project-specific details. This structure allows organisations and their service providers to negotiate standard commercial terms once and then rapidly authorise individual projects without renegotiating the legal framework each time.

SOWs are used extensively in information technology, digital transformation, cloud migration, software development, management consulting, marketing and communications, engineering, and professional services. Australian government agencies — at both Commonwealth and state levels — routinely require SOWs as part of their procurement processes under the Commonwealth Procurement Rules and relevant state frameworks.

The legal effect of a SOW depends on whether it is issued under a master agreement (in which case it takes effect as a binding variation or project order under that agreement) or as a standalone document (in which case it is itself the contract). In either case, the SOW creates legally binding obligations under the general law of contract and is subject to the Australian Consumer Law (Schedule 2 of the Competition and Consumer Act 2010 (Cth)).

Intellectual property considerations are particularly important in Australian SOWs. Under the Copyright Act 1968 (Cth), copyright in works created by an independent contractor vests in the contractor as author, not the client, unless there is a written assignment. A SOW that does not include an express IP assignment clause may leave the client without ownership of the software, designs, reports, or other deliverables it has paid for.

GST under the A New Tax System (Goods and Services Tax) Act 1999 (Cth) applies to project fees charged by GST-registered service providers at 10%, and the SOW should specify whether the project fee is GST-inclusive or GST-exclusive to avoid disputes.

A Statement of Work is the appropriate document to use when a business or government agency in Australia needs to formally define and authorise a specific project or body of work, whether issued under a master services agreement or as a standalone project contract.

IT and technology projects require SOWs to define the scope of software development, systems integration, cloud migration, cybersecurity assessment, or managed services engagements. Technology projects are particularly prone to scope disputes — a SOW with a detailed scope, clear out-of-scope exclusions, and a documented change management process is essential to managing cost and timeline risk.

Consulting and advisory engagements benefit from SOWs when the work involves defined deliverables (a strategy document, a process review report, a financial model) with clear acceptance criteria, rather than ongoing advisory retainer services. A SOW is appropriate where the scope is bounded and the engagement is expected to conclude on delivery of the specified outputs.

Marketing, design, and creative projects — including brand development, website design, advertising campaigns, and content creation — require SOWs to define the creative brief, the number of revision rounds included, the file formats to be delivered, and the intellectual property ownership of creative output.

Construction and engineering projects, including fitout, renovation, and infrastructure projects, benefit from SOWs issued under a head contract when multiple work packages or subcontracted packages need to be individually defined and authorised.

Government and public sector procurement frequently requires SOWs as part of the request for tender or request for proposal process. A well-drafted SOW is the foundation of a successful government procurement and contract performance framework.

A well-drafted Australian Statement of Work must address the following key elements to provide clear project definition, manage risk, and comply with applicable law.

Project Overview and Objectives — Every SOW should begin with a clear statement of the project name, background, and objectives. This contextualises the scope and gives both parties a shared reference point for interpreting the SOW's more specific provisions. Misalignment on project objectives is a common cause of disputes that could be avoided with a clear statement of purpose.

Scope of Work and Exclusions — The scope clause is the most commercially critical provision of any SOW. It must describe in specific, measurable terms what the service provider will do, including the specific activities, tasks, technologies, and processes covered. An express list of exclusions — work that is explicitly not included in the project fee — is equally important and prevents the client from asserting that excluded work was implied by the scope description.

Deliverables and Acceptance Criteria — The deliverables list specifies the tangible outputs the service provider will produce. Each deliverable should have defined acceptance criteria: objective, measurable standards against which the client will assess whether the deliverable meets requirements. A deemed acceptance mechanism (the deliverable is accepted if the client does not provide written rejection within the review period) protects the service provider from open-ended review periods.

Timeline and Milestones — The project timeline sets out the start date, target completion date, and key milestone dates. Milestones may also be linked to payment obligations (particularly in milestone-based payment structures). The SOW should address who bears responsibility for delays and how milestone dates are adjusted for delays caused by the client failing to fulfil its dependencies.

Fees, GST, and Payment Schedule — The total project fee, GST treatment, and payment schedule should be clearly specified. Common payment structures include upfront deposit plus completion payment, milestone-based payments, or time-and-materials billing. The SOW should specify the invoicing and payment process, the payment terms (days), and the consequences of late payment.

Change Management — A documented change request and Change Order process is essential to manage scope creep and protect both parties' interests. The process should specify how changes are requested, assessed, priced, and authorised, and should clearly state that changes are not effective until a Change Order is signed.

Client Dependencies — Many SOWs fail because the service provider cannot proceed without the client fulfilling certain obligations — providing access, making decisions, or supplying information. Documenting these dependencies and their deadlines, together with the consequence of delay (suspension of the service provider's obligation to meet milestones), is important for fair allocation of timeline risk.