Australia: But I want to keep making it! Who owns a signature dish when the chef responsible moves on?

Restaurants should ensure their employment contracts are clear about the ownership of recipes created in their kitchens.

A public dispute between an award-winning restaurant in Brisbane and its former head chef highlights an interesting issue as to who owns the rights to, and is therefore allowed to market, a signature dish when the relevant chef and restaurant part ways.

Followers of the gourmet food scene in Brisbane will most likely be familiar with the restaurant "Public", located in North Quay within the CBD. An extremely popular dish on the restaurant's menu is the "KFD (Kentucky Fried Duck)", which was reportedly created by chef Damon Amos when he worked at the restaurant in 2012.

Mr Amos left the restaurant in or about July 2015, and has opened a new restaurant in Woolloongabba on the outskirts of the CBD, called "Detour". Mr Amos wants to feature "KFD" on his new menu, but has publicly expressed his desire for Public to stop including the dish on its menu, which continues to be a highly sought-after dish for diners at Public. In fact, a number of the dishes reportedly served at Detour will be familiar to those who have dined at Public, with ants, fossilised carrots and lychees featuring prominently.

The question also came up recently in a decision decided by the District Court of Florida in Vraiment Hospitality LLC v Binkowski, in which the plaintiff alleged that, after a joint venture between the parties had failed, the defendant had started a further venture which served a "salted caramel brownie" recipe that the plaintiff had contributed to the joint venture.

The question became: can a chef demand that a former employer stop including certain dishes on its menu and, if so, when?

Does intellectual property law in Australia provide protection over recipes?

The issue is one that involves both a consideration of who owns any intellectual property rights that arise from the recipe, and whether those rights have been varied by the terms of the relationship between the restaurant and the chef. Looking first at the relevant areas of intellectual property as they relate to recipes:

  • the written form of the recipe can attract the protection of copyright, for example, if the recipe is recorded in a cookbook or something similar. This will, of course, only protect the author in so far as someone attempts to copy the exact form of the recipe. It will not protect the actual substance of the recipe, just the way it is expressed.
  • section 50(1)(b) of the Patents Act 1990 (Cth) states that an application for a patent may be refused where it the relevant invention is:
    • a substance that is capable of being used as food, and is a mere mixture of known ingredients; or
    • a process producing a substance that is capable of being used as food by mere admixture.
      This largely prevents the obtaining of patent protection for a recipe, unless it is particularly unusual or novel.
  • while it may theoretically be possible to obtain protection under the Designs Act 2003 (Cth) for the way in which the dish is presented, this would only protect the way in which the recipe is plated. It would not stop others from making a dish that tasted the same but looked slightly different.
  • it may be possible to obtain protection over a recipe as a "trade secret". KFC's Kentucky-Fried Chicken is one of the most famous examples of such protection being effective. Until very recently, McDonald's "Big Mac Special Sauce" was another. Obtaining protection in this regard however, requires that the recipe remain confidential and will remain effective only until a similar recipe is produced, or the original recipe is reverse-engineered.

The above discussion demonstrates that, unless a chef keeps his or her recipes for the most part secret, it is unlikely that they will be able to effectively protect them. Assuming, however, that trade secret protection can be obtained, the more pressing issue is which party obtains the benefit of that protection: the restaurant or the chef?

The answer will depend, to a large degree, upon:

  • the terms of the chef's engagement by the restaurant;
  • the time and manner in which the chef discovered upon, or created, the recipe and the supplier of the equipment and ingredients used.

What are the terms of the chef's engagement?

It is relatively commonplace in employment agreements for there to be intellectual property and confidential information clauses or similar included - that is, terms that make it clear that:

  • any intellectual property (which would include recipes that can satisfy the requirements of a trade secret) created by the employee in the course of the employee's employment is owned by the employer; and
  • information obtained during the course of the person's employment is, and remains even after the employment relationship is at an end, the confidential information of the employer and is not to be used outside of the course of the employee's employment.

It is also not uncommon for employers to include a waiver of moral rights clause or similar in relation to any works in which intellectual property rights might subsist. Additionally, section 35(6) of the Copyright Act 1968 (Cth) makes it clear that, as a general rule, an employer will own the copyright in works created by an employee in the course of their employment.

In circumstances where such clauses have been included when defining the relationship, it would become a relatively straightforward exercise for an employer to prevent someone in the position of Mr Amos using dishes devised during his time at a relevant restaurant from serving them at other restaurants after their relationship ends.

The position can be complicated slightly, however, where the chef alleges that the devised the dish in their own time, or outside of the course of their employment, or where the terms of the employee's contract are silent as to ownership of such intellectual property.

The default position is that the inventor of the relevant intellectual property is the owner of it, however where the person is employed in a role where invention of such items falls within the scope of their duties, the invention can be said to be owned by their employer. One expects that it could be a difficult exercise for an employee in the position of a former head chef of a restaurant to rebut the assertion that he or she was expected to devise new recipes and dishes to be served on the menu; indeed, that is often a key part of their role and could arguably be defined as a "duty to invent". Where the task of writing the relevant menu and implementing new dishes into it was specifically outlined in the chef's role, this duty to invent could be seen as an express duty within their employment. If it were not, you would expect the argument that such a duty should be implied.

In those circumstances, recipes and dishes which are produced whilst employed would be properly the property of the restaurant.

What about recipes that the chef brings to the restaurant?

A different result may arise in circumstances where a chef brings a particular technique, recipe or dish to a restaurant and includes it on the venue's restaurant unaltered and without need for further refinement through any equipment or ingredients supplied by the restaurant beyond those used prior.

In that circumstance, the chef is likely to argue that any rights that attach to that recipe (such as those arising out of categorisation as a trade secret) remain those of the chef.

However, a restaurant may seek to attack a chef's assertion that the recipe should receive such protection; for example:

  • if the chef shared the key components, or "secrets" of the recipe freely with other employees of the restaurant, customers and the like, it is unlikely that the chef could satisfy the confidentiality requirement of trade secrets. However, if he or she confidentially disclosed the recipe only to those who needed to know in order to assist to make it, and required that they not share the information, the result may differ.
  • similarly, the absence of any effort by the relevant chef to obtain a licensing arrangement with the restaurant upon placing the recipe on the restaurant's menu might be used as an inference that the chef did not actually protect the secrecy of the recipe and thus it should not be seen as a trade secret. This would not be conclusive however, if a chef shared the recipe with those within the restaurant freely without any effort to ensure that the restaurant knew that the chef wished to retain the information. It would be difficult in those circumstances for a chef to argue that it should be considered a "trade secret".
  • where the recipe in question can be reverse-engineered relatively easily, or is generic, Courts are unlikely to find that they will constitute trade secrets. In the highlighted decision of Vraiment Hospitality LLC, the Court held that the recipe was broadly available save for one alleged "secret ingredient" which, upon tasting the brownie, was not hard to decipher. As such, it was determined not to be a trade secret.

How should restaurants deal with this issue?

The difficulty highlighted above in establishing that something is a "trade secret" means that, to a large extent, restauranteurs are likely to expect that it will be a difficult exercise for a chef to prevent them from serving a dish that the chef implemented on their menu during their time as an employee. However, to ensure that there is no confusion:

  • restaurants should ensure that examples of the types of clauses discussed above are included in their contracts of employment for chefs expected to have any significant input into what is served in the restaurant.
  • if a chef is brought to a restaurant with the intention to serve a dish known to be in their repertoire, the rights of the restaurant to continue to use it after the chef departs should be discussed and any agreement documented at the outset.

In extreme cases (but certainly where recipes for particular dishes are known to be signatures of a particular restaurant), it may be prudent to have employees who are given details of the recipe sign separate non-disclosure agreements relevant to that disclosure, so as to ensure that any protection gained by its characterisation is not lost, and the restaurant's position is protected.

While this may seem dramatic, the scenario considered in this article as between Public and Mr Amos demonstrates that such steps may assist in avoiding any public reputational damage that could be suffered by either party.


Clayton Utz communications are intended to provide commentary and general information. They should not be relied upon as legal advice. Formal legal advice should be sought in particular transactions or on matters of interest arising from this bulletin. Persons listed may not be admitted in all states and territories.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Some comments from our readers…
“The articles are extremely timely and highly applicable”
“I often find critical information not available elsewhere”
“As in-house counsel, Mondaq’s service is of great value”

Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.