What is A Contractor Agreement? (2026 Updated)

If you’re hiring a contractor (or you’re the one being hired), it’s easy to think a quick email thread and an invoice will do the job.

But when a deadline slips, the scope grows, or payment gets delayed, you’ll quickly wish you had something clearer to fall back on.

This (2026 updated) guide explains what a contractor agreement is in New Zealand, why it matters, what to include, and the common mistakes we see when businesses try to “keep it simple” without protecting themselves from day one.

What Is A Contractor Agreement (And Why Do You Need One)?

A contractor agreement is a written contract between a business and an independent contractor that sets out the rules for the working relationship.

In plain terms, it answers questions like:

• What exactly is the contractor delivering?
• When do they need to deliver it?
• How much will they be paid (and when)?
• Who owns the work product (like designs, code, content, photos, or customer lists)?
• What happens if something goes wrong?

Even when you have a good relationship, a contractor agreement is still worth it because it gives both sides clarity. It can also help you avoid expensive disputes, protect your business IP, and reduce the risk of “employee vs contractor” confusion later on.

For many NZ businesses, contractor agreements sit alongside other core documents, like an Employment Contract (for employees) and a Service Agreement (for broader service-based engagements).

Contractor Agreement Vs Service Agreement: Are They The Same?

They’re closely related, and people often use the terms interchangeably.

Typically:

• A contractor agreement focuses on engaging an individual or contractor business to perform work as an independent contractor.
• A service agreement can be broader, and may cover an ongoing service provider arrangement (including deliverables, SLAs, and support terms).

Either way, the key is that the contract reflects what’s actually happening in practice, not just what you call it.

Contractor Vs Employee: Why Classification Matters In NZ

One of the biggest legal risks for businesses is treating someone like a contractor when they’re really an employee.

In New Zealand, labels aren’t everything. The courts and authorities look at the real nature of the relationship. That means if your “contractor” is working like an employee, you could face issues around:

• holiday pay and leave entitlements
• PAYE and tax obligations
• minimum employment rights
• unjustified dismissal processes (if you end the relationship improperly)

A well-drafted contractor agreement can help show the intended relationship, but it can’t “contract out” of employment law if the day-to-day reality points to employment.

Common Signs Someone Might Be An Employee (Even If You Call Them A Contractor)

There isn’t one single test, but these are common red flags:

• You set their hours and control how they do the work (not just what the result should be).
• They’re integrated into your team like staff (company email, reporting lines, approvals, uniforms).
• They work only (or mostly) for you, long-term, and can’t delegate the work to someone else.
• You supply all tools/equipment and cover expenses the way an employer typically would.

If you’re not sure, it’s worth getting advice early. Getting it wrong can be far more costly than putting the right paperwork in place upfront.

What Should A Contractor Agreement Include?

A good contractor agreement is practical and tailored. It doesn’t just list legal terms - it sets expectations so the relationship runs smoothly.

While every business is different, most contractor agreements in NZ should cover the following.

1. Parties And Relationship

This section confirms:

• who the parties are (including correct legal names)
• that the contractor is an independent contractor (not an employee, partner, or agent)
• the contractor is responsible for their own tax and insurance (where relevant)

It’s also common to include a “no authority to bind” clause so the contractor can’t enter into agreements on your behalf unless you’ve specifically authorised it.

2. Scope Of Work (Deliverables And How You’ll Work Together)

This is where most disputes start - not because people are unreasonable, but because “what we agreed” wasn’t written down clearly.

Your agreement should spell out:

• the services to be provided
• what success looks like (deliverables, formats, milestones)
• deadlines and dependencies
• who provides inputs (e.g. content, access to systems, product samples)
• the process for changes to scope (especially important if your project evolves)

If you’re working in stages, it can be smart to attach a scope of work (SOW) as a schedule, and update it as the project changes.

3. Fees, Invoicing, And Payment Terms

A contractor agreement should be crystal clear on money, including:

• whether pricing is fixed, hourly, daily, or milestone-based
• when invoices can be issued
• payment due dates (e.g. 7 days, 14 days, or end of month)
• whether GST applies
• what happens if there’s a dispute about an invoice

It’s also worth thinking about how you’ll handle additional work. If a contractor keeps doing “quick extras” without a clear approval process, costs can balloon fast.

4. Intellectual Property (Who Owns The Work?)

If you’re paying someone to create something for your business, you’ll usually want to own it - but you can’t assume that happens automatically.

Your contractor agreement should deal with IP clearly, including:

• who owns new IP created during the engagement (often assigned to the client)
• what pre-existing IP the contractor brings in (and whether you get a licence to use it)
• the difference between “work product” (what you’re paying for) and the contractor’s tools/templates

This is especially important for work like software development, branding, marketing content, photography, product design, and training materials.

If your business needs a more formal IP transfer, an IP Assignment can be used to clearly document ownership.

5. Confidentiality And Sensitive Information

Contractors often get access to information you wouldn’t want shared, such as:

• pricing and margins
• customer lists and CRM data
• business processes and strategy
• supplier terms
• product roadmaps

That’s why contractor agreements usually include confidentiality obligations. Depending on what’s being shared, you might also use a standalone Non-Disclosure Agreement (for example, before you share details with a contractor you haven’t decided to engage yet).

6. Privacy And Handling Personal Information

If your contractor will handle personal information (like customer details, patient/client records, or employee data), your agreement should make it clear what they can and can’t do with that information.

In New Zealand, the Privacy Act 2020 is the key law here. Practically, that means you should think about:

• security and storage (how data is protected)
• use limitations (only using data to provide the services)
• disclosure restrictions (no sharing with third parties unless authorised)
• data breach processes (who tells who, and when)

If you collect personal information through your website or platform, having a Privacy Policy is also part of building trust and setting expectations from day one.

7. Warranties, Liability, And Insurance

Most businesses want some comfort that the contractor will do the work properly, and that there are consequences if they don’t.

This section commonly covers:

• minimum standards (reasonable care and skill, compliance with law)
• rectification obligations (fixing defects in a set timeframe)
• limits on liability (where appropriate)
• indemnities (for example, if the contractor’s work infringes someone else’s IP)
• insurance requirements (professional indemnity, public liability, etc.)

How strong these clauses should be depends on your risk profile and bargaining power. If you’re engaging contractors for safety-critical work, you’ll also want to align these terms with your health and safety processes.

8. Term, Termination, And What Happens At The End

Your contractor agreement should set out:

• when the agreement starts and ends (project-based vs ongoing)
• termination rights (for convenience vs for breach)
• notice periods
• handover obligations (returning documents, transferring access, final deliverables)
• final payment and how disputes are handled

This is the “break glass in case of emergency” part of the agreement. You hope you won’t need it - but when you do, you’ll be glad it’s there.

Common Mistakes Businesses Make With Contractor Agreements

Most contractor problems aren’t caused by bad intent. They happen because people are busy, excited to get started, and trying to avoid paperwork.

Here are some common mistakes we see (and how to avoid them).

Using A One-Size-Fits-All Template

Generic templates often miss the things that matter most to your business: IP ownership, privacy, realistic deliverables, and workable termination rights.

They can also create confusion by including clauses that don’t match how you actually work (which can backfire if there’s a dispute).

Being Vague About Scope

If the scope is just “marketing support” or “website development”, you’re leaving room for disagreement later.

Instead, get specific. If you can list it, measure it, or attach it as a schedule, do it.

Not Dealing With IP Early

This is a big one.

For example, imagine you hire a contractor to build your eCommerce site, then later you want to switch developers. If the agreement doesn’t clearly assign IP to your business, you might struggle to access or reuse key assets.

Assuming Contractors Can Do Anything With Customer Data

If you hand a contractor a spreadsheet of customers or give them access to your CRM, you should be clear about limits and security expectations.

That’s not just best practice - it’s part of taking reasonable steps under privacy law.

Mixing Contractor And Employee Arrangements

Sometimes businesses use contractors for roles that look and feel like employment (like ongoing admin, full-time hours, fixed schedules, reporting to a manager).

If that’s what you need, you might be better off putting an employee arrangement in place (with the right processes and documents) rather than trying to “contractor-ise” the role.

Do You Need A Contractor Agreement For Every Contractor?

In practice, you don’t always need a long, complex contract for every engagement - but you do need clear terms.

As a general rule, the more risk involved, the more important it is to have a proper written contractor agreement.

It’s Especially Important If:

• the contractor is creating something valuable (software, designs, content, branding)
• the contractor will access sensitive information or personal data
• the project is high-value or time-critical
• you’re engaging the contractor ongoing, not just for a one-off job
• you’re relying on the contractor to represent your business to customers

If you’re engaging multiple contractors regularly (for example, designers, developers, marketers, delivery drivers, or subcontracted trades), it’s often worth standardising your process with a contractor agreement that you can reuse and tailor as needed.

And if the arrangement is more complex - for example, you’re hiring contractors as part of a larger resourcing model - it may also be worth checking whether a dedicated Sub-Contractor Agreement is more appropriate.

Key Takeaways

• A contractor agreement is a written contract that sets out the terms of engagement for an independent contractor, including scope, payment, timelines, and responsibilities.
• In New Zealand, calling someone a “contractor” doesn’t automatically make them a contractor - classification depends on the real working relationship, not just the label.
• A strong contractor agreement should cover deliverables, fees, IP ownership, confidentiality, privacy obligations, liability, and termination, so both sides know where they stand.
• Intellectual property is a common pain point, so it’s important to clearly document whether work product is assigned to your business and how pre-existing contractor IP is handled.
• If contractors handle personal information, your agreement should align with the Privacy Act 2020 and set clear expectations around security, permitted use, and data breaches.
• Templates can be risky if they don’t reflect your actual arrangement, so it’s worth getting a contractor agreement tailored to your business from the start.

If you’d like help drafting or reviewing a contractor agreement, or you’re unsure whether your working arrangement is really “contractor” or “employee”, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.