A master services agreement, usually shortened to MSA, is a framework contract that sets the core legal terms for an ongoing relationship between a service provider and a customer. Instead of renegotiating liability, confidentiality, payment and ownership rules every time you take on a new piece of work, you agree them once in the MSA, then document each individual job separately in a shorter document called a statement of work, or SOW.
This guide explains what an MSA actually is, how it splits its job with a statement of work, how an MSA becomes legally binding in Australia, and the mistakes that quietly create risk for a small business that relies on one. It is written for a business owner selling services, and it also covers the position of a business buying services under someone else's template.
What a master services agreement actually does
The MSA is the "ground rules" layer of a working relationship. It deals with the terms that should stay the same regardless of which project you are doing. That includes how the parties engage with each other, general invoicing and payment rules, who owns the intellectual property created, confidentiality, privacy and data handling, liability limits and indemnities, termination rights, and how disputes are resolved.
What an MSA deliberately does not do is pin down the commercial detail of any single job. The specifics of each engagement, such as the exact scope, the deliverables, the deadlines, the fees and the assumptions the work depends on, belong in the statement of work.
This two-layer design is what makes an MSA efficient. A business that delivers services under recurring or changing engagements, such as IT support, software development, marketing, consulting, engineering or creative services, can sign one MSA with a client and then move quickly through many projects, because the legal framework is already settled and each new project only needs a shorter SOW.
How an MSA works with a statement of work
The MSA and the SOW do different jobs, and the division of content between them is worth understanding before you draft or sign either document.
Terms that typically belong in the MSA include:
- How work is engaged: who may sign a statement of work on each side, and whether work can start before a signed SOW exists
- Payment: how you invoice, how quickly payment is due, whether late payment attracts interest, and how the customer can dispute an invoice
- Intellectual property: what happens to pre-existing background IP, client-supplied material, and new work created during a project
- Confidentiality and privacy: what information is confidential, what data can be accessed, and what happens to data on termination
- Risk: liability caps, exclusions of loss, indemnities, and the warranties each party gives
- Termination and disputes: when either side can end the relationship, the notice periods, and how disagreements are escalated
Terms that typically belong in the statement of work include:
- Scope: the services to be delivered and the specific deliverables
- Assumptions and dependencies: what the provider needs from the customer before work can proceed
- Timing: timelines, milestones and any acceptance testing
- Commercials: fees, rates and expenses for that particular project
- Governance: service levels, reporting, and the points of contact
The drafting point that matters most is the order of precedence. The documents should state clearly that if the MSA and a SOW ever conflict, one of them wins. Many businesses want the SOW to override the MSA for commercial scope items like timing and pricing, but not to override core risk settings like a liability cap unless that override is expressly agreed. Without this rule, a dispute can turn into an argument about which document applies instead of being solved on its merits.
How an MSA becomes legally binding in Australia
An MSA is a contract like any other, so it is binding if the usual elements of contract formation are present. For Australian purposes that means there is an offer, the offer is accepted, each party gives something of value in return, usually called consideration, and the parties intend to create a legally binding relationship.
The practical question with an MSA is rarely whether it is binding in the abstract. The more common issue is whether it has been properly executed so a company is clearly bound, and whether the document matches how the parties actually operate.
Where a party is a company, execution matters. Under s 127 of the Corporations Act 2001 (Cth), a company can execute a document without a common seal if it is signed by two directors, or by a director and a company secretary. A proprietary company with a single director who is also the sole company secretary can execute by that director's single signature. There are also technology-neutral signing rules under the Corporations Act, so electronic signing is generally available. If an MSA or a SOW is meant to be signed as a deed, the execution requirements are slightly different, which is one reason it is worth confirming how a document is expressed to be signed before relying on it.
A separate and very common gap is the mismatch between the paperwork and reality. If the MSA says work only starts after a signed SOW, but in practice work begins on the strength of emails and messages, then the parties have created a situation where the "deal" on the ground does not match the "deal" on paper. That mismatch tends to surface painfully at the point of an invoice being disputed or a scope disagreement emerging.
A worked example
Ash runs a five-person digital marketing agency in Brisbane. She signs a master services agreement with a national retailer, then sets out each campaign in a separate statement of work. The MSA sets a monthly retainer and a payment term of 14 days, caps her liability at the fees paid in the previous three months, keeps her reusable campaign templates as her own background IP, and requires any dispute to go through negotiation and then mediation before litigation.
When the retailer wants a new email campaign, Ash only needs the account manager and the retailer's marketing lead to sign a short SOW covering the scope, the timeline and the fee for that campaign. She does not renegotiate the liability cap, the confidentiality obligations or the IP rules every time.
The structure only works because the paperwork is followed. If Ash delivered campaigns week after week without a signed SOW, the retailer could later dispute what was approved, what deadline applied, and even whether the work was ordered at all. The MSA's efficiency depends entirely on the discipline of recording each job in a SOW.
Common misconceptions about MSAs
The first misconception is that signing the MSA is the same as agreeing the work. It is not. In most arrangements the MSA only sets the framework, and a specific job is not agreed until a statement of work is signed. A provider that starts work before a SOW exists may find it difficult to prove what the client actually asked for, what deadline applied and what it is entitled to invoice.
A second misconception is that "the client paid for it, so the client owns everything." Australian copyright law does not work that way. Under s 35 of the Copyright Act 1968 (Cth), the author of an original work is generally the owner of the copyright. A work created by an employee in the course of employment is owned by the employer, but works created by an independent contractor or under a commission are not automatically owned by the client unless ownership is transferred by agreement. So an MSA needs to state expressly what happens to new work, what the provider retains as background IP, and what the client gets a licence to use. Without that, a reusable template or a piece of code can be unintentionally handed over, or a client can be left without a clear right to use what they paid for.
A third misconception is that an MSA commits you to a rigid structure you cannot follow. In fact an MSA is highly customisable. If you deliver work through subcontractors, use third-party tools, or work in short agile sprints, the MSA can be drafted to reflect that reality. The document only becomes a trap when it is drafted for a delivery model the business does not actually use.
A fourth misconception, more relevant when you are the customer, is that a counterparty's template is fine to sign because it is "standard." Standard form contracts are only standard in the sense that the drafter wrote them. Where a counterparty has prepared the MSA, the risk sits where the draft puts it, and the terms may not reflect what you are actually paying for. Having the template reviewed before signing is usually the cheaper option than litigating a clause you never noticed.
How Artificer Legal can help with an MSA
An MSA is a document where small drafting choices decide who wins when things go wrong, so this is a genuine case for professional input at the drafting or review stage.
If you are a service provider, a practitioner can build the framework around how you actually deliver services, making sure the liability cap matches your pricing model, the background IP is protected, the order of precedence is clear, and the statement of work process is workable in your day-to-day operations. If you are the customer being asked to sign someone else's template, a lawyer can review the MSA and its attached SOWs and policies, identify where the risk sits, and negotiate the clauses that matter rather than the ones that happen to be prominent.
A practitioner also brings the practical detail that templates miss, such as confirming proper execution under s 127 of the Corporations Act 2001 (Cth), and checking that the drafting reflects the operational reality of how work starts, how changes are approved and how the relationship ends. Because an MSA is intended to last for years and govern many separate jobs, small improvements to its drafting are paid back many times over.
The decision an MSA forces you to make
The single point that most often decides whether an MSA protects a business is not any one clause, but the order of precedence and the way a job becomes agreed. If you take one thing from this guide, decide now what rule applies in your arrangement: does a signed statement of work override the MSA on commercial scope items but not on core risk settings, and can work ever start without a signed SOW?
Answering those two questions in writing turns an MSA from a piece of paperwork into a working framework you can rely on. Leaving them unanswered is where the value of the whole structure leaks away, because a disagreement about which document applies is the one dispute an MSA was supposed to prevent.