Contractor or Employee? Legal Risks for New Zealand Health App Businesses

Health app founders often move fast when bringing in clinicians, coaches, developers, moderators, and customer support staff. The legal problem is that worker status can be easy to get wrong, especially where someone is labelled a contractor but works much like part of the team. Common mistakes include relying on a template contractor agreement without looking at the real working relationship, controlling a contractor like an employee, and assuming remote or part time work automatically means contractor status.

For New Zealand health app businesses, the consequences can be expensive. A misclassified worker may claim minimum employment rights, holiday pay, KiwiSaver issues may arise, and a dispute can distract the business at the exact moment it needs to scale. The risk can be higher in health and wellness businesses because founders often want tight quality control, detailed protocols, and close supervision of people delivering app-based services.

This guide explains how contractor vs employee health app issues are assessed in New Zealand, what to check before you sign, and where founders usually get caught out.

Overview

In New Zealand, calling someone a contractor does not settle the issue. The real question is what the relationship looks like in practice, including control, integration into the business, and whether the person is genuinely operating their own independent business.

• Look at the actual day to day arrangement, not just the contract label.
• Check who controls hours, processes, pricing, and performance standards.
• Consider whether the worker can subcontract, work for others, and carry business risk.
• Make sure agreements match the reality of the relationship.
• Review privacy, confidentiality, and health information obligations alongside worker status.
• Reassess classification as your health app grows and roles become more structured.

What Contractor Vs Employee Health App Means For New Zealand Businesses

The main point is simple: New Zealand businesses need to classify workers based on the real substance of the relationship, not the title on the agreement.

For a health app business, that question often comes up with telehealth clinicians, nutrition coaches, fitness experts, wellness advisers, mental health support workers, software developers, product specialists, and customer success staff. Founders may prefer contractor arrangements because they seem more flexible. But if the business treats those people like employees, the label may not hold up.

Why worker status matters

Employee status affects rights and obligations that do not usually apply to true independent contractors. That can include minimum wage, holidays and leave entitlements, record keeping, disciplinary processes, and other Employment Relations Act issues. A worker who has been treated as a contractor may later argue they were really an employee all along.

That creates commercial risk as well as legal risk. Buyers, investors, and commercial partners often want comfort that the business has correctly documented key relationships. If your health app depends on a network of practitioners or support staff, worker classification can become a due diligence issue very quickly.

How New Zealand looks at the relationship

The quotable answer is this: New Zealand looks at the real nature of the relationship.

That means a written agreement matters, but it is not the whole story. Courts and authorities can look at what happens in practice. Before you classify someone as a contractor, founders should think about factors such as:

• How much control the business has over when, where, and how the person works.
• Whether the person is part of the business, or operating independently.
• Whether the person can work for competitors or other clients.
• Whether the person can send a substitute to do the work.
• Who provides tools, systems, and equipment.
• How the person is paid, including whether they invoice and carry financial risk.
• Whether the arrangement looks ongoing and dependent, or project based and arm's length.

No single factor decides the issue every time. The mix matters.

Why health app businesses face extra classification pressure

Health app businesses often need consistency, safety, and quality assurance. That is commercially sensible, but this is where founders often get caught. The more you prescribe scripts, workflows, shift windows, escalation paths, mandatory software use, meeting attendance, and performance management, the more the arrangement can start to look like employment.

That does not mean contractors are impossible in a health app setting. It means the structure must be thought through carefully. A specialist clinician who works with several platforms, chooses their own hours, uses their own professional judgement, invoices under their own business, and bears some commercial risk may be easier to support as a genuine contractor than a person rostered into daily app support under close internal supervision.

Examples founders recognise

A dietitian who joins your platform, sets available consultation blocks, provides services to multiple clients and businesses, invoices monthly through their own company, and can decline work is more likely to sit on the contractor side.

A care coordinator who works five days a week, must be online at set times, follows your detailed internal procedures, attends mandatory team meetings, reports to a manager, and cannot work elsewhere is more likely to raise employee classification risk, even if the agreement says contractor.

A software developer engaged for a fixed build with milestone payments and freedom over how the work is completed may fit a contractor model. But if that same developer becomes your full time product lead, is managed like staff, and is embedded long term in the business, you should revisit status before you sign the next agreement.

Legal Issues To Check Before You Sign

Before you sign a contract, match the legal documents to the practical reality of the role. If the business wants employee style control and commitment, an employment agreement may be the safer path.

1. Control and supervision

Control is one of the first things to assess. Ask yourself how much freedom the person really has.

If your health app requires someone to:

• work fixed hours or shifts,
• use mandatory scripts or standard responses,
• follow detailed internal processes,
• seek approval before taking leave, or
• report into a management hierarchy,

the arrangement may look less like independent contracting.

Some quality standards are reasonable, especially in regulated or sensitive health settings. But there is a line between setting outcomes and controlling the person as part of your workforce.

2. Integration into your business

If the worker looks and feels like part of the business, employee risk increases.

Founders should check whether the person has a company email address, internal title, manager, staff benefits, team KPIs, and an ongoing role central to day to day service delivery. The more integrated they are, the harder it may be to argue they are running their own business.

3. Ability to work for others

A true contractor usually has room to work for multiple clients. An arrangement that stops the person working elsewhere, or makes that impractical, can point the other way.

Some limits may still be appropriate. For example, confidentiality obligations, conflict rules, and carefully drawn restraints may be relevant in a health app business handling sensitive product information or user data. But an exclusivity clause in a contractor agreement should be treated with caution.

4. Subcontracting and substitution

A genuine contractor often has some ability to delegate or engage help, subject to sensible approval where clinical or sensitive work is involved.

If the business insists the work must always be performed personally, and the role depends on the individual showing up like an employee would, that may weaken the contractor position. In healthcare contexts, substitution rights need careful contract drafting because professional credentials, privacy obligations, and patient safety still matter.

5. Payment structure and business risk

Contractors usually invoice for services and carry some commercial risk. Employees are typically paid wages or salary through payroll.

Before you rely on a contractor model, consider whether the person:

• issues invoices,
• sets or negotiates fees,
• supplies some of their own equipment or tools,
• can make a profit by working efficiently, and
• bears some risk of loss or rework.

This area can have accounting and tax consequences, so it is sensible to involve an accountant or tax adviser as well.

6. Privacy and health information handling

Health app businesses do not only need the right worker status. They also need the right information handling rules.

Whether a person is a contractor or employee, you should spell out obligations around:

• access to user and patient information,
• confidentiality,
• secure system use,
• permitted disclosures,
• incident reporting, and
• return or deletion of data when the engagement ends.

New Zealand privacy obligations and data protection requirements can become especially important where workers access health information, triage content, or communicate directly with users through the app.

7. Intellectual property and platform ownership

If contractors are creating code, content, workflows, clinical resources, or marketing assets, ownership should not be left to assumption.

Your agreement should clearly deal with who owns work product, what rights are assigned to the business, and whether the contractor can reuse material elsewhere. This is particularly important for health apps where product value may sit in the software, brand assets, service protocols, or clinical content library.

8. Restraints, confidentiality, and non-solicitation

Founders often want protection against a clinician or coach leaving with users, referral sources, or staff. Those protections can be included, but they should be drafted carefully and kept reasonable.

Overreaching restrictions can be hard to enforce and may also sit awkwardly with an arrangement said to be independent. The clause should fit the role, the sensitivity of the information, and the business interest you are actually protecting.

9. Termination rights and practical exit

A contractor relationship should have a clear end point or termination mechanism. If your agreement copies employment style disciplinary steps without good reason, that can muddy the picture.

Before you sign, check what happens if the relationship is not working, how notice is given, what fees remain payable, what happens to platform access, and how users are transitioned safely if the worker provides health related services.

Common Mistakes With Contractor Vs Employee Health App

The biggest mistake is treating classification as a paperwork exercise. A contractor agreement that does not match day to day reality can create false confidence, not protection.

Using one template for every role

A clinician providing occasional specialist consults is not the same as a full time care navigator or an in house engineer. Yet founders often use the same contractor template across all of them.

Different roles create different legal signals. The agreement and operating model should reflect what that person actually does.

Controlling contractors like staff

This is one of the most common problems in app businesses. The business wants speed, consistency, and user trust, so it starts rostering contractors, requiring daily stand ups, reviewing time off, and measuring them against internal employment style KPIs.

Once that happens, the practical arrangement may point away from independent contracting. Before you hire your first worker into a tightly managed role, decide whether you really need an employee.

Ignoring change over time

A relationship that starts as genuine contracting can drift. A contractor may begin on a limited project, then stay for years, become the sole person in a function, and depend on the business for most of their income.

This is where regular reviews and contract review matter. Revisit worker status when responsibilities expand, service delivery becomes more centralised, or the person becomes deeply embedded in the business.

Missing the health specific operational issues

Health app founders can be so focused on classification that they forget adjacent risks. If a contractor is handling user health information, communicating clinical guidance, or accessing sensitive analytics, your contract also needs to cover confidentiality, privacy, data security, complaint handling, and scope of authority.

A badly drafted contractor agreement can leave gaps even if status itself is correct.

Assuming remote work means contractor status

Remote work is common in digital health. But working from home, setting video consult blocks, or joining via an app does not automatically make someone an independent contractor.

The legal question still comes back to the real nature of the relationship. A remote worker can still be an employee if the business controls the work in an employment like way.

Relying on verbal promises

Founders sometimes move quickly and rely on email threads or a call where everyone agrees the person is a contractor. That is risky.

Before you rely on a verbal promise, document the arrangement properly. The written terms should deal with status, scope, payment, confidentiality, intellectual property, privacy obligations, dispute handling, and exit.

Forgetting the brand and trust angle

Worker status is not only a back office issue. If a health app markets clinicians or coaches as part of its team, promises a highly managed care experience, and presents workers to users as core staff, those facts may not help a contractor argument later.

Public messaging, internal processes, and contracts should tell a consistent story.

FAQs

Can I just call someone a contractor in the agreement?

No. The label helps, but New Zealand looks at the real nature of the relationship. If the day to day arrangement looks like employment, the contract wording may not save it.

Are clinicians on a health platform always contractors?

No. Some clinicians may be genuine independent contractors, but others may be working in a way that looks more like employment. It depends on control, integration, independence, and the overall practical setup.

Does part time or casual work mean contractor status?

No. Part time and flexible arrangements can still be employment. The key question is not the number of hours, it is the true substance of the relationship.

What if I need strict quality standards because we are in health?

You can still set appropriate quality, safety, and compliance standards. The issue is whether those controls go so far that the person is effectively working as part of your business under your direction. The structure needs careful drafting and practical alignment.

When should a health app business review worker classification?

Review it before you sign, when a contractor's role expands, when someone becomes central to daily operations, or when you change how work is supervised, paid, or delivered through the platform.

Key Takeaways

• In New Zealand, worker status depends on the real nature of the relationship, not just the label in the contract.
• Health app businesses face particular risk because quality control, user safety, and clinical oversight can make contractor arrangements look more like employment.
• Before you classify someone as a contractor, check control, integration, ability to work for others, substitution rights, payment structure, and business risk.
• Contracts should also cover privacy, health information handling, confidentiality, intellectual property, and clear termination rights and processes.
• Review arrangements regularly, especially when a contractor becomes long term, heavily supervised, or central to your service delivery.
• Getting the structure right early can reduce dispute risk and make the business easier to scale, fund, or sell.

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