Technical Redundancy In NZ: Employer Obligations And Legal Steps

Sometimes a role disappears even though the business is still operating. You haven't "lost" an employee because of their performance - the work itself has changed.

That's where people often use the term technical redundancy. For small business owners, it can be one of the trickiest employment situations to manage because it often happens during times of growth, automation, restructuring, or new systems (not just downturns).

If you're facing a "technical redundancy" situation in New Zealand (or you're worried it might be on the horizon), the key is to treat it as both a commercial decision and a legal process. Getting the process wrong can turn a genuine business change into a personal grievance - even if your business reasons were sound.

Below, we break down what "technical redundancy" commonly means in practice, when it applies, and how to run a legally robust process that's fair, well-documented, and practical for your business.

What Is Technical Redundancy (And How Is It Different From "Normal" Redundancy)?

?Technical redundancy? is not a defined legal category in New Zealand. It's a commonly used label for a redundancy that arises because of a change in the way work is done - often due to technology, systems, automation, or updated processes.

In plain terms, the business still needs work done, but:

• the work is now done by software, technology, or machinery
• the work is now done by another role as part of a restructure
• the work has been centralised, outsourced, or streamlined
• the business no longer needs the same level of manual input (for example, a workflow is automated)

This differs from redundancy caused by a downturn (like losing a key client), where there may be less work overall. With "technical" redundancy situations, work may still exist - but the specific position no longer fits the new operating model.

Importantly, redundancy is not a "quick exit" option. Even where the redundancy is genuine, you still need to follow a proper process, including consultation and good faith obligations.

When Does Technical Redundancy Usually Come Up For Small Businesses?

Technical redundancy often happens during "positive" business change - which can make it feel counterintuitive.

Common examples we see in technical redundancy scenarios include:

Implementing New Software Or Systems

You move from paper-based admin to a cloud-based system, payroll platform, or stock/invoicing software. A role that used to be full-time data entry or manual reconciliation may reduce significantly or disappear.

Automation Or Equipment Upgrades

You invest in machinery, point-of-sale systems, booking tools, or automated production processes that reduce labour requirements in a particular position.

Restructure Of Duties Or Reporting Lines

You redesign your team structure so that tasks are absorbed into a different role (for example, combining reception and admin with customer support).

Centralisation Or Outsourcing

You shift functions like payroll, bookkeeping, IT support, or logistics to an external provider or a head office team (even in a small group of companies).

Business Sale Or Operational Transition

A sale or reorganisation can change how work is performed. If you're in this space, you'll want to consider employee impacts early, including how changes interact with employment arrangements.

Even if your commercial rationale is strong, the legal risk usually arises from how you implement the change - not the decision to change.

What Are Your Legal Obligations When Managing Technical Redundancy In NZ?

In New Zealand, redundancies are heavily shaped by the duty of good faith under the Employment Relations Act 2000. That means you generally need to be open, communicative, and genuine with employees about changes that may affect their job.

For employers, a lawful redundancy usually requires two big pieces:

• A genuine business reason (the role is no longer needed, including due to technological/process change)
• A fair process (consultation, consideration of alternatives, and proper notice/entitlements)

It's also critical to remember that redundancy is about a role, not an employee. If the underlying issue is performance or conduct, that needs a different pathway (and mixing the two is where many businesses get into trouble).

Your employment documentation matters here too. Your Employment Contract may contain provisions about restructuring, consultation steps, notice periods, selection criteria (where more than one employee could be affected), and redundancy compensation (if any). If it does, you'll need to follow it.

Do You Have To Pay Redundancy Compensation?

In NZ, redundancy compensation is not automatically required by law in every case. However, you may need to pay it if:

• your employment agreement provides for it
• it's been agreed as part of a settlement
• your workplace has an established practice that creates expectations (this is fact-specific, so get advice)

Even where no compensation is payable, you still need to correctly handle final pay, notice, and outstanding entitlements (for example, annual leave).

How To Run A Legally Sound Technical Redundancy Process (Step-By-Step)

If you're time-poor, here's the big picture: a strong redundancy process is structured, documented, and gives employees a real chance to provide feedback before decisions are final.

Below is a practical step-by-step approach many small businesses follow.

1. Clarify The Business Rationale (And Document It)

Before you speak with the employee, get clear internally on:

• what is changing (system, workflow, structure)
• why it's changing (efficiency, compliance, growth, cost, quality control)
• which roles are impacted, and how
• what the proposed new structure will look like

You don't need to provide confidential commercial information unnecessarily, but you do need enough detail to show the proposal is genuine and to allow meaningful consultation.

2. Prepare A Proposal And Start Consultation Early

You'll typically start by meeting with the affected employee and providing a written proposal that covers:

• what the proposed changes are
• why the changes are being considered
• what roles may be disestablished (and why)
• any new roles being created
• the consultation timeframe and how feedback can be given

This is also a good time to encourage the employee to bring a support person to meetings if they wish.

3. Consider Feedback With An Open Mind

Consultation isn't a box-ticking exercise. You should be prepared to genuinely consider feedback such as:

• alternative ways to achieve the efficiency change
• whether the role can be adjusted rather than removed
• whether reduced hours or a different split of duties is workable
• whether training/upskilling could allow redeployment into another role

If you're considering changing hours rather than ending a role, be careful - changing hours can still be a significant employment change and needs to be managed properly. In some cases, you may want tailored advice on reducing staff hours as an alternative to redundancy.

4. Look At Redeployment And Suitable Alternative Roles

Where possible, employers should consider redeployment before finalising redundancy - especially where your business has other roles available.

"Suitable" depends on factors like:

• pay level
• required skills and experience
• location and hours
• whether training could reasonably bridge the gap

If there is an alternative role available, you should usually discuss it with the employee and give them a fair opportunity to consider it.

If more than one employee could be affected (for example, you have two people doing similar work and only one role will remain), you'll generally need a fair and objective selection approach (often set out in the proposal), and you should consult on that approach too.

5. Make A Final Decision (And Communicate It Clearly)

After consultation closes, you can make a final decision. If the decision is to disestablish the role, your outcome letter should clearly set out:

• the final decision and effective date
• a summary of consultation and the main feedback raised
• your response to that feedback (why suggestions were or weren't adopted)
• notice period and what will happen during notice
• final pay items and next steps (handover, equipment return, etc.)

If you're unsure whether your documentation and process are strong enough, it's worth getting redundancy-specific support early. Many businesses get advice at the proposal stage to reduce risk later (including help with letters and meeting steps) through a redundancy advice package.

Notice, Final Pay, And "Can We Just Pay It Out?"

Once redundancy is confirmed, your focus shifts to cleanly wrapping up the employment relationship in a way that matches the contract and NZ employment law.

Notice Periods And Payment In Lieu

Your employee's notice period will usually be set out in their employment agreement.

Sometimes you may want the employee to finish immediately (for example, due to system access, customer relationships, or a sensitive restructure). In that case, you might consider payment in lieu of notice - but only if it's allowed under the employment agreement, or the employee agrees (ideally in writing). Doing this incorrectly can create avoidable legal issues.

Annual Leave And Other Entitlements

Redundancy often raises practical questions like: "Can we require them to take annual leave during the notice period?"

Sometimes you can, but there are notice requirements and timing rules to follow under the Holidays Act 2003 (for example, employers generally need to give notice before requiring annual holidays to be taken). If you're considering this, get clear on the legal position around annual leave so you don't accidentally mishandle entitlements.

Final pay often includes:

• salary/wages up to the final day of employment
• unused annual leave (paid out)
• any contractual redundancy compensation (if applicable)
• any other amounts owing under the employment agreement (commissions, allowances, reimbursable expenses, etc.)

Be Careful With "Resignations" And Shortcuts

In a restructure, it can be tempting to offer an employee a "choice" to resign. This is risky.

If an employee resigns because they feel pressured or because redundancy is inevitable, you may still face claims. It's usually safer to run a proper redundancy process and document it clearly, rather than trying to engineer a faster outcome.

Common Mistakes Employers Make With Technical Redundancy (And How To Avoid Them)

Technical redundancy can feel straightforward ("the system does the work now"), but common process mistakes can turn it into a dispute.

Here are issues to watch for.

1. Deciding First, Consulting Second

If your meetings feel like announcements rather than consultation, you increase the risk of claims that the decision was predetermined.

2. Treating It Like A Performance Exit

Sometimes the role could be adapted, but the real issue is that the employee isn't keeping up. If performance is the issue, you may need a performance process instead. If you need a structured approach in that scenario, a performance management process is usually the more legally appropriate pathway.

3. Not Considering Alternatives Like Reduced Hours Or Redeployment

Even if redundancy is likely, you should still consider reasonable alternatives raised in consultation (and document why they won't work if you reject them).

4. Changing Duties Without Clarifying Whether It's Actually A New Role

In technical redundancy, businesses sometimes "remove" a role but then create a new position that looks very similar. That can be legitimate, but you'll need to carefully manage:

• how selection works (if multiple employees are affected)
• whether it's really a different role (or just the same role with a new title)
• whether the affected employee should be considered for the new role

5. Weak Documentation

In redundancy disputes, documentation is often what decides whether your process looks fair and genuine. Keep clear written records of proposals, feedback received, meeting notes, and final decision letters.

If you're not sure what documents you should have on file, it can help to use a structured suite and checklist so nothing gets missed, especially if you're making multiple roles redundant.

Key Takeaways

• Technical redundancy is a common label for when a role is no longer needed due to changes in technology, systems, automation, or business processes (not necessarily because the business is struggling).
• To manage technical redundancy in NZ properly, you generally need both a genuine business reason and a fair, well-documented process, including meaningful consultation in good faith.
• Redundancy is about the role disappearing - if the real issue is performance or conduct, a redundancy process may be the wrong approach.
• Consultation should give employees a real opportunity to comment, and you should consider alternatives like redeployment, restructuring duties, or (where appropriate) reducing hours.
• If multiple employees are in the affected group, you'll usually need a fair and objective selection process (and to consult on it).
• Make sure you correctly manage notice, final pay, annual leave, and any contractual redundancy compensation - and be cautious with payment in lieu of notice unless the contract allows it (or the employee agrees).
• Good documentation (proposal, feedback, decision letters) is one of the most practical ways to protect your business if the process is later challenged.

If you'd like help running a redundancy process the right way - including drafting the proposal and outcome letters and guiding you through consultation - you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

This article provides general information only and isn't legal advice. Employment law outcomes can turn on the specific facts and the wording of the employment agreement, so it's a good idea to get tailored advice before taking action.