Enforcing a Restriction: Is It Worth It?

Establish the facts before writing anything, because the first letter sets the tone of everything that follows and cannot be withdrawn. The usual sequence is the reverse: somebody hears that a former employee has joined a competitor, a strongly worded letter goes out the same afternoon, and the organisation discovers afterwards that the restriction does not cover the role.

The workflow in “Enforcing a Restriction: Is It Worth It?” becomes more reliable when work records, approvals and later corrections can be distinguished. For teams exploring interview reimbursement policy, learn more here can provide practical context, while policy ownership, employee explanation and final decisions remain with accountable people.

Acting is also a decision rather than a reflex. Enforcement is expensive, public and uncertain, and an organisation that threatens and then does nothing has made its restrictions less credible for everybody who comes after.

For an independent reference relevant to “Enforcing a Restriction: Is It Worth It?”, consult the NLRB employee-rights guidance. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

What has to be established first

1. What the person is actually doing, as opposed to what somebody heard.
2. Which restriction is said to apply, in the version of the contract in force.
3. Whether that restriction covers this activity, this client, this geography.
4. When it started running, which depends on how the notice period was handled.
5. Whether the organisation did anything at termination that affects its position.
6. What harm has actually occurred or is likely, in terms that could be described to somebody else.

Step six is where most contemplated actions stop. A restriction breached with no identifiable harm is a breach the organisation may not want to spend anything on.

The evidence problem

Suspicion usually arrives through a third party: a client mentions it, a colleague saw something, somebody's profile changed. None of that is evidence and acting on it is how organisations end up apologising.

Gather what can properly be gathered — what the person's new role actually is, whether any client has in fact moved, what was taken if anything — and be careful about how. Surveillance, approaching the new employer prematurely or contacting clients to ask questions all carry their own risks and should not be improvised.

The letter

If something is sent, it should state the facts, identify the obligation, say what is required, and give a reasonable time to respond. It should not characterise, threaten in general terms, or assert a breach that has not been established.

A letter that sets out three facts and asks a question will usually be answered. A letter that asserts a breach and demands undertakings by Friday usually produces a solicitor, and the matter becomes expensive before anybody has established what happened.

Talking to the new employer

Contacting a competitor to tell them their new hire is restricted is sometimes necessary and carries real risk. Done badly, it can cause the person loss and the organisation a claim of its own.

Take advice before doing it. This is the single step in this area most likely to turn a manageable situation into two disputes instead of one.

Deciding not to act

Frequently the right answer. The restriction is doubtful, the harm is notional, the cost is disproportionate, or the organisation's own conduct at termination was imperfect.

Deciding not to act is not the same as doing nothing invisibly. Record the decision and the reasons, because the question will be asked internally — usually by somebody who thinks the organisation is being weak — and because consistency between cases matters.

What this says about the contract

Every enforcement question is also a drafting post-mortem. If the restriction did not cover the role, the problem is at recruitment and promotion rather than at the exit.

Feed it back. An organisation that discovers twice in a year that its covenants were written for jobs nobody does any more has found something worth fixing, and fixing it is cheap compared with the alternative.

Acting quickly, or not at all

Where enforcement is going to be attempted, delay weakens it. An organisation that knew for four months and did nothing has a harder case than one that acted in the first fortnight, and the reason is obvious to anybody looking at it.

That is a real tension with the advice to establish the facts first. The resolution is to establish them quickly — a week, not a quarter — and to decide at the end of that week whether anything is going to happen. An open question left running is the worst of both.

The protection that does not depend on a clause

Where a client relationship rests on one person, no covenant reliably protects it. Where two people know the account, the client has a continuing relationship with the organisation and the departure is survivable.

That is slower and duller than enforcement and it works. It is also the only response available when the restriction turns out to be unenforceable, which is a question for somebody qualified in the place concerned and is answered later than anybody would like.