Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
- Overview
FAQs
- Do I always need a written subcontract if I already have a good relationship with the contractor?
- Should my subcontract copy every clause from the head contract?
- Can I make the subcontractor responsible for all client claims?
- What if the client contract changes after I sign the subcontract?
- Does a contractor agreement protect me if the person is really working like an employee?
- Key Takeaways
If your business delivers work through subcontractors, the biggest risk is often not the subcontractor agreement on its own. It is the gap between that agreement and the head contract you have already signed with your client. That gap is where margins disappear, uninsured liabilities show up, and deadlines become impossible to manage. Common mistakes include passing down too few obligations, accepting broad client promises from subcontractors that do not match the head contract, and treating a contractor relationship like an employment arrangement without checking how the arrangement works in practice.
A proper sub-contractor agreement and head contract review helps you spot those issues before you sign a contract, before you classify someone as a contractor, and before you rely on a verbal promise about timing, scope, or responsibility. For New Zealand businesses, that review is not just about legal wording. It is about making sure the person doing the work can actually help you meet the promises you have made upstream, while protecting your business if something goes wrong.
Overview
A subcontracting arrangement only works when the downstream contract supports the promises in the upstream contract. If the two documents do not line up, your business can end up responsible to the client for obligations your subcontractor never agreed to carry.
The review should focus on risk allocation, operational fit, and whether the contractor relationship reflects how the work will really be done.
- Match the scope of work in the subcontract to the deliverables, specifications, and service standards in the head contract
- Check deadlines, milestones, reporting duties, and acceptance processes in both contracts
- Review who carries liability for defects, delays, rework, IP issues, privacy issues, and third party claims
- Confirm indemnities, limitations of liability, and exclusions are commercially sensible and back to back where needed
- Make sure payment terms let you manage cash flow and deal with client non-payment, variations, and disputed invoices
- Check insurance obligations, health and safety responsibilities, and compliance with site or customer policies
- Review confidentiality, intellectual property ownership, and use of client information
- Test whether the subcontractor arrangement could look more like employment in practice
- Confirm termination rights, step-in rights, and what happens if the head contract ends early
- Remove any reliance on side conversations that are not reflected in the written terms
What Sub-contractor Agreement and Head Contract Review Means For New Zealand Businesses
A sub-contractor agreement and head contract review means checking whether your downstream contractor document properly supports the obligations your business owes under the client contract. It is less about reading each contract in isolation, and more about seeing how they work together in the real job.
This matters for construction businesses, agencies, IT providers, trades, logistics operators, event businesses, and service companies that scale by using outside specialists. It also matters for startups that use contractors because they do not yet want to hire employees. Before you sign, the practical question is simple: if the subcontractor fails, delays, or walks away, what exposure does your business still carry under the head contract?
Why the head contract comes first
The head contract is the promise your business makes to the client. It usually sets the scope, service levels, acceptance criteria, deadlines, warranty periods, privacy obligations, reporting requirements, and termination rules.
If you engage a subcontractor without checking those terms, the subcontract may leave key obligations out. That can create a one way risk flow, where your client can enforce strict duties against you, but you cannot enforce equivalent duties against the person doing the work.
For example, your client contract might require a 24 hour response time, detailed reporting, and strict confidentiality around customer data. If your subcontract only says the contractor will provide services with reasonable care, that wording may be far too loose for what you have promised.
Back to back obligations, but not blindly
Many businesses hear that subcontract terms should be back to back with the head contract. That idea is useful, but it needs judgment. You often want the subcontractor to carry the obligations that relate to their part of the work, but not every clause should simply be copied down word for word.
Some head contract obligations only make sense at your business level. Others may be too broad to pass on without negotiation. A careful contract review asks:
- Which head contract duties should be flowed down directly to the subcontractor?
- Which obligations should stay with your business because they relate to overall project management or client relationship handling?
- Which clauses need adjustment because the subcontractor only performs part of the services?
- Which client terms are too risky to accept unless the subcontractor also takes responsibility for the same risk?
This is where founders often get caught. They either ignore the head contract and use a generic contractor template, or they copy the client contract into the subcontract without checking whether it actually fits the commercial arrangement.
Contractor classification still matters
A strong written agreement helps, but New Zealand businesses should also think about whether the arrangement genuinely looks like subcontracting in practice. Before you classify someone as a contractor, look at the real working relationship, including:
- Who controls how, when, and where the work is done
- Whether the person can work for others
- Whether they invoice for services and manage their own tax position
- Whether they can subcontract or delegate
- Whether they use their own tools, systems, or staff
- Whether they are integrated into your business in a way that resembles an employee role
If the relationship functions more like employment, a contractor agreement alone may not solve the issue. That can affect risk allocation, leave expectations, and disputes about entitlements. It is worth checking early, especially before you hire your first worker or build a team around long term contractor arrangements.
NZ specific pressure points
New Zealand businesses should also look at the local compliance context around the services being delivered. Depending on the work, that may include health and safety duties, privacy obligations, fair trading concerns in client representations, industry standards, or licence style requirements such as certifications, accreditations, or site access approvals.
For example, if your subcontractor deals with customer data, enters client premises, makes marketing claims, or performs regulated technical work, your subcontract should clearly allocate those responsibilities. A head contract may assume your business has all of that covered. If the subcontract does not, the legal and commercial exposure usually sits with you first.
Legal Issues To Check Before You Sign
The best contract review identifies the clauses that affect delivery, cash flow, and liability on day one. Before you sign, focus on the parts that can create immediate exposure if the project changes or the subcontractor underperforms.
Scope of work and service standards
The subcontract should describe the work with enough detail that you can tell whether the subcontractor has met their obligations. Vague wording creates disputes later, especially when the head contract contains tight performance expectations.
Make sure the subcontract lines up with:
- Detailed specifications and technical requirements
- Client service levels or response times
- Deliverable formats and acceptance testing
- Any obligation to fix defects or provide rework
- Any support, maintenance, or post-completion period
If the head contract allows the client to require changes, the subcontract should also explain how variations are approved, priced, and documented.
Timing, milestones, and delay risk
If your client can claim for delay, your subcontract should clearly deal with timing and extensions. This is especially important where the subcontractor is responsible for a critical path item.
Look closely at:
- Start dates, completion dates, and milestone dates
- What counts as a delay event
- Notice requirements for claiming more time
- Whether liquidated damages or other delay costs under the head contract can be passed through
- What happens if the client changes the timetable
A verbal assurance that a contractor can meet the deadline is not enough. If the timing matters to your client contract, it should be reflected in the written subcontract.
Payment mechanics and cash flow
Payment terms should support the way the project actually works. A mismatch can force your business to fund the job for longer than expected.
Questions to review include:
- When invoices can be issued and what supporting information is required
- Whether payment is linked to milestones, acceptance, or completion
- How disputed invoices are handled
- Whether retention, holdbacks, or set-off rights apply
- How variations and out of scope work are priced and approved
- Whether your obligations to pay are affected by client payment timing
Pay when paid wording can be sensitive and may not always solve the commercial problem you think it solves. The drafting should be considered carefully, and the broader project risk still needs to be managed.
Liability, indemnities, and limits
This is usually the hardest part of the review, and often the most valuable. If the head contract exposes your business to broad claims, you need to know whether the subcontract provides a realistic way to recover losses caused by the subcontractor.
Check the position on:
- Liability for defective work, negligence, and breach of contract
- Indemnities for third party claims, property damage, or IP infringement
- Caps on liability and whether they are the same in both contracts
- Exclusions for indirect or consequential loss
- Responsibility for client claims that arise from the subcontractor's acts or omissions
- Whether the subcontractor has the financial capacity to stand behind the risk they are accepting
A strong indemnity is less useful if the subcontractor is uninsured or undercapitalised. The review should look at the legal clause and the practical recovery position.
Insurance and health and safety
Insurance requirements should reflect the work and the project environment. The subcontractor may need public liability, professional indemnity, statutory liability, motor vehicle cover, or other project specific insurance.
Health and safety also needs clear allocation. In New Zealand, duties can overlap, especially where more than one business is involved at the same workplace. The contract should set out:
- Site rules and compliance obligations
- Who provides inductions, equipment, and supervision
- Incident reporting requirements
- Responsibility for subcontractor workers and lower tier contractors
- What happens if the client or principal imposes additional site requirements
The main risk is assuming health and safety can be outsourced completely. It cannot. Your contractual arrangement should support active coordination and cooperation.
Intellectual property, confidentiality, and privacy
If the subcontractor creates material for your client, the contract should state who owns it, when ownership transfers, and what rights each party keeps. This issue comes up regularly in software development, design, marketing, consulting, and product work.
Also review:
- Confidentiality obligations owed to your client and your business
- Use of pre-existing materials, templates, code, or know how
- Permissions for subcontractor portfolio use or publicity
- Handling of personal information under the Privacy Act 2020 and any related data protection requirements
- Data security expectations and breach notification processes
If the head contract promises that all work product belongs to the client, your subcontract should not leave ownership with the subcontractor by default.
Termination, suspension, and step-in rights
The subcontract should give your business practical options if the project starts going wrong. A right to terminate is useful, but sometimes you need earlier intervention tools.
Check whether the contract covers:
- Termination for breach, insolvency, or repeated default
- Termination for convenience, if that exists in the head contract
- Suspension rights for non-performance or safety issues
- Step-in rights, where your business can take control of part of the work
- What happens to materials, IP, equipment, and partially completed work on exit
- Whether the subcontract automatically ends if the head contract ends
Without these clauses, you may still owe the client a smooth transition while having limited leverage over the subcontractor.
Common Mistakes With Sub-contractor Agreement and Head Contract Review
The most common mistakes happen when businesses treat the subcontract as an admin task instead of a risk management tool. A few shortcuts at the start can create expensive problems later.
Using a generic subcontract template
A template may be a useful starting point, but it rarely captures the actual obligations in the client contract. If your head contract includes unusual standards, reporting duties, security obligations, or acceptance rules, a generic form may miss them entirely.
This is especially risky for founders who move quickly and accept the provider's standard terms from one side while reusing an old contractor agreement on the other.
Failing to review the full head contract
Some businesses only check the pricing and scope pages of the head contract. That misses the clauses that often matter most, including delay liability, indemnities, IP ownership, confidentiality, insurance, and termination rights.
A proper review means reading the schedules, attachments, statements of work, and incorporated policies too. The small print often contains the obligations you need to pass down.
Assuming “independent contractor” wording settles classification
Labelling someone a contractor does not automatically make it so. If your business controls the person like an employee, requires exclusive service, and integrates them deeply into the team, the written label may carry less weight than the real facts.
This is where businesses can get caught when they want flexibility but operate the arrangement like a standard staff role.
Leaving variations to email chains
Project changes often happen quickly. The problem is that scope creep, extra cost, and deadline changes become hard to prove if the contract does not require written approval and a clear variation process.
Before you spend money on setup, before you commit additional resources, and before you rely on a verbal promise from the client or subcontractor, make sure the change process is documented.
Ignoring practical enforcement issues
Even well drafted clauses have limits if the subcontractor has no insurance, no assets, or no realistic ability to absorb a claim. Legal drafting should be paired with commercial due diligence.
That might include checking identity, business structure, trading history, references, relevant licences or certifications, and evidence of current insurance.
Not aligning termination consequences
If the head contract ends suddenly, your business needs to know whether you can stop work under the subcontract, recover client property, and avoid ongoing payment obligations. Businesses often forget to connect these exit clauses across both agreements.
The result can be a messy situation where the client relationship ends but the subcontract still technically continues.
FAQs
Do I always need a written subcontract if I already have a good relationship with the contractor?
Yes. A written subcontract helps record the scope, timing, liability, payment, confidentiality, IP, and termination terms. Good relationships can still break down when deadlines slip, the client changes scope, or payment is disputed.
Should my subcontract copy every clause from the head contract?
No. The goal is alignment, not blind duplication. The subcontract should pass down relevant obligations for the subcontractor's part of the work, while adjusting clauses that only make sense at the head contractor level.
Can I make the subcontractor responsible for all client claims?
Not automatically. The contract can allocate risk, but the wording needs to be clear and commercially realistic. You should also consider insurance, liability caps, and whether the subcontractor can actually meet the exposure they are taking on.
What if the client contract changes after I sign the subcontract?
You should check whether the subcontract lets you flow through approved changes, including scope, timing, pricing, or compliance obligations. If it does not, you may need a formal variation with the subcontractor before the new client commitments can safely be passed down.
Does a contractor agreement protect me if the person is really working like an employee?
Not necessarily. New Zealand businesses should look at the real nature of the relationship, not just the label in the contract. Control, integration, exclusivity, and how the work is performed can all matter.
Key Takeaways
- A sub-contractor agreement and head contract review is about making sure your downstream contract supports the promises your business has already made upstream
- The key areas to align are scope, service levels, timing, payment, liability, indemnities, insurance, confidentiality, privacy, IP, and termination rights
- Back to back drafting can help, but only if the obligations are tailored to the subcontractor's actual role in the project
- Contractor classification should be checked in practice, not just described in the contract
- Written variation processes, clear risk allocation, and workable exit rights can prevent expensive disputes later
- Commercial checks matter too, including insurance, capability, and whether the subcontractor can realistically stand behind the obligations they accept
If you want help with risk allocation, contractor classification, liability clauses, or termination terms, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.








