Black Friday10% off any legal service

IT Contractor Agreement Template NZ: What To Include

byAlex Solo9 min read

Do you really need a written IT contractor agreement, or will an email chain and a statement of work do?

The reassuring answer is that it doesn't have to be complicated, but for project builds, support retainers and software consulting, you do want the key terms in writing before anyone touches code, systems or client data.

A good agreement helps you set scope, payment, IP ownership, confidentiality, support expectations and contractor status. That matters even more now that New Zealand has a contractor gateway test under the Employment Relations Amendment Act 2026.

Do IT Consultants Need A Written Contractor Agreement?

Yes, you should have a written contractor agreement for IT consulting work because the risks usually sit in the details.

IT projects often involve a mix of strategy, implementation, code, integrations, credentials, confidential information and ongoing support. If the contract only says build website or provide IT support, you may end up arguing about what was actually included.

Your agreement should make the commercial deal easy to understand. At a minimum, it should cover:

  • Who the parties are: Use the correct legal names, Companies Office details and NZBN where relevant.
  • The scope: Describe the project, deliverables, support tasks, IT services or consulting services.
  • Fees and payment: Set the hourly rate, fixed fee, milestone payments, expenses and GST position.
  • Timeframes: Include start dates, milestone dates and what happens if the client delays feedback or access.
  • IP ownership: Say who owns new work, existing tools and reusable materials.
  • Data and confidentiality: Set clear rules for accessing systems, personal information and confidential business information.
  • Support obligations: Spell out response times, availability, exclusions and handover.
  • Ending the contract: Include termination rights, notice, payment on termination and return or deletion of materials.

Without a written agreement, you may struggle to recover unpaid invoices, prove what was out of scope or stop a client using your pre-existing software tools in a way you never agreed to.

Can I Use An IT Contractor Agreement Template?

Yes, a template can be a useful starting point, but it shouldn't be treated as a finished contract for a technology project.

Free templates often use generic consulting language. That can miss the clauses that matter most for software, cybersecurity, cloud migration, managed services and support work. Your contract should match how your business actually works.

Fill-In Outline For An IT Contractor Agreement

Here is a practical outline you can use to brief your legal team or check a draft. A lawyer should tailor it before you use it with clients or contractors.

  1. Parties: Insert the legal names, trading names, NZBNs and contact details.
  2. Services: Describe the consulting, development, IT support services or managed services being provided.
  3. Statement Of Work: Attach a clear scope, milestones, deliverables, assumptions and exclusions.
  4. Fees: Set fixed fees, hourly rates, retainers, expenses, GST, invoicing dates and payment deadlines.
  5. Client Responsibilities: List access, information, approvals, hardware, licences and testing the client must provide.
  6. Change Control: Explain how extra work is quoted, approved and billed.
  7. IP: Separate new deliverables, pre-existing tools, open source components and licences.
  8. Confidentiality: Protect business information, credentials, security details and client data.
  9. Privacy And Security: Set rules for personal information, breach notification, access controls and overseas storage.
  10. Support: Include service hours, response targets, exclusions, maintenance windows and escalation steps.
  11. Contractor Status: Confirm the relationship and make sure the wording matches the working arrangement.
  12. Liability: Set sensible limits, exclusions and indemnities for your risk profile.
  13. Termination: Explain notice, immediate termination events, final invoices and handover.

If you're using a technology consulting contract in New Zealand, the big question isn't whether the template looks professional. It's whether the clauses actually protect the way you deliver work.

Who Owns The IP In Software And Technology Consulting Work?

It depends on what kind of IP you're talking about, so your contractor IP clause should be very clear.

Under the Copyright Act 1994, copyright ownership can work differently depending on whether the creator is an employee, a contractor, or someone commissioned to create particular works. For example, commissioned computer programs can have special ownership rules. That said, relying on default copyright rules is risky because most IT projects involve more than one type of asset.

A good software contractor agreement should split IP into clear buckets:

  • Background IP: Your pre-existing code, frameworks, scripts, libraries, templates, know-how, processes and tools.
  • Project IP: New deliverables created specifically for the client under the project.
  • Third Party IP: Open source software, plugins, APIs, stock assets, vendor documentation and licensed products.
  • Client Materials: The client's data, branding, systems, content and confidential information.
  • Licence Rights: What each party can use, copy, modify, commercialise and share after the project ends.

Say you run a Christchurch software consultancy and build a custom booking platform for a client for $18,000. You use your own reusable authentication module that you developed years ago. The client should receive the rights they need to use the booking platform, but you probably don't want to give away ownership of your authentication module for future projects.

Your IP clause can say the client owns, or is licensed to use, the final deliverables while you keep ownership of your background IP. It can also stop the client from reselling your tools as a separate product unless you've expressly agreed to that.

If trade marks are involved, remember that registered trade marks sit with IPONZ. Your contract shouldn't promise that a name, logo or software product is protected as a trade mark unless that has actually been checked or registered.

What Should The Contract Say About Confidentiality And Data Security?

Your contract should say exactly how confidential information and data must be handled, because IT contractors often get access to sensitive systems.

Confidentiality clauses shouldn't only cover obvious business secrets. They should also cover source code, credentials, architecture diagrams, security settings, customer lists, pricing, product roadmaps, analytics, incident reports and internal policies.

Privacy also matters if you handle personal information. The Privacy Act 2020 applies to New Zealand agencies, including many businesses, and sets rules for collecting, using, storing and disclosing personal information. If there's a privacy breach that's likely to cause serious harm, the Privacy Commissioner and affected people may need to be notified.

Your IT contractor agreement should include practical security obligations, such as:

  • using multi-factor authentication where available
  • not sharing administrator credentials
  • only accessing systems for the agreed work
  • keeping devices, repositories and cloud tools secure
  • not transferring data outside approved systems without consent
  • telling the client promptly about suspected security incidents
  • returning or securely deleting data when the contract ends
  • getting approval before using subcontractors or offshore support teams, and documenting any sub-contractor agreement

If your client is in healthcare, fintech, SaaS, education or another data-heavy sector, generic confidentiality wording usually won't be enough. The contract may need more detailed security standards, audit rights, incident timelines and rules for overseas storage or support access.

Can A Contract Stop An IT Consultant Being Treated As An Employee?

No, a contract alone can't magically turn an employee relationship into an independent contractor relationship, but it's now a bigger part of the picture in New Zealand.

The Employment Relations Act 2000 looks at the real nature of the relationship. That means the written agreement matters, but so does what actually happens day to day.

The Employment Relations Amendment Act 2026 introduced a contractor gateway test. In broad terms, if the arrangement meets the gateway requirements, the worker is treated as a contractor for employment status purposes. Those requirements focus on things like:

  • having a written agreement that says the worker is an independent contractor
  • not stopping the worker from working for other businesses, including competitors
  • not requiring the worker to be available at set times or for minimum hours, or allowing subcontracting
  • not ending the contract just because the worker turns down extra tasks or engagements

If the gateway isn't met, the usual real nature of the relationship test can still apply. That can look at control, integration into the business, economic reality and how the parties actually behave.

For a technology consulting contract, this means your paperwork and working practices should line up. If you call someone a contractor but give them fixed employee-style hours, require exclusivity, put them into your internal reporting structure and treat them like staff, the contract may not do the job you expect.

The practical consequence can be significant. If an individual is really an employee, your business may have obligations around minimum employment standards, leave under the Holidays Act 2003, holiday pay, termination process and other employment rights. If you're engaging individual IT contractors, get the setup right at the beginning.

What Should A Technology Consulting Contract Say About Support And Service Levels?

It should set clear support obligations, because support is where many IT projects become messy.

A project build and an ongoing support and maintenance arrangement aren't the same thing. If your agreement doesn't separate them, a client may expect unlimited bug fixes, training and troubleshooting after the project fee has been paid.

Your support terms should cover:

  • Support period: For example, 30 days of defect support after go-live, then paid support after that.
  • Support hours: Standard business hours, after-hours support or 24/7 support if agreed.
  • Response targets: How quickly you'll acknowledge critical, high, medium and low priority issues.
  • Resolution approach: Whether you promise a fix, a workaround or reasonable efforts.
  • Exclusions: Problems caused by third party systems, client changes, misuse, missing licences or out-of-scope features.
  • Service credits: Whether any credits apply, and if so, how they're capped.
  • Maintenance windows: When planned downtime can happen.
  • Handover: What documentation, credentials or training will be provided at the end.

Example: Support Terms In Practice

Aroha runs a Wellington SaaS consultancy. She agrees to migrate a client's customer portal for $12,000, then provide support for $1,500 per month.

Her contract says critical outages get a response within 2 hours during support hours, and she will use reasonable efforts to provide a fix or workaround within 1 business day. Service credits are capped at 10% of the monthly support fee, so the maximum credit for a month is $150.

That structure gives the client comfort without turning Aroha into an insurer for every possible outage. It also helps her price the support work properly.

What Should I Check Before Signing Or Sending The Agreement?

You should check that the agreement matches the commercial deal, the technical delivery model and the legal risks for the project.

Before you sign or send an IT contractor agreement or service agreement, work through this checklist:

  • Scope: Are the deliverables specific enough to tell what is included and what is out of scope?
  • Dependencies: Does the client need to provide access, content, licences, environments or approvals by set dates?
  • Change Requests: Is there a simple process for approving extra work before you do it?
  • Payment: Are payment dates, milestones, late payment consequences and expenses clear?
  • IP: Does the agreement protect your background IP and deal with open source or third party software?
  • Privacy: Have you covered personal information, security incidents, subcontractors and data return or deletion?
  • Contractor Status: If an individual contractor is involved, does the working arrangement support contractor status under the 2026 gateway context?
  • Fair Trading: Are your promises about performance, security and capability accurate under the Fair Trading Act 1986?
  • Consumer Guarantees: If both parties are in trade and you want to contract out of the Consumer Guarantees Act 1993, does the contract say so and is it fair and reasonable?
  • Liability: Are liability caps, exclusions and indemnities commercially sensible for the size and risk of the project?

Pay close attention to sales language too. If your proposal promises guaranteed uptime, complete security or a specific business result, that wording can come back into the contract. Keep your promises accurate and achievable.

Key Takeaways

  • An IT contractor agreement should cover scope, payment, IP, confidentiality, data security, contractor status, support and termination.
  • Templates can help you start, but technology contracts need tailoring for software, systems access, personal information and support obligations.
  • Your contractor IP clause should separate background IP, project deliverables, third party tools and licence rights.
  • Privacy Act 2020 obligations matter if you handle personal information, especially where systems access or security incidents are involved.
  • The 2026 contractor gateway test makes the written agreement important, but your day-to-day working arrangement still needs to match contractor status.
  • Support terms should set response targets, exclusions and caps so you don't accidentally agree to unlimited support.

If you'd like help with tailoring your IT contractor agreement, contractor IP clauses, confidentiality and data security terms, or contractor status settings, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

Protect your brand

What intellectual property should you protect?

If a name, logo, design or other creative work matters to the business, check who owns it, what permissions you need and whether clearance or registration is appropriate.

Alex Solo
Alex SoloCo-Founder

Alex is a co-founder of Sprintlaw. 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.

Protect your brand

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.