Subcontractor Agreements for Construction Project Managers in New Zealand

If you manage construction projects in New Zealand, a vague subcontractor deal can blow up fast.

The common problems are usually the same: the scope is not pinned down, the payment terms do not match project milestones, and the contract says someone is an independent contractor without dealing properly with control, health and safety, or site obligations. Another frequent issue is relying on the head contract to “cover everything”, even though the subcontractor has never agreed to those terms directly.

A well-drafted subcontractor agreement for construction project manager work should do more than confirm a daily rate. It should spell out who does what, who carries the risk for delays and defects, what happens when the principal changes the job, and how disputes are handled before they disrupt the whole build. If you are about to sign, renew, or issue a subcontract for project management services, this guide explains what the agreement should cover, what New Zealand businesses need to watch for, and the mistakes that often create expensive arguments later.

Overview

A subcontractor agreement for a construction project manager sets the legal and commercial rules for how project management services will be delivered on a building project. It should align with the realities of construction work in New Zealand, including site safety duties, payment timing, programme changes, and the difference between a genuine contractor relationship and something that looks more like employment.

• Define the exact services, deliverables, site responsibilities, and reporting lines.
• Match payment terms to milestones, variations, retentions if any, and invoice approval processes.
• Address health and safety duties, insurance obligations, indemnities, and liability caps.
• Deal clearly with delays, defects, rework, suspension, and termination rights.
• Make sure the contractor classification reflects how the relationship will work in practice.
• Check that the subcontract lines up with the main project contract where necessary.

What Subcontractor Agreement for Construction Project Manager Means For New Zealand Businesses

A subcontractor agreement for construction project manager work is the document that turns a handshake or proposal into enforceable written terms. For New Zealand businesses, it is often the main tool for controlling delivery risk when an external project manager is coordinating trades, programme dates, budgets, procurement, or client reporting.

Construction project managers are commonly engaged in different ways. A head contractor might subcontract project management support on a specific build. A developer might engage a project manager directly for procurement and coordination. A specialist consultancy might send a project manager into a project under a services agreement. The label matters less than the substance. Before you sign, the agreement needs to match what the person or business will actually do on the job.

What work is usually covered?

The agreement should describe the services in plain language, not just use a broad title like “project management services”. In practice, that may include:

• project planning and programme management
• coordination of subcontractors and suppliers
• site meetings, progress reports, and client communication
• procurement support and contract administration
• budget tracking and variation management
• quality monitoring and practical completion processes
• health and safety coordination responsibilities, where applicable

If the role includes authority to issue instructions, approve invoices, sign off on work, or commit the business to costs, the contract should say so expressly. This is where founders often get caught. They assume the project manager can “just handle it”, but there is no clear written authority and no limit on what they can approve.

Why a standard services contract is often not enough

A generic contractor template rarely fits a live construction project. Project management work sits in the middle of programme risk, trade coordination, site access, and client expectations. If the agreement does not deal with those moving parts, you can end up arguing about practical points that should have been settled on day one.

For example, if a subcontractor project manager misses a key coordination deadline, does that make them liable for the knock-on delay costs? Can they rely on information supplied by others? Do they have to attend site daily, or only at scheduled milestones? If the principal changes the scope, how is the project manager’s fee adjusted? A proper subcontractor agreement answers those questions before money is lost.

Contractor or employee?

Calling someone a subcontractor does not automatically make them one. New Zealand law looks at the real nature of the relationship. If you control their hours closely, require exclusive service, provide all tools and systems, and treat them like part of your internal management structure, there is a risk the arrangement could be viewed as employment rather than an independent contractor relationship.

That matters because employment obligations are different from contractor arrangements. Before you classify someone as a contractor, think carefully about:

• whether they can work for other clients
• whether they invoice through their own business entity
• whether they control how they perform the services
• whether they provide their own equipment or systems
• whether they can subcontract or appoint personnel, subject to approval
• how integrated they are into your business operations

If the practical reality points in the other direction, the contract wording alone will not fix it.

How it fits into the wider project documents

The subcontractor agreement should not sit in isolation. A construction project often has a head contract, consultant agreements, purchase orders, site rules, health and safety plans, and programme documents. If the project manager is expected to comply with parts of those documents, the agreement should identify which ones apply and how they are incorporated.

That said, avoid dumping every project document into the subcontract without review. Some obligations might be too broad, inconsistent, or unsuitable for a project management subcontractor. The cleaner approach is to list the specific documents that apply and make sure there is no conflict between them.

Legal Issues To Check Before You Sign

The main legal issues are scope, risk allocation, and practical control of the relationship. Before you sign a contract, you want the document to reflect how the project will actually run, not how someone hopes it will run in the best-case scenario.

Scope of services and deliverables

The scope should set out exactly what the construction project manager will do, what they will not do, and what outputs are expected. If reporting, procurement, or contract administration is part of the role, say that clearly. If they are not responsible for design, cost certification, engineering approval, or direct site supervision, that should be clear too.

Useful drafting points include:

• the project name, site, and stage covered
• specific services and deliverables
• required attendance on site or at meetings
• response times and reporting obligations
• who can give instructions to the subcontractor
• any authority limits for approving cost or time changes
• documents, standards, or methods the subcontractor must follow

Loose scope wording often creates disputes over whether extra tasks are included in the agreed fee.

Fees, invoices, and payment triggers

Payment terms should match the way the work is delivered. A day-rate model can work for short engagements, but milestone or monthly fees may be more practical for longer builds. The agreement should also deal with reimbursable expenses, approval requirements, and when invoices can be disputed.

Before you accept the provider's standard terms, check whether the payment clause covers:

• the fee basis, hourly, daily, milestone, monthly retainer, or fixed price
• when invoices can be issued and what supporting information is required
• payment due dates
• whether there is any right to withhold payment for disputed amounts
• how variations or additional services are approved and priced
• what happens if the project is suspended or terminated early

If the subcontractor’s fees depend on approval from your own client, the contract should say that carefully and fairly. Poorly drafted “pay when paid” style language can create commercial tension and may not solve the cash flow problem you are trying to manage.

Variations and scope changes

Construction projects change constantly. The agreement should say how changes to services are requested, approved, priced, and recorded. Verbal instructions on site are a major source of argument, especially where the project manager later invoices for work the client thought was included.

A sensible clause will cover:

• who can authorise a variation
• whether approval must be in writing
• how urgent work is handled if time does not allow formal paperwork first
• how fee and time impacts are assessed
• when the subcontractor can refuse out-of-scope work

Health and safety duties

Health and safety cannot be treated as a generic boilerplate issue on a construction project. The agreement should identify the project manager’s responsibilities on site, including compliance with site rules, incident reporting, inductions, and cooperation with the main contractor or principal’s safety systems.

The contract should not assume the project manager carries all health and safety risk just because they are coordinating people. A better approach is to define each party’s responsibilities in a way that matches the work and the site arrangements. Before you rely on a verbal promise about “who covers safety”, get it in writing.

Insurance, liability, and indemnities

Insurance and liability clauses decide who carries the cost when something goes wrong. For a construction project manager, the relevant cover may include public liability insurance and professional indemnity insurance, depending on the services provided. The agreement should state what insurance must be maintained, at what level if appropriate, and for how long.

Liability clauses also need close review. Watch for:

• unlimited liability for delay, cost overruns, or third-party claims
• broad indemnities that are not tied to fault or breach
• liability caps that are too low to be meaningful
• exclusions that remove liability for the subcontractor’s most important obligations
• no carve-out for fraud, wilful misconduct, or confidentiality breaches where relevant

The right risk position depends on the project, the bargaining power of the parties, and the nature of the services.

Intellectual property, confidential information, and records

Project managers often prepare reports, programmes, procurement schedules, meeting minutes, and commercial records. The agreement should say who owns those materials and whether the hiring business can continue using them if the engagement ends.

Confidentiality provisions should also cover pricing, client information, subcontractor details, and commercially sensitive project data. If the project manager handles personal information, for example contact details in project records, make sure your processes also line up with privacy and data protection obligations in New Zealand.

Term, suspension, and termination

You need a clear exit path before the project goes off track. The contract should say when the engagement starts, whether it ends on practical completion or another date, and what happens if the project is delayed, paused, or cancelled.

Termination clauses usually need to cover:

• termination for breach, after notice and a chance to fix the problem where appropriate
• termination for insolvency or serious safety failures
• termination for convenience, if one party wants flexibility
• what fees are payable up to termination
• handover of documents, records, and site information
• ongoing obligations after termination, such as confidentiality and payment

Dispute resolution and practical enforcement

A dispute clause should help keep the project moving while issues are sorted out. That usually means a stepped process, such as senior discussion first, then mediation, before formal proceedings if needed. The contract can also require the subcontractor to continue performing undisputed work during a dispute, so long as that is fair and realistic.

The goal is not to create a long legal process. The goal is to give the parties a practical way to deal with arguments over variations, delays, or invoices before the project relationship collapses.

Common Mistakes With Subcontractor Agreement for Construction Project Manager

The most common mistakes are practical, not technical. Businesses often sign quickly, assume the project manager “knows how we work”, and leave the hard points to be sorted out later. That is usually when cost, delay, and responsibility become contested.

Using a one-page scope or quote as the whole agreement

A quote may confirm price and broad services, but it usually does not deal with programme slippage, authority limits, confidentiality, liability, termination, or health and safety. Before you sign, ask whether the document would still help if the relationship became strained. If the answer is no, it is not enough.

Assuming contractor wording fixes a bad classification

If the project manager works like a member of your internal team, is managed like an employee, and does not operate an independent business in any meaningful way, contractor language may not protect you. This is a risk point before you hire your first worker into a project-style role and call them a subcontractor for convenience.

Leaving the main contract disconnected from the subcontract

If your business has obligations to a client under a head contract, but your project manager subcontract does not mirror the key parts they must comply with, the gap can be expensive. You may owe obligations upstream without having a clear right to pass them down.

At the same time, copying the entire head contract into the subcontract can create unfair or unworkable obligations. The better approach is selective alignment.

Not documenting variation approval

Site instructions happen fast. A director or foreman asks for extra coordination, another meeting series, or urgent procurement work. Weeks later, the project manager invoices for additional time and the business disputes it. A written variation process avoids most of that friction.

Giving broad authority without limits

A project manager may need authority to keep the build moving, but unlimited authority can expose your business to commitments you did not approve. The agreement should set clear approval thresholds for:

• spending money
• approving subcontractors or suppliers
• agreeing time extensions
• signing off defects or completion stages
• issuing instructions that change scope

Ignoring ownership of project documents

If the engagement ends badly, access to project records becomes critical. Without clear clauses, you can end up arguing over whether reports, schedules, and commercial documents must be handed over in editable form, or at all.

Accepting broad indemnities without checking insurance

An indemnity can make a subcontractor responsible for losses beyond what their insurance actually covers. The same risk applies in reverse if your business gives a broad indemnity. The wording should be checked against the real insurance position, not assumed away.

Relying on verbal assurances about timing and responsibility

Statements like “we will sort delays as they come up” or “that is included” often fall apart when pressure rises. Construction projects move quickly, but that is exactly why the paperwork matters. Before you rely on a verbal promise, get the term written into the agreement or at least confirmed clearly in the contract documents.

FAQs

Does a construction project manager subcontractor agreement need to be in writing?

It is strongly advisable. Oral arrangements are harder to prove and often leave key issues unresolved, especially scope changes, payment triggers, and liability.

Can I just use my standard contractor agreement?

Sometimes as a starting point, but construction project management usually needs extra clauses for site duties, programme changes, authority limits, project documents, and delay-related risk.

What is the biggest risk if I misclassify a subcontractor as an employee?

The biggest risk is that the real legal relationship may not match the contract label. That can create exposure to employment-related obligations and disputes. The day-to-day reality matters more than the title.

Should the agreement include health and safety obligations?

Yes. On a construction project, site safety duties and reporting expectations should be clearly allocated in writing so there is less room for confusion about who is responsible for what.

Can a subcontractor project manager approve costs on my behalf?

Only if the agreement gives them that authority. It should also set spending limits, approval pathways, and any matters that must be referred back to your business.

Key Takeaways

• A subcontractor agreement for construction project manager work should clearly define services, deliverables, authority, and exclusions.
• The agreement needs to deal with construction-specific issues such as site obligations, programme changes, delay risk, and health and safety responsibilities.
• Payment terms should match how the work is actually performed and should include a workable variation process.
• Calling someone a contractor is not enough if the real relationship looks more like employment.
• Liability, indemnities, insurance, confidentiality, and ownership of project records should be reviewed carefully before you sign.
• The subcontract should align with the key project documents without blindly importing every upstream obligation.
• If you are reviewing or negotiating subcontractor agreement for construction project manager and want help with scope drafting, contractor classification, liability clauses, contract review, and variation terms, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.