Contract Review Checklist for New Zealand Security Companies

If you run a security company in New Zealand, a bad contract can lock you into underpriced work, unclear responsibilities, and risk that should never have been yours. Founders often sign a client's standard agreement too quickly, assume insurance clauses are routine, or rely on verbal promises about hours, patrol scope, alarm response times, or liability caps. Those mistakes usually only show up once there is a complaint, damage claim, non-payment issue, or staff problem on site.

A proper contract review checklist for security company work helps you spot those issues before you sign. It tells you what the agreement really says about services, performance standards, cancellations, subcontracting, privacy, payment terms, and who carries the risk if something goes wrong. If you provide guarding, mobile patrols, alarm monitoring support, event security, concierge services, or site access control, this guide sets out the key legal points New Zealand businesses should review before accepting the other side's written terms.

Overview

A security services contract should clearly match the real job, the real risks, and the commercial deal you actually agreed. The goal is not to make every contract long or complicated, it is to make sure the contract allocates responsibility in a fair and workable way before you commit staff, equipment, and insurance cover.

A practical contract review usually focuses on whether the contract properly defines the services, protects your payment position, limits unfair liability, and deals with privacy, staffing, and termination rights in a way your business can actually comply with.

• Check the scope of services, service levels, site instructions, and response times.
• Review payment terms, price adjustment rights, extra charges, and dispute rules.
• Confirm liability limits, indemnities, exclusions, and insurance obligations.
• Look at term length, renewals, termination rights, and notice periods.
• Check staffing obligations, subcontracting rights, health and safety responsibilities, and client cooperation duties.
• Review privacy, confidentiality, data handling, and access to incident records or CCTV material.
• Confirm who owns reports, procedures, and other intellectual property created under the contract.
• Make sure variations must be in writing and that verbal promises are not left hanging outside the agreement.

What Contract Review Checklist for Security Company Means For New Zealand Businesses

For a New Zealand security business, contract review means checking whether the written agreement matches your operations, your legal obligations, and the level of risk your business can actually carry.

Security work is different from many other service contracts because the service often involves vulnerable premises, after-hours attendance, emergency decision-making, personal information, and the possibility of theft, damage, injury, or false expectations about what your staff can prevent. A contract that looks standard can still create serious exposure if it assumes you guarantee outcomes instead of providing agreed services with reasonable care and skill.

In practice, this review matters most in founder moments such as these:

• before you sign a large commercial client's standard services agreement
• before you accept a shopping centre, construction site, school, or event venue contract
• before you agree to take over an existing site from another provider
• before you rely on a verbal promise that staffing numbers or patrol hours can be adjusted later
• before you spend money on setup, uniforms, site-specific inductions, vehicles, or technology for the job

Why security contracts need extra care

The main risk is expectation gap. A client may assume your guards are responsible for stopping all theft, property damage, trespass, or misconduct, even where the contract only covers observation, reporting, and basic response procedures.

If the contract does not clearly explain the service boundaries, you may face arguments about underperformance after an incident, even if your team followed the agreed site instructions. This is where founders often get caught.

New Zealand legal context

Your contract sits alongside general New Zealand contract law and wider business obligations. Depending on the services and client type, issues may also overlap with the Fair Trading Act 1986, the Consumer Guarantees Act 1993 in some cases involving consumers rather than business-to-business contracts, the Privacy Act 2020, employment obligations, and health and safety responsibilities.

That does not mean every contract needs pages of legal theory. It means the agreement should accurately describe what you do, what you do not do, and how problems are handled if the service is disrupted or an incident happens.

What a review is trying to achieve

A good contract review is not just about finding legal wording that sounds risky. It is about answering practical questions that affect your margins and operations.

• Can you realistically meet the service levels with your current team and systems?
• Will you be paid on time, including for variations, overtime, and urgent call-outs?
• Have you agreed to liability clauses that go beyond your fee level or insurance cover?
• Do you have enough control over rosters, replacements, and subcontractors?
• Can the client terminate too easily after you have incurred setup costs?
• Does the contract deal properly with complaints, incident reporting, and investigations?

If the answer to those questions is unclear, the contract probably needs work before you sign.

Legal Issues To Check Before You Sign

Before you sign, make sure the contract says exactly what your security company is being hired to do, what it is not responsible for, and what happens if the arrangement changes.

1. Scope of services and site instructions

The scope should be specific enough that both sides can tell whether the service has been performed. Generic wording such as "provide security as required" is usually too vague.

The agreement should spell out details such as:

• guarding hours and roster expectations
• mobile patrol frequency and route assumptions
• alarm response obligations and expected attendance windows
• event security duties, crowd control expectations, and access rules
• concierge or front desk duties that sit alongside security work
• incident reporting requirements and escalation paths
• site-specific instructions, including keys, access cards, lock-up procedures, and emergency contacts

If the client wants broad flexibility, include a written variation process. Otherwise, the scope can drift without a matching fee increase.

2. Service levels and unrealistic guarantees

Your contract should promise a service standard you can control, not an outcome you cannot guarantee.

Security providers should be careful with wording that suggests you guarantee no theft, no trespass, no vandalism, or constant prevention of all incidents. A fair contract usually states that you will provide the agreed services with reasonable care and skill, follow site procedures, and report incidents promptly. That is very different from promising that loss will never occur.

3. Fees, invoicing, and price changes

Payment clauses should protect cash flow and reflect how security work actually changes over time.

Check whether the contract covers:

• hourly rates, fixed fees, minimum call-out charges, and public holiday rates
• billing frequency and payment deadlines
• late payment consequences
• reimbursement for equipment, parking, consumables, or site-specific costs
• fee increases for wage changes, increased compliance costs, or expanded scope
• charges for urgent extra shifts, overtime, or extra reporting requests

If pricing is fixed for a long term without any review mechanism, the contract can become unprofitable very quickly.

4. Liability, indemnities, and exclusions

This is often the most heavily negotiated part of a security agreement because the dollar value of a claim can be far greater than the contract fees.

Focus on whether your liability is capped, whether indirect or consequential loss is excluded, and whether the client is asking for broad indemnities. A clause that makes you liable for "all loss arising in connection with the services" may be far too wide, especially if the client controls site security systems, lighting, keys, or staff access procedures.

Many security companies try to align liability caps with a multiple of fees paid under the contract or available insurance. The right position depends on the job, but unlimited liability should raise immediate concern.

5. Insurance requirements

Insurance wording needs to match the policies you actually hold and the limits your broker has arranged.

Check the types of insurance required, the minimum cover limits, and whether the contract imposes notification obligations, certificates of currency requirements, or unusual endorsements. If the client requires cover you do not carry, do not assume it can be arranged cheaply or quickly. Confirm it with your broker before you sign.

6. Term, renewal, and termination rights

A workable security contract gives both sides clear exit rights without unfairly exposing you to stranded costs.

Review the initial term, any automatic renewal, termination for breach, termination for convenience, and notice periods. If you need to recruit, train, and induct staff for a site, a client right to terminate on a few days' notice may leave you carrying avoidable losses. It can also create employee management issues if the contract disappears without warning.

7. Staff, subcontractors, and replacements

The contract should let you manage your workforce properly while still meeting reasonable client standards.

Watch for clauses that:

• require named personnel only, with no practical replacement process
• stop you from using subcontractors or casual coverage at all
• let the client reject staff without clear grounds
• shift all induction and training cost to you without limit
• attempt to restrict your ability to roster staff safely and lawfully

If the client needs key personnel for a sensitive site, that can be documented, but there should still be a clear process for illness, leave, emergencies, and performance management.

8. Privacy, confidentiality, and data handling

Security companies regularly handle sensitive information, including incident details, contact information, access logs, CCTV-related material, and internal procedures.

Your contract should say what information you collect, how it is used, who can access it, how long records are retained, and what happens when the contract ends. If the client provides personal information to you, or asks you to handle data on its behalf, privacy obligations should be stated clearly and aligned with the Privacy Act 2020.

9. Health and safety responsibilities

Health and safety clauses should reflect who controls the site and who controls the workers.

Clients sometimes draft these clauses as if the security provider is responsible for every safety issue at the premises. That is usually too broad. The contract should recognise shared responsibilities, including the client's role in site hazards, inductions, emergency procedures, and communication of known risks.

10. Incident reporting and evidence preservation

If something goes wrong, the contract should make it easy to establish what happened and what each party must do next.

Look for clear rules on incident reporting timeframes, access to logs, preservation of CCTV or bodycam material if used, cooperation in investigations, and authority to speak to police, insurers, or third parties. Confusion here can turn an operational issue into a legal and reputational problem.

11. Non-solicitation and staff poaching

Many security companies invest heavily in recruiting and site training. A contract can protect that investment if drafted carefully.

Some agreements include restrictions on the client hiring your guards directly during the contract or for a period afterwards. These clauses need to be reasonable to be useful, but they are often worth considering where you place staff in client-facing roles for long periods.

12. Entire agreement and variation clauses

Before you rely on a verbal promise, check whether the contract says the written document is the entire agreement.

If it does, side discussions about extra guards, notice periods, or minimum hours may not help you later unless they are written into the contract or added through a valid variation process. This is one of the simplest but most expensive mistakes SMEs make.

Common Mistakes With Contract Review Checklist for Security Company

The most common mistake is signing on the assumption that a standard client contract is non-negotiable. It usually is negotiable, especially where the wording does not fit the actual service model.

Accepting broad liability for client-controlled risks

Security providers often inherit risk for things they do not control, such as faulty alarms, broken gates, poor lighting, missing keys, defective CCTV, or inadequate staffing instructions from the client. If those risks are not carved out, you may be blamed for losses caused by the site's own weaknesses.

Failing to define the service boundary

A contract that says "security services" without detail can create disputes about what was included in the price. For example, a client may expect bag checks, detailed visitor logs, regular perimeter inspections, and written compliance reporting, even though your quote only allowed for static guarding.

Clear schedules, post orders, and written instructions reduce that risk.

Ignoring the commercial effect of termination clauses

Founders often focus on winning the work and overlook how quickly it can be taken away. A short termination for convenience clause can make a contract unstable, particularly if you had to buy equipment, assign vehicles, or recruit additional staff to service the site.

Missing fee adjustment rights

Security businesses are vulnerable to margin pressure because labour is usually the biggest cost. If the contract has no mechanism for rate review after wage increases, public holiday loading, or changes in service scope, the work may become unsustainable.

Relying on the quote instead of the signed agreement

A quote might mention the service hours and price, but the signed contract usually controls the legal relationship. If the quote and the contract conflict, the business that signed without checking may lose the benefit of the better commercial terms.

Overlooking privacy wording

Security contracts often touch personal information even where the parties do not focus on it at the start. Incident reports, access logs, and CCTV-related communications can all carry privacy implications. Weak privacy wording can lead to poor internal practices, client disputes, and unnecessary disclosure problems.

Agreeing to staffing promises you cannot guarantee

Some clients ask for the same named guards every shift or require replacement staff within unrealistic timeframes. If your contract guarantees this without qualification, you may be in breach because of ordinary staff illness, emergencies, or leave. The better approach is to commit to suitable qualified replacements and a reasonable process.

Not checking contract consistency across documents

Security arrangements often involve multiple documents, such as a master agreement, schedule of services, site post orders, health and safety annexures, confidentiality terms, and procurement conditions. Those documents can conflict.

Founders should check for inconsistencies across:

• pricing and payment terms
• hours of service
• site instructions
• liability caps
• insurance requirements
• termination rights
• reporting obligations

If the document set is inconsistent, ask for an order of precedence clause so everyone knows which document governs.

FAQs

Do New Zealand security companies need a written contract with every client?

No, not always, but a written contract is strongly recommended. Security services carry operational and liability risk, and a written agreement makes it much easier to define scope, fees, reporting obligations, and risk allocation.

Can a client make a security company liable for any theft or damage on site?

A contract can try to do that, but it should be reviewed carefully. Broad liability clauses may be unfair commercially and may not reflect what your business actually controls. Before you sign, check whether liability is capped and whether losses outside your control are excluded.

What should be included in a security services scope?

The scope should cover the exact services, locations, service hours, patrol frequency, incident response steps, reporting requirements, equipment use, and any site-specific instructions. If a duty matters to the client, it should be written down clearly.

Why does privacy matter in a security contract?

Privacy matters because security providers often handle personal information through logs, access records, incident reports, and CCTV-related material. The contract should say how that information is used, protected, shared, and returned or deleted when the engagement ends.

Should a security company accept a client's standard terms without changes?

Usually not without review. Standard client terms are often drafted to favour the client on liability, termination, and service expectations. Before you accept the provider's standard terms from the other side, check whether they fit your actual operations and insurance position.

Key Takeaways

• A contract review checklist for security company work should focus on scope, service levels, payment, liability, insurance, staffing, privacy, health and safety, and termination rights.
• The contract should describe what your business will do with reasonable care and skill, not guarantee outcomes you cannot control.
• Unlimited liability, vague service descriptions, and easy client termination rights are common red flags.
• Site instructions, variations, and verbal promises should be documented in writing before you sign.
• Privacy, incident reporting, and client cooperation obligations matter because security work often involves sensitive information and shared operational risk.
• Reviewing the whole document set, not just the quote or cover page, can prevent expensive disputes later.

If you want help with service scope clauses, liability limits, privacy obligations, and termination terms, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.