Employee Non-Solicitation Agreement Template UK

What this UK template is for

Use this for a narrow UK post-termination non-solicitation covenant aimed at customers, prospects, staff or suppliers with whom the employee had material dealings.

This page keeps the Batch 035 family identity but rebuilds the instrument for UK use. The document uses UK workplace vocabulary, asks for status and work location, and avoids US-only concepts such as at-will employment, CAN-SPAM or FLSA where they do not belong.

The template is designed to create an auditable record. A future HR manager, payroll officer, client, employee, worker, tribunal, regulator or adviser should be able to see what was requested, approved, paid, deducted, recognised, restricted or acknowledged without reconstructing the story from emails.

How UK law changes the document

UK restrictive covenants are tested under restraint-of-trade principles. The employer should identify the legitimate business interest, limit duration and scope, and avoid using a non-solicit as a disguised non-compete.

For this reason, the page does not simply translate the US master. It changes the governing assumptions, the compliance checklist, the signature wording and the data-storage note. Where the UK has a public process or regulator guidance, the template points to that process instead of inventing a private shortcut.

The document also distinguishes acknowledgement from agreement. Many HR records need a signature to show receipt or discussion, but that signature should not accidentally waive statutory rights, settle claims, alter employment status or promise that a policy overrides the law.

What the Jotform source misses

The Jotform non-solicitation document is short and does not force the drafter to identify protected clients, staff, time period, role exposure or reasonableness. That makes it easy to draft something broader than needed.

Thin PDF templates often look polished because they collect a name, date and signature. The problem is that the legally important questions sit outside those blanks: who approved the decision, what source of law applies, what evidence supports it, whether pay or data is affected, and what response route the affected person has.

This version adds those controls. It asks for version dates, work location, policy basis, response or appeal route, and storage treatment. It also uses named clauses instead of brittle numbered self-references, because optional document blocks can change numbering during rendering.

Recordkeeping and data protection

Most documents in this batch are employment records. The ICO says organisations should give privacy information when collecting worker data and should build data protection into employment record systems. That matters for ordinary personnel documents, and even more where the document contains health, monitoring, disciplinary, performance or rota information.

Keep the completed employee non-solicitation agreement in the file where it belongs. Payroll deductions, sickness records, disciplinary evidence, performance reviews, home-working approvals and marketing lists do not all belong in the same access group or retention schedule.

Free-text boxes should be used carefully. They should record facts, reasons, decisions and next steps, not speculation, unnecessary diagnoses, protected characteristics, gossip or legal conclusions that the signer is not qualified to make.

When not to use this template

Do not use this for junior staff with no client influence, for all customers worldwide, or to stop someone accepting work where there was no solicitation. Get advice before relying on it in a dispute.

Do not use it where a collective agreement, regulator, court, insurer, public-sector procedure or prescribed statutory form requires a different document. Do not use it to punish protected activity, avoid pay, collect unnecessary medical data, make a hidden contractual variation or describe a worker as self-employed, worker or employee contrary to the reality of the relationship.

If the matter is high-value, disputed, cross-border, union-related, dismissal-related, equality-sensitive, medical, security-critical or likely to lead to litigation, use this as a drafting start only and get advice before sending it.

Clause-by-clause guide

Legitimate business interest

Legitimate business interest should be completed with UK facts: the correct party names, worker status, work location, policy version, approval route, response route and any pay, data, equality or recordkeeping effect. This clause is intentionally named so users can refer to it without relying on shifting document numbers.

Restricted customers

Restricted customers should be completed with UK facts: the correct party names, worker status, work location, policy version, approval route, response route and any pay, data, equality or recordkeeping effect. This clause is intentionally named so users can refer to it without relying on shifting document numbers.

Restricted staff

Restricted staff should be completed with UK facts: the correct party names, worker status, work location, policy version, approval route, response route and any pay, data, equality or recordkeeping effect. This clause is intentionally named so users can refer to it without relying on shifting document numbers.

Restricted suppliers

Restricted suppliers should be completed with UK facts: the correct party names, worker status, work location, policy version, approval route, response route and any pay, data, equality or recordkeeping effect. This clause is intentionally named so users can refer to it without relying on shifting document numbers.

Duration

Duration should be completed with UK facts: the correct party names, worker status, work location, policy version, approval route, response route and any pay, data, equality or recordkeeping effect. This clause is intentionally named so users can refer to it without relying on shifting document numbers.

Geographic and role scope

Geographic and role scope should be completed with UK facts: the correct party names, worker status, work location, policy version, approval route, response route and any pay, data, equality or recordkeeping effect. This clause is intentionally named so users can refer to it without relying on shifting document numbers.

Carve-outs

Carve-outs should be completed with UK facts: the correct party names, worker status, work location, policy version, approval route, response route and any pay, data, equality or recordkeeping effect. This clause is intentionally named so users can refer to it without relying on shifting document numbers.

Remedies and severance

Remedies and severance should be completed with UK facts: the correct party names, worker status, work location, policy version, approval route, response route and any pay, data, equality or recordkeeping effect. This clause is intentionally named so users can refer to it without relying on shifting document numbers.

UK compliance checklist

Check these UK points before using the employee non-solicitation agreement.

• Identify the business interest

  A covenant should protect connections, confidential information or workforce stability, not simply prevent competition.

  UK Supreme Court - Tillman v Egon Zehnder Ltd [2019] UKSC 32

• Keep duration proportionate

  The UK government has considered statutory limits on non-competes, and reasonableness remains central for employment covenants.

  GOV.UK - reform of non-compete clauses consultation response

• Use contact-based limits

  A customer restriction should usually focus on customers or prospects the employee dealt with or influenced during a lookback period.

• Separate non-solicit from non-compete

  Do not prevent all work for a competitor unless separately drafted and justified. This template is non-solicitation only.

• Avoid no-poach competition risk

  Employer-to-employer no-poach arrangements can raise competition-law issues and are not this document.

  GOV.UK - reform of non-compete clauses consultation response

• Preserve lawful responses

  The agreement should not stop a customer, colleague or supplier approaching the former employee without solicitation unless a lawful non-dealing covenant is separately justified.

How to complete this UK template

1. Identify the UK document purpose. Choose the template because it matches the UK record you need, not because the US source title is familiar. If Acas, HMRC, the ICO, a tribunal rule, a regulator or a collective agreement requires a different form or process, use that required process first and keep this document as the supporting record.
2. Use local worker language. Complete the fields with the worker status, work location, manager, dates, policy version and pay or data effect. UK law often distinguishes employee, worker and self-employed contractor, so the document should not call everyone an employee unless that is correct.
3. Check pay, data and equality controls. Before signing, check whether the document affects pay deductions, sick pay, flexible working, monitoring, medical data, religious dress, disability adjustments, trade union activity or post-termination restrictions. Those issues are where thin PDF templates usually fail.
4. Give the affected person a response route. Where the document affects a worker, give them a practical route to ask questions, correct facts, add comments, request an adjustment, appeal or escalate to HR. A signature should say whether it is acknowledgement only or agreement to a term.
5. Store it in the right file. Keep the signed document with the correct personnel, payroll, marketing, client or recognition record. Medical information, monitoring logs and sensitive complaint material should have stricter access controls and retention rules than a normal acknowledgement.

Frequently asked questions

Related templates

• Employee Confidentiality Agreement Template UK
• Employment Contract Template (UK)