Subconsultant Agreements for Design Projects in New Zealand

If you bring in a designer, drafter, engineer, specialist consultant or technical adviser to help deliver a client project, a handshake or a short email chain is rarely enough. The problems usually show up later, when the client asks for changes, the subconsultant misses a deadline, or everyone assumes they own the design files. Founders and project leads often make the same mistakes: they accept vague scopes, leave liability terms untouched, or rely on the head contract without making sure the subconsultant is actually bound to the parts that matter.

A well-drafted subconsultant agreement for design projects helps you control those risks before you sign. It sets out who is doing what, when they must do it, what standard they must meet, who owns the intellectual property, and who carries the cost if something goes wrong. For New Zealand businesses, that matters whether you work in architecture, engineering, interiors, digital design, specialist drafting or broader professional services.

This guide explains what a subconsultant agreement should cover, the legal issues to check before you accept the provider's standard terms, and the common traps that catch design businesses when project pressures take over.

Overview

A subconsultant agreement is the contract between the lead consultant and the outside specialist engaged to perform part of a design project. In New Zealand, the agreement needs to do more than confirm fees. It should mirror the right parts of the client contract, allocate risk in a commercially sensible way, and avoid gaps around scope, deliverables, liability and IP ownership.

• Define the services, deliverables, programme and review process clearly.
• Check whether key obligations from the head contract need to flow down to the subconsultant.
• Set payment terms, variations, reimbursable expenses and invoicing timing.
• Deal with intellectual property, moral rights, licences and use of background materials.
• Allocate liability, indemnities, insurance obligations and any caps on exposure.
• Cover confidentiality, privacy, conflicts, health and safety, and professional standards.
• Include workable clauses for delays, defective work, termination rights and dispute resolution.

What Subconsultant Agreement for Design Projects Means For New Zealand Businesses

A subconsultant agreement for design projects is the document that makes your project chain legally workable. If your business has promised services to a client, but another consultant will perform part of that work, you need a contract that lines up those obligations properly.

In practice, this usually applies where a lead consultant engages another business or sole trader for specialist input. That might be a structural engineer supporting an architect, a lighting designer assisting an interior studio, a BIM consultant helping a design team, or a specialist drafter preparing technical documentation. The lead consultant remains responsible to the client under the head contract unless that contract says otherwise. That is why the subconsultant agreement matters so much.

The Agreement Sits Under Your Main Client Contract

The head contract with your client is usually the starting point. If you owe deadlines, design standards, confidentiality obligations, insurance requirements or intellectual property promises to the client, you may need the subconsultant to comply with matching obligations.

This is often called a flow down arrangement. The idea is simple: if you are taking on risk at the top of the project, you do not want a gap lower down.

That does not mean copying every clause from the client contract without thinking. Some client terms may be too broad, unrealistic or commercially unfair for a smaller specialist consultant. The key is to identify the obligations that genuinely need to be passed through and draft them clearly.

Scope Is Usually the First Pressure Point

The biggest source of conflict is often not a dramatic breach. It is a fuzzy scope. A subconsultant may think they are providing concept advice only, while the lead consultant assumes detailed coordination, revisions and attendance at meetings are included in the fee.

Before you sign a contract, the scope should answer basic project questions in plain language:

• What exact services are included?
• What documents, drawings, reports or models must be produced?
• What assumptions apply, such as information to be supplied by others?
• How many revisions or review rounds are included?
• Who signs off deliverables?
• What deadlines, milestones or response times apply?
• What is expressly excluded?

If your project moves in stages, separate the stages. Concept, developed design, documentation, site observation and post-completion support can each carry different timing, fees and risk.

Design Projects Raise Special IP and Reliance Issues

Design work usually creates intellectual property. That may include plans, drawings, models, renderings, specifications, software outputs, presentations or technical methodologies. If ownership and licence terms are not clear, disputes can emerge long after the work is delivered.

The agreement should state whether the lead consultant will own project-specific deliverables, whether the subconsultant keeps ownership but grants a licence, and whether any existing templates or proprietary systems are carved out as background IP. This is especially important where the client expects broad rights to use the completed design.

Another practical issue is reliance. Clients, builders, funders or other consultants may want to rely on the subconsultant's work. If the agreement is silent, the lead consultant may end up making promises it cannot pass through. That needs to be addressed before you rely on a verbal promise that the specialist will “stand behind the work”.

Professional Standards Matter

Many design businesses assume a generic contractor agreement will do the job. Usually it will not. A subconsultant in a design project is often providing professional services, not just labour. That means the contract should deal with standards of care, compliance with laws and codes, professional registrations where relevant, and insurance suitable for the discipline involved.

For example, a drafting subcontract may be different from a professional engineering engagement. Some projects also involve site access, health and safety coordination, data handling or sensitive client information. Those points need tailored wording, not a recycled one-page template.

Legal Issues To Check Before You Sign

The right time to sort out risk is before you sign, not after the first invoice or the first design revision blowout. A subconsultant agreement should be read alongside the head contract, project brief and any proposal documents so the obligations line up.

1. Flow Down Obligations

The main legal question is whether the subconsultant is bound to the parts of your client contract that affect delivery. If your client requires confidentiality, response times, attendance at meetings, insurance levels or particular standards, the subconsultant agreement should either repeat those obligations or attach the relevant head contract terms.

Be careful with blanket incorporation clauses. A line saying the subconsultant is bound by “all terms of the head contract” can create uncertainty if the subconsultant has never seen that contract or if some terms make no sense in the subcontracting context.

A better approach is usually to identify the clauses that apply, such as:

• scope and deliverables
• programme and milestone dates
• confidentiality
• client approvals and review processes
• insurance obligations
• health and safety requirements
• intellectual property commitments
• standards of care and compliance obligations

2. Fees, Variations and Payment Triggers

Payment disputes often come from poor contract drafting, not bad faith. The agreement should state whether the fee is fixed, hourly, stage-based or capped. It should also set out what counts as a variation and how a variation must be approved.

If your client only pays you after approval of a design stage, think carefully before agreeing to pay the subconsultant on a different basis. “Pay when paid” wording can be risky and may not solve the commercial problem if the reason for non-payment is disputed work quality rather than timing. Clear milestone and invoicing clauses usually work better than trying to leave the issue vague.

It also helps to specify:

• when invoices can be issued
• what supporting records are required
• whether expenses must be pre-approved
• what happens if the project is paused
• whether late changes trigger extra fees

3. Intellectual Property and Use Rights

IP drafting should match the way the project will actually be used. If the lead consultant has promised the client ownership or a broad licence to use design outputs, the subconsultant agreement must support that promise.

The agreement should deal with:

• ownership of newly created project materials
• licence rights for the lead consultant and client
• background IP the subconsultant brings to the project
• whether source files, editable files or native files must be handed over
• moral rights consents where appropriate
• limits on reuse for other sites or future stages

These points are especially important if the relationship ends early. Without clear wording, the lead consultant may have paid for work it cannot lawfully adapt or complete through another provider.

4. Liability, Indemnities and Insurance

The main risk is simple: you may be liable to your client for losses caused by the subconsultant, even if the subconsultant's own contract gives you very little recourse. That is where founders often get caught.

Look closely at any clause dealing with:

• caps on liability
• exclusions for indirect or consequential loss
• indemnities for third-party claims
• liability for delay
• liability for defective design or documentation
• liability for infringement of third-party intellectual property rights
• professional indemnity, public liability and other insurance requirements

There is no single “correct” liability position. The right position depends on your industry, the project size, the head contract and the subconsultant's role. But you should always check whether the risk you have accepted from the client is larger than the risk the subconsultant is willing to accept from you.

5. Standard of Care and Compliance

A design subconsultant should usually be required to perform services with reasonable care and skill and in line with applicable professional standards. The contract may also need the subconsultant to comply with project specifications, statutory requirements, codes, and instructions that are properly issued through the project process.

For regulated professionals, registration and practising requirements may also matter. The agreement can require the subconsultant to maintain any relevant qualifications, licences or registrations during the project and notify you of any issue that affects their ability to perform the work.

6. Confidentiality, Privacy and Data Handling

Design projects often involve commercially sensitive information, site data, client plans, security details or personal information. If the subconsultant will access personal information, even incidentally, the Privacy Act 2020 may become relevant to how information is handled, stored and shared.

The agreement should set practical rules around confidentiality and, where relevant, a privacy notice or data handling process:

• who can access project information
• how information may be stored or transmitted
• whether offshore storage or subcontracting is allowed
• when information must be returned or deleted
• how data incidents must be reported

7. Termination, Suspension and Handover

Projects change. Budgets get cut, clients pause work, scopes move, and relationships break down. Your agreement should explain what happens if the arrangement ends early.

Before you accept the provider's standard terms, check whether you can suspend the work, terminate for breach, terminate for convenience, and obtain a proper handover of project materials. A handover clause is often critical in design work because unfinished files, notes and source material may be needed so another consultant can continue the project.

8. Dispute Resolution

Disputes on live projects need a practical pathway, not just a threat. A stepped dispute clause can help preserve working relationships while keeping timeframes moving. It might require senior representatives to meet first, then mediation, before court or arbitration options are considered.

The exact process depends on the project and bargaining position, but silence is rarely helpful when deadlines are tight and multiple parties are involved.

Common Mistakes With Subconsultant Agreement for Design Projects

The most common mistakes are avoidable. They usually happen when businesses move fast, trust the working relationship, or assume the head contract will somehow fill the gaps.

Using a Generic Contractor Template

A standard services agreement may miss design-specific issues like reliance, revision limits, file formats, intellectual property use, and professional indemnity insurance. If the work is specialist design input, the contract needs to reflect that reality.

Leaving the Scope Too Broad

Phrases like “assist with design documentation as required” sound flexible but create arguments later. They do not tell you how much work is included, how quickly the subconsultant must respond, or whether extra rounds of revision are chargeable.

When the scope is unclear, every variation discussion becomes harder. This often leads to strained client relationships because the lead consultant is stuck between the client and the specialist.

Failing to Match the Head Contract

If your client contract says you must meet certain deadlines or provide rights in deliverables, but your subconsultant agreement says nothing similar, you have a gap in the project chain. That gap can leave you exposed even where the subconsultant caused the issue.

This is especially common where the head contract was heavily negotiated, but the subconsultant was engaged quickly on standard terms.

Assuming IP Ownership Is Obvious

Paying for design work does not always mean you automatically own every file and underlying right. New Zealand businesses often discover this when they try to switch consultants, amend designs, or give the client editable files. The contract should make those rights explicit.

Accepting Unlimited Liability Without Realising It

Some subconsultant contracts are silent on liability. Others include very broad indemnities or leave the subconsultant effectively uncapped while the lead consultant's own exposure to the client is much larger. Either way, the commercial risk may be out of step with the project value.

You should compare the exposure under both contracts, not review each agreement in isolation.

Forgetting About Insurance Evidence

It is not enough to require insurance in theory. The agreement should say what cover is required, when it must be maintained, and whether certificates or other evidence need to be provided on request. This matters most for professional indemnity cover and for projects where significant third-party loss could arise from errors.

Relying on Verbal Change Requests

Design projects evolve quickly, and teams often agree changes in meetings or messages. If your contract does not require written terms for approved scope changes, it becomes much harder to resolve fee or timing disputes. A short written variation process can save a lot of friction later.

Ignoring Handover on Exit

When relationships end, the immediate problem is usually practical. Who has the latest files, calculations, mark-ups and correspondence? A strong handover clause helps the project continue and reduces the risk of a deeper dispute.

FAQs

Does a lead consultant need a written subconsultant agreement for every design project?

Not every engagement has the same level of risk, but a written agreement is strongly recommended whenever another consultant is contributing to client-facing deliverables. Even small projects can create disputes about fees, delays, IP ownership and responsibility for errors.

Can a subconsultant just work under the client's contract terms?

Not safely on its own. The subconsultant should have its own contract with the lead consultant. Relevant client obligations can be flowed down, but the subconsultant still needs clear terms about fees, scope, liability, IP and termination.

Who owns the designs created by a subconsultant?

That depends on the contract. Ownership is not always automatic just because the work was paid for. The agreement should clearly state who owns project deliverables, what licences apply, and whether background IP is excluded from transfer.

Should the subconsultant's liability match the lead consultant's liability to the client?

Not always exactly, but the two positions should be compared carefully. If the lead consultant has accepted broad obligations to the client, yet the subconsultant has very limited responsibility back to the lead consultant, the risk allocation may be commercially unsafe.

What happens if the project ends before the subconsultant finishes?

The contract should set out the termination and suspension rules, what fees are payable up to that point, and what materials must be handed over. This is particularly important for design files, drafts, notes and partially completed deliverables needed to continue the project.

Key Takeaways

• A subconsultant agreement for design projects should do more than confirm price. It should clearly allocate scope, timing, IP rights, liability and project responsibilities.
• The agreement should be checked against the head contract so important obligations are properly flowed down to the subconsultant.
• Scope, variations, design revisions, deliverables and approval processes should be drafted in practical detail before you sign.
• Intellectual property, source files, background materials and handover rights are common pressure points in design work and should be addressed expressly.
• Liability caps, indemnities, insurance, confidentiality, privacy and termination rights should be reviewed in light of the actual project risk.
• A tailored written agreement can reduce disputes, protect your client relationship and make it easier to manage changes when the project shifts.

If you want help with scope drafting, intellectual property clauses, liability caps, head contract flow down terms, and contract review, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.