Latest / From Kitchen to C-Suite™ / Loose lips sink shifts: Safeguarding your kitchen, bar, and brand.
Transcript
- Brad Peters: So To the vision that This is Kitchen to see Sweet. Welcome to the show. Imagine a packed Friday night. I mean, you know the exact vibe, right? ⁓ absolutely. The dining room has that perfect low-lit hum to it. Exactly. And the ticket printer in the kitchen is just chattering away like a machine gun. Your line cooks are moving in that ⁓ that synchronized, unspoken dance. Saute pans are firing on all cylinders. It's just organized chaos. It is. It's this beautiful high wire act that you have spent Year maybe even decades, honestly perfecting. Yeah. You're standing at the pass, you're expediting plates, and you're feeling that rush of adrenaline that only comes when a service is just going flawlessly. Best feeling in the world. Right. But then, right in the middle of the seven point thirty rush, your newest prep cook decides to pull out his smartphone. ⁓ Yeah. He's standing by the walk in freezer. Maybe the delivery driver stacked the produce boxes haphazardly or You know, maybe there's a temporary spill of stock on the floor that just hasn't been mopped up yet because you're deep in the weeds. Which happens in literally every kitchen. Exactly. But he records a quick ten second panning video of the mess. He uploads it to TikTok with some trending audio track and the caption This place is a literal biohazard lol. Wow. And then he just puts his phone back in his pocket and goes back to chopping onions. He doesn't think anything of it. It's just content to him. Right. It's just a joke for his friends. But within minutes, the algorithm picks it up. It hits a local for you page, 200 views. An hour later it's at twenty thousand. The local health department gets tagged in the comments. A local food blogger reposts it. Yep. And suddenly you have a massive existential brand crisis on your hands, and you haven't even finished serving the main courses. And the terrifying part is that isn't just a hypothetical nightmare. That is the actual operational reality of the industry today. Yeah. You have A single operational moment, completely stripped of its broader context, packaged for maximum shock value, and broadcast to the world in real time. Which is exactly why we are doing this deep dive for you today. You reached out to us because you are in the middle of scaling your operation. Like you're taking your business from two locations to five this year, and you had this sinking realization. That the old school stuff doesn't work anymore. Right. The handshake agreements with your chefs that informal what happens in the kitchen stays in the kitchen mentality, it simply won't hold up in court anymore. No, not at all. So our mission today is to build your armor. We are exploring the critical triad of protection for hospitality businesses, and that means hotels, restaurants, bars, private clubs of all sizes. From mom and pop up to massive corporate chains. Exactly. We are unpacking why strict social media policies Comprehensive non-disclosure agreements and restrictive covenants are like no longer optional corporate jargon. We're gonna show you how to implement them without destroying the culture you've built. And, you know, to really understand the mechanics of this armor, we have to recognize the unique paradox of the hospitality industry. What do you mean by paradox? Well, think about the physical spaces you operate. This is an industry where incredibly private, intimate, or sensitive human behaviors Unfold in public facing spaces. Right, like dining with family or unwinding with alcohol. High stakes, corporate networking, too. It all happens in these highly scrutinized spaces. The barrier between what is private and what is public is ⁓ it's porous by design. Yeah, that makes sense. So to figure out how to seal those pores, we are pulling from a massive, incredibly diverse stack of sources today. We're looking at legal guidelines from the New York City Bar Association. We are dissecting complex national labor relations board rulings, like the famous Chipotle case. ⁓ that one is fascinating. It really is. And we're evaluating trade secret analyses from the International Journal of Law, Management, and Humanities. And we're even ripping apart the IPO prospectus of an aviation security company called Clear Secure Inc. Okay. I know you're probably driving to a supplier right now thinking, why on earth are we looking at an airport security company's financial documents to figure out my bartender's employment contract? Right, it sounds totally disconnected. But stick with us because it is gonna make perfect sense. Building a hospitality brand is like baking a delicate souffle. It takes hours of precise, dedicated work, careful measuring, perfect temperature control. And one slammed oven door ruins it. Exactly. A single loud noise, or in this case, one careless tweet from a disgruntled employee collapses the whole structure instantly. And you can't put the air back in the souffle once it falls. You really can't. So let's look at the environment that creates that risk. We are operating inside what our sources call the convenience economy, combined with the era of total two hundred and forty-seven surveillance. And you know, the word surveillance usually brings up images of security cameras on the ceiling. Yeah, like Big Brother watching you. But the reality is much more decentralized now. The surveillance state in your restaurant is the fact that every single front of house and back of house employee Have a high definition broadcast studio sitting right in their apron pocket. Yeah, their smartphone. Exactly. What the source material emphasizes, and what you really need to prepare for mechanically, is the sheer volume of operational moments that can be weaponized. The literature highlights three very specific threat vectors. Okay, let's break those down. The first is what we categorize as BOH hygiene sensationalism. Back of house hygiene sensationalism. Okay, but mechanically, how does that actually play out differently than just, you know, a customer leaving a bad Yelp review about a dirty fork? Well, the difference is the perceived insider authority. When a customer complains, they are an outsider looking in. People take it with a grain of salt. Right. But when an employee posts a video from inside the kitchen, the audience implicitly trusts it as this authentic whistleblower moment, even if it's an entirely fabricated or totally out of context. ⁓ wow. Yeah, I can see that. Take a classic kitchen prank, a line cook jokingly tosses a perfectly good piece of chicken across the prep table to another cook and they film it for last. Just blowing off steam. Exactly. And they throw the chicken in the trash immediately after, but the video cuts off before the chicken hits the garbage. I see where this is going. Right. To the algorithm and to the viewer, it looks like severe cross-contamination and a massive health code violation. This kind of sensationalism bypasses standard customer service channels. And goes directly to public health department investigations. And local news desks. Because the algorithm is literally designed to reward outrage, it doesn't pause to verify if the cutting board was sanitized afterward. It really doesn't. Okay. So that's the first vector. What is the second threat we're looking at? Customer altercations. The dynamic of dispute resolution has fundamentally changed. If a bartender gets into an argument with a patron over, say a fake ID. Or A server confronts someone about a dine and dash attempt. Right. The immediate instinct of everyone involved, including the bystanders, is to pull out a phone and live stream it. It's crazy how fast the phones come out now. It is. And the mechanical issue here is that when your employee is caught on camera arguing, even if they're entirely in the right enforcing your policies, your venue is immediately dragged into a public trial by a jury of millions of internet commenters. Because the context of the argument is totally lost. All that remains is the visual of your staff yelling at a customer. Exactly. And the internet loves to play judge and jury. They really do. Okay, so the third vector mentioned in our sources is review site retaliation, which I think is fascinating because it's no an internal breach of protocol. It is, yeah. This occurs when an employee takes a customer complaint personally. Let's say a guest leaves a mildly negative review on Google or TripAdvisor. About slow service. Nothing crazy, just a standard two star review. Right. But a disgruntled server who maybe had a bad night uses their personal account, or worse, exploits weak password hygiene to gain access to the official company account. ⁓ no. Yeah. And they respond aggressively. They might attack the customer's character or reveal personal details about the customer's visit. Like, well, you were six margaritas deep and yelling at your husband. Exactly. And this instantly escalates a manageable two star review. Into a spectacular public relations disaster. Now, the sources make an important distinction here. What's that? Large hotel chains and massive corporate restaurant groups generally absorb these social media shocks better. Let me break down why that is mechanically. A massive hotel chain has an entire Crisis communications team sitting in a corporate office in Chicago or New York. Right. They have a whole department for this. They have social listening software that flags the viral video the second it starts trending. They have pre written press releases ready to go, but you the listener scaling from two locations to five. You are the crisis communications team. You are. You are the one getting the frantic text message at midnight. And yet the liability is exactly the same. I was reading the Jeffre Mangles source on hotel liability and the legal mechanism there is genuinely terrifying. Well, it really is. It notes that operators can face direct legal liability for unauthorized posts made by their employees. So if your front desk agent posts something defamatory about a guest or reveals that a specific celebrity is staying in room 402, the hotel can actually be sued for invasion of privacy or defamation. Yeah, that legal mechanism is called respondent superior, meaning the employer is held responsible for the actions of employees performed within the course of their employment. Even if the employee was violating your verbal rules. Yes, even then. The courts often look at whether the employer provided the tools and the access that allowed the breach to happen in the first place. Wow. This is why the template provided by the New Mexico Restaurant Association such a crucial piece of source material for this deep dive. It doesn't just offer rules, it establishes a core, defensible philosophy. How so? The template recognizes that an employee's participation in social media is a personal activity on their own time. However, It explicitly constructs a legal bridge by stating that as an employee, you are a representative of the brand 2004 seven. I have to challenge this though. Let's look at it from the perspective of an operator who runs a high volume late-night dive bar. The floors are sticky, the music is loud, and the staff is edgy. That's the brand. Right. That's what people pay for. Are we really supposed to micromanage 22-year-old bartenders on their Instagram accounts? Does a local dive bar really need the same level of bureaucratic paranoia as a five-star international hotel? Doesn't that just kill the authentic culture? I see the tension there. I really do. But it isn't about paranoia, and it certainly isn't about forcing a dive bar to act like the Ritz Carleton. Okay, then what is it about? It's entirely about risk management and liability. The dive bar might not have paparazzi looking for celebrity gossip, but it absolutely have a liquor license. That can be revoked if a video surfaces of bartenders overserving clearly intoxicated patrons for a TikTok challenge. ⁓ that's a great point. Right. It has a health department rating to maintain. It has a commercial lease that likely includes a morality clause. Managing that liability requires a legally sound social media policy. You cannot simply stand in the pre-shift meeting and say, hey guys, use common sense. Don't post bad things. Because common sense is not a legally defensible standard in an employment tribunal. Precisely. To protect the business, you have to write a policy that restricts harmful behavior without violating federal law. And navigating those federal laws is incredibly tricky. That brings us to the actual mechanics of crafting the policy. We have to walk the National Labor Relations Board tightrope. And let's clear up the biggest misconception right out the gate here. ⁓ the first amendment thing. Yes. As an employer, you will constantly hear employees claim, You can't fire me for my Facebook post. I have freedom of speech, First Amendment. But legally, how does the First Amendment actually function in a private restaurant? The First Amendment is vastly misunderstood in the workplace. The text of the First Amendment restricts the government from infringing on free speech. Right. The government. Yeah. Not the manager of a steakhouse. Exactly. It does not apply to private employment. If an employee at a private company tweets that their manager is an idiot, Or that the restaurant's new uniforms are ugly, the First Amendment does not protect them from being fired. Private employers generally have the right to terminate employees for public speech that harms the company's interests. Okay, so the Constitution isn't going to stop you from firing the person who posted the messy freezer video. But there is a massive federal trap waiting for you, and it is called the National Labor Relations Act, or the NLRA. This is where it gets complicated. It really does. This law was designed specifically to protect the rights of private sector employees to join together to improve their wages and working conditions. And the mechanism it uses to do that is protecting what is called concerted activity. Let's break down the legal mechanics of concerted activity because it is the pivot point of this entire legal framework. Concerted activity occurs when two or more employees take action for their mutual aid or protection regarding the terms and conditions of their employment. So it has to be a group effort. Not always. It can also involve a single employee acting on the authority of other employees or seeking to initiate group action. And the National Labor Relations Board, the federal agency that enforces the NLRA, has definitively ruled that this protection extends fully into the digital realm of social media. Let's put a hypothetical on that so it can see how it works on the ground. Let's say your servers are frustrated because the new tip pooling system feels unfair. Very common scenario. Very common. So one of them goes home, logs onto Facebook and posts, The new tip pool at work is essentially wage theft. I'm losing fifty dollars a shift. Who else is feeling this? And then three other servers comment on the thread, agreeing and discussing how to bring it up to management. In that scenario, even if the post makes the restaurant look terrible, and even if it's publicly visible to all their friends and family, that Facebook thread is highly likely to be classified as protected concerted activity. Really? Even if it's bad mouthing the business publicly. Yes, because they are discussing wages and working conditions for their mutual aid. If you, as the owner, see that post and fire the server for making the brand look bad, you have just committed an unfair labor practice. Yikes. You are violating federal labor law and the NLRB can force you to reinstate that employee with back pay and mandate that you post notices admitting your legal violation in your own break room. That is a massive operational risk. So how does this impact the actual language you use when you are writing your employee handbook? Because I know a lot of operators just want to write a simple rule that says employees are prohibited from posting confidential information or making disparaging remarks about the company online. And that is exactly what you cannot do. This is where we have to deeply analyze the Chipotle NLRB ruling, which is detailed extensively. In the littler law firm source we were reviewing. What did the NLRD say about Chaportlay's policy? Well, the NLRB does not just look at whether you fired someone unfairly, they heavily scrutinize the language of your policies to see if it would chill an employee's rights. Let's unpack that term chill. It means the policy is written so broadly or vaguely that a reasonable employee would read it and think, ⁓ I better not talk about my wages or complain about unsafe. Kitchen equipment because this rule says I can't be disparaging. Exactly. The sheer existence of the rule intimidates them out of exercising their federal rights. That's right. In the Chipotle case, the administrative law judge struck down several of the company's social media rules. Why? Because of the mechanics of the wording. What was wrong with the wording? The judge ruled that an employer cannot broadly prohibit the use of a company logo in non-work-related communications. More importantly, You cannot use vague, undefined terms like prohibiting confidential or inaccurate information without providing highly specific examples of what those words actually mean. Because if you just say don't post confidential info, a young line cook might assume their eighteen dollar an hour wage is confidential. Right. So they stay silent, effectively chilling their right to discuss wages with their co-workers. That is the exact legal rationale. If the rule is vague, the NLRB assumes the employee will interpret it as Restricting their legally protected Section 7 rights. And what about just putting a disclaimer at the end of the handbook? Littler source points that out as a critical failure point for many operators. A lot of companies will write a terribly broad, restrictive social media policy and then slap a single sentence at the end of the handbook that says nothing in this policy is intended to infringe upon your rights under the National Labor Relations Act. Trevor A legal band aid. Exactly. And the courts have explicitly stated that a generic legal band-aid will not save an otherwise illegal, overly broad policy. So we know what a bad policy looks like. It's vague, it uses broad terms like disparaging, and it relies on a catch-all disclaimer. Let's look at the gold standard. The Landry's policy. Yes. Our sources include the Landry's restaurant employee portal guidelines. Landry's is a massive hospitality corporation. They own everything from Morton's the Steakhouse to the Bubba Gump Shrimp Co. When their corporate lawyers write a policy, they are writing it to withstand federal scrutiny across tens of thousands of employees. It's battle tested. Exactly. So what makes their policy work mechanically? It works through ruthless specificity. They do not rely on common sense or broad platitudes. First, they strictly forbid commenting on a guest's conduct. And they give a specific operational example. Like what? Explicitly stating that employees cannot comment on the amount of any tip or gratuity left by a guest. ⁓ that's smart. That protects the guest's privacy and the brand's reputation without infringing on labor rights. Second, they forbid posting discriminatory, obscene, or libelous material, which are categories of speech that are not protected by the NLRA. Makes sense. Third, they require employees who identify themselves as Landry's workers to post a specific disclaimer. If they are expressing a personal political or social opinion, forcing a separation between the brand identity and the individual's identity. The classic views expressed are my own and do not reflect the views of my employer. Precisely. But the most masterful part of the landry's policy is how they handle the NLRB trap. They don't just hide a disclaimer at the back of the book, they explicitly carve out the employees' rights right there in the social media section. It's front and center. Yeah. They write In plain accessible English, that nothing in this policy prohibits the employee from exercising their right to communicate with the public or their coworkers about conditions of employment, labor disputes, wages, or hours. They draw the boundary lines in bright neon ink. By providing specific examples of what is allowed, like discussing wages and specific examples of what is not allowed, like discussing a specific guest tip, they remove the ambiguity, they eliminate the chilling effect. But let's bring this back to the floor. You're the GM, you're managing a team of forty people, you see a post from an employee that says this restaurant is a garbage dump and the food is basically dog food. Ouch. Yeah. As a manager, how do you mechanically tell the difference between protected concerted activity and a toxic employee who is just actively sabotaging the business because they have a bad attitude? Where is the line? The Pennsylvania legal guidance source addresses this specific tension perfectly. The legal dividing line is the connection to working conditions. The connection. Right. The courts look at the intent and the context of the speech. Disparaging remarks that are completely unconnected to any matter protected by the NLRA, like maliciously insulting the food quality to drive away customers or making fun of a specific customer's appearance on Twitter, are generally unprotected, fireable offenses. The employee is acting maliciously to harm the business, not to improve their working conditions. But what if they say The food is dog food because management refuses to fix the broken walk-in cooler and we are forced to serve spoiled meat. That completely flips the legal analysis. Yeah. Now the disparaging remark about the food is directly tied to a complaint about working conditions and workplace safety. Even if they use profanity. Even if the employee uses profane language or the post causes severe reputational damage, the NLRB is highly likely to view it as protected speech because the core of the message is a labor dispute. It is an incredibly delicate tightrope, which is why having an explicit policy with concrete examples is the only way you survive a legal challenge when you inevitably have to terminate someone for crossing the line. So we spent a lot of time talking about the external threat, how you manage what your employees broadcast to the outside world, and how you stop them from weaponizing their smartphones against your reputation. Right, the social media side. But what about the inverse? What happens when the threat isn't an employee broadcasting something out? But rather an employee taking your most valuable internal assets and walking out the front door. ⁓ the internal threat. Yes. That brings us to the velvet rope, the hospitality NDA, and treating privacy as a premium product. You know, when you say NDA non disclosure agreement, the immediate association is Silicon Valley. We think of software engineers guarding source code or high finance executives protecting merger details. Sure. Typically associate heavy legal paperwork with a similar or an event coordinator? Exactly. I know a lot of operators listening are thinking, I run a restaurant group, not a tech startup. Why do I need military-grade NDAs for my staff? Because in the modern hospitality industry, your intangible assets are often more valuable than your physical inventory. Give me an example. Let's look at the protection of VIP and high-profile guests. If you run a boutique hotel, a high-end restaurant, or a private club, Think about the sheer volume of sensitive data your staff handles daily. Your front desk agents, your housekeepers, your private dining room servers, they all have direct, unfiltered access to highly sensitive human intelligence. They know the exact itineraries of traveling celebrities. They know which corporate boards are booking private dining rooms to discuss unannounced mergers. They know the personal, sometimes illicit habits of high net worth individuals. And that information has immense market value. Imagine a high-stakes corporate acquisition is being hammered out over dinner in your private room. A server overhears the financial terms and texts a friend or tweets about it vaguely. Or a housekeeper takes a photo of a prominent politician's hotel room and sells it to a tabloid. A leak of that magnitude doesn't just cost you the business of that one client. It violently destroys the venue's entire reputation for discretion. And in high-end hospitality, discretion isn't just a perk, it is a premium product. It really is. It is often the primary reason a client chooses your venue over a competitor. I like to think of an NDA and hospitality like the velvet rope outside an exclusive VIP lounge. The document itself is the rope. It legally and physically establishes the strict boundary between what belongs to the public and what is fiercely protected inside. I love that analogy. And just like a velvet rope, it requires enforcement. Your HR policies are the bouncers and your trade secrets are the VIPs. But it also serves a massive psychological function, doesn't it? ⁓ absolutely. The psychological deterrence is arguably just as important as the legal enforcement, especially in an industry characterized by high turnover and a younger, often seasonal workforce. Right. Many 19-year-old busers or junior prep cooks entering the workforce simply might not possess the professional context to realize that filming a behind-the-scenes video of a VIP event or snapping a picture of a proprietary prep sheet is a massive breach of trust. To them, it's just content. It's just a cool thing they saw at work. Exactly. But if you change the onboarding mechanics, if on day one, before they even see the kitchen, you have them sit down and sign a formal legally binding nondisclosure agreement, it fundamentally shifts the tone of the employment relationship. It professionalizes the environment instantly. Yes. You are signaling to them the information, the recipes, and the guests you're about to see have real quantifiable value, and we trust you to protect them. If you break that trust, there are legal consequences. It sets the baseline expectation before a mistake can even happen. The via source we analyzed breaks down the necessary mechanics of a solid NDA into four pillars. What are those? First, definition. The document must explicitly define what constitutes confidential information. You can't just say keep secrets. You have to list guest itineraries, proprietary recipes, financial margins, and vendor lists. Be specific, just like the social media policy. Exactly. Second, duration. How long does the obligation last? Usually it extends beyond the termination of employment. Third, permissions. Under what specific circumstances is disclosion allowed? For example, reporting a crime or responding to a subpoena. Right. And finally, consequences. What are the legal and financial penalties for breaching the agreement? And while NDAs create a fortress around your people and your privacy. They also serve as the critical infrastructure protecting the very foundation of why your business exists in the first place. Your intellectual property, the food, the beverage program, the operational systems. Which brings us to the concept of trade secrets. But before we dissect how to legally protect your recipes, let's take a brief moment to acknowledge the organizations that make this level of deep dive analysis possible for our listeners. This podcast is supported by the generous commitment of our sponsors, and we extend a special thank you. To HRB Universal. Their dedication to providing comprehensive resources and promoting excellence is key to empowering professionals across the culinary and hospitality industries. We also want to acknowledge the Plate and Poor Collective Equity Partner Program. This initiative exemplifies a true commitment to fostering shared success and equitable growth within the food and beverage sector, helping entrepreneurs build a more inclusive and thriving future. The journey to the C suite is fueled by innovation, relentless dedication, and the right network. We encourage you to engage with the resources and support offered by our sponsors. For details on how to connect with HRB Universal and the Plate and Poor Collective Equity Partner Program, visit hrbuni.aj.com or just Google HRB Universal. All right, we're back. We were just outlining how the velvet rope of an NDA protects your guest data. Now let's turn that protection inward. We need to talk about protecting the secret sauce. We are diving deep into trade secrets and intellectual property in the food and beverage industry. It are crucial to understand that when lawyers use the term trade secret, they aren't just using a casual descriptive phrase. It is a highly specific legal designation. Right. It has weight to it. It does. Our source material relies heavily on the definitions outlined in 18 USC section 1839 and the Defend Trade Secrets Act, or DTSA, to grasp how trade secrets function mechanically. You have to contrast them with patents. This is a huge point of confusion for operators. I hear chefs and owners say all the time, I finally perfected my grandmother's cookie recipe. I need to get it patented before someone steals it. I hear that all the time too. Let's break down why that is almost always the wrong legal maneuver. Legally, patenting a recipe is incredibly difficult, highly expensive, and often counterproductive. The fundamental mechanism of a patent requires you to publicly disclose Your exact invention, every ingredient, every temperature, every process to the federal government. So it's not a secret anymore. Exactly. This information becomes part of the public record. In exchange for telling the world how you made it, the government grants you a temporary monopoly to profit from it, usually for twenty years. Once that time expires, the recipe is public domain. Anyone can use it legally. You are literally handing the playbook to your competitors and just asking them to wait twenty years. But it Trade secret operates in the exact opposite logic. Correct. The power of a trade secret is that you never publish it, you never file it with the government. And because it remains entirely out of the public domain, the legal protection can last indefinitely. It doesn't expire in twenty years. What's a good example of that? The classic, most famous example of this, referenced right in the International Journal of Law source, is the Coca-Cola formula. It was created in 1886. It has never been patented. Because they relied on trade secret law. It is remained protected for over a century. But the courts don't just magically declare your recipe a trade secret because you say it is. You have to prove it. Right. According to the federal statutes, a recipe or an operational process must meet three strict mechanical criteria to qualify for federal protection. First, it must have independent economic value derived from not being generally known. Meaning The secrecy itself is what makes it valuable. If everyone knows how to make your signature dish, it loses its premium status. Exactly. Second, it must not be readily ascertainable by proper means. And third, and this is the failure point, for ninety percent of restaurants, the owner must take reasonable measures to protect it. Let's deeply explore that third criterion. What actually constitutes a reasonable measure in the chaotic reality of a commercial kitchen? Well, the courts understand that a restaurant is not a classified military bunker. You don't need armed guards for your spice rub. No, of course not. But you cannot simply leave the master recipe binder sitting open on the stainless steel prep counter for the dishwashers, the delivery drivers, and the HVAC repairman to read. Mechanically, reasonable measures means implementing strict access control. It means establishing a need to know architecture for your information. Let's use a signature spice rub as a hypothetical. Your front of house servers do not have a need to know the exact ratios of paprika, cumin, and proprietary dried chilies in that rub. They only need to know if it contains common allergens to protect the guests. Right. Therefore, giving a server access to the recipe violates the reasonable measures standard. Only the back of house prep cook, tasked with mixing the reb, needs the formula. And even then, many large operations will pre-mix the spices in off site commissary. Or use coded bags bag A mixed with bag B so that even the line cooks don't know the full formula. ⁓ that's clever. Furthermore, reasonable measures absolutely mandates that any employee who does have access to the formula must sign an NDA, acknowledging its status as a protected trade secret. You are compartmentalizing the data. But I want to explore an edge case here, something I hear operators argue about constantly. Let's say I own a BBQ joint. Okay. I spend five years perfecting a proprietary BDQ sauce. I put it on the menu and I sell it to thousands of people every single week. I am literally handing my product to the public on a paper plate. Haven't I technically published the recipe? Haven't I forfeited my trade secret by selling it? That is a brilliant question that gets to the heart of the law. If we connect this to the legal definitions in the DTSA, selling the finished synthesized product does not reveal the underlying data. Explain that. Well, a customer can taste the sauce. They can identify that it has molasses and mustard in it, but they cannot taste the specific ambient temperature of your smoker. They cannot taste the exact geographic source of your wood chips, or the seventy-two hour fermentation process you use for the peppers, or the precise mathematical ratios of the ingredients. ⁓ I the process and the ratios remain hidden. Which brings up the crucial distinction between reverse engineering and misappropriation. Yes. This is vital. Trade secret law does not protect you from lawful reverse engineering. So if someone figures it out on their own? Right. If a competitor buys a gallon of your BBQ sauce at retail price, takes it to a food science lab, runs it through a mass spectrometer, and lawfully reverse engineers the exact recipe, you have no legal recourse. You lost the secret fair and square. Wow. Okay. However, if your sous chef, who signed an NDA, steals the digital recipe file from your office computer and takes it to a competitor to recreate the sauce, that is misappropriation. It is theft. And what happens then? The legal remedies for misappropriation are severe. Under federal law, courts can grant injunctions to stop the competitor from selling the sauce, and they can force the thief to surrender an account of profits. An account of profits? Mechanically, that means the court looks at the competitor and says, You made five hundred thousand dollars BBQ sauce. You must write a check for five hundred thousand dollars to the original owner. It strips them of every dime of unjust enrichment. Yes, it completely nullifies their advantage. Protecting those hidden techniques, those recipes, those margins, it is fundamentally about securing the data of your brand. And when we talk about securing data and identity at the absolute highest, most uncompromising level, we have to look outside the hospitality industry. We have to look at sectors where a data breach isn't just a PR crisis, but a catastrophic security failure. Which is the perfect pivot to understanding why we are looking at an aviation security company. If you want to scale your restaurant group, you have to scale your understanding of privacy. We are zooming way out from the micro level of a single line cook's NDA to the macro level of identity protection. To do this, we are analyzing the IPO perspectives of Clear Secure Inc. For listeners who might not travel frequently, Clear is the company that operates those biometric verification kiosks at airports, the ones that allow you to scan your eyes or your fingerprints to skip the traditional TSA ID check. Right. But why are we reading a 200-page financial prospectus from an airport security company to learn about hospitality management? That's a million dollar question. Because Clear is not actually an aviation company. They are a data trust company. Their entire business model is built on a single powerful premise, which they state explicitly in their prospectus. You are always you. You are always you. Yes. They use immutable biometric data to create frictionless journeys through highly secure environments, not just thirty-eight airports, but major sports stadiums and health pass networks. We're looking at them because of how relentlessly they manage the mechanics of trust. Let's break down those mechanics. CLEAR operates in an environment regulated by the Department of Homeland Security. They have achieved what is called a FSMA high rating. The Federal Information Security Modernization Act. Achieving a FISMA high rating is incredibly difficult. It requires an organization to implement the most stringent data protection controls, continuous monitoring, and incident response protocols. So military grade security. Basically. It means the data that's encrypted both in transit and at rest. But beyond the technical hashing of data, CLEAR makes an absolute uncompromising corporate pledge. They will never sell member data to third parties. So privacy isn't just compliance issue for them. Privacy is their actual product. Their product is trust. Exactly. And the financial results of that absolute trust are staggering. Let's look at the numbers in the prospectus. In 2020, during the height of a global pandemic that absolutely decimated the travel industry, Clear still generated over $230 million in revenue. That's insane. More importantly, they boast a net promoter score, or NPS, of 75. For context, an NPS of 75 is absurdly high for any industry, let alone a company that deals with the inherently stressful environment of airport security. People actively love interacting with their security protocol. Because the friction has been removed. And the trust is absolute. And when you establish that level of trust, it scales exponentially. The prospectus details the mechanics of Clear's network effects. How does that work? When they launched, it took them seven excruciating years to acquire their first one million members. They had to build the infrastructure of trust from scratch. But once that network was secure, once the public believed the data was safe. It took them less than a year to hit the next million members, and then the next. Trust scales rapidly. I see the direct application to the hospitality operator scaling from two to five locations. Both the clear biometric kiosk at the airport and your restaurant's NDA or data privacy policy are essentially verification gates. Yes, verification gates. They establish a strict perimeter of trust and security. Only once you pass through that gate are you allowed access to the Fast Lane or the VIP room. or the proprietary recipes. If a hospitality group treats its guest data, its internal IP, and its employee NDAs with the same relentless obsessive security architecture that clear treats biometric eye scans, they build an unbreakable bond with their market. Your high net worth guests will return. And they will bring their networks because they know your discretion is absolute. It creates a moat around your business that competitors cannot easily cross. But Understanding the macro importance of this data architecture is great theory. The reality is hospitality leaders need to know how to practically implement these gates on Monday morning without completely alienating their staff. Right. You can't just walk into the kitchen tomorrow and demand everyone sign a forty-page biometric data agreement. You will have a mass walkout. So let's talk about implementation and the operational matrix. How do we systematically structure these legal policies across different tiers of employees? It requires a tiered Highly customized approach. You cannot treat a part-time busser exactly the same way you treat an executive chef who has been with you for a decade. The legal paperwork must match the level of access. Let's break down the matrices synthesized from our legal sources. We'll start at the base level, frontline staff. Okay, this tier includes your servers, your host stand, your housekeepers, your barbacks. What are the mechanical requirements for their armor? For the front line, the legal architecture is focused on containment. You need a standard, easily understandable NDA paired with the highly specific social media policy we discussed earlier. The goal here is simple: prevent the viral TikTok videos from the kitchen and stop low-level leaks of guest privacy. Keep it simple. Right. The NDA should explicitly state: do not speak to the press on behalf of the company, do not take unauthorized photos in VOH areas, and do not share internal memos. It should be written in plain language, not dense legalese. Now we move up the ladder to mid level staff. This is your sous chefs, your LEMIXologists, your event coordinators, your sommelier, the people who are actively creating or managing the product. How does their protection differ? Here, the risk profile changes from mere containment to active IP protection. The NDA for this tier needs to be significantly more robust. It must explicitly outline your trade secrets. It needs to legally cover specific plating techniques. The proprietary fermentation processes for your syrups and your exclusive vendor pricing lists. Because they touch the IP every day. Because these employees actually have their hands on the intellectual property daily, the legal protection must be surgically tailored to those specific assets. And finally, we reach the apex, executive leadership, your general managers, directors of operations, regional chefs. At this level, you are protecting the macro strategy of the business. Our source analyzing the Hard Rock Hotel's franchise disclosure document. The FDD illustrates just how complex these protections must be at the executive tier. They see the whole board? They do. These individuals have access to the entire corporate playbook, future expansion plans, detailed financial margins, real estate negotiations, and franchise renewal rights. Their restrictive covenants are the most comprehensive, often involving heavy confidentiality clauses that extend years beyond their employment. I have to play devil's advocate here though. I go back to the culture of the industry. The hospitality world is famous for its vibrant, creative, slightly chaotic family style energy. It's why people love working in it. It is. If I sit a newly promoted twenty four year old lead bartender down and slide a dense ten page legal document across the desk, doesn't that inherently kill the vibe? Doesn't it scream I don't trust you? It's a very common operator fear. Yeah. But the food law firm source provides a brilliant paradigm shift on this exact issue. They argue that we need to reframe how we view these documents. Reframe it how? An NDA should not be presented as a weapon or a threat. It is simply the modernized legal version of a professional handshake. When framed correctly during onboarding, it conveys peaceful intentions. It protects both parties by clarifying the rules of engagement. I see. And most importantly, it elevates the professionalism of the craft. When you ask a bartender to sign an NDA for a cocktail menu, you're telling them that The work you are doing here is high level. It matters. It is valuable enough that we legally protect it. It creates pride, not fear. I love that reframing. But the New York City Bar Association source also offers a crucial warning regarding implementation the concept of operational friction. They advise that operators must not make these rules so burdensome that they actively hinder daily operations. Yes. The legal mechanics cannot destroy the operational flow. Reasonable measures must actually be reasonable. Right. If you implement a policy that forces your line cooks to sign out a physical logbook, get a manager's signature, and unlock a safe every single time they need to check the ratio for the house vinaigrette during a dinner rush, the system will fail. The cooks will just start memorizing it wrong. Or they will bypass the security out of frustration, or they will just quit. The security architecture must be as frictionless as the clear kiosks at the airport. There is one more massive shift in the legal landscape we have to cover before we wrap up. It fundamentally changes how operators protect their businesses. We have to talk about the death of the non-compete clause. This is perhaps the most urgent takeaway for operators who haven't updated their contracts in the last three years. Historically, the restaurant industry relied heavily on non-compete agreements. An owner would write a contract stating, If you leave my employment, you cannot work as a chef. At any competing restaurant within a 10 mile radius for two years. It was a blunt force instrument to stop talent from walking across the street. Why is that strategy dead? Because the legal and regulatory landscape has violently shifted. Driven by aggressive new enforcement strategies from the Federal Trade Commission, the FTC blanket non competes for rank and file workers are now viewed as illegally restricting trade and depressing wages. So they are unenforceable. If you attempt to enforce a broad non compete on a line cook, or a mid-level manager today, not only will a judge likely throw it out, but you may invite federal regulatory scrutiny upon your entire business practices. It is a massive legal hazard. So if you can't use a non-compete to trap the employee, how do you protect the business? You pivot entirely to the NDA and the non-solicitation agreement. This is why the NDA is so critical. Under the new legal paradigm, you cannot stop your lead bartender from quitting and taking a job at the rival bar down the street. They have the right to earn a living. Right. However, a properly executed, robust NDA absolutely prevents them from taking your proprietary cocktail recipes, your customized syrup formulas, and your VIP client list with them when they go. You can't lock up the human, but you must lock up the data. And as we look at these legal contracts, the sources also emphasize a technical detail that operators often overlook. Jurisdictional definitions. Let's explain the mechanics of that. It's a small clause that saves hundreds of thousands of dollars in legal fees. Your agreements must specify exactly which regional court has the exclusive power to enforce the contract. Where did we see that in the sources? We see a perfect example of this in the Bodegas Tio Pepe source material, where the company explicitly designates the courts of Dorez de la Frontera in Spain as the sole jurisdiction for disputes. Why does that matter? Let's say you operate a restaurant group in Chicago, your former executive chef, who signed an NDA, quits. moves to California and starts publishing your trade secrets in a cookbook. If your NDA doesn't have a jurisdictional clause, that former employee could force you to fly your legal team to California to fight the battle in a court that might have very different trade secret precedents. ⁓ that sounds like a nightmare. By writing in a jurisdictional definition, you mandate that the fight happens on your home turf under Illinois law. It as about controlling the battlefield before the war even starts. So let's pull all of this together. We've gone from the chaos of a Friday night TikTok to the federal mechanics of the NLRB to the biometric data of airport security. What is the ultimate takeaway for the operator listening right now? The takeaway is that the armor is no longer optional. In a hyperconnected convenience economy where every employee is a potential broadcaster, and where intangible IP is your most valuable asset, relying on good vibes and handshake agreements, is operational negligence. Strict. Legally compliant social media policies, surgically crafted NDAs, and compartmentalized trade seeker protections are the fundamental architecture of modern hospitality management. We started this deep dive talking about a prep cook posting a video of a messy walk-in freezer. But as we close out, I want to leave you with a final forward-looking question to ponder as you scale your business. We are moving into an era where identities and business assets are increasingly digitized and intertwined. Whether it's Sierra's massive biometric network or your restaurant's digital footprint. So think about this. What happens when the lines blur completely? It is the absolute frontier of hospitality law. Exactly. Imagine your bartender goes wildly viral on TikTok. Not for posting a messy kitchen, but for being incredibly talented. They are fast, they are charismatic, they're doing flair bartending, and they build an audience of two million followers. A huge asset. But they are filming these videos while standing behind your bar, using your liquor inventory, wearing your branded uniform during hours you are paying them for. When that bartender leaves to start their own brand, who owns that digital clout? Who owns the algorithmic value generated in your space? The employee or the venue? It is a complex multimillion dollar question that every hospitality leader will soon have to answer, and your contracts better be ready for it. Absolutely. We look forward to having you join us for our next episode of From Kitchen to C-Suite, where we will continue to explore captivating topics designed to elevate your career and entrepreneurial drive. Dumb as a beat. Whether you're commuting or chilling on the couch, we've got you covered. It's on the go. Subscribe and listen via Riverside and from Kitchintosuite.com or our website, hrb-un I.com. You can also search for us on Apple Podcasts, Spotify, YouTube, Amazon Music, Audible, iHeartRadio, or Deezer, or wherever you get your daily audio fix. Took HRB Network wherever you go. Download the new mobile web app, HRDUN and I.com forward slash APP. Ooh, on the big screen. Level up your experience by watching the From Kitchen to Sea Suite podcast on the HRB Network on Roku or Fire TV. On social media, at HRB Uni or at HRB Universal. Until our next broadcast, continue to innovate and strive for superior achievement.