TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
Home/Case Studies/Corporate
№ 242 Case Study — Corporate

A Misdirected Email, a Closing Deadline, and a Contract That Was Ready for It

A shared supplier's account manager sent confidential pricing to the wrong inbox during the busiest week two Owen Sound companies had ever had. The agreement itself decided what happened next.

Corporate8 min readOwen Sound, OntarioWhen confidential information walks out
All Corporate case studies
ClientJi-ho and Min-ji, an optometrist and a pharmacist who jointly own two related companies
The issueA shared supplier's account manager sent confidential pricing and formulation data to a competitor by mistake, during closing week on an unrelated deal
ServiceInvoked the supply agreement's own breach and cure provisions instead of starting a lawsuit, containing the leak within days
ResolutionPrevention: the information was recalled and confirmed unused before any competitive harm occurred

The situation

The email landed in the inbox of a rival optical lab on a Wednesday afternoon in early July, three days before a long weekend and, though nobody at that lab knew it, four days before Ji-ho and Min-ji were scheduled to close the sale of a minority stake in their businesses to an outside investor. Jelena, the account manager at the specialty lens and compounding supplier both companies used, had meant to send a comparative pricing sheet internally to a colleague. She sent it, instead, as a reply-all on a thread that had, months earlier, briefly included a contact at the competing lab during an unrelated industry event follow-up that nobody had thought to remove from the recipient list since.

Ji-ho ran an optometry practice group and Min-ji ran an independent pharmacy group, two separate companies under common ownership between the two of them, sharing back-office functions, a supply relationship, and a single confidentiality and supply agreement with the vendor that served both businesses out of efficiency and long habit. Combined, the two companies sat in the high single-digit to low double-digit millions in annual revenue, built over a decade into a business worth enough that an outside investor had spent four full months on diligence before agreeing to buy a minority position in both entities together, a deal that was supposed to close before the long weekend so the funds would land cleanly before month-end for tax and accounting reasons on both sides.

The pricing sheet Jelena sent was not itself catastrophic on its own. What made it serious was what came bundled with it lower in the same email thread: proprietary formulation notes for a custom lens coating the two companies had spent two years developing exclusively in partnership with this supplier, covered specifically by the confidentiality terms of their agreement precisely because it was the kind of detail that gave the businesses their genuine edge over larger regional competitors with more marketing budget but no equivalent product.

Min-ji found out from a friend at the competing lab, who forwarded the email straight back with a one-line note simply asking if it was meant for them. It arrived on Ji-ho's phone at 4:40 on the Wednesday afternoon, with the closing scheduled for Monday morning and the investor's own counsel, at that very moment, still finishing its final confirmatory review of exactly the kind of proprietary information that was now sitting, unprompted, in a rival's inbox.

The risk we had to size

The immediate legal question was straightforward: the supply agreement between the two companies and their vendor contained a standard confidentiality clause, and Jelena's misdirected email was, on its face, a breach of it by the vendor, regardless of whether the disclosure was accidental. What was not straightforward was what that breach actually put at risk, and how fast, because the timeline mattered as much as the substance.

Two risks ran in parallel and had to be sized separately. The first was competitive: if the rival lab's staff read and retained the formulation notes, the two years of development work behind that coating lost real value, whether or not the rival ever used it directly, because the whole point of keeping it confidential was that a competitor did not have it. The second risk was transactional, and in the short window available, it was the more urgent one. The investor's counsel was, at that exact moment, confirming that the target companies' confidential information and intellectual property were properly protected, a standard closing condition. If that same counsel learned independently that a confidentiality breach involving core proprietary information had just occurred and was unresolved, it had real potential to delay or reprice the closing, regardless of how quickly the underlying leak itself got contained.

Sizing the risk meant answering three questions inside about eighteen hours: could the disclosure be walked back before the rival lab's staff meaningfully absorbed or acted on it, did the supply agreement give a clean, fast mechanism for doing that without resorting to a court application nobody had time for before Monday, and could the investor's diligence team be told about the incident on terms that read as competent crisis management rather than as a company with a confidentiality problem.

The agreement itself, read closely, answered the second question well. It included a notice-and-cure structure requiring the vendor to act immediately on notice of any breach, a right to demand written confirmation that any misdirected confidential information had been destroyed or was unused, and language entitling the companies to seek an urgent court order if the vendor failed to cooperate, without waiting out any lengthy notice period first. That last piece, built into the contract months before anyone knew it would matter, turned a problem that could have needed a rushed court application into one that could, if the vendor cooperated, be resolved through the contract's own machinery in days rather than weeks.

What we did

  1. Sent formal breach notice to the vendor within hours, invoking the agreement's cure clause directly. We drafted and sent notice that same evening citing the specific confidentiality provision breached and demanding, under the agreement's own terms, immediate written confirmation of exactly what had been sent, to whom, and what concrete steps the vendor was taking to recall it, because starting the contractual clock immediately, rather than waiting until morning, was the fastest lever available to us and to our clients.
  2. Contacted the rival lab directly and requested destruction, not through threats but through the ordinary confidentiality norms already binding this tight regional industry around inadvertent disclosure. A short, professional letter asked the rival lab to confirm it had not reviewed the formulation details closely, to delete the email entirely, and to certify both facts in writing, which most businesses operating in a small regional industry are willing to do quickly and without friction, precisely because they may well need the same courtesy returned to them someday.
  3. Required the vendor to obtain and forward that certification itself, rather than taking the companies' word for it secondhand. We insisted the vendor, not our clients directly, handle the follow-up conversation with the rival lab, since the vendor held the actual ongoing commercial relationship and whatever credibility existed with that recipient, and made unmistakably clear in writing that fulfilling this request was itself part of what cure under the agreement required of them.
  4. Briefed the investor's counsel proactively, before diligence could surface the incident independently and unexplained. Rather than wait to see whether the issue would surface on its own during final review, we disclosed it directly to the investor's legal team on Thursday morning, framed clearly with the full timeline, the contractual response already well underway, and the certification process already in motion, which let the investor's counsel see a resolved or actively resolving issue rather than an unexplained gap in the data room.
  5. Confirmed the underlying formulation itself did not need to change as a result. Once destruction was certified by both the vendor and the rival lab, we assessed carefully whether any further protective step, such as amending the formulation itself or accelerating any protection available for it, was genuinely warranted, and concluded the brief, contained exposure did not require it, avoiding an unnecessary and needlessly costly overreaction to an incident that had already been closed.
  6. Documented the entire response in a closing-condition memo for the transaction file. We prepared a short, clear written record for the deal file describing the incident, the contractual mechanism invoked, and the certifications obtained from both the vendor and the rival lab, so the investor's diligence record showed a resolved matter with a clean paper trail rather than an open gap, which mattered directly for the closing certificate signed the following Monday morning.
  7. Reviewed the supply agreement's confidentiality terms for the next renewal, once the closing itself was safely behind everyone. With the immediate crisis past and the deal closed, we went back to the underlying agreement and tightened the internal-distribution language and the vendor's own staff training obligations ahead of the next renewal cycle, to reduce the odds of the same kind of accidental reply-all mistake happening again to either company.
  8. Held a short debrief with Ji-ho and Min-ji on internal handling of shared vendor threads. We recommended a simple internal rule, that any thread involving proprietary formulation detail be flagged and kept on a restricted distribution list rather than a general one, so that even a vendor's own mistake would have less room to travel as far as this one nearly did.

The outcome

The rival lab confirmed by Thursday evening, less than twenty-four hours after the original email went out, that it had not been opened by anyone beyond the initial recipient, deleted it from its systems, and provided the written certification the agreement required to close the loop. The vendor cooperated fully once formal notice was sent, in part because its own exposure under the agreement's breach provisions gave it every practical incentive to resolve the matter quickly and visibly rather than dispute a claim it was unlikely to win.

No formulation detail ever reached anyone who could plausibly use it competitively, and the closing went ahead exactly as scheduled on Monday morning, with the investor's counsel treating the disclosed incident as a well-handled, immaterial matter noted in the file rather than a live concern requiring further diligence. The deal closed on its original terms, without repricing, without delay, and without any renegotiation of the purchase price, which was the outcome that mattered most given how much of the two companies' negotiating position, built over the prior four months of diligence, would have been undone by a last-minute reopening of terms so close to funding.

Ji-ho and Min-ji did not need to prove damages, seek a court order, or terminate the vendor relationship at all, because the problem was caught and closed within a single business day, before it ever became the kind of loss that requires a legal remedy rather than a quick correction. The episode's lasting effect was mostly on the contract itself going forward: the renewal signed later that year carries meaningfully tighter internal-handling language for exactly the kind of shared-thread mistake that started the whole week, a small, permanent change built directly from four days neither owner wants to repeat, and a reminder that the strongest protection is the one written into the agreement long before anyone needs it.

What you can learn from this

  • A confidentiality agreement with a clear notice-and-cure mechanism can resolve a breach in days, without a court application, if you invoke it immediately and precisely.
  • An accidental disclosure is not automatically harmless, and it is not automatically catastrophic. What matters is how fast it is contained relative to whether the recipient acts on it.
  • If a confidentiality incident occurs during a transaction, disclose it to the other side's counsel proactively. A resolved issue you raised reads very differently than an open one they discover.
  • Written certification of destruction or non-use from an accidental recipient is worth pursuing even in an informal, close-knit industry. It converts an assumption into evidence.
  • The best time to negotiate a strong breach and cure clause is before you need it. Review confidentiality terms in shared or long-standing supplier agreements before, not after, an incident.
This case study is entirely fictional. It does not describe any real client, file, or matter handled by Treadstone Law, and it is not a real file with details changed. All names, people, properties, businesses, dollar amounts, dates, and events are invented, and any resemblance to a real person, business, or situation is coincidental. Fictional scenarios like this one illustrate the kinds of legal issues people in Ontario commonly face and how a lawyer can help. They are general information, not legal advice — no two matters unfold the same way, and nothing here predicts the outcome of any real case. Reading a case study does not create a lawyer-client relationship. If you are facing something similar, speak with a lawyer about your specific circumstances.

This is a corporate problem we handle

Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.

ContactStart a File →