Service agreement clauses: what every Australian business needs in writing

You've received a draft service agreement from a new client or counterparty, or you're about to send your own template for the first time. Either way, the instinct is usually to scan for the obvious things — price, scope, end date — and sign. That instinct misses most of the clauses that actually matter when something goes wrong.

A service agreement is the governing contract between two businesses for the delivery of services. It records what is being provided, on what terms, at what price, and what happens if either side fails to perform or wants to exit. Unlike a consumer-facing terms document, a B2B service agreement sets out the full commercial relationship — it does not merely evidence a deal, it defines one. Where a master services agreement (MSA) governs the ongoing relationship and statements of work (SOWs) govern individual projects, a standalone service agreement covers both functions in one document.

Parties and term

A service agreement should open by identifying the parties with precision.

Full legal name: use the registered business name or company name, not a trading name alone.
ABN or ACN: essential for tax invoicing and establishing that the counterparty is a legal entity rather than a sole trader using a brand.
Authorised signatories: for companies, check that the people signing have authority to bind the entity under the Corporations Act 2001 (Cth). Two directors, or one director and a company secretary, is the standard safe execution method.
Term: specify the start date, whether the agreement runs to a fixed end date or continues until terminated, and how it renews (automatic rollover versus written notice to renew).

The trap here is leaving the term silent or using language like "until the project is complete" without defining what completion means. That ambiguity frequently resurfaces in disputes about whether an ongoing retainer has actually ended.

Scope, deliverables and change control

This is the clause that most service agreements get dangerously wrong.

The scope clause should state in plain English what the provider will deliver, the key assumptions underpinning that commitment, and — just as importantly — what is excluded. A scope clause that says only "marketing services" gives neither side any protection.

Deliverables are the outputs: specific documents, software builds, reports, designs, advisory services. Name them. If they vary by project, attach a short schedule or SOW format and reference it here.

Change control is the mechanism for agreeing and pricing any work outside the original scope before it starts. Without it, the provider either absorbs extra work or faces a dispute about whether the variation was agreed. A workable change control clause needs:

a written request from either side;
a turnaround time for the provider to quote the variation; and
written acceptance before extra work commences.

The variant the client will push for is no change control at all — or a change control process that lets the client direct variations unilaterally and sort out the price later. Resist both. If the scope changes, the price and timeline should be agreed at the same time.

Pricing, invoicing and payment terms

Clear payment mechanics protect cash flow. The clause should address:

Pricing model: fixed fee, milestone-based, hourly rate, retainer, or a combination. State which applies and what triggers each invoice.
GST: confirm whether fees are quoted inclusive or exclusive of GST.
Deposit: an upfront payment reduces exposure if the client does not pay or terminates early.
Due date and late payment: specify the number of days to pay, the right to charge interest on overdue amounts, and — critically — the right to suspend work while invoices remain outstanding. Without a suspension right, the provider must keep performing even when unpaid.
Disputed invoices: require the client to notify any dispute within a short window (seven to fourteen days) and pay the undisputed portion by the due date.

Intellectual property ownership

IP is the clause most commonly left vague and most often fought over.

The default position under Australian law is that the creator owns the copyright in what they produce — unless the parties agree otherwise. That means a client who pays for a design, a software build, or a written report does not automatically own the IP in it. The service agreement must address three questions:

Assignment or licence? If the client needs to own the output outright (common for bespoke software, logos, or marketing assets), the agreement must contain a written assignment of IP effective on payment in full. If the provider is granting a right to use rather than transferring ownership, define the scope, duration and exclusivity of the licence.
Background IP: IP the provider brings to the engagement (existing tools, code libraries, methodologies) is typically licensed to the client for use in the deliverables, not assigned. State this explicitly.
Moral rights: under the Copyright Act 1968 (Cth), individual creators retain moral rights (including the right of attribution) regardless of assignment. If the creator is an employee, the employer owns the copyright; if a contractor, their own moral rights remain.

The trap the other side usually pushes for is broad assignment language that sweeps in the provider's background IP without payment of additional consideration. That wording can transfer tools the provider uses across every engagement to a single client.

Confidentiality

Both sides typically share information they would not want disclosed publicly — pricing, client lists, technical methods, commercial strategies. The confidentiality clause should:

Define "confidential information" broadly but with a standard carve-out for information that is publicly available, already known to the recipient, or independently developed.
Impose an obligation to use the information only for the purposes of the engagement and to protect it with reasonable security measures.
Set out who within each organisation may receive the information (limiting disclosure to personnel who need it).
State a duration — either a fixed period after the engagement ends (two to five years is common) or indefinitely for genuinely sensitive categories.

For many B2B service agreements, a standalone NDA is executed before substantive discussions begin; the service agreement then picks up those obligations and extends them for the life of the engagement.

Warranties, liability and indemnities

This is where the commercial risk allocation happens — and where Australian law imposes real limits on what the parties can agree.

Warranties

The provider typically warrants that services will be delivered with due care and skill. Under Schedule 2 of the Competition and Consumer Act 2010 (Cth) (the Australian Consumer Law), this guarantee applies automatically to the supply of services to certain purchasers and cannot be excluded. In a B2B context the ACL guarantee position is more nuanced, but do not rely on broad exclusions to override guarantees that apply by operation of law.

Liability cap

A liability cap limits what either party can recover. Common approaches are a multiple of the fees paid (often one to three times), the amount recoverable under the provider's professional indemnity or public liability insurance, or a fixed dollar figure. The cap should also exclude certain heads of loss — typically indirect or consequential loss, loss of revenue, and loss of data — but exclusions that purport to override ACL consumer guarantees or that are unconscionable will not be enforced.

Indemnities

Keep indemnities narrow. An indemnity for third-party IP infringement (where the provider's deliverables infringe a third party's rights) is reasonable. A broad mutual indemnity against any loss is difficult to insure against and often renders the liability cap meaningless. Check whether any indemnity is carved out of the cap.

Unfair contract terms

If the service agreement is a standard form contract — the same document offered to multiple clients without negotiation — the unfair contract terms regime under the ACL applies. Since 9 November 2023, it is unlawful to propose, use or rely on an unfair term in a standard form contract with a small business, defined as one that employs fewer than 100 people or has an annual turnover of less than $10 million. Maximum penalties for bodies corporate are substantial. Review standard templates against the regime before sending them to clients who fall within the threshold.

Termination and offboarding

A well-drafted termination clause covers three scenarios:

Termination for convenience: either party may exit with reasonable written notice (commonly 30 to 90 days for ongoing engagements). On termination for convenience, the client pays for all work performed to the date of termination.
Termination for cause: immediate termination (or termination on short notice, such as five to ten business days) where the other party has materially breached the agreement and failed to remedy within a cure period, or has become insolvent.
Consequences of termination: specify what happens to deliverables in progress, who holds what materials, how access to systems and platforms is unwound, and whether the provider must assist with transition to a new supplier.

The trap is termination clauses that allow one side to exit without paying for work already performed. That one-sided drafting is exactly the kind of term the UCT regime targets in standard form contracts.

Dispute resolution and governing law

A practical sequence is senior representative escalation, then mediation through a recognised body, then litigation or arbitration as the backstop. The clause should also name the governing law and the courts before which proceedings may be brought. Most Australian businesses nominate the state where they operate or where the services are delivered.

Optional clauses worth considering

These are not universal, but they come up often enough to warrant deliberate inclusion or exclusion:

Non-solicitation: prevents either party from poaching the other's staff or clients during and for a reasonable period after the engagement. Enforceability depends on reasonableness in scope and duration.
Subcontracting: if the provider will engage subcontractors, state whether client consent is required and confirm that the provider remains liable for subcontractor performance.
Insurance: specify minimum coverage — commonly public liability and professional indemnity — especially where the nature of the services creates exposure.
Privacy and data handling: if the engagement involves personal information, address the Privacy Act 1988 (Cth) obligations. Businesses with annual turnover of $3 million or less are generally exempt from the Australian Privacy Principles, but many enterprise clients require contractual compliance regardless, and health service providers are covered regardless of turnover.
Force majeure: limits liability for delays caused by events outside a party's control, but should include a cut-off so that a prolonged event allows termination rather than indefinite suspension.

Where Artificer Legal can help

Service agreements look deceptively simple. The structure is familiar and templates are widely available. The difficulty is in the drafting choices — scope language that actually matches how the provider delivers, IP allocation that the provider can live with across multiple clients, liability wording that is enforceable and insurable, and UCT-compliant standard terms.

At Artificer Legal, we review and draft service agreements with a focus on where the commercial risk sits and whether the document actually functions as intended:

Scope and change control: we tighten ambiguous scope language and build change control processes that match how the provider actually operates, not how a generic template assumes they operate.
IP and background IP: we identify what the provider is actually creating and whether the default assignment language they've received would strip them of tools they need for other clients.
Liability and indemnity alignment: we check that the cap, the exclusions, and any indemnities are consistent with each other and with the provider's insurance cover — a mismatch between the cap and the policy can leave a gap that neither side intended.
UCT compliance: for providers using standard-form templates across multiple clients, we audit the terms against the current unfair contract terms regime before a problem arises.

Whether you are sending or receiving the draft, the questions are the same — where has the risk been pushed, does the liability cap hold together, and is the scope clause precise enough to be enforced.

The change control clause

The most consistently underestimated clause in a service agreement is change control — not the liability cap, not the IP assignment, not the termination rights. Most disputes between service providers and clients don't start with catastrophic failure; they start with scope creep that was never formally agreed, priced, or documented. One party believed the variation was included; the other believed it was an extra. Without a written change control process, the dispute resolves either through the provider absorbing the cost or through litigation where contemporaneous emails become the contract.

A service agreement that works is one both parties actually follow. The scope must be precise enough to be meaningful, the change control simple enough to be used, and the payment terms matched to the provider's cash flow. When those three things align, the remaining clauses — IP, liability, termination — rarely need to be invoked.