Project Management Agreements in New Zealand

A project can go off track quickly when the deal with your project manager is vague. Founders and business owners often sign a short proposal, rely on verbal promises about timing, or assume the project manager will carry all risk for delays and budget overruns. Those are common mistakes, and they usually show up when the build stalls, contractors start arguing about scope, or invoices arrive for work you thought was included.

A well-drafted project management agreement helps set the rules before money is spent and expectations harden. It should spell out what the project manager is actually responsible for, who approves changes, how fees work, what happens if subcontractors or suppliers cause delays, and how disputes get handled. If you are about to sign a contract for a fit-out, property development, technology implementation, construction-related coordination, or another business project in New Zealand, this guide explains the key legal issues to sort out before you sign.

Overview

A project management agreement is the contract that sets out how a project manager will plan, coordinate, report on and administer your project. In New Zealand, the right terms matter because the agreement often sits between several moving parts, including consultants, contractors, suppliers, landlords, and your own internal team.

The main value of the agreement is clarity. It allocates responsibility, manages risk and gives both sides a workable process when timing, scope or budget changes.

Define the services clearly, including what is excluded
Set out milestones, reporting obligations and decision-making authority
Explain the fee model, reimbursable costs and when invoices are payable
Deal with delays, variations and events outside the project manager's control
Cover liability caps, indemnities and insurance requirements
Protect confidential information and any project documents or intellectual property
State how either party can terminate and what happens on exit
Include a dispute process that suits a live commercial project

What Project Management Agreement Means For New Zealand Businesses

A project management agreement is not just an admin document, it is the operating rulebook for a live commercial job. Before you sign a contract, you need to know whether the project manager is acting as an adviser, an agent with authority to bind you, or something closer to a lead consultant with broader control.

That distinction matters because it affects who can give instructions, approve costs, sign contractor paperwork and carry responsibility when something goes wrong. Many business owners assume the project manager will “handle everything”, but the contract often says something narrower.

What the agreement usually covers

Most project management agreements in New Zealand are service contracts. They usually describe the project manager's role in planning, coordination, procurement support, contractor management, reporting and practical completion, but the exact mix varies from project to project.

The agreement should identify key details such as:

the project itself, including site, business purpose and any defined stages
the services to be delivered at each stage
the project manager's authority limits
your responsibilities as the client
the expected programme or timetable
the fee structure and payment triggers
how changes will be approved

If your project touches property works, a warehouse fit-out, office relocation, software roll-out, procurement process or franchise build, these details should be specific. Generic wording creates room for disagreement later.

Project manager or contractor, the difference matters

A project manager is usually not the same as the builder, tradesperson, software developer or supplier doing the underlying work. Their role is often to coordinate and administer the project, not to guarantee every outcome delivered by third parties.

This is where founders often get caught. If the agreement says the project manager will use reasonable care and skill to coordinate the project, that is very different from promising the project will be completed by a fixed date or fixed price.

Before you rely on a verbal promise, check whether the contract makes the project manager responsible for:

selecting and appointing contractors
supervising quality
monitoring health and safety compliance
approving payment claims
keeping the budget within agreed limits
reporting risks and delays promptly
obtaining consents or licences where needed

If these tasks sit elsewhere, your agreement should say so clearly.

Why New Zealand context matters

New Zealand businesses often use project managers for commercial fit-outs, refurbishments, developments, systems implementations and expansion projects. These jobs regularly involve layered contracts, and your project management agreement should line up with the rest of the project documents.

For example, if the project manager is expected to administer a building contract, review consultant reports or coordinate a landlord consent or approval process, the wording should match those arrangements. If the project manager is handling project data, stakeholder contact details or staff information, privacy obligations may also come into play under the Privacy Act 2020.

Marketing and pre-contract statements matter too. If a provider represents that they can deliver outcomes, experience levels or timelines they cannot support, there can be issues under the Fair Trading Act 1986. That is one reason to make sure the written agreement matches the proposal, pitch and email promises.

Consumer law style standards can still influence service expectations

Even in a business-to-business deal, parties often assume “common sense” service standards will fill the gaps. That is risky. While consumer protection rules such as the Consumer Guarantees Act 1993 do not always apply in a standard business contract, the broader commercial expectation remains the same, the service description should be accurate and the obligations should be written down.

If your project manager is providing services to your business, the better approach is to document the service standard expressly. That may include reporting frequency, escalation timing, meeting attendance, record keeping and document handover at the end of the project.

Legal Issues To Check Before You Sign

The legal issues that matter most are scope, authority, liability and exit. Before you accept the provider's standard terms, make sure the agreement reflects how your project will work in practice, not just in theory.

Scope of services and exclusions

The scope is usually the first point of dispute. If it is too broad, you may pay extra for work you thought was included. If it is too narrow, the project manager can say a key task was never part of the deal.

The contract should separate included services from excluded services. It should also identify assumptions that the project manager is relying on, such as timely access to the site, information from your team, or approvals from third parties.

Good scope wording often covers:

planning and project scheduling
budget tracking and cost reporting
procurement or tender coordination
stakeholder meetings and reporting
contract administration support
risk identification and escalation
quality monitoring or defect management
handover and close-out deliverables

Authority to act on your behalf

You should never leave authority vague. If the project manager can approve costs, instruct contractors or sign documents as your agent, that power needs clear limits.

Before you sign, decide:

what spending threshold needs your written approval
whether the project manager can issue instructions directly to contractors
whether they can approve variations
whether they can bind your business to any third-party terms
what approvals can be given by email and by whom

If these rules are missing, you can end up paying for decisions your business never meant to authorise.

Fees, expenses and variation pricing

The fee clause should tell you exactly how charges are calculated. A percentage-of-project-cost fee, a fixed fee, a stage-based fee and an hourly rate model all create different incentives and risks.

The agreement should cover:

the fee basis
what counts as reimbursable expenses
whether subcontractor or specialist consultant costs are included
when invoices can be issued
whether disputed amounts can be withheld
how variations are priced and approved

If the project budget is tight, add a requirement for written approval before the project manager incurs any non-routine external cost.

Timing, delays and dependency risk

Most projects slip because multiple parties are involved, not because one person simply failed to do their job. Your contract should deal with dependency risk openly.

Check whether the agreement explains:

whether dates are estimates or binding deadlines
what happens if your team causes delay
what happens if landlords, councils, contractors or suppliers cause delay
how delay notices must be given
whether fees continue during suspended periods

If the project manager is expected to maintain a programme, the reporting obligation should be specific. Monthly updates may be too slow for a fast-moving job.

Liability, indemnities and insurance

Liability clauses often decide the practical outcome of a dispute. A low liability cap can leave your business carrying a much larger loss than expected.

Key points to review include:

any cap on the project manager's total liability
whether indirect or consequential loss is excluded
what indemnities each party gives
whether liability is reduced if others contributed to the loss
what insurance obligations the project manager must meet, such as professional indemnity or public liability cover

There is no single correct liability setting for every project. A small advisory role may justify a different risk allocation from a manager with broad control over procurement and project administration.

Confidentiality, privacy and project documents

Projects often involve sensitive information, including budgets, supplier pricing, plans, staff details and future business strategy. The agreement should protect that information during the project and after it ends.

If the project manager handles personal information, such as employee details, tenant contacts or customer data for a systems roll-out, you may also need privacy wording or a privacy notice that reflects responsibilities under the Privacy Act 2020.

You should also check who owns:

project schedules and reports
templates and tools
site photos and records
procurement documents
final handover materials

Sometimes the project manager keeps ownership of pre-existing materials but grants you a licence to use them. In other cases, the client owns all deliverables created specifically for the project.

Termination and handover

You need a clean exit route before the relationship turns difficult. If the project is live, termination without a handover plan can create immediate operational problems.

The agreement should state:

when either party can terminate for convenience
what counts as serious breach
how much notice is required
what fees are payable on termination
what documents and information must be handed over
whether the project manager must assist with transition to a replacement provider

This matters most where the project manager has the key records, contractor relationships or programme knowledge.

Common Mistakes With Project Management Agreement

The most common mistake is assuming a proposal or statement of work is enough. Before you spend money on setup or commit to contractors, make sure the agreement deals with how the project will actually be managed day to day.

Relying on verbal promises about delivery

A business owner may be told that the project manager will “take full responsibility” or “keep the budget under control”, but the signed contract may only promise reasonable efforts. If the wording does not match the sales conversation, the written document usually carries more weight.

Ask for key promises to be written into the agreement, especially around timing, approvals, reporting and escalation.

Using unclear scope language

Phrases like “end-to-end management” or “full coordination” sound helpful, but they are not precise enough on their own. They do not tell you who procures consultants, who approves invoices, or who monitors defects.

When scope is unclear, each side reads the contract in its own favour. That usually means cost disputes once the project is underway.

Ignoring the interaction with other contracts

A project manager rarely operates in isolation. There may be leases, building contracts, consultancy agreements, software licences, supply contracts or internal governance requirements sitting around the same project.

If the project management agreement does not align with those documents, gaps appear. For example, a project manager may be expected to administer a contractor contract they have no authority to enforce, or they may be blamed for milestones that depend on landlord consent.

Accepting broad exclusions and a very low liability cap

Standard terms often exclude delay losses, lost profits, third-party losses and any issue linked to supplier performance. On top of that, liability may be capped at a very low amount, sometimes only a few months of fees.

That may be acceptable for a limited advisory engagement. It may not be acceptable for a high-value project where management failures could trigger significant commercial losses.

Failing to document variation control

Projects change. The legal problem is not that change happens, it is that no one agrees on who approved it and what it costs.

Your agreement should require clear variation requests and approvals. Email approval can work, but the contract should say who can authorise changes and when work may proceed.

Overlooking records and reporting

If a dispute arises, the strongest position usually belongs to the party with a clear paper trail. A project manager should be required to keep records of instructions, meetings, budgets, risks and changes.

Without those records, it becomes much harder to work out whether delays or overruns were foreseeable and who was told about them.

Forgetting post-termination access

Some businesses only discover at the end that key project files sit in the provider's systems or personal email folders. If there is no handover obligation, the transition can be messy and expensive.

The agreement should say what must be delivered on exit, in what format, and how quickly.

FAQs

What is a project management agreement?

It is a contract between your business and a project manager that sets out the services, fees, authority, timing, liability and exit arrangements for the project.

Does a project manager guarantee the outcome of the project?

Not always. Many agreements only require the project manager to use reasonable care and skill. If you expect responsibility for budget control, deadlines or contractor management, that should be stated clearly in the contract.

Can a project manager bind my business to other contracts?

Only if the agreement gives them authority to do so, or if your business otherwise authorises it. The contract should set clear approval limits so there is no confusion about who can commit your business.

Should I use the provider's standard project management agreement?

You can, but you should get a contract review before you sign. Standard terms often favour the provider on scope, variations, liability caps, payment timing and termination rights.

What happens if the project ends early?

That depends on the termination clause. A good agreement will explain notice periods, payment for work done, return of documents, and transition support if a new provider takes over.

Key Takeaways

A project management agreement should clearly define the project manager's role, authority and limits.
The most important issues to review before you sign are scope, fees, variations, delay risk, liability, confidentiality and termination.
Verbal promises and broad marketing language are not enough, key expectations should appear in the written contract.
Your agreement should fit with the rest of the project documents, including contractor, consultant, lease or procurement arrangements.
Clear reporting, record keeping and handover obligations make disputes easier to prevent and easier to resolve.
Legal review is especially useful where the project is high value, time sensitive, or depends on multiple third parties.

If you want help with scope drafting, liability caps, variation clauses, and termination rights, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.