Contractor vs Subcontractor: What NZ SMEs Should Check

If you run a small business, the line between a contractor and a subcontractor can get blurry fast. A builder engages a specialist tiler. A marketing agency brings in a freelance designer. An IT consultant outsources part of a project to a developer. The paperwork often looks simple, but the legal risk sits in the details.

Common mistakes include calling someone a contractor when the working relationship looks more like employment, assuming a subcontractor has no direct legal impact on your business, and relying on a short quote or verbal promise instead of a clear written agreement. Those mistakes can lead to payment disputes, liability gaps, insurance problems and messy arguments about who is responsible when work goes wrong.

This guide explains what contractor vs subcontractor means in New Zealand, what business owners should check before they sign, and where SMEs most often get caught. If you are hiring external workers, managing project chains, or passing work down to another provider, this is the point where the contract structure really matters.

Overview

A contractor is usually engaged directly by the client to provide services or complete a defined job. A subcontractor is usually engaged by that contractor to carry out part of the contractor’s scope, rather than being appointed directly by the end client.

The labels matter less than the actual arrangement. Before you classify someone as a contractor, or allow a contractor to subcontract work, you need to check who the legal parties are, who controls the work, who carries liability, and what the written contract actually says.

• Who is contracting with whom, and whether the subcontractor has any direct rights against the client
• Whether the relationship could be treated as employment rather than genuine contracting
• What work can be subcontracted, and whether landlord consent is required first
• Who is responsible for quality, defects, delays, health and safety, and customer complaints
• How payment terms work across the contractor and subcontractor chain
• What insurance, confidentiality, privacy and intellectual property terms apply
• How the arrangement ends, including handover obligations and post-termination restrictions

What Contractor Vs Subcontractor Means For New Zealand Businesses

The practical difference is simple: the contractor is appointed to deliver the agreed result, and the subcontractor is brought in by that contractor to help fulfil it. The legal consequences become important when something goes wrong, or when the real working relationship does not match the label on the document.

Who is the contractor?

A contractor usually has a direct contract with the client. That contractor agrees to deliver services, labour, a project outcome, or a defined package of work for an agreed price.

For example, a construction company may contract directly with a property developer to complete a fit-out. A software consultant may contract directly with a retailer to build an internal system. A digital agency may contract directly with a customer to manage a campaign.

In each case, the contractor is the party the client expects to perform. Even if the contractor uses outside help, the contractor usually remains responsible to the client unless the contract clearly says otherwise.

Who is the subcontractor?

A subcontractor is generally engaged by the main contractor, not by the end client. The subcontractor performs some or all of the work the contractor has promised to deliver.

That might be a plumbing business engaged by a head contractor on a build, a videographer engaged by a marketing agency, or a specialist developer engaged by an IT contractor for one part of a software project.

The subcontractor’s main legal relationship is usually with the contractor. Unless there is a separate direct agreement, the end client may have no contract with the subcontractor at all.

Why the distinction matters

The distinction matters because responsibility does not automatically move down the chain. If your business signs up as the main contractor, you may still be on the hook to the client for defects, missed deadlines, poor conduct, data issues, or IP problems caused by your subcontractor.

This is where founders often get caught. They assume that if a subcontractor caused the issue, the client must deal with the subcontractor directly. Usually, that is not how it works unless the contract structure was designed that way from the start.

Contractor or employee?

The other major issue is misclassification. Calling someone an independent contractor does not guarantee they are one at law. In New Zealand, the real nature of the relationship matters.

If you control when, where and how a person works, require personal service, fold them into your team like an employee, and they are economically dependent on your business, there is a real risk the arrangement could be challenged as employment rather than contracting.

That matters before you hire your first worker and before you classify someone as a contractor. A written agreement helps, but the day to day reality carries a lot of weight.

Common business scenarios

SMEs run into contractor vs subcontractor issues in all sorts of settings, including:

• Construction and trade businesses using specialist subcontractors on site
• Agencies outsourcing creative, technical or delivery work
• Consultants engaging other specialists to complete part of a client brief
• Ecommerce and product businesses outsourcing warehousing, fulfilment or tech projects
• Professional service firms bringing in short-term experts under their own client contract

Each setup needs its own contract logic. A simple template copied from another job may not deal properly with liability, deliverables, confidentiality, or the right to subcontract.

Legal Issues To Check Before You Sign

Before you sign, make sure the paper trail matches how the work will actually happen. The main legal risk is not the title of the agreement, it is the gap between expectations and what the contract says about control, responsibility and performance.

1. The contract chain

Start with the chain of contracts. You need to know whether the end client contracts with the main contractor only, or whether the subcontractor also has direct obligations or rights.

This affects who can sue whom, who can withhold payment, and who must fix defective work. It also affects whether a subcontractor can rely on terms in the head contract, or whether those terms need to be repeated in the subcontract.

Before you accept the provider's standard terms, check:

• who the legal parties are
• whether subcontracting is allowed
• whether client consent is required before work is passed on
• whether the subcontract must mirror obligations in the head contract
• whether the contractor remains fully liable for subcontracted work

2. Scope of work and deliverables

Unclear scope is one of the biggest drivers of disputes. If you are the contractor, your agreement with the client should say exactly what you are delivering, by when, and to what standard. If you are engaging a subcontractor, your subcontract should align with those obligations.

Problems arise when the contractor promises more to the client than the subcontractor has agreed to provide. That creates a liability gap. Your business may owe the client a result that your subcontractor never committed to deliver.

A good agreement should clearly set out:

• the services or works included
• anything excluded from the scope
• timelines, milestones and dependencies
• acceptance criteria or sign-off process
• who supplies materials, information, equipment or access
• what happens if the scope changes

3. Payment terms and flow-down risk

Payment disputes often sit in the space between the head contract and the subcontract. A client pays late. The contractor has no cash flow. The subcontractor still expects payment. Or the subcontractor invoices for work the client says was never approved.

Your documents should deal with:

• pricing model, such as fixed fee, hourly rate or stage payments
• when invoices can be issued
• what supporting records are required
• whether payment depends on client approval or client payment
• retentions, set-off rights or disputed amount procedures
• what happens if the project is paused or terminated early

These terms can be especially important in project-based industries such as construction, fit-out, events, software and creative services. Businesses should also speak with an accountant or tax adviser about tax treatment and invoicing practices.

4. Liability for defects, delays and third party claims

If your customer suffers loss, they usually look first to the party they contracted with. If that is your business, you need a clear right to recover from the subcontractor where the subcontractor caused the problem.

Check whether the contract covers:

• who is responsible for rework and defect rectification
• delay consequences and extension of time rights
• indemnities for negligence, property damage or third party claims
• caps on liability and any carve-outs
• exclusion of indirect or consequential loss
• time limits for claims

Liability clauses should be read carefully before you rely on a verbal promise that “we always sort issues out if they come up”. If the written contract is silent, your position may be much weaker than you expect.

5. Health and safety responsibilities

In New Zealand, health and safety duties can overlap across different parties on the same job. If you are engaging contractors and subcontractors, you need to think beyond the contract label and focus on who controls the work, the workplace and the risks.

A contract should support practical systems around inductions, site rules, incident reporting, required competencies and coordination with other providers. This is especially important where multiple businesses operate on one site or where specialist high-risk work is involved.

6. Insurance

Insurance is often assumed rather than checked. That is risky. A contractor may think the subcontractor is covered under a project policy. The subcontractor may think public liability is enough. The client may expect professional indemnity cover for advice-based services.

Before you sign, confirm:

• what insurances each party must hold
• minimum cover levels
• whether proof of currency is required
• whether subcontractors must hold the same or similar cover
• who bears uninsured losses if a policy does not respond

7. Confidentiality, privacy and intellectual property

These issues matter well beyond the tech sector. A subcontractor may see pricing, customer lists, designs, software code, internal systems, business plans or personal information. If nothing is documented, your business may have limited protection if that material is misused.

Where relevant, the contract should deal with:

• confidential information and permitted use
• privacy obligations and a privacy notice where personal information is handled
• who owns new intellectual property created during the job
• whether existing materials are licensed or assigned
• return or deletion of business information at the end of the work

If your subcontractor is producing content, software, plans, designs or other custom material, ownership should be stated clearly. Do not assume payment automatically gives your business all IP rights.

8. Restraints, non-solicitation and direct dealing

Contractors often worry that a subcontractor will approach the client directly, poach staff, or use the engagement to cut them out of future work. Those concerns need to be addressed carefully in the contract.

Restrictions should be reasonable and tied to a legitimate business interest. Clauses that are too broad may be harder to enforce. The practical answer is usually a focused non-solicitation or non-circumvention clause with sensible time and scope limits.

9. Termination and handover

When a project relationship ends, the business issues become very practical very quickly. Who keeps working during a notice period? Who hands over files? Who returns materials? What happens to incomplete work?

Your agreement should cover termination for convenience, termination for breach, what fees remain payable, and what assistance is required on exit. This is particularly important where the subcontractor has access to client systems, customer data or project-critical know-how.

Common Mistakes With Contractor Vs Subcontractor

The most common mistakes happen when businesses move too quickly and rely on labels instead of structure. A short form quote, a basic purchase order or a verbal arrangement can leave major gaps once money, deadlines and customer expectations are on the line.

Treating the label as the legal answer

Calling someone a contractor or subcontractor does not settle the issue. If the facts suggest an employment relationship, or if the subcontractor is effectively acting as your business in front of the client, the real arrangement matters more than the heading on the PDF.

Using mismatched contracts

A frequent problem is where the client contract promises one thing, but the subcontract says another. For example, the head contract may include strict delivery dates, broad warranties and IP assignment, while the subcontract is silent on those points.

That leaves the contractor carrying obligations it cannot pass down. Before you sign a contract with the client, make sure your subcontractor agreement can support what you are promising.

Allowing subcontracting without controls

Some businesses allow a contractor to outsource freely without any approval step. That can create quality, confidentiality and safety issues, especially where the end client expects a named provider or specialist expertise.

If subcontracting is allowed, the contract should say whether consent is needed, whether it can be withheld, and whether the contractor remains fully responsible for subcontractor performance.

Forgetting about client-facing conduct

A subcontractor may be the person the client actually sees on site or in meetings. If the subcontractor behaves poorly, makes unauthorised promises, or gives misleading statements about timing or scope, your business may wear the commercial fallout.

Set expectations around communications, branding, authority levels and who can approve changes. This also helps reduce Fair Trading Act risk if representations are being made to customers.

Ignoring privacy and data access

Founders often focus on price and delivery, then realise later that a subcontractor had broad access to customer or staff information. If personal information is involved, privacy and data protection obligations should be built into the arrangement from the start.

This matters before you hand over databases, system logins, mailing lists or customer support records. Data access should be limited to what is actually needed for the job.

Relying on insurance assumptions

Another common mistake is assuming someone else’s insurance will pick up the loss. If a subcontractor damages property, causes delay, or gives faulty advice, there can be real uncertainty unless the insurance obligations and liability settings are clearly drafted.

Leaving disputes to “sort out later”

Dispute clauses rarely get attention when everyone is optimistic. But when a project stalls, a payment is withheld or defective work is alleged, the process matters. A simple escalation path can stop a commercial issue from becoming a full-blown relationship breakdown.

FAQs

Is a subcontractor the same as an employee?

No. A subcontractor is usually an independent business engaged by a contractor to perform part of the work. But if the real relationship looks like employment, the label alone will not decide the issue.

Can a contractor use a subcontractor without telling the client?

Only if the contract allows it or the client otherwise agrees. Some contracts prohibit subcontracting, while others allow it with prior written consent. Before you sign, check the clause rather than relying on assumptions.

Who is liable to the client if the subcontractor gets it wrong?

Usually the main contractor, because that is the party with the direct contract with the client. The contractor may then have a separate claim against the subcontractor under the subcontract.

Does a subcontractor need a written agreement?

Yes, in practical terms it should. A written subcontract helps define scope, payment, confidentiality, liability, IP ownership, health and safety expectations, and termination rights. Verbal arrangements create unnecessary risk.

Can a subcontractor deal directly with the client?

They can if the contract structure permits it, but this should be controlled carefully. Direct dealing can blur authority, create payment confusion and weaken the contractor’s position unless the arrangement is clearly documented.

Key Takeaways

• A contractor usually contracts directly with the client, while a subcontractor is usually engaged by the contractor to perform part of that work.
• The label is not enough. The real legal position depends on the actual working relationship, the contract chain and the day to day facts.
• Before you classify someone as a contractor, check whether the arrangement could instead look like employment.
• Before you sign, make sure scope, payment terms, liability, insurance, health and safety, confidentiality, privacy and intellectual property are clearly covered.
• If you are the main contractor, you will often remain responsible to the client even when the issue was caused by a subcontractor.
• Your subcontract should align with your client contract so you are not left carrying obligations you cannot pass down.
• Written agreements and practical controls are the best way to avoid disputes, responsibility gaps and expensive misunderstandings.

If you want help with contractor agreements, subcontractor terms, misclassification risk, or liability clauses, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.