A master services agreement (MSA) is the contract that sets the ground rules for an ongoing relationship between two businesses, usually a provider and a customer, before any specific piece of work is agreed. Instead of negotiating a fresh contract for every project, the parties agree the framework once, and each new job is added underneath it. This guide explains what an MSA covers, how it works with statements of work, service level agreements and other supporting documents, and where Australian businesses most often get caught out.
There is no statutory definition of a master services agreement. The label describes a kind of framework contract, and like any contract it is governed by ordinary Australian contract law. What makes an MSA distinctive is structure rather than statute: one set of terms that applies across many separate pieces of work, so the parties never have to renegotiate the legal basics from scratch.
The job of a master services agreement
An MSA operates as an umbrella over the relationship. It settles the baseline rules once, at the start, so that everything that follows can move quickly. Those baseline rules cover things like who owns the intellectual property created during the relationship, how confidential information and customer data are handled, how liability is capped, how payment works, and how either party can end the arrangement.
A point that surprises many business owners is that an MSA on its own commits nobody to anything. It is a framework, not an order. The customer is not obliged to buy services just because an MSA is signed, and the provider is not obliged to supply them. Each specific engagement is scoped and committed separately, usually through a statement of work or order form. That separation is deliberate: it lets the parties agree the big legal picture once and keep each individual deal small and fast.
This structure suits recurring relationships particularly well. SaaS providers, software developers, IT services firms, marketing agencies and professional services businesses all use MSAs because their customers typically come back in phases: implementation, onboarding, integrations, training, then ongoing support and expansion. With an MSA in place, each phase can be added quickly without reopening the core legal terms every time.
The terms an MSA settles once
The core of an MSA is a set of clauses that would otherwise have to be renegotiated for every job. In most agreements they cover the following:
- Scope and governance: how work is requested, accepted, varied and rejected, and who is authorised to approve changes on each side.
- Intellectual property: who owns what is created. The default under Australian law is that the author of a work owns the copyright in it, under s 35 of the Copyright Act 1968 (Cth), and an assignment of copyright has no effect unless it is in writing signed by the assignor, under s 196 of the Copyright Act 1968 (Cth). The parties can agree something different, and the MSA is where that agreement is recorded, for example a licence to the customer rather than a transfer of ownership.
- Confidentiality and data: obligations to keep each other's information confidential, and how personal information is protected. Where the Privacy Act 1988 (Cth) applies, APP 11 requires an entity to take reasonable steps in the circumstances to protect personal information from misuse, interference, loss and unauthorised access or disclosure.
- Liability and caps: which party bears which risks, and how liability is capped or excluded. Australian courts read exclusion and limitation clauses according to their natural and ordinary meaning in the context of the whole contract, as the High Court explained in Darlington Futures Ltd v Delco Australia Pty Ltd (1986) 161 CLR 500. The consumer guarantees in the Australian Consumer Law cannot be excluded by contract under s 64, although for services supplied to businesses a term limiting liability to re-supplying the services can be valid under s 64A.
- Payment: fees, invoicing, GST, late payment interest and set-off rights.
- Term, termination and survival: when the MSA starts and ends, how either party can end it early, and which obligations continue after it ends.
These are the terms that take time to negotiate. Settling them once is the whole point of the structure. Every document added later can focus on the commercial detail of one piece of work.
The documents that sit beneath the MSA
The MSA does not work alone. In a typical engagement it sits at the top of a small stack of documents, each of which draws its authority from the MSA and adds a specific layer of detail.
A statement of work (SOW) or order form describes one piece of work: the deliverables, timeline, price, assumptions and acceptance criteria. It is the document that actually commits the parties to that job, and it incorporates the MSA's terms by reference. A service level agreement (SLA) sets performance standards for the ongoing service, such as uptime targets, support response times, incident categories and service credits. A data processing agreement (DPA) or security schedule deals with privacy and data handling between the parties, and technical policies may sit alongside it.
Because several documents apply at once, MSAs usually include an order of precedence clause stating which document wins if the terms conflict. Many agreements give the MSA priority on the overarching legal and commercial terms, and the SOW priority on anything specific to that project. The drafting choice matters: a business that assumes the MSA always prevails can be surprised when a detailed SOW term is given effect instead.
The same layered logic applies at the end of the relationship. If the MSA expires while SOWs are still running, the outcome depends on what the MSA says. Most agreements include a survival clause stating that the MSA's terms continue to govern active SOWs until they are completed or terminated. If the MSA is silent, the parties face real uncertainty about which terms apply to in-progress work, which is why a survival clause is worth checking before signing rather than after.
A master services agreement in practice
Consider Bluewater Software, a Perth-based SaaS company that sells a logistics platform to small and medium retailers. Bluewater's customer, a national homewares chain, comes through its website, and the commercial team wants to close the deal without weeks of legal back and forth.
Bluewater signs a master services agreement once. The MSA sets out who owns the intellectual property in the platform (Bluewater keeps ownership and grants the customer a licence), a liability cap of twelve months of fees, confidentiality obligations on both sides, payment terms of 30 days, and a clause stating that the MSA's terms survive for any SOW still in progress if the MSA ends. The first piece of work is then scoped in a short SOW: implementation and data migration over eight weeks, with acceptance criteria the customer can test against. An SLA attached to the SOW promises 99.5% uptime and defines service credits if Bluewater misses it.
Six months later the customer asks for a new integration with its inventory system. Because the framework is already in place, the work is agreed in a two-page SOW referencing the MSA, and the job starts within days. When the customer's procurement team later insists it owns the integration code because it paid for the build, Bluewater points to the MSA: the customer has a licence to use the work, not ownership of it, because that is what the parties wrote down. A dispute about whether the SOW's acceptance criteria override the MSA's liability cap is resolved by the precedence clause, which gives the SOW priority on project-specific matters. When the customer eventually signs with a larger competitor and the MSA is terminated, the survival clause keeps the confidentiality and licence terms running for the SOW still being wound down.
Where businesses get MSAs wrong
The most expensive misunderstanding about MSAs is that paying for work means owning it. Under Australian copyright law the author of a work is the first owner of the copyright, and an assignment must be in writing. A customer that pays for a bespoke build without an assignment clause receives a licence at most, and a provider that assumes the customer will never claim ownership can find the assumption tested precisely when the relationship ends badly. Neither side should rely on an unspoken expectation: the MSA is where ownership is decided.
A second confusion is treating an MSA as just a longer set of terms and conditions. Terms of service are usually standard form: prepared by one party, offered on a take-it-or-leave-it basis, and accepted online. Standard form contracts are treated specially under the Australian Consumer Law. An unfair term in a standard form consumer or small business contract is void under s 23, and since penalties were introduced, proposing or relying on an unfair term can expose a business to a penalty under s 224 of up to the greater of $100 million, three times the benefit obtained, or 30% of adjusted turnover. A negotiated MSA is a different animal, but any part of the arrangement that is offered on a standardised, non-negotiated basis can still attract that scrutiny. The small business test is broad: a contract qualifies if a party employs fewer than 100 people or has turnover under $10 million, so most Australian customers of an MSA will be covered.
A third error is assuming the MSA always overrides everything beneath it. Precedence is a drafting choice, and many agreements deliberately give the SOW priority on project-specific points. And a fourth is treating a liability cap as a guarantee of protection. Caps and exclusions are construed by their natural and ordinary meaning, and a badly drafted cap may not cover the loss the business assumed it would, while consumer guarantees cannot be excluded at all.
Getting a lawyer to review your MSA
An MSA rewards professional attention because the cost of getting it wrong is spread across every future engagement. A commercial lawyer will map the document stack to the way the business actually sells: which terms belong in the MSA, which belong in each SOW, and whether the precedence and survival clauses produce the outcome the business expects. They will draft the intellectual property provisions so ownership and licences match the commercial model, size liability caps against insurance cover, and flag any standard form risk under the unfair contract terms regime.
The practical benefit is speed and reuse. A well-drafted MSA is signed once and used for years, and each new deal reduces to a short SOW. A lawyer reviewing the template before it goes to the first customer is far cheaper than untangling ownership or liability disputes across a portfolio of live contracts.
The ownership question to answer before you sign
Before committing to an MSA, either as provider or customer, ask the question that decides most disputes later: if the relationship ended tomorrow, who would own the work product, and which obligations would continue? The answer should be findable in the document, not assumed from who paid whom. If you cannot point to the clause that says who owns what was built and what survives the end of the agreement, that is the gap to close before you sign.