1. What the MSA binds and what it doesn't
  2. The essential clauses
    1. How scope is defined — and who controls it
    2. How long the agreement lasts and how it ends
    3. How and when payment is made
    4. Who owns the intellectual property
    5. How liability is limited
    6. Unfair contract terms — a compliance issue, not just a negotiating point
    7. Indemnities — who pays when a third party sues
    8. Confidentiality and data handling
    9. Dispute resolution
  3. Optional and situational clauses worth considering
  4. How Artificer Legal can help
  5. The IP ownership clause

A vendor sends you a master services agreement and says it's their "standard template." Your instinct is to scroll to the signature page. Resist that instinct.

A master services agreement (MSA) is the contract that sits above every piece of work you do together. Unlike a one-off service contract, an MSA governs multiple projects — sometimes for years — by establishing a fixed set of rules that apply each time a new statement of work (SOW) is issued. Get the MSA wrong at the start and every downstream project inherits the same problem.

This guide walks through the clauses that matter most, the drafting choices each one forces, and the traps that regularly cause disputes between Australian businesses.

What the MSA binds and what it doesn't

An MSA creates the legal framework. The SOW (or purchase order, or project schedule) creates the individual obligation. The two documents work together: the MSA sets the "how" — liability caps, IP ownership, confidentiality, dispute resolution — and the SOW sets the "what" — scope, deliverables, timeline, and project-specific fees.

This structure is useful precisely because it separates the commercial terms you negotiate once from the operational details you agree project by project. But it also creates a risk: if the MSA and a SOW contradict each other, which document wins? A well-drafted MSA answers that question explicitly. A poorly drafted one leaves it for a court.

The essential clauses

How scope is defined — and who controls it

The scope clause in the MSA describes the universe of services the agreement covers. It does not specify what you will actually do on any given project — that lives in the SOW. But it does matter, because disputes about whether particular work falls under the MSA at all come back to this clause.

Watch for:

  • Vague catch-all language ("any services the parties agree to from time to time") that could pull work into the agreement you did not intend to include
  • Clauses that allow the client to vary scope unilaterally, without a signed SOW or written approval
  • No mechanism for raising a change request when client instructions expand the scope mid-project

A clear scope clause names the categories of services covered, requires a written SOW for each engagement, and specifies that scope changes need written agreement from both parties.

How long the agreement lasts and how it ends

Every MSA needs a clear answer to two questions: when does it expire, and how can either party end it early?

Term. MSAs can run for a fixed period (say, two years, automatically renewing unless notice is given) or on a continuing basis until terminated. The risk with automatic renewal clauses is that they often require notice of non-renewal 60 or 90 days before the end of the term — easy to miss.

Termination for convenience. Many MSAs allow either party to terminate without cause on notice (30, 60, or 90 days is typical). Check whether that right is mutual or one-sided. A termination for convenience clause that only runs in one direction is worth pushing back on.

Termination for cause. This covers material breach, insolvency, or regulatory non-compliance. Check whether the defaulting party gets a cure period (typically 14–30 days) before the other party can act, what happens to active SOWs on termination, and whether accrued payment obligations survive (they should).

How and when payment is made

The payment clause sets the billing structure that applies across all SOWs. Details about specific project fees belong in the SOW, but the MSA fixes the rules:

  • Are invoices due within 14, 30, or some other number of days from issue?
  • Does late payment attract interest, and at what rate?
  • Who bears expenses — travel, software, subcontractors — and is pre-approval required?
  • If the client disputes an invoice, can they withhold the whole amount or only the disputed portion?

The variant most service providers push for: the right to suspend services (or terminate for cause) after a specified period of non-payment. Clients often push back. A compromise is a cure period and written notice before suspension kicks in.

Who owns the intellectual property

IP ownership is the clause most commonly underdrafted and most frequently litigated. Under s 35 of the Copyright Act 1968 (Cth), where a person creates a work under a contract of service (that is, as an employee), copyright vests in the employer. Where a person creates a work as an independent contractor — under a contract for services — copyright ordinarily remains with the creator unless the contract says otherwise.

For most MSAs, the service provider is not the client's employee. That means, absent a specific assignment clause, the service provider may retain copyright in everything produced under the agreement — code, designs, reports, written materials.

Common approaches:

  • Full assignment on payment. The client owns all deliverables once paid. Standard for bespoke software and creative work. Providers should carve out pre-existing IP and internal tools.
  • Licence only. The provider retains ownership and grants the client a licence. More common where the provider's core methodology is embedded in every engagement.
  • Background / foreground IP split. The provider retains IP it brought to the table; deliverables created specifically for the client are assigned or exclusively licensed. This is often the most balanced structure for technology and consulting MSAs.

Whatever the arrangement, the MSA should specify what happens to IP after termination — whether a licence survives, and on what terms.

How liability is limited

A limitation of liability clause caps what either party can recover if something goes wrong. Almost every MSA includes one. The drafting choices matter enormously.

The cap itself. Providers typically cap liability at fees paid under the relevant SOW (or all fees paid under the MSA in the preceding 12 months). Clients often want a higher cap tied to total contract value or an uncapped remedy for specific loss categories.

Exclusion of consequential loss. Most MSAs exclude indirect or consequential loss — lost profits, loss of data, loss of business opportunity. These exclusions are commercially standard but should be mutual.

Carve-outs. Even a tightly capped MSA should carve out liability for:

  • Death or personal injury caused by negligence
  • Fraud or wilful misconduct
  • Breach of confidentiality
  • Breaches of IP ownership obligations

Be alert to clauses that exclude liability for negligence in terms broad enough to erase meaningful protection. Australian courts will read exclusion clauses narrowly where the language is ambiguous, but that is a remedy of last resort, not a drafting strategy.

Unfair contract terms — a compliance issue, not just a negotiating point

If the MSA you are being asked to sign is a standard form contract — meaning it was prepared by the other side and you have little or no opportunity to negotiate its terms — it may be subject to the unfair contract terms (UCT) regime under Schedule 2 of the Competition and Consumer Act 2010 (Cth) (the Australian Consumer Law).

Since 9 November 2023, the UCT regime was significantly expanded. A business qualifies as a "small business" for UCT purposes if it employs fewer than 100 people or has annual turnover of less than $10 million. Critically, the 2023 amendments removed any contract value threshold — so the UCT regime can apply to a high-value MSA between two businesses if one qualifies as a small business. And from that date, proposing, using, or relying on an unfair term is itself prohibited and can attract substantial penalties, not merely render the term void.

Terms that have attracted UCT scrutiny in commercial contracts include:

  • Unilateral variation rights (one party can change price or scope without consent)
  • Automatic renewal with inadequate notice periods
  • Broad indemnities that expose one party to loss well beyond what they caused
  • Termination rights available to one party only

If you are the smaller party to an MSA and the counterparty has used essentially the same template across many customers, the UCT regime may give you more leverage in negotiation than you realise.

Indemnities — who pays when a third party sues

An indemnity clause requires one party to cover the other's losses in specified circumstances, including legal costs. In an MSA, indemnities typically address IP infringement claims, personal injury or property damage caused by the provider's personnel, and regulatory fines arising from a party's breach of law.

The trap is the uncapped, broadly worded indemnity. A clause requiring the provider to indemnify the client against "any loss arising in connection with the services" is functionally unlimited and can dwarf the contract value. Indemnities should:

  • Be limited to losses caused by the indemnifying party's own acts or omissions
  • Not duplicate the liability cap (or the relationship between indemnities and the cap should be spelled out)
  • Require the indemnified party to take reasonable steps to mitigate its loss

Confidentiality and data handling

Most MSAs include a mutual confidentiality obligation. Check the definition of "confidential information" — does it cover all business information disclosed in connection with the engagement, or only information expressly marked as confidential? Broad, mutual definitions are preferable for both parties.

Key drafting points:

  • How long does the obligation survive termination? Perpetual obligations are common for genuinely sensitive information; a 2–5 year sunset is typical for general business information.
  • What are the permitted disclosures — to lawyers, auditors, employees who need to know?
  • Is legally compelled disclosure a carve-out (it should be), and must the disclosing party give notice before complying?

Where the MSA involves handling personal information, compliance with the Privacy Act 1988 (Cth) is a separate obligation. Businesses with annual turnover above $3 million are generally covered by the Act and must handle personal information in accordance with the Australian Privacy Principles. MSAs in technology and data-intensive sectors often include a privacy annex that allocates responsibilities between the parties.

Dispute resolution

A dispute resolution clause charts the path from disagreement to resolution without automatically triggering litigation. The typical structure is: negotiation first (escalating to senior management), then mediation, then arbitration or court proceedings.

For Australian businesses, consider:

  • Which state or territory law governs the agreement (this determines which courts have jurisdiction)
  • Whether mediation is mandatory and which body administers it (the Australian Disputes Centre is commonly nominated)
  • Whether either party can seek urgent injunctive relief without going through the steps — particularly important for IP and confidentiality breaches
  • Where the counterparty is overseas: whether Australian courts or arbitration under an international framework applies

Optional and situational clauses worth considering

  • Force majeure. Excuses performance if extraordinary events make it impossible — pandemics, natural disasters, government orders. Useful in long-running MSAs; worth defining narrowly to avoid opportunistic reliance. Check whether it suspends obligations or terminates the agreement entirely.
  • Assignment and subcontracting. Without a restriction, either party can assign their rights or delegate their obligations. If the relationship is personal to specific personnel or the client's approval matters, restrict assignment without prior written consent.
  • Insurance. Specifying minimum insurance requirements (professional indemnity, public liability, cyber) provides a baseline for both parties and may be required by industry codes or government contracts.
  • Survival. Identifies which clauses survive termination — confidentiality, IP ownership, payment obligations, and indemnities at a minimum.
  • Entire agreement. Confirms that the MSA (and its schedules) constitute the whole agreement, superseding pre-contractual representations and prior drafts.

An MSA presented as "standard" is rarely risk-neutral for both parties. When Artificer Legal reviews an MSA, we work through the document in commercial weight order — IP, liability, indemnities, payment — rather than clause sequence. The clauses that most often need pushing back on are the ones that look boilerplate: uncapped indemnities tucked into a definitions clause, liability carve-outs that nullify the cap, confidentiality obligations with no sunset.

For clients entering an ongoing services relationship, we typically:

  1. Identify the provisions posing the greatest financial exposure and open negotiation there first — giving ground on lower-stakes clauses builds goodwill for the fights that matter.
  2. Propose specific redlines rather than general objections, which keeps negotiation productive.
  3. Flag whether the contract structure engages the UCT regime and what leverage that may give you.
  4. Review the attached SOW template to ensure it works with the MSA rather than against it.

If you are the party issuing the MSA, we review it from the other side's perspective first — the best way to find provisions a counterparty will reject, and to draft terms robust enough to hold up.

The IP ownership clause

In most MSA disputes, the outcome turns on the IP ownership clause — not because it is always the subject of the claim, but because it determines the leverage both sides have. A provider who retains copyright in deliverables can, in theory, prevent the client from using work they have paid for. A client who holds an assignment can use deliverables with a new provider the moment the relationship ends. Each position creates powerful incentives — or chilling effects — on how the other party behaves when things go wrong.

Negotiating IP at the start of the relationship, before either party has invested heavily in the engagement, is far easier than litigating it later. It is also the clause most commonly deferred with the intention of "sorting it out in the SOW," which rarely happens.

Key points for any MSA review:

  • The MSA governs every project under it — errors in the template compound across every SOW issued.
  • The unfair contract terms regime applies to standard form contracts with businesses employing fewer than 100 people or turning over less than $10 million, and it now prohibits (not just voids) unfair terms.
  • Under the Copyright Act 1968 (Cth), independent contractors retain copyright in works they create unless the MSA assigns it to the client.
  • Limitation of liability clauses and indemnities interact — both need to be read together to understand your actual exposure.
  • Confidentiality, data handling, and Privacy Act compliance should be addressed explicitly, not left to implication.
  • A clear dispute resolution pathway reduces the cost of resolving disagreements without litigation.