Are Restrictive Covenants Enforceable In The UK?

If you’re hiring your first employees (or growing quickly), it’s normal to worry about what happens if a key person leaves with your customer relationships, supplier contacts, or product know-how.

That’s exactly why restrictive covenants exist. But the big question we hear from founders and small businesses is whether restrictive covenants are enforceable in practice, or whether they’re just “nice-to-have” clauses that fall apart when challenged.

In this guide, we’ll walk you through how restrictive covenants work in the UK, when they’re likely to be enforceable, and how you can draft them in a way that genuinely protects your business (without going too far and creating risk for yourself).

What Are Restrictive Covenants (And Why Do They Matter For Small Businesses)?

Restrictive covenants are contract terms that restrict what a worker can do after their employment ends.

For a small business or startup, they’re usually aimed at protecting the value you’ve built, like:

• customer relationships and goodwill
• confidential information (pricing, strategy, product roadmap, internal processes)
• your team (preventing “poaching”)
• supplier and partner relationships

In practice, restrictive covenants are often included in an Employment Contract and/or in separate documents for senior hires.

Common Types Of Restrictive Covenants

Most UK employment restrictive covenants fall into a few core categories:

• Non-compete clauses – restricting someone from working for a competitor or starting a competing business for a set period.
• Non-solicitation clauses – restricting someone from approaching and trying to win over your clients/customers/suppliers.
• Non-dealing clauses – restricting someone from doing business with your clients/customers (even if the customer approaches them).
• Non-poaching clauses – restricting someone from recruiting or enticing away your employees/contractors.
• Confidentiality clauses – restricting misuse or disclosure of confidential information (this often applies during and after employment).

As a growing business, you’ll often use a mix of these. For example, a sales lead might have non-solicitation and non-dealing restrictions, while a technical lead might have tighter confidentiality restrictions and (in some cases) a short non-compete.

So, Are Restrictive Covenants Enforceable In The UK?

Yes, restrictive covenants can be enforceable in the UK - but only if they’re carefully drafted and genuinely necessary. Put another way: restrictive covenants can be enforceable in the UK, but they’re not automatically enforceable just because they’re written into a contract.

UK courts generally start from the position that people should be free to work and earn a living. So if you want to restrict a former employee, you (as the employer) need to justify the restriction.

The Two Core Legal Tests (In Plain English)

Restrictive covenants are more likely to be enforceable where:

1. You have a legitimate business interest to protect
2. The restriction goes no further than reasonably necessary

If a clause is wider than it needs to be, a court may find it unenforceable (and it may refuse to enforce it). In limited cases, the court may be able to “sever” (remove) certain wording and enforce the rest, but you shouldn’t rely on this. That’s why “copy and paste” covenants are risky - what seems normal in one industry or role can be unreasonable in another.

What Counts As A “Legitimate Business Interest”?

Examples commonly accepted in the UK include:

• Customer connections and goodwill (especially where the employee had key client relationships)
• Trade secrets and confidential information (the more sensitive and specific, the better)
• Stability of your workforce (for example, preventing a senior employee from poaching your team)

Simply wanting to stop competition because it’s inconvenient isn’t enough. But protecting relationships and know-how you’ve paid to build usually is.

What Does “Reasonably Necessary” Mean In Practice?

“Reasonable” normally comes down to:

• Duration (how long the restriction lasts)
• Scope (what activities are restricted)
• Geography (where the restriction applies, if relevant)
• The employee’s role and seniority (what access they had to clients, strategy, or confidential information)

For example, a short non-solicitation clause for a client-facing employee is often easier to justify than a long non-compete for a junior employee with no real access to sensitive business information.

Non-competes are commonly the most difficult to enforce, which is why many employers prefer tighter non-solicitation/non-dealing clauses instead. If you’re considering a non-compete, it’s worth reading about Non-Compete Agreements and how duration and job role can affect enforceability.

How To Draft Restrictive Covenants That Are More Likely To Be Enforced

If you want covenants that actually stand a chance of being enforceable, the goal is to make them specific, role-appropriate, and no broader than needed.

1. Match The Covenant To The Risk (Not A Template)

Start by identifying what you’re really trying to protect. For example:

• If the risk is client loss: focus on non-solicitation and non-dealing.
• If the risk is staff being poached: use a non-poaching clause tailored to your team structure.
• If the risk is sensitive know-how: strengthen confidentiality and IP protections.

One practical approach is to draft a “menu” of restrictions and apply them depending on seniority and access. This is especially helpful for startups where roles evolve quickly - but you still want the restrictions to stay defensible.

2. Keep The Time Period Realistic

Timeframes should tie back to a real business need, such as how long it takes for:

• client relationships to “cool off” and be reassigned
• confidential information to become outdated
• a replacement hire to step in and stabilise accounts

There isn’t a one-size-fits-all number. But as a general rule, the longer the restriction, the harder it is to justify.

If you’re unsure what’s typical (and what tends to be challenged), it helps to understand restrictive covenant time limits in the UK and how they’re assessed.

3. Be Precise About The “Who” And The “What”

Ambiguity is your enemy. Instead of trying to restrict “all clients”, consider:

• clients the employee personally dealt with
• clients they had material contact with in the last X months
• named accounts (for senior sales roles)

Similarly, define what “competition” means for your business. A blanket “you can’t work in tech” clause is unlikely to be reasonable. But “you can’t work for a direct competitor providing X service to Y customer segment” is much easier to defend.

4. Don’t Forget Confidentiality (Often Your Strongest Protection)

Even if a non-compete ends up being unenforceable, strong confidentiality obligations can still protect you from misuse of sensitive information.

Confidentiality can sit inside an employment contract. In some situations, businesses may also use a standalone Non-Disclosure Agreement for extra clarity - for example, where founders, early hires, or contractors have deep access to commercially sensitive information.

It’s also worth being clear internally about what you treat as confidential and how you protect it (access controls, password management, limiting who sees pricing models, etc.). These practical steps can matter if you ever need to show a court that the information was genuinely confidential.

5. Use Supporting Clauses Like Garden Leave (Where Appropriate)

Sometimes, a well-drafted garden leave clause can reduce your reliance on long post-termination restrictions. If someone is on garden leave, they’re still employed (and still bound by employment duties), but they’re not actively working and building relationships on behalf of your business.

This can be particularly useful for senior or client-facing roles where you want a clean handover period.

Common Mistakes That Make Restrictive Covenants Unenforceable (And How To Avoid Them)

When employers ask whether restrictive covenants are enforceable, it’s often because something has already gone wrong - a key hire has resigned, and now the business is scrambling to work out what protection it actually has.

These are some of the common drafting and process issues we see.

Using The Same Clauses For Everyone

A “one size fits all” approach is a common reason covenants fail. Restrictions that might be reasonable for a sales director may be completely unreasonable for a junior admin assistant.

Make sure the covenant reflects:

• the employee’s seniority
• their access to strategy, pricing, trade secrets, and client relationships
• the reality of your market and competitors

Going Too Broad On Non-Competes

Non-compete clauses are often the first thing founders reach for - but they’re also the easiest to overdo.

If your true concern is client poaching, you’re usually better protected by a targeted non-solicitation and non-dealing clause, rather than a sweeping non-compete that tries to block someone from working in their industry altogether.

Not Updating Contracts When Roles Change

In startups, people get promoted quickly. That’s great - but it can create a legal gap if someone started in a junior role (with light restrictions), then later became a senior person with access to major accounts or confidential strategy.

When someone’s role materially changes, you should review the contract and restrictions. This might involve a contract variation and (importantly) making sure the updated terms are properly agreed.

Weak Definitions Of “Confidential Information”

Confidentiality clauses that try to label everything as confidential can be hard to rely on. It’s usually better to define categories and give examples relevant to your business (pricing, margins, pipeline, product roadmap, supplier terms, customer lists, etc.).

If an employee does breach confidentiality, the consequences can be serious - but your ability to enforce your rights depends heavily on how your documents are drafted and what you can prove. This is why it’s worth understanding confidentiality breaches from an employer risk perspective.

What Should You Do When A Key Employee Leaves (Or You Suspect A Breach)?

Even well-drafted restrictive covenants don’t enforce themselves. If someone resigns and you’re concerned, there are sensible steps you can take straight away to protect your business - without overreacting or escalating unnecessarily.

Step 1: Check The Paperwork (And What Actually Applies)

Start by confirming what agreements apply to the employee, such as:

• their employment contract and any variations
• any confidentiality agreement
• any bonus/commission plan terms (sometimes these include restrictions)
• any settlement agreement (if relevant)

If you don’t have a signed, up-to-date contract in place, it can be much harder to rely on restrictions later - which is why getting your Employment Contract right from day one is so important.

Step 2: Manage The Exit Professionally

A structured offboarding process can reduce risk. Consider:

• reminding the employee (in writing) of their post-termination obligations
• collecting company devices and ensuring data is returned
• confirming that confidential information hasn’t been retained
• moving key client relationships to another team member quickly

If you’re using garden leave, make sure you apply it in line with the contract and keep communication clear and measured.

Step 3: Act Quickly If There Are Red Flags

If you suspect a breach (for example, clients suddenly being contacted, staff being approached, or confidential information being used), early legal advice matters.

In many cases, the options can include:

• sending a formal letter putting the former employee (and sometimes their new employer) on notice
• seeking undertakings (promises to stop the conduct)
• applying for an injunction (a court order to stop the breach)
• claiming damages (compensation) if you’ve suffered a provable loss

The right approach depends on what your contract says, the evidence you have, and what outcome you need. It’s also important to be proportionate - heavy-handed threats can backfire if your clauses are too broad.

Step 4: Use The Situation As A “Legal Health Check”

When a key person leaves, it’s often the moment founders realise their legal protections haven’t kept up with growth.

It may be a good time to review:

• whether your restrictive covenants match current roles
• whether your confidentiality and IP clauses are strong enough
• whether contractors are correctly covered (contractors need different drafting to employees)
• what access controls you have around sensitive information

These steps won’t eliminate risk completely, but they can put you in a much stronger position if you ever need to enforce your rights.

Key Takeaways

• Are restrictive covenants enforceable? Yes - restrictive covenants can be enforceable in the UK, but only where they protect a legitimate business interest and go no further than reasonably necessary.
• Restrictions should be tailored to the employee’s role, seniority, and access to clients or confidential information, rather than copied across the whole team.
• Non-competes are usually the hardest restrictions to enforce, so many businesses prefer targeted non-solicitation and non-dealing clauses where appropriate.
• Clear, well-drafted confidentiality obligations are often one of the most practical ways to protect your business, especially for startups with fast-moving strategy and product information.
• If a key employee leaves, move quickly: confirm what applies, manage the offboarding properly, and get advice early if you suspect a breach.
• As your team grows and roles change, review and update your contracts so your protections keep pace with the reality of your business.

If you’d like help reviewing or drafting restrictive covenants that fit your business (and are designed to be enforceable), you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.