A master service agreement (MSA) is a framework contract that sets the standing commercial and legal terms for an ongoing relationship between two businesses, usually a service provider and a customer. Instead of negotiating payment, intellectual property, confidentiality and liability from scratch for every job, the parties settle those terms once in the MSA, and each individual job is then documented against it. The result is faster deals, consistent terms across projects, and a single document that determines how disputes will be resolved.
This article explains what an MSA is and how it works with statements of work, the clauses it typically contains, a worked example of an MSA in action, and the misconceptions that cause the most trouble for Australian small businesses.
What a master service agreement is
An MSA is an umbrella contract that governs a continuing relationship rather than a single transaction. It records the terms the parties want to apply to all of their dealings: how work is requested and accepted, how it is priced and paid for, who owns the intellectual property created along the way, how confidential information is protected, what happens if something goes wrong, and how the relationship can be brought to an end. Because those terms are settled once, later jobs do not require a full renegotiation of the same ground. Renegotiating the same terms for every job is exactly the problem the MSA solves.
The key mechanic is the statement of work (SOW), sometimes called a work order or purchase order. The MSA establishes the framework; each SOW describes one specific project, including the services to be delivered, the deliverables, the fees, the timeline and any milestones. The SOW is executed against the MSA, so the master terms apply to the project without being restated in full.
What an MSA does not do, on its own, is commit either party to a particular project. A framework agreement that simply sets standing terms usually leaves each engagement to be authorised separately by a SOW. So before you sign, it pays to check whether the MSA itself obliges you to perform work or purchase services, or whether it only sets the rules for work you later agree to in writing.
The core elements of an MSA
MSAs vary from industry to industry, but a commercial MSA in Australia typically covers the same ground. The main elements are:
- Scope and engagement: how services are requested and accepted, usually through a SOW, and what happens when the customer's requirements change mid-project.
- Payment terms: the rates or pricing schedule, invoicing and payment timing, interest on late payments, and who bears taxes such as GST.
- Intellectual property: who owns the IP in the deliverables, what licence the customer receives to use them, and that each party keeps the IP it brought to the relationship.
- Confidentiality and data: obligations to protect confidential information, and how personal information is handled under privacy law.
- Warranties: promises about the standard of the services, that the deliverables will be fit for the agreed purpose, and that each party has authority to enter the agreement.
- Liability and indemnities: a cap on liability (often a multiple of the fees paid), exclusion of consequential loss, and indemnities for third-party claims, personal injury and property damage.
- Insurance: minimum levels of public liability, professional indemnity and workers compensation cover, usually supported by certificates of currency produced on request.
- Termination: notice periods, termination for breach, and what happens to work in progress, IP and confidential information when the relationship ends.
- Dispute resolution: agreed steps such as negotiation and mediation before court proceedings, plus the governing law and the courts that will hear a dispute.
The terms in this list are not decorative boilerplate. Liability caps and indemnities are where the real money sits, and they interact directly with the insurance each party carries. A cap of twelve months' fees might suit a low-risk web support arrangement but be completely inadequate for a job where a software error could bring down a client's systems. Before signing, you need to know what risk each clause allocates to you, not just what the headline fee is.
A worked example: an agency, a retailer and three projects
Consider a Melbourne web design studio with six staff that signs an MSA with a national retailer wanting ongoing website work. The MSA sets the studio's hourly rates and invoicing terms, confirms that the studio keeps its pre-existing code libraries while the retailer owns the finished website, caps the studio's liability at the fees paid in the previous twelve months, requires $10 million in public liability insurance, and lets either side end the relationship on 30 days' notice. Each piece of work is then agreed in a short SOW: the first covers a new product page, the second a monthly maintenance retainer, and the third a migration of the retailer's old site.
The value of the structure shows up when things go wrong. Suppose the rushed migration causes data loss on the old site and the retailer demands compensation. The dispute turns on the MSA, not the SOW: the liability cap fixes the studio's maximum exposure, the indemnity wording decides whether particular losses are covered at all, and the dispute resolution clause determines whether the matter goes to mediation first. The parties agreed all of that months before the migration was ever discussed. That is the practical point of an MSA, and why the negotiation of its terms deserves more attention than the SOWs that follow.
Common misconceptions about MSAs
"An MSA is a complete contract, so a signed MSA means the job is booked."
An MSA sets the framework; the work itself is committed through a SOW. Unless the MSA contains a minimum commitment, such as an exclusivity arrangement or a guaranteed volume of work, neither party is bound to provide or purchase particular services until a SOW is agreed. Read the MSA for anything that commits you to work you have not yet scoped.
"An indemnity means the other side's insurer pays for everything."
An indemnity is a contractual promise to compensate the other party for specified losses, not a policy of insurance. Its value depends on the wording, on the indemnifying party actually having the money or cover, and on how a court reads it. Australian courts construe indemnity clauses strictly, and clear words are required before a party will be held to have agreed to indemnify the other against the consequences of its own negligence: see Andar Transport Pty Ltd v Brambles Ltd (2004) 217 CLR 424. An indemnity that looks broad in a template can turn out to be narrow in a courtroom, which is why the clause and the insurance behind it need to be read together.
"It is just a standard form, so the terms are what they are."
The terms are not whatever the drafter wants them to be. Under the Australian Consumer Law (ACL), which is Schedule 2 of the Competition and Consumer Act 2010 (Cth), an unfair term in a standard form consumer or small business contract is void: s 23 of the ACL. A small business contract includes one where a party employs fewer than 100 people or has turnover under $10 million, which covers most SMEs. Since the regime was strengthened, proposing or relying on an unfair term is itself a contravention, and a company faces a penalty of up to the greater of $100 million, three times the benefit obtained, or 30% of adjusted turnover (s 224 of the ACL). Terms that let one party terminate or vary the contract unilaterally, or that limit one party's right to sue, appear on the statute's example list of terms that may be unfair (s 25 of the ACL). A one-sided template MSA is not merely unfavourable; parts of it may be unenforceable, and the party proposing them carries real exposure.
"We are business to business, so consumer law does not touch us."
The consumer guarantees themselves generally protect consumers, but suppliers still cannot contract out of them: a term that excludes, restricts or modifies the guarantees is void under s 64 of the ACL. For services supplied to a business, liability for failure to comply with a guarantee can be limited to re-supplying the services or paying the cost of having them supplied again, but only where that limitation is fair and reasonable (s 64A of the ACL). An MSA that purports to exclude liability for defective work altogether may contain a clause that a court will simply strike out.
When a lawyer should review your MSA
The right time for legal input is before signing, not after a dispute erupts. The situations that most clearly warrant a review are when you are asked to sign the other side's template, when you are drafting your own MSA for clients, and when the MSA is one of several interlocking documents such as a software licence, a services agreement and an insurance policy.
A commercial lawyer's job here is practical. They will mark up the draft so that the risk allocation matches the commercial deal, explain the trade-offs in the liability cap and indemnity provisions, check the MSA against the unfair contract terms regime, and make sure the SOWs incorporate the MSA correctly without contradicting it. They will also check the interaction between the indemnities and the insurance each party must carry, because an indemnity that is not backed by cover is often worth little in practice. For a business that relies on repeat work, that review is usually a modest cost against the price of a single badly drafted clause.
What your MSA commits you to before work starts
Before you sign an MSA, ask what it obliges you to do today, not just on the first project. Does it commit you to minimum volumes of work or exclusivity? What would it cost you to walk away, and what notice do you need to give? If your biggest client stopped paying tomorrow, would the termination clause let you stop work and recover your money, or would you be locked in? Those answers come from the MSA's commitment, termination and liability terms, not from the SOWs that follow. Read those clauses before the framework is signed, because they decide disputes years before they happen.