Next of Kin or Emergency Contact? Privacy Rules for NZ Employers

Many New Zealand employers use the terms next of kin and emergency contact as if they mean the same thing. They do not. That mix-up can cause real problems when a worker is injured, becomes unwell at work, or when HR staff collect more personal information than they actually need. Common mistakes include asking for “next of kin” on every onboarding form without explaining why, assuming the listed person has legal authority to make decisions, and storing sensitive contact details without a clear privacy process.

If you are hiring staff, this matters before you send out an employment agreement or your standard new starter paperwork. The guide below explains the difference between next of kin and emergency contact, what New Zealand employers usually need to collect, when the wording on your forms should change, and how privacy law affects the way you ask for, store and use that information.

Overview

An emergency contact is usually the person you call if something happens at work and you need to urgently reach someone connected to the employee. Next of kin is a broader personal or family term, but it does not automatically give that person legal authority in employment, medical, or estate matters.

For most New Zealand businesses, the safer and clearer approach is to ask for an emergency contact rather than next of kin, unless you have a specific and lawful reason to collect something different.

  • Use “emergency contact” on onboarding forms if the purpose is to contact someone urgently about a workplace incident or health event.
  • Tell employees why you are collecting the information, how it will be used, and who inside the business can access it.
  • Collect only what you reasonably need, usually the contact’s name, relationship to the employee, and phone number.
  • Do not assume a next of kin can make legal, medical, or employment decisions for the worker.
  • Review employment packs, HR systems, and health and safety forms so your wording is consistent.
  • Store contact information securely and update it regularly as part of your privacy and personnel record practices.

What Next of Kin Vs Emergency Contact Means For New Zealand Businesses

The practical answer is simple: employers usually need an emergency contact, not a next of kin.

That distinction matters because the label shapes what staff think they are agreeing to, what managers think they can do with the information, and whether your data collection is actually necessary for the purpose you say it serves.

What is an emergency contact?

An emergency contact is the person your business can try to reach if an employee has an accident, medical episode, or urgent welfare issue connected with work. In most workplaces, this is an operational and health and safety measure.

For example, if a staff member collapses on site, is taken to urgent care, or is involved in a serious incident while travelling for work, your business may need to notify somebody quickly. That is the core purpose of collecting an emergency contact.

What is next of kin?

Next of kin is not a standard employment law concept. It usually refers to a person’s closest family member or someone they identify as their nearest relative.

In business practice, the problem is that the term carries assumptions. Managers may assume the next of kin must be contacted first, has authority to receive detailed information, or can make decisions on the employee’s behalf. Often, none of those assumptions is correct.

Why the distinction matters

The main legal issue is purpose. Under New Zealand privacy principles, personal information should be collected for a lawful purpose connected with your business functions, and the information collected should be necessary for that purpose.

If your purpose is emergency notification, asking for “next of kin” can be too vague and potentially misleading. The wording does not clearly tell the employee what you need the information for. It can also encourage your business to collect extra personal information that is not needed.

This is where founders often get caught. They copy a form from another employer, leave an old “next of kin” field in the HR platform, and never explain the difference. Later, when something goes wrong, the business is left guessing who to contact and what it is permitted to say.

What employers normally need to collect

In many cases, the minimum useful emergency contact details are:

  • the contact person’s full name
  • their relationship to the employee
  • a primary phone number
  • sometimes a secondary phone number

You may not need the contact’s address, date of birth, or other personal details unless there is a genuine operational reason. Asking for more information than you need increases your privacy risk without giving much practical benefit.

What employers should not assume

A listed contact is not automatically authorised to:

  • make medical decisions for the employee
  • receive full details about the employee’s health
  • change employment arrangements
  • collect final pay information or employment records
  • act for the employee after death

If a serious event occurs, your team should still be careful about what information is disclosed and to whom. An emergency call may justify limited information, but that does not mean unrestricted sharing.

Where this shows up in real workplaces

This issue often appears in ordinary founder moments, not just major emergencies. Before you hire your first worker, you may prepare a one-page employee details form and wonder what to ask for. Before you sign with a payroll or HR software provider, you may accept a standard template that uses outdated terminology. Before you rely on a verbal promise from a manager that “we only use it in emergencies”, you need to check whether your documents and employee privacy notice actually say that.

If you use casual staff, shift workers, field technicians, drivers, or lone workers, clear emergency contact wording is even more important. In those settings, the business may need to act quickly, and confusion around who should be contacted can waste valuable time.

The safest approach is to treat emergency contact details as employee-related personal information collected for a specific workplace purpose, then make sure your forms, policies, and internal practices all match that purpose.

Before you sign a new employment pack, outsource HR administration, or adopt a standard onboarding template, there are a few legal points worth checking.

Privacy Act compliance

New Zealand’s Privacy Act 2020 matters here because you are collecting personal information about both the employee and another identifiable person, the emergency contact. Even though the employee gives you the details, your business still needs a lawful and sensible reason to hold them.

Your collection notice or privacy wording should make clear:

  • what information is being collected
  • why it is being collected
  • how it will be used
  • who inside the business may access it
  • what happens if the information is not provided
  • how the employee can request correction or updates

You do not always need a long standalone privacy notice for this specific issue, but your employee privacy notice, onboarding form, or staff policy should cover the basics in plain language.

Health and safety obligations

Emergency contact information often supports your health and safety procedures. If a worker is injured or becomes seriously unwell, your business should be able to respond quickly and appropriately.

That does not create a free pass to collect whatever you like. The information still needs to be relevant to the health and safety purpose. For most roles, a name and contact number are enough.

If the role involves remote work, travel, hazardous environments, or higher safety risk, you may need more detailed procedures around emergency escalation. In that case, the legal issue is usually less about collecting more personal data and more about having a clear incident response process.

Employment agreement and policy wording

Your employment agreement does not usually need a detailed clause about next of kin or emergency contact. But your overall employment documents and workplace policies should be consistent.

Check whether your documents use mixed terms, for example:

  • the employment agreement says emergency contact
  • the onboarding form says next of kin
  • the HR system says nominee
  • the health and safety handbook says family contact

Inconsistent wording creates confusion and makes privacy explanations harder. It can also cause practical mistakes during a stressful incident.

Employers sometimes ask whether they need the emergency contact’s consent directly. In many routine cases, the employee provides the information and tells the contact they have been nominated. What matters most is that your business handles the information transparently and only uses it for the stated purpose.

A sensible process is to tell employees to provide details only for someone who is aware they may be contacted in a workplace emergency. That keeps the process practical without overcomplicating onboarding.

Access and disclosure limits

Not everyone in the business needs access to emergency contact details. Usually, access should be limited to people with a genuine need, such as HR, payroll administrators where relevant, a business owner, or specific managers responsible for incidents.

Before you accept the provider’s standard terms for HR software or a shared admin system, check who can view personnel records and whether access permissions can be limited. This is especially important in smaller businesses where one shared spreadsheet can end up being visible to too many people.

Retention and updates

Emergency contact details go stale quickly. Staff move flat, change relationships, separate from partners, or prefer a different support person. A contact record that has not been reviewed for three years may be worse than useless.

Build updates into ordinary HR practice:

  • ask new starters to confirm the details during onboarding
  • prompt staff to review them annually
  • request updates after a name change or major personal change, where appropriate
  • remove the details when they are no longer needed, subject to your lawful record-keeping requirements

Special situations

Some workplaces deal with more complicated scenarios. An employee may not want a spouse contacted. They may nominate a friend instead of a family member. They may have a protection or safety concern that makes one contact unsafe to call.

Your form should allow the employee to choose the right person for an emergency. This is another reason “next of kin” can be the wrong label. It pushes people toward a family-based answer when the actual need is an emergency response contact chosen by the employee.

Common Mistakes With Next of Kin Vs Emergency Contact

The biggest mistake is using familiar wording without checking what problem the information is meant to solve.

Once that happens, a series of smaller issues usually follows. Here are the ones we see most often in business documents and HR processes.

Using the wrong label on forms

If your actual purpose is emergency notification, calling the field “next of kin” is a drafting problem and a practical problem. It is not just semantics. The label can affect who an employee names and what your team thinks they can do with that information.

A cleaner option is wording such as “Emergency contact details” with a short explanation that the person may be contacted if there is an urgent workplace health, safety, or welfare issue.

Collecting more information than needed

Founders sometimes build long onboarding forms because it feels efficient to gather everything at once. But personal information should be collected with a purpose. If you do not need a contact’s address or other background details, leave those fields out.

The main risk is not only privacy complaints. Extra data also creates extra admin, more opportunities for error, and more information to protect if systems are lost or accessed improperly.

Assuming family status equals authority

A common misunderstanding is that a spouse, parent, or adult child can automatically direct the business or receive all information about the worker. That is not how authority works.

Your managers should know the difference between:

  • contacting someone to let them know there has been an emergency
  • sharing limited necessary information
  • handing over confidential employment or health information
  • acting on instructions from a third party

Those are different steps, and each needs judgment.

Leaving privacy wording too vague

Another mistake is burying emergency contact collection inside a broad statement that the business may collect “personal information for employment purposes”. That wording is often too general to be useful to staff or managers.

Specific plain-English wording is better. Staff should understand why the information is being requested and how it will be used. Clear wording also helps managers avoid using the information for unrelated reasons.

Failing to update records

People change jobs, relationships, homes, and phone numbers. If your records are outdated, the person you contact in an emergency may be unreachable or may no longer be the person the employee wants involved.

This problem is especially common in fast-growing businesses that onboard quickly but do not revisit personnel data later.

No internal process for emergencies

Even good forms are not enough if no one knows what to do in practice. If an incident happens after hours, on a work trip, or at a client site, who is authorised to access the contact details? What information can they share? When should senior management be told?

A short internal process can answer those questions. Without one, staff may over-share, under-share, or delay action while trying to work out what is permitted.

Copying overseas templates

Many businesses use template HR documents from Australia, the United Kingdom, or software libraries built for multiple countries. Those documents may use language that does not fit your New Zealand privacy practices or your actual workplace procedures.

Before you sign or roll out a template, check whether the terminology matches what your business really needs. Small wording fixes can prevent bigger confusion later.

FAQs

Should New Zealand employers ask for next of kin or emergency contact?

Usually, employers should ask for an emergency contact. That term is clearer and better matched to the purpose of contacting someone during a workplace emergency.

No. Being listed as next of kin does not automatically give someone legal authority to make employment, medical, or financial decisions for the employee.

Can we keep emergency contact details in the employee file?

Yes, if the information is collected for a clear workplace purpose and stored securely. Access should be limited to people who genuinely need it.

Do we need to tell employees why we collect the details?

Yes. Your forms or privacy wording should explain why you are collecting the information, how it will be used, and who may access it.

What should we do if an employee does not want to list a family member?

Let them choose the person they want contacted in an emergency. The right contact may be a friend, partner, flatmate, or another trusted person, not necessarily a relative.

Key Takeaways

  • For most New Zealand employers, emergency contact is the right term to use, not next of kin.
  • The difference matters because next of kin does not automatically have authority to make decisions or receive unrestricted information.
  • Collect only the details you reasonably need for emergency notification, and explain the purpose clearly.
  • Make sure your onboarding forms, privacy wording, HR systems, and health and safety processes all use consistent language.
  • Limit access to emergency contact details, keep records secure, and review them regularly so they stay accurate.
  • Train managers on what they can and cannot disclose if they need to contact someone about an employee emergency.

If you want help with employee onboarding documents, privacy wording, HR policies, and incident response procedures, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

Get your customer-facing terms right

What should your privacy and online terms cover?

If you collect customer data, sell online or run marketing campaigns, your public terms and privacy documents should match the real customer journey.

Alex Solo
Alex SoloCo-Founder

Alex is Sprintlaw’s co-founder and principal lawyer. 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.

Get your customer-facing terms right

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.