What Is a Statement of Work?

Why the two-document structure works

Negotiating IP ownership, liability caps, insurance and termination for every project is slow and expensive. The MSA/SOW structure separates the negotiation that happens once from the detail that changes every engagement. The commercial benefit is speed: new work can start on a two-page SOW signed by a project sponsor, without going back through legal. For an in-depth walkthrough of the umbrella agreement itself, see our guide to master services agreements in Australia.

What belongs in the MSA (not the SOW)

• Intellectual property ownership and licensing, including pre-existing materials and third-party components.
• Confidentiality, privacy and data handling obligations.
• Warranties, indemnities, liability cap and insurance requirements.
• Term, termination, suspension and the consequences of termination.
• Subcontracting, personnel, non-solicitation and dispute resolution.
• Order of precedence — which document wins if a SOW contradicts the MSA.

What belongs in the SOW

• Scope, and express exclusions. What is out of scope is as important as what is in.
• Deliverables described specifically enough that a third party could tell whether they have been delivered.
• Acceptance criteria and process. Who tests, against what standard, in how many days, and what happens if the customer stays silent — deemed acceptance clauses matter here.
• Milestones and dates, and whether dates are estimates or commitments.
• Fees and payment triggers — fixed fee, capped time and materials, or milestone-based, plus expenses and GST treatment.
• Assumptions and customer dependencies. Access to systems, data, decision-makers and sign-off timeframes, with a stated consequence if they are not met.
• Named personnel and any key-person substitution rules.
• Change control — the form, who can sign, and that work does not proceed until it is signed.

The order of precedence clause

Every MSA/SOW structure needs one, and the drafting choice has consequences. The safer default is that the MSA prevails over a SOW except where the SOW expressly identifies the MSA clause it varies and states that it does so. Without that qualifier, a project manager can quietly override the liability cap or IP position in a delivery document that legal never sees.

Where SOWs go wrong

• The proposal becomes the SOW. A marketing document full of aspirational language is imported as the contractual scope. Rewrite it, or expressly state that only the scope table is contractual.
• No acceptance mechanism. Work is complete but never accepted, so the final payment sits unpaid indefinitely.
• Scope creep by email. Additional work performed on goodwill, then disputed. A one-page change request template solves most of this.
• Assumptions with no consequence. Listing dependencies is pointless unless the SOW says what happens to price and timeline when they are not met.
• SOWs that outlive the MSA. Address whether SOWs on foot continue after the MSA expires, and on what terms.