If your business engages independent contractors, a well-drafted contractor agreement is not optional. It is the document that defines the relationship, protects your IP, and gives you recourse if something goes wrong.
This post covers what a contractor agreement needs to do, what to include in one, and the legal risks of misclassifying workers under Australian law.
What is a contractor agreement in Australia?
A contractor agreement is a contract between a business and an independent contractor that sets out the terms of the engagement. It covers the scope of work, how and when the contractor gets paid, who owns the IP, what stays confidential, and how the arrangement ends.
Unlike an employment contract, a contractor agreement reflects the fact that the contractor operates their own business. They are not an employee. That distinction matters legally, and your agreement should reflect it clearly.
Contractor vs employee: why the distinction matters in Australia
This is where most businesses get into trouble. If you engage someone as a contractor but the actual working arrangement looks more like employment, the law may treat them as an employee regardless of what the contract says.
The Fair Work Act 2009 and the Australian Taxation Office both apply multi-factor tests to assess the true nature of the relationship. The relevant factors include the degree of control the business has over how the work is done, whether the contractor can subcontract or delegate, who supplies tools and equipment, whether the contractor bears financial risk, and whether the work is for the business or the contractor's own enterprise.
Getting this wrong has real consequences. It can mean back payment of leave entitlements, superannuation obligations, payroll tax liability, and penalties under the Fair Work Act. The contract itself will not save you if the substance of the arrangement says employee.
What to include in a contractor agreement
Scope of work
Define exactly what the contractor is engaged to do. Vague scope is the most common source of disputes. Include specific deliverables, timelines, and any milestones. If the engagement involves recurring services, describe what that looks like in practice.
Payment terms
Specify the fee structure (fixed price, hourly, milestone-based), when invoices are to be submitted, and your payment turnaround. Include any expense reimbursement arrangements and how those are approved and processed. If you are engaging on a retainer, set out what that covers and what falls outside it.
Who owns the IP in a contractor agreement?
Under Australian copyright law, the person who creates a work owns it, not the person who paid for it. That default rule applies to contractors. If a developer builds your platform, a designer creates your brand assets, or a copywriter writes your website, they own that work unless your agreement says otherwise.
An IP assignment clause transfers ownership from the contractor to your business. Without one, you may be able to argue for an implied licence to use the work in the way it was intended, but that licence is unlikely to cover sub-licensing, adapting the work, or using it as part of a business sale or capital raise.
A few things to watch in the drafting. First, the assignment should cover work created during the engagement, not just work formally delivered. Second, contractors often bring pre-existing tools, code libraries, or materials into the project. Those do not get assigned, but your agreement should give you a licence to use them to the extent they are embedded in the deliverables. Third, if the contractor is a company rather than an individual, make sure the assignment clause binds the entity.
Confidentiality
Contractors will often have access to sensitive business information. A confidentiality clause defines what information is confidential, restricts how it can be used, and survives termination of the agreement. This is especially important where the contractor may work with your competitors.
Termination
Include provisions for how the engagement ends, both with and without cause. Specify notice periods, what happens to work in progress, and any post-termination obligations. For longer engagements, consider including a termination for convenience right so you are not locked in indefinitely.
Dispute resolution
Most contractor disputes do not go to court. They get resolved (or not) through emails, uncomfortable phone calls, and eventually someone walking away. A dispute resolution clause gives that process some structure.
The standard approach is tiered: the parties first try to resolve the issue directly, then move to mediation if direct negotiation fails, and only then to litigation or arbitration. The value of this is not that it forces anyone to mediate, it is that it creates a cooling-off period before either party does something that makes resolution harder. It also tells both sides what the process looks like before a dispute arises, which tends to make people more reasonable when one does.
For most contractor engagements, a simple two-stage clause (negotiation, then mediation) is enough. Arbitration makes sense for higher-value or more complex arrangements where you want a binding private outcome without going to court.
Liability and indemnity
These clauses define who is responsible for what if something goes wrong. A well-drafted limitation of liability clause caps your exposure. An indemnity clause allocates responsibility if the contractor's work causes loss to a third party. Both need to be carefully calibrated to the nature of the engagement.
Types of contractor agreements
The type of agreement you need depends on the structure of the engagement. For a defined project with specific deliverables and an end date, a project-based agreement works well. For ongoing support, a retainer agreement sets out the recurring scope and fee. Where a primary contractor engages a subcontractor to deliver part of a larger project, a subcontractor agreement governs that relationship separately.
Each has slightly different drafting considerations, particularly around IP, termination, and the flow of obligations from the head contract down.
Common mistakes
The most common issues in contractor agreements are vague scope, missing IP assignment clauses, and confidentiality provisions that are too narrow or that expire too soon. Payment terms that do not address what happens when an invoice is disputed are also a recurring problem.
A related issue is using a generic template without adapting it to the actual engagement. A template that does not reflect how the parties actually work together creates ambiguity, and ambiguity gets resolved in disputes, not before them.
Process matters as much as the document
A well-drafted agreement does not help much if it is signed after work has already started. Get the agreement executed before the contractor begins. If something goes wrong in the first week, you want a signed contract, not an email chain.
For repeat engagements with the same contractor, consider keeping the main agreement in place and using a short statement of work for each project. The statement of work captures the specific deliverables, timeline, and fee for that engagement, while the main agreement handles the legal framework. This means you are not redrafting from scratch each time, and both parties know what governs the relationship.
Review the agreement if the engagement changes significantly. A contractor brought on for a defined project who ends up working regular hours on an ongoing basis is a different arrangement, and the original contract may not reflect it accurately. That gap is worth closing before it becomes a classification problem.
This post is general information only and does not constitute legal advice. If you are putting a contractor agreement in place or want to review an existing one, speak to a lawyer at Plumlaw.