Employment Contracts for New Zealand Healthtech Startups

Hiring in a healthtech startup can move fast. You find a great engineer, clinician advisor, product lead or customer success manager, then rush out an offer letter copied from another business. That is where founders often get caught. Common mistakes include calling someone a contractor when they work like an employee, using generic confidentiality clauses that do not properly cover patient-related information, and inserting restraint clauses that are so broad they may be hard to enforce.

For New Zealand healthtech businesses, an employment contract is not just an admin document. It sets the ground rules for pay, duties, IP ownership, privacy expectations, notice, holidays and workplace policies in a sector where software, data and clinical trust matter. Before you hire your first worker, before you classify someone as a contractor, and before you rely on a verbal promise, it helps to know what your contract needs to say and where standard templates fall short. This guide explains the main legal points, the founder traps to avoid, and what to check before you sign.

Overview

An employment agreement for a New Zealand healthtech startup should reflect both standard employment law rules and the extra realities of handling sensitive data, building regulated products and protecting valuable intellectual property. The right contract will not fix every people problem, but it gives you a lawful starting point and reduces confusion when your team grows quickly.

A strong employment contract for a healthtech business usually needs to deal with role clarity, IP, privacy, contractor risk and fair termination processes from day one.

• Confirm whether the worker is genuinely an employee, casual employee, fixed-term employee or independent contractor.
• Include all mandatory employment agreement terms required under New Zealand employment law.
• Set out clear duties, reporting lines and workplace expectations, especially where clinical, technical and operational work overlap.
• Cover confidentiality in a way that reflects health information, commercially sensitive data and product development materials.
• State who owns software code, datasets, inventions, documentation and other intellectual property created in the role.
• Use trial period or probation clauses carefully, and only if they meet legal requirements.
• Check restraint, non-solicit and conflict clauses are reasonable and tailored to the role.
• Align the contract with privacy policies, security procedures and internal workplace policies.
• Make sure pay, leave, hours and termination clauses are consistent with minimum employment standards.

What Employment Contract Healthtech Startups Means For New Zealand Businesses

For a New Zealand healthtech company, the employment contract is where startup pace meets legal reality. It needs to be practical enough for a growing business and precise enough to deal with sensitive information, specialist workers and valuable technology.

Healthtech teams often combine software development, healthcare knowledge, operations and sales. A standard employment template from a retail or general SaaS business may miss the issues that matter most when staff can access clinical workflows, patient-facing systems, algorithm logic or proprietary integrations.

Employment agreements are mandatory for employees

If you hire someone as an employee in New Zealand, you need a written employment agreement. Individual employment agreements must include key legal terms, including the names of the employer and employee, a description of the work, where the employee will work, agreed hours or an indication of the arrangements relating to hours, pay, and an explanation of how employment relationship problems will be handled.

The contract also needs to reflect minimum rights that cannot be signed away. That includes minimum wage, holidays, leave entitlements and the duty to act in good faith. If your agreement says less than the law requires, the legal minimum still applies.

Healthtech roles often blur traditional boundaries

A healthtech startup might hire a registered clinician to help with product design, a software engineer who can see test patient data, or a customer support lead who handles sensitive escalations from healthcare providers. The contract should reflect what the worker actually does, not just a job title that sounded right in a funding deck.

Before you hire your first worker, think about whether each role involves:

• access to personal or health information
• product or code development
• clinical input or regulated decision-making
• customer relationship ownership
• sales incentives or commission arrangements
• remote work, on-call work or flexible hours

Those details affect confidentiality clauses, IP ownership wording, conflict terms, policy references and performance expectations.

Privacy and confidentiality deserve special treatment

Many healthtech founders assume a one-line confidentiality clause is enough. It usually is not. If your team handles health information, user data, security protocols, provider contracts or product roadmaps, your contract should define confidential information in a realistic way and tie that back to privacy and security obligations.

Employment agreements should not try to replace your broader privacy compliance work. You may still need internal privacy policies, access controls, staff training and incident response processes. But the contract should make it clear that staff must follow those systems and keep information secure during and after employment.

Intellectual property is often the real asset

In many healthtech startups, the most valuable asset is what your people create. That could be source code, machine learning models, clinical decision support logic, user interface designs, standard operating procedures, documentation, analytics frameworks or product improvements suggested by team members.

If ownership is vague, disputes can arise later when a founder-level early employee leaves or when investors carry out due diligence. A properly drafted contract should clearly state that intellectual property created in the course of employment belongs to the business, subject to any limits required by law and any agreed exceptions for pre-existing materials.

Before you sign, check that the agreement deals with:

• pre-existing IP the employee brings into the role
• ownership of new work created during employment
• moral rights consents where relevant
• obligations to disclose inventions or product improvements
• return of company property, code repositories, devices and records when employment ends

Good faith still matters in a startup

Fast growth does not remove employment law obligations. New Zealand employers must deal with employees in good faith. That affects recruitment, consultation, performance management, restructuring and termination.

Founders sometimes assume a flexible startup culture means informal arrangements are enough. In practice, verbal promises about equity, remote work, bonuses or changing responsibilities can become expensive later if the written terms do not match what was discussed.

Legal Issues To Check Before You Sign

Before you sign a healthtech employment contract, make sure the legal basics are right first, then tailor the agreement to the role. The main risk is not usually one dramatic clause, it is a stack of small drafting problems that create uncertainty when things go wrong.

1. Is the worker really an employee or a contractor?

This is one of the biggest risk areas for startups. Calling someone a contractor does not make them one. In New Zealand, the real nature of the relationship matters. If the person works set hours, is integrated into your team, uses your systems, and is subject to your control, they may legally be an employee even if the contract says otherwise.

This matters in healthtech because early teams often use part-time clinicians, product consultants and engineering freelancers in ways that become employee-like over time. Before you classify someone as a contractor, look closely at:

• how much control you have over when, where and how the work is done
• whether they can work for others
• whether they provide their own equipment and carry business risk
• whether they invoice as an independent business
• whether they are integrated into your core operations

If you get this wrong, you can face claims for employee entitlements and other compliance issues.

2. Are the mandatory terms included?

An employment agreement should include the legally required terms. Founders often start with an overseas template or a lightweight offer letter that misses basics around hours, place of work, dispute resolution language or availability arrangements.

Healthtech businesses also need to be realistic about working patterns. If your support team handles urgent after-hours issues for healthcare clients, or your implementation staff travel between provider sites, the contract should clearly state how that works.

3. Is there a valid trial period or probation clause?

Trial periods and probation arrangements are not interchangeable. If you want to use one, the wording and process matter. A trial period is only available in certain circumstances and needs to be agreed in writing before the employee starts work. If you miss the timing or use the clause incorrectly, you may lose the benefit you expected.

Founders often make the mistake of sending the agreement after the person has effectively begun work. Before your new hire starts, make sure the final signed contract is already in place.

4. Does the role description match reality?

A vague role description causes problems later. It can make performance management harder, create confusion about overtime or availability, and lead to arguments about whether the employee was expected to contribute to product strategy, compliance work or customer support.

In healthtech, role descriptions should be broad enough for a startup but specific enough to anchor expectations. A useful clause usually covers:

• the main purpose of the role
• key duties and responsibilities
• reporting structure
• requirement to follow lawful and reasonable directions
• whether duties may change as the business grows

5. Are confidentiality and privacy clauses fit for purpose?

Confidentiality wording should reflect the types of information the employee will handle. Generic drafting may not adequately describe source code, product architecture, security credentials, health-related data, research outputs or customer implementation material.

If the role includes access to personal information, especially sensitive information, the contract should also require compliance with your privacy notice and information security policies. The agreement should support your broader obligations under New Zealand privacy law, but it should not overpromise in a way your internal systems cannot deliver.

6. Is IP ownership clear and commercially useful?

If an employee helps build your product, ownership should not be left to implication. The agreement should clearly say what belongs to the company and when employees must sign further documents to confirm ownership if needed.

This becomes especially important before a capital raise, acquisition discussion or major partnership. Investors and counterparties often want to know that the business, not individual staff members, owns the code, product features and internal know-how it relies on.

7. Are restraint clauses reasonable?

Non-compete, non-solicit and non-dealing clauses can be useful, but only if they are reasonable and tailored to the employee's role. A broad restraint copied from a foreign template may be difficult to enforce, especially for junior staff.

For a senior product leader or sales lead with deep customer relationships, a narrower restraint may be more defensible. The clause should target a legitimate business interest, such as protecting customer relationships, trade secrets or confidential know-how.

8. Do your policies and contract work together?

The employment agreement should not sit in isolation. If it refers to workplace policies, data handling rules, remote work requirements, device use standards or disciplinary procedures, those policies should actually exist and be internally consistent.

This is where founders often get caught. They include policy references in the contract but have never written the policies, or they adopt generic policies that do not match how the team actually works.

Common Mistakes With Employment Contract Healthtech Startups

The most common contract mistakes in healthtech are preventable. They usually happen when founders move quickly, borrow a template from another business, or assume employment documents are all broadly the same.

Using a generic template that ignores healthtech risks

A standard startup contract may cover pay and notice, but miss the practical issues that matter in your business. If your worker can access health information, clinical workflows, research data or security systems, the contract should say more than a generic confidentiality sentence.

Templates can be a useful starting point, but they need tailoring. A contract for a warehouse manager or hospitality worker will not suit a healthtech product manager, clinician liaison or machine learning engineer.

Relying on a contractor agreement for an employee-like role

Many startups want flexibility and lower upfront commitment, so they engage people as contractors first. The problem is that the working relationship can shift quickly. A part-time advisor becomes a regular weekly contributor, then starts managing staff, attending all-hands meetings and using company systems full time.

If the person is really operating as an employee, a contractor label may not protect the business. Review working arrangements regularly, especially after fundraising, product expansion or major team changes.

Leaving IP ownership unclear with early hires

Early employees often make founder-level contributions. They may design the product architecture, create core workflows, write major portions of code or help build a proprietary clinical process. If the contract does not clearly assign ownership, that can create due diligence issues later.

Founders sometimes assume employment automatically solves this. It is safer to spell ownership out clearly and deal with pre-existing IP at the start, before there is any disagreement about who contributed what.

Overreaching on restraints

A clause that says an employee cannot work in the healthtech sector anywhere for a long period is unlikely to give you the practical protection you want. Courts look at reasonableness. Overreach can weaken your position.

A better approach is to identify the actual risk. Do you need to stop a senior employee soliciting key customers, poaching staff or using trade secrets? If so, draft for that specific concern.

Promising benefits or flexibility outside the written contract

Founders often recruit with enthusiasm and make informal commitments about bonuses, shares, title changes, permanent remote work or future promotions. If those arrangements matter, they should be documented properly.

Before you rely on a verbal promise, ask whether it should be included in the contract, a separate incentive document or another formal record. Loose promises can create disputes even where everyone started with good intentions.

Sending the contract too late

Another frequent mistake is rushing the contract through after the person has already started. That creates problems for trial periods and can weaken your position generally. It also sets the tone that paperwork is secondary, which is not ideal in a regulated or data-sensitive business.

Before your new hire begins work, make sure the final version is signed and the employee has had a fair opportunity to review it and ask questions.

Ignoring the link between contracts and internal systems

A strong contract cannot compensate for weak internal practice. If your agreement says staff must protect confidential information, but everyone shares passwords or accesses live data unnecessarily, the legal drafting only goes so far.

Employment contracts work best when they align with real procedures around:

• data access permissions
• device and account management
• onboarding and offboarding
• security training
• incident reporting
• document retention and return of property

FAQs

Do New Zealand healthtech startups need a written employment agreement?

Yes. If you are hiring an employee, you should have a written employment agreement that includes the required legal terms and reflects the actual role. A short offer letter on its own is usually not enough.

Can we use the same employment contract for every team member?

Usually no. Some core clauses can stay consistent, but contracts should be tailored for the role, seniority, access to sensitive data, commission structure, IP exposure and any special working arrangements.

Is a contractor agreement safer for early-stage hiring?

Not necessarily. A contractor agreement only suits a genuine independent contractor relationship. If the person works like an employee in practice, calling them a contractor can create legal risk rather than reduce it.

Do we need special clauses if staff handle patient or health information?

Often yes. The agreement should include stronger confidentiality and privacy-related obligations, and should link staff to your internal privacy and security procedures. The exact wording will depend on what data they access and what the business does.

Can we stop an employee from joining a competitor?

Sometimes, but only to a reasonable extent. Restraint clauses need to protect a legitimate business interest and be tailored to the employee's role. Broad, generic non-compete clauses are more likely to be challenged.

Key Takeaways

• New Zealand healthtech startups should use written employment agreements that include the required legal terms and reflect how the role actually works.
• Generic startup templates often miss key issues around privacy, confidentiality, sensitive data access and intellectual property ownership.
• Before you classify someone as a contractor, check whether the real working relationship looks more like employment.
• IP clauses matter early, especially where staff are building code, workflows, algorithms, research outputs or other valuable know-how.
• Trial periods, probation terms, restraints and policy references need careful drafting and correct process to be useful.
• Contracts should align with your internal systems for onboarding, security, data access and offboarding.

If you want help with employee agreements, contractor classification, intellectual property clauses, privacy and confidentiality terms, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.