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.
- Overview
Legal Issues To Check Before You Sign
- 1. Is the trigger event defined clearly?
- 2. What happens once the trigger event occurs?
- 3. Is notice required?
- 4. Is there a cure period or grace period?
- 5. Does the clause fit with the rest of the contract?
- 6. Could the clause be challenged as unfair or uncertain?
- 7. Can your business actually monitor the trigger?
- Key Takeaways
A trigger event is one of those contract terms that sounds technical until it costs your business time, money, or leverage. Many New Zealand founders sign an agreement assuming they can deal with changes later, only to find that a missed milestone, a change in ownership, or a late payment automatically activates new rights for the other side. That is where businesses often get caught.
Common mistakes are treating trigger events as standard boilerplate, failing to define exactly what counts as the event, and overlooking what happens once the event occurs. Another frequent issue is relying on a verbal explanation from the other party instead of checking the clause itself.
If you are wondering what is a trigger event in a contract, the short answer is that it is a specified event that activates a legal consequence. The real question is whether the clause is drafted clearly, fairly, and in a way your business can actually manage before you sign.
Overview
A trigger event is a defined circumstance in a contract that causes something else to happen, such as a right to terminate, a payment becoming due, a restraint ending, shares vesting, or extra obligations kicking in. These clauses are common in commercial contracts, investment documents, shareholder arrangements, leases, supply agreements, and service agreements used by New Zealand businesses.
The clause itself is not necessarily a problem. The risk sits in vague drafting, unrealistic thresholds, and consequences that are out of proportion to the event.
- Identify the exact event that activates the clause.
- Check whether the wording is objective, measurable, and easy to prove.
- Review what rights, payments, restrictions, or deadlines begin once the trigger event occurs.
- Confirm whether notice must be given, and who must give it.
- Look at any cure period, grace period, or chance to fix the issue.
- Make sure the clause aligns with the rest of the agreement, especially termination, default, and dispute provisions.
- Test the clause against real business scenarios before you sign.
What What Is a Trigger Event Means For New Zealand Businesses
A trigger event clause tells you when the contract changes gear. It names a future event and attaches a legal result to it.
In plain English, the clause answers two things. First, what event has to happen. Second, what consequence follows if it does.
For example, a software subscription agreement might say that if a customer is more than 20 working days late with payment, the provider can suspend access. A shareholder agreement might say that if a founder stops working in the business, their unvested shares are automatically bought back or lapse. A commercial lease might say that if the tenant assigns the business without consent, the landlord can terminate.
These clauses are not limited to default situations. A trigger event can also be tied to positive milestones or neutral business changes. It could be a funding round, a revenue target, a key hire, a sale of shares, a change of control, a force majeure event, expiry of an exclusivity period, or a material breach that is not remedied in time.
Where trigger events commonly appear
New Zealand SMEs are most likely to come across trigger events in the following documents:
- Shareholders agreements and founders agreements, where events can affect vesting, buy back rights, drag along or tag along rights, and decision making powers.
- Investment documents, where milestones may release funding tranches or activate investor protections.
- Supply and distribution contracts, where stock shortages, minimum order failures, or territory breaches can change rights.
- Service agreements, where non payment, failure to meet service levels, or confidentiality breaches may lead to suspension or termination.
- Commercial leases, where assignment, insolvency related events, or repeated defaults may allow landlord action.
- Loan and security documents, where missed repayments or covenant breaches may trigger default rights.
- Employment related incentive documents for senior staff, where a resignation, dismissal, or business sale can affect equity or bonuses.
Why the wording matters so much
A trigger event clause only works properly if the event is clear enough to identify. Words like “material”, “significant”, “reasonable dissatisfaction”, or “adverse change” can be useful, but they can also create arguments if the contract gives no guidance on what they mean.
Before you accept the provider's standard terms or a draft from an investor, test the clause with practical examples. Ask yourself whether an independent person could tell exactly when the trigger occurred. If the answer is no, the wording probably needs work.
This matters because once a trigger event happens, the consequence may be automatic. The other party may not need to negotiate with you first. They might gain a right to terminate, call in payment, suspend services, buy shares, or demand performance within a very short timeframe.
Examples from founder and SME situations
Consider a few common business moments:
- A founder signs a shareholders agreement that says leaving the business is a trigger event, but the document does not clearly distinguish between resignation, redundancy, illness, or mutual exit. A dispute starts later over whether the founder is a good leaver or bad leaver.
- A retailer signs supply terms that make any delivery delay by the customer in providing forecasts a trigger event for price changes. The retailer later finds costs have increased automatically.
- A business enters an exclusive distribution arrangement where failure to hit minimum sales is a trigger event that ends exclusivity. The target was unrealistic from day one.
- A SaaS customer agrees that a “security incident” is a trigger event for immediate suspension, but the term is drafted so broadly that even a minor issue can stop access.
Each example shows the same point. The clause may be commercially sensible, but only if the event and its consequences match the deal the parties actually intended.
Legal Issues To Check Before You Sign
The main legal issue is not whether trigger events are allowed, it is whether the clause is clear, enforceable, and commercially workable in your specific contract. Before you sign, check the event, the evidence, the process, and the consequence as a package.
1. Is the trigger event defined clearly?
The event should be specific enough that both parties can tell when it has happened. Vague drafting creates room for opportunistic arguments.
Look for objective measures where possible, such as:
- a payment being more than a stated number of working days overdue
- a founder ceasing to be employed or engaged by the company
- revenue falling below an agreed threshold for a defined period
- a required consent not being obtained by a set date
- shares being transferred without following pre-emptive rights procedures
If the event relies on judgment, the contract should explain the standard. For instance, a “material breach” clause works better if the agreement says what counts as material or gives examples.
2. What happens once the trigger event occurs?
The consequence should be proportionate and spelt out. This is where businesses sometimes focus too much on the event and not enough on the result.
The clause may provide for:
- termination rights
- suspension of services or supply
- acceleration of payment obligations
- loss of exclusivity
- share vesting, buy back, or transfer rights
- step in rights for an investor or principal
- extra reporting obligations
- liquidated damages or other pre-agreed outcomes
Check whether the outcome is automatic or optional. Automatic consequences can be harsh if the trigger event is minor or disputed. Optional rights can be more manageable, especially if they require notice.
3. Is notice required?
A trigger event clause often works alongside a notice provision. If the contract requires notice, the clause should say who must give it, how it must be given, and when it is effective.
This matters in practice. A party may believe a trigger event happened weeks ago, while the other side argues the consequence never took effect because formal notice was not served properly.
Before you rely on a verbal promise that “we would never enforce it that strictly”, check the notice mechanics in the signed agreement. Contract rights usually turn on the written terms, not later recollections.
4. Is there a cure period or grace period?
Many trigger event clauses are fairer if they allow time to fix the problem. A cure period gives your business a chance to remedy a breach before more serious consequences apply.
For example, a service agreement might allow 10 working days to fix a payment default after notice. A supply agreement might give 15 working days to remedy a quality issue. A shareholders agreement may distinguish between curable and non curable events.
Without a cure period, a small operational slip can produce a disproportionate legal result.
5. Does the clause fit with the rest of the contract?
A trigger event should not be read in isolation. It needs to line up with related clauses, especially:
- termination provisions
- default and breach clauses
- restraint and confidentiality obligations
- share transfer mechanics
- dispute resolution steps
- force majeure provisions
- limitation of liability clauses
- lease consent or assignment provisions
Conflicts between clauses are common in heavily negotiated agreements. One clause may say termination is immediate, while another requires notice and a remedy period. A share vesting clause may conflict with the valuation mechanism elsewhere in the document. Those inconsistencies create expensive arguments later.
6. Could the clause be challenged as unfair or uncertain?
Commercial parties in New Zealand generally have freedom to agree on trigger events, but the wording still needs to be sufficiently certain to be enforceable. If a clause is too vague, internally inconsistent, or impossible to apply, it may be difficult to enforce as written.
In standard form B2B contracts, unfair contract terms rules can also matter in some cases. Whether those rules apply depends on the contract and the parties involved, so legal advice is worth getting if the clause seems one sided or hidden in standard terms.
The Fair Trading Act can also become relevant if one party was misled about how a trigger event clause would operate. That does not mean every disagreement becomes a statutory issue, but it does mean businesses should avoid casual side explanations that contradict the contract wording.
7. Can your business actually monitor the trigger?
A clause is only useful if your business can track it. This sounds operational, but it is a legal risk issue too.
If a trigger depends on hitting revenue thresholds, delivery dates, reporting obligations, or consent deadlines, make sure someone in the business owns that process. Otherwise, you may miss the event entirely or fail to respond within the timeframe the contract allows.
This is especially relevant in growing businesses where founders sign the contract, but finance, operations, or account managers end up managing performance later.
Common Mistakes With What Is a Trigger Event
The most common mistake is assuming the trigger event clause is standard and low risk. In reality, these clauses often decide who has leverage when the relationship changes.
Accepting broad wording without examples
Founders often accept terms like “material adverse effect” or “serious misconduct” without asking how those expressions apply in their context. That may be workable in some agreements, but where the outcome is severe, the clause should include examples, thresholds, or a decision process.
Missing automatic consequences
Some businesses focus on whether the event is likely, but not on whether the result is automatic. That is risky in share documents, finance documents, and service terms.
For instance, if a change in control automatically terminates a contract, a business sale or group restructure can accidentally disrupt key supplier or customer contracts.
Overlooking notice and timing rules
A right may exist on paper but still fail in practice if your business does not follow the notice clause. Timing also matters where a remedy period runs from receipt of notice, not from the date the issue first happened.
Here is where SMEs often get caught:
- sending notice to the wrong email or physical address
- assuming informal email chains count as formal notice
- failing to keep evidence that notice was sent and received
- waiting too long and losing strategic leverage
Not stress testing the clause against real scenarios
A good drafting question is simple: what would happen if this event occurred next month? If nobody around the table can explain the sequence clearly, the clause needs refinement.
Test scenarios such as:
- a founder leaves due to burnout or illness
- a customer pays late during a seasonal cash flow crunch
- a landlord refuses consent for an assignment connected to a sale
- an investor milestone is missed by a small margin
- a supplier suffers a temporary systems outage
Real world examples expose gaps that legal language can hide.
Relying on side conversations
Businesses sometimes sign on the basis that “we would never use the clause like that”. If that reassurance matters, it should be reflected in the document itself.
Entire agreement clauses often state that the written contract contains the whole agreement between the parties. That can make it harder to rely on informal explanations later.
Forgetting the downstream impact on other documents
A trigger event in one agreement can affect another. A change in control clause in a customer contract may matter for investment documents. A founder exit trigger can affect IP assignments, restraint obligations, and governance rights. A lease default can ripple into a bank facility if premises access is central to operations.
Before you sign, think across the document set, not just within a single contract.
FAQs
Is a trigger event the same as a breach?
No. A trigger event can be a breach, but it can also be a neutral or planned event, such as a funding milestone, expiry date, change in control, or founder exit.
Are trigger event clauses enforceable in New Zealand?
Often yes, provided the clause is sufficiently clear, consistent with the rest of the contract, and not affected by other legal issues such as uncertainty or potentially unfair standard terms concerns.
Can a trigger event happen automatically without notice?
Sometimes yes. It depends on the wording. Some clauses create automatic consequences, while others require formal notice before rights can be exercised.
What is an example of a trigger event in a shareholders agreement?
A common example is a founder ceasing to work in the business. That event may trigger share buy back rights, vesting consequences, or a process for valuing and transferring the shares.
What should I do before I sign a contract with a trigger event clause?
Check what the event is, how it is measured, whether notice is required, whether there is time to fix the problem, and what consequence follows. If the clause could materially affect payment, control, termination, or ownership, get legal advice before you sign.
Key Takeaways
- A trigger event is a specified event in a contract that activates a legal consequence, such as termination, suspension, payment, or share transfer rights.
- The key drafting questions are what the event is, how you know it has happened, whether notice is needed, whether there is a cure period, and what result follows.
- Trigger event clauses commonly appear in shareholders agreements, investment documents, supply and service contracts, leases, and finance documents used by New Zealand businesses.
- The biggest risks are vague wording, automatic consequences, unrealistic thresholds, and inconsistencies with other parts of the contract.
- Founders and SMEs should test trigger event clauses against real business scenarios before they sign, especially where ownership, cash flow, or critical supplier relationships are involved.
- If you are reviewing or negotiating what is a trigger event and want help with contract drafting, negotiating termination and notice provisions, reviewing shareholder or investment documents, and checking default consequences, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.







