Non-solicitation Clauses for Quality Assurance Consultancies in New Zealand

If you run a quality assurance consultancy in New Zealand, your client relationships are often your most valuable asset. That is exactly why non-solicitation clauses matter. They are meant to stop one party from poaching clients, staff, contractors, or referral sources after a project ends, but plenty of business owners sign them without checking how wide they are, how long they last, or whether they line up with the actual commercial risk.

The common mistakes are predictable. A consultancy accepts a client’s standard terms without noticing a clause that blocks future work across an entire sector. A founder copies a restraint from another contract that is far broader than necessary. Or the agreement refers vaguely to “customers and personnel” without clearly defining who is covered. Those gaps can create real problems before you sign a contract, especially where your consultants move between client sites and build strong day-to-day relationships.

This guide explains what a non-solicitation clause for quality assurance consultancy usually covers in New Zealand, what to check before you sign, where businesses often get caught, and how to make the clause more practical and enforceable.

Overview

A non-solicitation clause is a contractual promise not to actively approach certain clients, employees, contractors, or other business contacts for a defined period. In a quality assurance consultancy, the clause should be tied to genuine business interests such as protecting client relationships, confidential information, and investment in specialist staff, rather than trying to eliminate ordinary competition.

• Check exactly who is protected, including whether the clause covers clients, prospective clients, employees, contractors, suppliers, or referral partners.
• Check what conduct is actually restricted, such as active poaching, accepting unsolicited approaches, marketing to a broad audience, or hiring through a recruiter.
• Check whether the time period and geographic scope are reasonable for the work involved.
• Check how the clause interacts with confidentiality, intellectual property, privacy, restraint of trade, and non-compete provisions.
• Check whether key terms are defined clearly enough to be workable in day-to-day business.
• Check whether the clause is mutual or one sided, especially where both parties have valuable commercial relationships.

What Non-solicitation Clause for Quality Assurance Consultancy Means For New Zealand Businesses

For New Zealand businesses, a non-solicitation clause is usually about protecting relationships, not banning competition altogether. The clause should target a real risk, such as a consultant using access gained during an engagement to lure away a client’s staff or to shift a client account to a competing advisory business.

Quality assurance consultancies sit in a relationship driven space. Your consultants may work closely with manufacturing teams, software delivery teams, compliance managers, laboratory staff, or supply chain leads. That access can create trust quickly, which is commercially valuable but also sensitive.

Because of that, clients often ask for non-solicitation language in their service agreements. A consultancy may also want similar protection in contracts with staff, contractors, subcontractors, and referral partners. The legal issue is not whether protection is allowed in principle. The issue is whether the clause goes further than reasonably necessary.

What the clause usually tries to protect

A well drafted clause normally protects a legitimate business interest. In this context, that often means:

• client goodwill built during the consultancy engagement
• confidential information about systems, testing processes, pricing, risk controls, or internal team structures
• relationships with specialist staff and contractors
• investment in training, introductions, and business development

For example, a food quality consultant embedded in a client’s production environment may learn who the decision makers are, what audit issues the business is trying to solve, and when procurement decisions are likely to be made. A software QA consultant may gain insight into budgets, project roadmaps, and the internal capability gaps a client plans to fill. A non-solicitation clause can reduce the risk that this information is used to divert work or talent unfairly.

How non-solicitation differs from non-compete

A non-solicitation clause is not the same thing as a non-compete clause. A non-compete generally tries to stop a business or individual from competing at all, or from providing similar services in a market or area. A non-solicitation clause is narrower. It usually focuses on active approaches to defined people or organisations.

That distinction matters in New Zealand because broader restraint clauses are more likely to face enforceability problems. If your real concern is poaching of named clients or key personnel, a tailored non-solicitation clause is often more realistic than a blanket ban on working in the same sector.

Who can be covered

The wording can vary a lot. Depending on the deal, a non-solicitation clause for quality assurance consultancy might cover:

• current clients the consultancy serviced during the contract period
• prospective clients the parties pitched to together
• employees and contractors introduced during the engagement
• subcontractors with specialist technical knowledge
• suppliers, certifiers, or channel partners where the relationship is commercially significant

This is where founders often get caught. A clause that protects “any customer of the client group” can be much wider than a clause protecting only customers the consultant had material dealings with. A clause covering “personnel” may be unclear about whether it includes independent contractors, secondees, and casual workers.

What counts as solicitation

Solicitation usually means actively encouraging someone to move business or employment. It can include direct contact, targeted emails, recruitment approaches, or deliberate use of relationship knowledge gained under the contract.

But not every situation is obvious. If a former client contacts your consultancy on their own, is that still banned? If you post a public job ad and a client’s employee applies, have you solicited them? If you send a newsletter to your whole database, does that count as targeting a protected client? These points should be dealt with expressly, not left to guesswork.

Legal Issues To Check Before You Sign

Before you sign a contract, the main legal question is whether the clause is clear, proportionate, and tied to a legitimate commercial interest. If the clause is too broad, too vague, or harsher than necessary, it may be difficult to enforce and harder to operate in practice.

1. Is the clause protecting a legitimate business interest?

New Zealand courts are generally cautious about restraint style provisions. A business cannot simply block another party from competing because it would prefer less competition. The clause needs to protect something recognisable, such as confidential information, customer relationships, or workforce stability.

Ask what specific risk exists in your engagement. For example:

• Will your consultants be introduced to key client contacts and procurement decision makers?
• Will they work closely with the client’s specialist quality team?
• Will they receive sensitive commercial information that could be used to target the client later?
• Has the client invested heavily in introducing your team to its network?

If you cannot identify the real interest being protected, the drafting may be too generic.

2. Are the restricted people clearly defined?

The clause should identify the protected group with enough precision that both sides can follow it. Terms like “clients”, “customers”, “staff”, and “contacts” need context.

Better drafting often distinguishes between:

• clients you directly provided services to
• prospective clients where there was a live proposal or tender
• employees you had direct dealings with
• contractors or subcontractors engaged on the project

This matters because a QA consultancy may have broad exposure to an organisation but only meaningful influence over a small group of people. Overly wide definitions can stop ordinary business development far beyond the original project.

3. Is the restricted conduct specific enough?

The clause should say what is actually prohibited. “Solicit”, “entice”, “canvass”, and “interfere with” may sound standard, but they can overlap or create uncertainty.

A practical clause should clarify whether it covers:

• direct approaches only
• indirect approaches through another business or recruiter
• accepting work from a person who approached you first
• general advertising not aimed at the protected group
• responses to public tenders or procurement processes

If those scenarios are not addressed, disputes often turn on facts neither side documented properly at the time.

4. Is the time period reasonable?

The length of the restraint needs to match the commercial context. For many consultancy arrangements, six to twelve months is more likely to be defensible than a longer period, but there is no universal rule. What is reasonable depends on the client cycle, the sensitivity of the relationship, and the consultant’s level of access.

A short diagnostic engagement may justify a shorter period than a long embedded project where the consultant became closely involved with the client’s internal team. If the contract includes cascading restraint periods, make sure they are drafted carefully and reflect a genuine attempt to use the least restrictive option that still protects the business interest.

5. Does the geographic scope make sense?

Geographic limits matter less when relationships are national or online, but they still need thought. A nationwide restriction may be harder to justify if the work only related to one site or one business unit. In specialised quality assurance services, the more useful limiter may be the identity of the protected clients rather than a broad territorial ban.

6. How does the clause fit with other contract terms?

A non-solicitation clause does not stand alone. Before you accept the provider’s standard terms, check how it interacts with the rest of the agreement and whether a broader contract review is needed.

Key areas to review include:

• confidentiality clauses, especially around client lists, pricing, testing methods, and internal procedures
• intellectual property clauses, including ownership of reports, templates, testing artefacts, and process documents
• privacy obligations and data protection, where staff or contact details are used in CRM systems or recruitment activity
• termination clauses, including whether the restriction applies on expiry, termination for convenience, or breach
• dispute resolution clauses, in case there is a disagreement about whether contact was solicited

A narrow non-solicitation clause can often do the heavy lifting when paired with a strong confidentiality clause. Without that supporting framework, businesses sometimes overreach on restraints to fill drafting gaps elsewhere.

7. Is the clause mutual?

Some engagements justify a one way clause. For instance, a client may give a consultancy unusual access to a large internal team and want protection against poaching. But many projects are more balanced. A consultancy may introduce specialist contractors, methods, and trusted delivery staff that also need protection.

If both sides bring valuable relationships to the table, a mutual clause may be more commercially fair and easier to negotiate.

8. Are there practical exceptions?

Good drafting often includes sensible carve outs. Depending on the deal, these might cover:

• general marketing not directed at protected persons
• public tenders and open procurement processes
• people who independently approach the other party without prior solicitation
• hiring through a genuinely broad recruitment process, subject to limits
• entities already in an existing business relationship before the contract started

These exceptions can make a major difference to how workable the clause is after the project ends.

Common Mistakes With Non-solicitation Clause for Quality Assurance Consultancy

The most common mistake is treating the clause as standard boilerplate when it actually controls future revenue opportunities and hiring decisions. A few lines of vague drafting can create months of uncertainty once a project wraps up.

Using a clause copied from a different industry

Quality assurance work varies widely across software, manufacturing, food, medical, education, logistics, and professional services. A clause taken from a recruitment, franchise, or pure sales contract may not fit the way your consultancy actually operates.

For example, a clause written for a recruiter may focus heavily on candidates and placements, while a QA consultancy may need more nuance around project teams, subcontractor expertise, and tender participation.

Protecting every possible contact

Founders sometimes assume wider means safer. Usually it means harder to justify and harder to live with. A clause covering every client, affiliate, employee, supplier, and potential customer of a large enterprise client may reach far beyond the relationships your team actually touched.

A narrower clause is often stronger because it is easier to connect to a genuine commercial interest.

Leaving “solicitation” undefined

If the agreement does not explain what conduct is off limits, each side may apply a different meaning after the relationship ends. One side may say a public LinkedIn post is ordinary advertising. The other may say it was aimed at protected personnel.

That uncertainty is expensive. It can also chill legitimate business activity because your team becomes reluctant to market or hire at all.

Ignoring contractor and subcontractor arrangements

Many quality assurance consultancies rely on independent contractors or specialist subcontractors. If your customer contract contains a strict non-solicitation clause, but your subcontractor agreements do not line up with it, you may face a mismatch in obligations.

For instance, your consultancy might promise not to poach client personnel, while your own contractor remains free to approach them because their contract says nothing. Consistency across your contract suite matters.

Forgetting the evidence problem

Even a well drafted clause can be difficult to rely on if the facts are fuzzy. Businesses often rely on verbal understandings about who introduced whom, whether a prospect was already in the pipeline, or whether a candidate approached independently.

Before you rely on a verbal promise, make sure the agreement and your internal records support your position. Keep written records of:

• which clients and personnel were introduced during the engagement
• who owned pre existing relationships
• which tenders or proposals were already active
• how an approach or application was first made

Using non-solicitation to replace basic contract hygiene

A restraint clause cannot fix every commercial risk. If your scope of services is vague, your confidentiality terms are thin, your IP ownership is muddled, and your contractor agreements are inconsistent, a non-solicitation clause alone will not solve the problem.

This is especially true where consultants create audit reports, process maps, testing scripts, training materials, or templates. The contract should say who owns or can use those materials after the project ends.

Agreeing to one sided terms without a pricing discussion

If a client wants a broad restriction that limits your ability to hire, market, or accept work from a segment of the market after the engagement, that is a commercial concession. It may affect how you price the project and how you allocate staff.

Too often, consultancies accept the clause late in procurement without revisiting the fee model or delivery plan.

FAQs

Are non-solicitation clauses enforceable in New Zealand?

They can be, but only to the extent they are reasonable and protect a legitimate business interest. Clauses that are too broad, vague, or punitive are more likely to cause problems.

Can a quality assurance consultancy still respond to a public tender?

Often yes, if the clause is drafted sensibly. The contract should ideally say whether public tenders, open procurement processes, and general market approaches are excluded from the restriction.

Does a non-solicitation clause stop a former client contacting us first?

Not always. Some clauses prohibit only active solicitation, while others also restrict accepting work from protected clients for a period. You need to check the exact wording before you sign.

Should the clause cover employees and contractors?

It often should, especially in specialised consulting businesses that rely on key people. The contract should be clear about who counts as protected personnel and what hiring activity is restricted.

How long should a non-solicitation clause last?

There is no fixed period, but the duration should reflect the real commercial risk. Shorter periods are usually easier to justify than lengthy restraints, particularly where the engagement was limited in scope.

Key Takeaways

• A non-solicitation clause for quality assurance consultancy should protect genuine business interests, not eliminate normal competition.
• The most important drafting points are who is protected, what conduct is restricted, how long the clause lasts, and whether the scope is commercially reasonable.
• Clear definitions matter, especially for clients, prospects, employees, contractors, and what counts as solicitation.
• The clause should work alongside confidentiality, IP, privacy, termination rights, and contractor terms rather than trying to do everything on its own.
• Founders often get caught by broad standard terms, vague wording, and missing carve outs for public tenders, general advertising, or unsolicited approaches.
• Good records and aligned contracts across staff, contractor, and client arrangements make the clause easier to manage in practice.

If you want help with contract drafting, restraint scope, confidentiality terms, and contractor agreements, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.