Contractor or Subcontractor? Legal Differences for NZ Businesses

If you engage people on projects, the line between a contractor and a subcontractor matters more than many business owners realise. A common problem is assuming the label in your agreement settles everything, using a head contract that says nothing useful about who can subcontract work, or treating payment and control arrangements casually because the job feels short term. Those mistakes can create disputes about who is responsible for delays, defective work, health and safety duties, insurance gaps, or even whether someone has really been engaged as an independent contractor at all.

This guide answers the practical questions New Zealand businesses usually ask before they sign. It explains what contractor vs subcontractor means, when the distinction changes your legal risk, what to include in your contracts, and where founders often get caught when they rely on verbal arrangements or recycled templates.

Overview

A contractor usually contracts directly with the client or principal to deliver agreed services or works. A subcontractor is engaged by that contractor to perform part of those obligations, which means the subcontractor often has no direct contract with the end client unless separate documents say otherwise.

• who the legal customer is, and who is directly responsible for performance
• whether the main contract allows subcontracting or requires consent
• how payment flows, including timing, set-off rights, and what happens if the client does not pay
• which party carries liability for defects, delays, health and safety, and damage
• who owns intellectual property, plans, designs, reports, and other deliverables
• what insurance each party must hold and maintain
• whether the relationship could look more like employment than genuine contracting
• how disputes, variations, and termination rights will be handled before work begins

What Contractor Vs Subcontractor Means For New Zealand Businesses

The key difference is who sits in contract with whom, and that difference affects responsibility, risk, and control from day one.

In a straightforward contractor arrangement, your business hires an independent contractor directly. You agree the scope, price, timing, service levels, and other commercial terms with that person or company. If the work goes wrong, your business usually looks to the contractor under that agreement.

In a subcontractor arrangement, there is an extra layer. Your business may hire a main contractor, and that contractor may then engage one or more subcontractors to complete parts of the work. Alternatively, your business may itself be the contractor and bring in subcontractors to help meet its obligations to a client.

Why the distinction matters in practice

It matters because legal responsibility does not always follow the person doing the work on site. If you are the client, your claim is usually against the contractor you signed with, not automatically the subcontractor who carried out the task. If you are the contractor, your client will usually expect you to remain responsible for your subcontractors' work unless the contract says otherwise.

This is where SMEs often get caught. A founder may believe a subcontractor relationship shifts all risk down the chain. Often it does not. The head contractor can still be liable to the client for delays, rework, non-compliance, or poor workmanship, then has to recover losses separately from the subcontractor under the subcontract.

Contractor does not mean employee, but labels are not enough

Calling someone a contractor or subcontractor does not automatically make them one. New Zealand law looks at the real nature of the relationship. If, before you classify someone as a contractor, the arrangement gives you a high level of control over their hours, methods, tools, exclusivity, and integration into your business, there may be risk that the relationship looks more like employment.

This question can arise whether you hire someone directly as a contractor or bring them in as a subcontractor under a larger project. The written terms matter, but the day to day reality matters too.

Points that often influence the analysis include:

• how much control you exercise over when, where, and how the work is done
• whether the worker can subcontract or send a replacement
• whether they supply their own tools, equipment, and insurance
• whether they work for multiple clients or are tied mainly to your business
• whether they invoice for completed services rather than receiving wages
• whether they carry business risk, such as having to fix defective work at their own cost

If there is any doubt, get advice before you sign. Misclassification issues can become expensive quickly.

Common business scenarios

Construction is the clearest example. A developer may engage a building company as the main contractor. That building company then subcontracts plumbing, electrical, roofing, or joinery work. The developer's main legal relationship is with the building company. The building company then manages separate subcontracts below it.

The same logic applies outside construction. A marketing agency may win a client project and subcontract design, copywriting, or web development. An IT provider may contract with a customer and subcontract cloud migration work. A manufacturer may accept a supply contract and subcontract specialist fabrication. In each case, the contract chain changes who owes what to whom.

When direct rights need special drafting

If you want direct rights against a subcontractor, you usually need documents that clearly create them. Otherwise, you may have to rely on your claim against the main contractor only. This can matter where the subcontractor handles sensitive data, creates valuable IP, attends your site, or performs a critical compliance function.

Before you rely on a verbal promise that everyone is "on the same page", check whether your contract structure actually gives your business enforceable rights where you need them.

Legal Issues To Check Before You Sign

The safest approach is to treat contractor and subcontractor arrangements as risk allocation documents, not just pricing documents.

1. Can the contractor subcontract at all?

Your first check is the main contract. Some contracts allow subcontracting freely. Others require written consent, permit subcontracting only for specific tasks, or make the contractor fully responsible for every subcontractor it appoints.

Before you sign a contract, confirm:

• whether subcontracting is allowed
• whether the client's prior written consent is required
• whether there are conditions on who can be appointed
• whether the contractor remains fully liable for the subcontractor's work
• whether certain obligations must be flowed down into the subcontract

If the head contract is silent, do not assume you can pass work down without consequences.

2. Scope of work and deliverables

Most disputes start because the scope is vague. If you are a contractor using a subcontractor, the subcontract should state exactly what work is included, what standards apply, what deliverables are due, and what sits outside scope.

The drafting should also align with the head contract. If your client expects specific milestones, reporting, testing, specifications, or sign-off procedures, your subcontract should mirror those requirements where relevant. Otherwise, the contractor may owe the client more than the subcontractor owes the contractor.

3. Payment terms and pay-when-paid risk

Payment terms need careful wording because cash flow pressure often sits with the middle party.

Questions to settle before you accept the provider's standard terms include:

• when invoices can be issued
• what supporting documents are required
• whether payment depends on milestone completion or time worked
• whether there are retention amounts, set-offs, or back charges
• what happens if the client disputes part of the work
• what happens if the client pays late or not at all

Some businesses assume they can simply say a subcontractor gets paid when the client pays. That can be risky, unclear, or commercially unfair depending on the drafting and context. Payment clauses should be tailored carefully, especially in project work. Tax treatment also needs separate advice from your accountant or tax adviser.

4. Liability for defects, delay, and third party loss

If a subcontractor causes delay or defective work, the contractor may still be liable upstream to the client. That means your contracts should spell out who fixes defects, who bears rectification costs, and whether the contractor can recover losses from the subcontractor.

Look closely at:

• service levels and performance standards
• defect correction periods
• liquidated damages or delay consequences in the head contract
• indemnities for property damage, IP infringement, confidentiality breaches, or regulatory non-compliance
• liability clauses and any excluded losses

Many SMEs only focus on the contract price. The bigger issue is often what sits behind a failure to perform.

5. Health and safety duties

Health and safety cannot be left to assumption, especially where multiple businesses work together at one site. New Zealand businesses should clearly document who manages site induction, supervision, hazards, incident reporting, training, and compliance with site rules.

If you are the contractor engaging subcontractors, your practical coordination duties may be significant even where the subcontractor controls its own workers. If you are the client, you still need clarity on who is responsible for what on your premises or project.

6. Insurance

Insurance should match the actual risk, not just a template list copied from another deal.

Depending on the work, you may need to specify:

• public liability insurance
• professional indemnity insurance
• contract works insurance
• vehicle or equipment cover
• cyber cover where data or systems are involved

Your agreement should state minimum cover levels where appropriate, evidence requirements, and who bears uninsured losses if a policy does not respond.

7. Intellectual property, confidentiality, and data

If the work includes designs, plans, code, reports, training materials, product specifications, or customer information, ownership and permitted use need to be clear. A contractor may promise a client that the client will own all project outputs, but if the subcontract says something different, the contractor can end up in breach.

Where personal information is handled, privacy obligations also matter. The party collecting, storing, or processing data should know exactly what it can do with that information, how it must protect it, and what happens at the end of the engagement, including any privacy notice requirements.

8. Variations, termination, and dispute process

Project work changes. The contract should say how changes are requested, priced, approved, and documented. If you leave this loose, extra work can quickly become an argument about whether it was included.

Termination rights are equally important. Before you spend money on setup or assign staff to the project, know:

• whether termination is allowed for convenience
• what notice is required
• what happens to work in progress and unpaid invoices
• whether step-in rights apply
• what materials, equipment, and confidential information must be returned

A simple dispute process can also save time, such as requiring senior discussions before formal escalation.

Common Mistakes With Contractor Vs Subcontractor

The most expensive mistakes usually happen when business owners treat the arrangement as informal because they trust the other party or need the work done quickly.

Using one agreement for every job

A recycled template often misses the main point of the deal. A subcontract for labour only is different from a subcontract involving design responsibility, client data, specialist equipment, or safety critical works. Generic wording can leave major gaps around scope, liability, and IP.

Ignoring the head contract

If you are the contractor, your subcontract should line up with what you promised the client. This is called flow down in practice, but the core idea is simple: do not promise your client one thing and ask less of your subcontractor. If the head contract requires certain standards, reporting, warranties, or insurance obligations, the subcontract should reflect that where relevant.

This is where founders often get caught. They sign a polished client contract, then send the subcontractor a short quote acceptance with almost no legal terms.

Relying on labels instead of the real relationship

Some businesses call someone a subcontractor, but then manage them like an employee. They set fixed hours, require personal service, supply all equipment, stop them working elsewhere, and roll them into the internal team. If the practical reality points away from genuine independent contracting, the label may not protect the business.

Leaving payment mechanics unclear

Disputes about payment often come down to timing and evidence. If there is no clear invoicing process, no milestone approval method, and no agreed response to defects or partial completion, a cash flow problem can become a legal dispute fast.

Clear drafting matters most where there are:

• multiple stages of work
• materials supplied by one party and labour by another
• reliance on third party approvals or inspections
• holdbacks or retention amounts
• possible offsets for rework or delay costs

Forgetting insurance and risk transfer

Many businesses assume each party's normal insurance will sort everything out. That is not always true. Policies may exclude parts of the work, impose conditions, or leave gaps between property damage, professional advice, and cyber incidents. The contract should say who carries which risk if something goes wrong.

Not documenting changes

Verbal changes create confusion over price and scope. A client asks for extra work, the contractor tells the subcontractor to get on with it, and nobody records the revised cost or timing. Weeks later, everyone remembers the conversation differently.

A short written variation procedure is one of the easiest ways to reduce dispute risk.

Missing confidentiality, restraint, or non-solicitation terms where they matter

Not every contract needs these clauses, but some do. If the subcontractor will access your customer list, pricing, know-how, or key project contacts, think about what protections are justified. The drafting should be reasonable and relevant to the relationship.

Assuming consumer style protections do not matter in business services

Even in business to business arrangements, service quality and marketing claims still matter. Statements about expertise, delivery times, compliance, or outcomes should be accurate. Overpromising in proposals or statements of work can create liability issues later, particularly if the written contract does not deal with assumptions and exclusions properly.

FAQs

Is a subcontractor legally different from a contractor?

Yes. A contractor usually contracts directly with the client or principal, while a subcontractor is engaged by that contractor to perform part of the work. The difference mainly affects who owes obligations to whom and who bears project risk under the contract chain.

Can a contractor in New Zealand hire a subcontractor without telling the client?

Sometimes, but only if the main contract allows it. Many agreements require the client's consent or impose conditions on subcontracting. Before you sign, check the head contract rather than assuming subcontracting is permitted.

Can a subcontractor claim payment directly from the end client?

Usually not, unless there is a direct agreement or specific legal basis allowing that claim. In most cases, the subcontractor's contract is with the contractor, so payment rights sit against that contractor.

What if a subcontractor acts more like an employee?

The legal label may not decide the issue. If the real relationship involves high control, personal service, little independence, and integration into the business, there may be a risk the arrangement is closer to employment. Get advice before you classify someone as a contractor if the facts are not clear.

Who is responsible for defective work done by a subcontractor?

As between client and contractor, the contractor is often still responsible under the head contract. The contractor may then have rights against the subcontractor under the subcontract, but only if that document clearly allocates responsibility for defects, rework, and loss.

Key Takeaways

• The difference between a contractor and subcontractor is mainly about contract structure, direct obligations, and who carries risk.
• Labels alone are not enough. The real working relationship can affect whether someone is genuinely an independent contractor.
• Before you sign, check whether subcontracting is permitted and whether the subcontract matches the head contract.
• Scope, payment, liability, health and safety, insurance, privacy, confidentiality, IP ownership, and variation clauses should all be tailored to the actual job.
• Most disputes start with vague scopes, informal instructions, verbal promises, and inconsistent paperwork across the contract chain.
• If you are reviewing or negotiating contractor vs subcontractor and want help with contract drafting, subcontractor terms, risk allocation, and employment classification issues, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.