In this article
A chef resigns, opens two streets over, and within two months your signature dish is — almost word for word — on his menu. The first question every owner asks is: is that even allowed? The answer is almost always yes, and the reason is that almost nobody has set up even one of the four layers that could ever protect a recipe.
The layer that doesn't exist
Start with what doesn't exist, because that is where most of the confusion lives. Nowhere in the European Union is there a right that protects a cooking method, a recipe or a combination of ingredients as such. No patent — a patent protects a technical invention that must be novel, and "more butter, less cooking time" is not an invention in that sense. No copyright on the taste itself — that has been explicitly excluded by the EU's own Court of Justice. No automatic ownership just because you thought of it first.
That is not an oversight by lawmakers. A cooking method is an idea, and intellectual-property law across the whole EU never protects a bare idea — only the concrete form it was fixed in, or the circumstances under which it was kept secret. Once you understand that, the rest of this article falls into place: every layer below protects something OTHER than the recipe itself, and three of the four never touch the problem your business is actually asking about.
Four layers, weakest to strongest
Four legal instruments come close to "protecting a recipe", and they do fundamentally different things. Weakest to strongest — and from almost never useful to what actually does the most work in practice.
1. Copyright: protects the card, never the cooking
Copyright arises automatically the moment you fix something original — a text, a photo, a drawing. A recipe you write down, in your own words, falls under that in principle: nobody may copy your recipe card word for word without permission. But that is the only thing protected. The method itself — the order of steps, the temperatures, the ratios — is not a "work" in the copyright sense, and is therefore free for anyone to reproduce as long as they do not copy your text.
The EU's Court of Justice said so explicitly in Case C-310/17, Levola Hengelo BV v Smilde Foods BV (judgment of 13 November 2018): the taste of a food product cannot be protected by copyright, because a taste cannot be pinned down with the precision that a "work" under the Copyright Directive requires. A competitor who tastes, reverse-engineers and rewrites your dish in their own words infringes no copyright — however identical the result tastes.
2. Trademark: protects the name, not the dish
A trademark registration protects the name under which you sell something — "Chez Marie's Flemish Stew", say — not the dish behind it. A competitor may copy your exact recipe as long as they put it on their menu under a different name, and the reverse is also true: someone using your name for a completely different dish DOES infringe your trademark. It is the mirror image of what an owner actually wants to protect.
Anyone who genuinely needs to lock down a specific name should read on in trademark protection for your restaurant — that guide covers exactly that: the name, the logo and how to register them. For the recipe itself, a trademark offers nothing.
3. Trade secret law: the only layer that can genuinely win a recipe
Directive (EU) 2016/943 on the protection of trade secrets is the only EU-wide rule that can protect a recipe as such — provided you meet three conditions. The information must be secret, it must derive commercial value from that secrecy, and — this is the point where almost every business fails — you must be able to show that you took reasonable steps to keep it secret.
That last condition is not a formality; it is the heart of the law. A recipe binder left openly in the kitchen, a group chat where the whole team shares the method, or a trainee who shadows for three days and sees everything — those are all circumstances under which a court will find that no secret ever existed to protect. Without demonstrable measures there is legally nothing to fall back on, which is exactly why this layer is almost never invoked: nobody set it up in advance.
4. Contract: what actually does the work
A non-disclosure agreement (NDA) and a non-compete clause are not intellectual property at all — they are simply a contract, and that is exactly why they work best. They apply the moment someone signs, they require no proof afterwards that something was "original" or "secret enough", and they are the only layer that can stop someone BEFORE the damage is done, rather than suing for compensation years later.
The non-compete clause of a departing head chef is the best-known form, and the conditions under which it holds up — salary threshold, compensation, duration — vary sharply per EU country. Those figures are worked out in non-compete clauses: what happens when your chef leaves. For the recipe itself, a simple NDA is often enough: new staff sign for confidentiality before they ever see the recipe binder, full stop.
On one axis: how often each layer actually helps against a STOLEN RECIPE — not a stolen name, not copied text.
"Often" here does not mean "legally strong in general" — trade secret law is a solid regime on paper. It means: how often this layer actually saves you when one specific recipe gets stolen, given what most businesses have or haven't set up beforehand.
What actually happens when a chef leaves
Four layers on paper is one thing; what happens in practice when it goes wrong is another. This is the sequence as it usually plays out — and what each layer can still do for you at each point.
Three moments, and at each one which layer carries the most weight.
At this point nothing is lost yet. If a Contract: what actually does the work was signed, it applies from this exact moment — this is the only point where you can still PREVENT rather than repair.
Legal in itself: someone may open a business elsewhere. The question now is what they took with them. Without a breached Contract: what actually does the work, you have nothing concrete at this point, even if it already feels like theft.
Only now does it become clear exactly what was taken. This is the point where most owners call a lawyer for the first time — and where a Trade secret law: the only layer that can genuinely win a recipe set up in advance is the difference between a strong case and a feeling of injustice with no evidence.
Notice how the strongest layer shifts as time passes. On day 0, a properly drafted contract is your best card. By month 2 the damage is already done — even the strongest layer is now mostly about claiming compensation, not undoing what happened.
The recipe protection score
"Reasonable steps" is not a vague phrase — it is a concrete list of things a court checks. Tick what you already do and see immediately where your trade secret would hold up today, and where it wouldn't.
Your recipe protection score
Nine questions, taken directly from the "reasonable steps" test in Directive (EU) 2016/943. Nothing is sent or stored — everything runs in your browser.
—
This score is a practical translation of the legal test, not legal advice. Whether a court finds your measures "reasonable" depends on your specific situation and on the country the case is heard in.
What you can do today
- Write down your most important recipes, on paper or digitally, and literally mark them "confidential" — it costs nothing and is the foundation of every other measure.
- Have every new hire sign a short confidentiality clause before their first shift, separate from a full employment contract.
- Limit who may see the full recipe binder to a small team, and keep track of who has access.
- Agree explicitly on what may and may not be shared when someone leaves — a confidentiality reminder takes a five-minute conversation.
- If a name has genuinely become your identity, register it — but treat that as the last step, not the first.
Protection isn't a law, it's a habit
The uncomfortable truth is that three of the four layers almost never do anything for a stolen recipe. Copyright protects your text, not your method. A trademark protects your name, not your dish. What's left is a regime that only works if you set it up beforehand, and a contract that only applies if something was signed.
That is exactly why most owners end up empty-handed when it happens: not because the law fails them, but because nobody ever walked through the nine questions above before a chef walked out the door.
Do the same for the rest of your business. A registered trademark protects your name, a properly drafted non-compete clause protects what a departing key employee may do, and together they cover exactly the gap a recipe alone can never close.