1. What the scope clause actually does
  2. How the price is calculated and when you get paid
  3. Timelines, dependencies, and what delays cost
  4. Warranties and what the law already guarantees
  5. Liability, caps, and the limits of exclusion
  6. Intellectual property ownership and licensing
  7. Confidentiality obligations
  8. Term, termination, and what happens on exit
  9. Dispute resolution
  10. Compliance references
  11. Situational clauses worth considering
  12. How Artificer Legal can help you get this right
  13. The scope clause prevents disputes from arising

A counterparty has sent you a draft services agreement. Or your lawyer has returned a template and asked you to review it before the next call. Or you are the one filling in the blanks on a standard-form document before a new client signs. In each of these moments, the document in front of you is doing more than recording what was agreed — it is allocating risk, setting the default rules if something goes wrong, and determining who carries the cost of misunderstanding.

A business contract is an operational tool, not a legal formality. It displaces the assumptions the law would otherwise make about your relationship. In the absence of written terms, courts reconstruct an agreement from conduct, correspondence, and industry custom — an exercise that is expensive and unpredictable. A well-drafted contract forecloses that exercise by answering, in advance, the questions most likely to arise.

What the scope clause actually does

The scope clause is where most commercial disputes begin. It defines what you will do or supply, what you will not, and what constitutes acceptable completion.

  • Define deliverables with objective criteria. "A functional website" is not a deliverable. "A live website meeting the technical specification in Schedule 1, accepted by the client in writing" is.
  • State what is excluded. If third-party integrations, training, or ongoing support are out of scope, say so explicitly. Silence is routinely read as inclusion.
  • Build in a variation mechanism. Describe how changes are proposed, priced, and approved. Without a variation clause, every scope discussion becomes a contractual dispute about whether the original terms have been varied by conduct.

The trap most often missed here is scope creep driven by informal instructions — a Slack message asking for "just one more thing", acknowledged by silence. The variation clause is your protection; it does nothing if it is ignored in practice.

How the price is calculated and when you get paid

Payment terms that seem obvious at signing are the first point of friction when a client relationship sours.

The clause should cover:

  • The fee structure (fixed price, time and materials, retainer, or a combination) and the basis for calculating any variable component.
  • The invoicing schedule — when invoices are issued, not just when they are due.
  • The payment due date and what happens when it passes: interest, suspension of work, or both.
  • What expenses are included in the fee and which are billed separately, including any approval threshold.

The variant counterparties push hardest on is extended payment terms — 60 or 90 days instead of 14 or 30. For a small business, that gap directly affects cash flow. Push back by tying payment milestones to delivery milestones rather than accepting a single end-of-project invoice date.

Timelines, dependencies, and what delays cost

A clause that sets a delivery date without addressing what happens when the client fails to provide approvals, content, or access is a trap for the supplier. If you cannot start or complete your work without something from the counterparty, say so and state the consequence: an automatic extension of the delivery date (and potentially the fees) by the number of days the client's input is late.

Also address what constitutes acceptance. If the client has a right to review and approve a deliverable, specify the review period, the criteria for rejection, and what happens if no response is given within the period. A deemed acceptance provision — under which silence after a defined period constitutes approval — protects against indefinite review loops.

Warranties and what the law already guarantees

Warranties are contractual promises about quality, fitness for purpose, or compliance. The clause should state clearly what promises you are making and, equally clearly, what you are not.

The constraint here is statutory, not just commercial. Under the Competition and Consumer Act 2010 (Cth), the Australian Consumer Law (Schedule 2) implies guarantees into contracts for goods and services supplied to consumers and, in some contexts, to small businesses. These guarantees — covering acceptable quality, fitness for disclosed purpose, and correspondence with description — cannot be excluded by contract under s 64 of the ACL. A clause that purports to exclude them has no effect and may itself attract scrutiny.

Practically, this means:

  • Draft warranty clauses to reflect what you can actually deliver consistently.
  • Include a remedy mechanism (repair, replacement, re-supply) that satisfies the ACL without over-promising.
  • Do not rely on a broad "as is" exclusion — courts will read down or void exclusions that conflict with statutory guarantees.

Liability, caps, and the limits of exclusion

A limitation of liability clause does two jobs: it caps the total damages recoverable against you, and it excludes certain categories of loss (typically indirect or consequential loss) from recovery altogether.

The cap is usually set by reference to the fees paid under the contract — often the fees paid in the preceding 12 months, or the total contract value. The practical question is whether your professional indemnity or public liability insurance aligns with the cap. A cap higher than your insurance coverage is a promise you cannot fund.

  • Consequential loss exclusion: Loss of profit, loss of revenue, and loss of data are the categories most commonly excluded. The clause must be specific; a generic "indirect loss" carve-out may not catch the losses it is intended to exclude.
  • ACL carve-out: You cannot exclude liability for death or personal injury caused by negligence, nor liability for conduct that would constitute fraud. Any limitation clause that purports to do so is void, and a court may read the entire clause down if it cannot be severed cleanly.
  • Unfair contract terms: Since 9 November 2023, changes to the unfair contract terms regime under the ACL mean that proposing, using, or relying on an unfair term in a standard-form contract — including overreaching liability exclusions — is prohibited and attracts civil penalties. For standard-form contracts with small businesses where the upfront price is under $300,000 (or $1 million for contracts longer than 12 months), regulators and courts will scrutinise one-sided indemnity and liability provisions closely.

Intellectual property ownership and licensing

IP clauses cause disproportionate disputes because the parties often hold incompatible assumptions. The author of the work defaults to ownership under the Copyright Act 1968 (Cth) — which means that unless the contract says otherwise, a contractor who builds your website or writes your marketing copy owns the copyright, not you.

The clause needs to address three distinct questions:

  1. Pre-existing IP: What background IP does each party bring to the engagement, and what rights does the other party have to use it?
  2. Newly created IP: Who owns IP created specifically under this contract? If it transfers to the client, is that on payment of the full fee, or on signing?
  3. Licence scope: If IP does not transfer, what licence does the recipient get — exclusive or non-exclusive, for what purpose, in what territory, and for how long?

For software, design, and creative work, these are rarely interchangeable. A developer retaining ownership of custom code while granting a licence may be commercially reasonable; the same position on a logo created specifically for your brand is not.

Confidentiality obligations

Confidentiality clauses protect information shared during the engagement — pricing, client lists, technical know-how, strategy — from being used or disclosed outside the deal. The clause should define:

  • What counts as confidential (usually broad, with specific carve-outs for information that is already public or independently developed).
  • The obligations attached: do not disclose, do not use outside the permitted purpose, take reasonable steps to protect.
  • The duration: confidentiality obligations should survive termination of the contract, often for two to five years, or indefinitely for trade secrets.

Where confidentiality matters before a contract is signed — during a pitch, a due diligence process, or early negotiations — a standalone non-disclosure agreement (NDA) should precede the main contract. The NDA covers the gap; the confidentiality clause in the main contract covers the engagement itself.

Term, termination, and what happens on exit

This clause is often the most consequential and the most skimmed. It governs three distinct scenarios.

Termination for convenience: Either party ends the contract without breach. The clause should state the required notice period (typically 14 to 90 days depending on the engagement), what happens to work in progress, and how final invoicing is handled.

Termination for breach: One party ends the contract because the other has materially breached its obligations. Best practice includes a cure period — an opportunity to remedy the breach within a defined time before termination takes effect. Without it, disputes about whether a breach was material become disputes about whether the termination itself was lawful.

Exit obligations: What must each party do on termination? Return or destroy confidential information, transfer data, hand over project files, complete work in progress to a defined stage, or cease using licensed IP. These obligations are frequently overlooked until a relationship has already broken down.

Dispute resolution

A dispute resolution clause is not just procedural tidiness. It determines how much a disagreement will cost to resolve and whether the commercial relationship can survive it.

A sensible structure escalates through three stages:

  1. Internal escalation — a nominated senior contact from each side, with a defined number of days to resolve informally.
  2. Mediation — a structured but non-binding process using a nominated mediator or a recognised mediation provider. Significantly cheaper and faster than litigation.
  3. Arbitration or litigation — as a last resort, with the governing law and jurisdiction specified. For most Australian business contracts, the governing law is the state where the business is based.

Courts will enforce an escalation clause — meaning that a party who goes straight to litigation without following the prescribed steps may have its proceeding stayed until it does. This matters when one side is in a hurry and the other is not.

Compliance references

Contracts sit alongside a web of mandatory law. The clause should reference, and require both parties to comply with, the statutory obligations that govern the engagement:

  • The Privacy Act 1988 (Cth) if either party will collect, use, or hold personal information — including an obligation to maintain and comply with a privacy policy.
  • Workplace health and safety laws if the work is performed at a site or involves physical services.
  • The Fair Work Act 2009 (Cth) if subcontractors or staff are deployed — the National Employment Standards cannot be contracted out of.
  • Any industry-specific regulatory requirements (licences, registrations, professional standards) that must be maintained during the engagement.

A compliance clause does not guarantee compliance; it allocates responsibility for it and creates a mechanism for exit if the other party loses a required accreditation.

Situational clauses worth considering

  • Restraint of trade: If the engagement gives the other party access to your clients or key staff, a carefully scoped post-engagement restraint may protect your competitive position — but restraints are enforceable only to the extent reasonable in scope, geography, and duration.
  • Step-in rights: In long-term contracts where your deliverables are critical to the client's operations, the client may want a right to assume control of the work if you become insolvent or cease trading. Address this explicitly rather than leaving it to negotiation in a crisis.
  • Survival clause: Certain obligations — confidentiality, IP ownership, limitation of liability, dispute resolution — should continue after the contract ends. A survival clause lists them explicitly and removes doubt about whether termination extinguishes them.
  • Assignment: State whether either party can assign the contract (or its rights under it) without the other's consent. Without an assignment clause, the default position under general law is ambiguous and may allow assignment in circumstances you would not accept.
  • Set-off: A set-off clause allows one party to deduct amounts owed to it from amounts it owes to the other. If you are the supplier, a broad set-off clause in the client's favour can directly affect when and how much you are paid.

The clauses that look standard are often the ones that cause the most damage, because they are the ones both sides stop reading. At Artificer Legal, our review of a business contract typically focuses on three things: whether the risk allocation is proportionate to the fees and the nature of the engagement; whether the statutory floor (ACL, Privacy Act, Fair Work Act) has been properly observed rather than merely referenced; and whether the document will actually work in practice when the relationship is under stress.

In negotiations, we push back hardest on liability exclusions that are broader than the counterparty's insurance coverage supports, on IP clauses that leave ownership ambiguous on payment, and on dispute resolution clauses that require arbitration in a jurisdiction or under rules that are disproportionately expensive for the value of the contract. We negotiate in priority order — scope and payment terms first, because they drive the commercial relationship; liability and IP second, because they determine the downside; boilerplate last, because that is where the traps are buried.

If you are receiving a counterparty's standard form, we will mark it up with a negotiation position. If you are building your own template, we will draft it to your risk profile and the specifics of your industry.

The scope clause prevents disputes from arising

The scope clause is the most important clause in most commercial contracts — not because it is the most legally technical, but because it is the one that determines whether a dispute arises at all. Vague scope invites disagreement about what was promised; objective, specific scope with a clear variation mechanism removes the ambiguity that turns a business misunderstanding into litigation. Every other clause in the contract operates on the assumption that what was agreed can be identified. The scope clause is what makes that identification possible.

Business contracts work when they reflect the actual agreement between the parties, allocate risk in a way both sides understand and accept, and comply with the statutory framework that applies regardless of what the contract says. The essential clauses — scope, payment, IP, liability, confidentiality, and termination — each carry a distinct job, and each carries distinct traps for the party who skims them. Reading the back half of the document as carefully as the commercial terms is not overcaution; it is how you avoid funding your counterparty's legal costs in a dispute that a clearer clause would have prevented.