What a bakery's recipe binder was actually worth on paper

The situation

The number that started this whole conversation was seventy thousand dollars, give or take. That was Marieke's rough estimate of what it would cost her bakery in lost margin over a single year if a competitor got hold of the recipe formulations her grandmother had developed decades earlier and a rival started undercutting on the products those recipes made possible. It was not a hypothetical number. It was built from watching what happened to a nearby bakery after a similar recipe reportedly leaked to a competitor, and from Marieke's own sense of how much of her revenue, in a company generating somewhere between two hundred fifty thousand and a million dollars a year, rode on products nobody else in the city made quite the same way.

Marieke had taken over the bakery from her father a few years earlier, inheriting not just the ovens and the storefront but a small, tightly held set of recipes that had never been written down in any one place except a binder kept in the back office, and more recently, scanned into a shared folder that most of the kitchen staff could access to do their jobs. Bram had been the bakery's production manager for almost three years, one of the few employees trusted with the full recipe set, along with supplier pricing that Marieke considered nearly as sensitive as the recipes themselves.

When Bram gave notice that he was leaving to open his own bakery a few neighbourhoods over, Marieke's first reaction was not anger. It was a kind of dread about process. She had no fixed routine for what happened when someone with Bram's level of access left: no checklist for what devices needed to be returned, no way of confirming what had been copied before someone's last day, and no clear sense of what she was entitled to ask for versus what would feel like an accusation.

What worried Marieke most was not really the worst-case scenario, a wholesale theft of every recipe in the binder. It was the much more likely, harder to see version: a departing employee genuinely not realizing that a phone full of photographed prep sheets, or a personal laptop still logged into the shared recipe folder, was a problem at all. She wanted a process that would catch that ordinary carelessness reliably, predictably, and without turning every departure into a confrontation or a legal bill she could not plan for.

Nirosha, a veterinary technician who had helped Marieke informally with the bakery's staffing paperwork as a favour between neighbours, was the one who first suggested Marieke put a number on the risk instead of just worrying about it in the abstract. Nirosha had no background in law or baking, but a practical instinct for turning a vague worry into something concrete, and the seventy thousand dollar estimate came out of an afternoon the two of them spent going through the bakery's sales figures together.

What was actually at stake

Trade secret protection in Ontario does not come from a registration or a government filing the way a patent or trademark does. It comes from taking reasonable steps to keep genuinely confidential business information secret, and from being able to show, if it ever mattered, exactly what those steps were. A recipe that everyone in the kitchen can access freely, with no confidentiality agreement, no access controls, and no consistent exit process, is much harder to protect after the fact, because the business itself has not treated it as a secret worth protecting.

For Marieke, this meant the seventy thousand dollar estimate was not really about what Bram might do with the recipes on his way out. It was about whether the bakery, as a matter of routine, treated its recipes and pricing information the way the law expects a business to treat something it is calling a trade secret. If a dispute ever arose, whether with Bram or with a future employee, the bakery's own inconsistent handling of that information could undercut its ability to claim it had been protected at all.

The second piece of what was at stake was cost predictability, which mattered to Marieke as much as the recipes themselves. She had heard stories from other small business owners about disputes over departing employees running into tens of thousands of dollars in fees with uncertain outcomes, and she was clear from the first conversation that she did not want a program built around the assumption that every departure would end in litigation. She wanted something she could run herself, at a cost she could budget for, that would meaningfully lower the odds of a problem rather than promise to win a fight after one had started.

Bram, for his part, had given no indication he intended to take anything with him. He had been a good employee for three years, and the departure was amicable. But Marieke's instinct, one we agreed with, was that the value of a good exit process is precisely that it does not depend on guessing correctly about any one departing employee's intentions. A predictable process applied evenly to everyone protects the recipes regardless of whether the person leaving that particular day happens to be trustworthy, which is a question no employer can reliably answer in advance.

Nirosha stayed involved through the early planning conversations, mostly asking the kind of blunt, practical questions a lawyer sometimes forgets to ask a small business owner directly, like whether Marieke actually knew, off the top of her head, how many personal phones had ever been used to photograph a prep sheet in the kitchen. Marieke did not know, and that gap between what she assumed and what she could actually confirm became one of the clearest arguments for building a structured process instead of continuing to rely on trust and habit.

What we did

1. Reviewed the bakery's existing confidentiality terms. Marieke's employment agreements had a brief, generic confidentiality clause that did not specifically identify the recipes or pricing information as protected, so we started by confirming what, if anything, currently obligated any staff member to keep that information secret once they had already left the bakery for good and gone to work somewhere else.
2. Drafted a specific confidentiality schedule identifying the protected information. Rather than relying on a vague clause, we added a schedule to the employment agreement naming the recipe formulations and supplier pricing specifically as confidential, which matters because trade secret protection under Ontario law is strongest when a business can show it clearly identified, in writing, exactly what it considered secret.
3. Built a standard exit checklist covering devices and access. We created a one-page checklist for every departure involving recipe or pricing access, covering personal devices that had been used for work, return of any physical copies still floating around the kitchen, and confirmation of removal from the shared digital folder, so the process did not depend on Marieke remembering every detail under time pressure on someone's last day.
4. Designed a short, fixed-form exit interview. The interview asked a consistent set of questions about what devices had been used, whether anything had been copied or forwarded, and reconfirmed the employee's ongoing confidentiality obligations in plain language, giving Marieke a documented record of every departure without requiring a lawyer to sit in the room for each one, which was exactly the kind of ongoing legal cost she had told us she wanted to avoid.
5. Set access permissions to expire automatically at departure. We worked with Marieke's point-of-sale and file-sharing provider to make sure access to the recipe folder and supplier records was revoked the same day as an employee's last shift, rather than relying on someone remembering to do it manually days or weeks later, once the urgency of a busy kitchen had already moved on.
6. Capped the process at a predictable cost. We built the checklist and interview script so that, for the ordinary departure, Marieke could run the entire process herself in under an hour with no legal involvement and no legal bill at all, reserving the cost of actual legal advice for the rare case where something in the exit interview raised a genuine concern.
7. Ran the process with Marieke for Bram's departure as a live test. Rather than leaving her to figure out the new checklist alone the first time it mattered, we walked through Bram's exit with her step by step, confirming his devices, his access revocation, and his signed acknowledgment of the confidentiality schedule, so the first real use of the program also served as her training on it.
8. Gave Marieke a plain-language summary she could hand to staff at hiring. Alongside the exit-side process, we drafted a short document explaining the confidentiality expectations in ordinary language for new hires to review and sign on their first day, so the obligations that mattered at departure were never a surprise introduced only once someone was already halfway out the door.

The outcome

Bram's departure went through the new process cleanly. He returned the one physical copy of a prep sheet he had at home, confirmed he had not photographed or forwarded any recipe pages, and signed the acknowledgment of the confidentiality schedule without objection. His access to the shared folder was revoked the same afternoon as his last shift. The whole exit interview took about twenty minutes, and Marieke ran it herself using the script, with no legal fees beyond the initial setup work.

There was no dispute, no leaked recipe, and no indication that Bram's new bakery used anything from Marieke's files. That is the least dramatic possible outcome, and exactly the one Marieke had hoped for. The program was never really about catching a thief. It was about making the ordinary, honest departure predictable and low-cost, while making sure a dishonest one would meet a bakery that could already show its recipes had genuinely been treated as secrets.

Marieke has since run the same process for two other staff departures, each costing nothing beyond her own hour. She said the biggest change was not really about the recipes at all: she no longer dreaded a staff member handing in notice, because she finally had a process instead of a vague worry.

Nirosha, who had prompted the whole exercise with her question about the seventy thousand dollar figure, later told Marieke that watching the process actually work for Bram's departure was the first time the abstract number had felt real to her. The recipes were never in serious danger during this particular departure, but the predictability Marieke had asked for, a fixed, low-cost routine she could run herself without dread, turned out to be worth more to her day to day than the specific dollar figure that had started the conversation.

What you can learn from this