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

A Complaint Letter Uncovered a Second Employee the Bakery Never Trained

A customer's accessibility complaint about a small Picton bakery led to a discovery neither co-founder had known about: a second staff member who had never been trained at all, with the provincial office's deadline for a response days away.

Corporate9 min readPicton, OntarioAccessibility for customers
All Corporate case studies
ClientGhada and Karim, co-founders of a small Picton bakery, managing the response remotely
The issueA customer accessibility complaint exposed a second employee who had never been trained, with days left before the provincial office's deadline to respond
ServiceClosed the training gap remotely, documented the training going forward, and responded to both the complaint and the provincial office directly
ResolutionLoss contained: the complaint and gap were real, but the damage was limited by acting quickly and correctly once it surfaced

The situation

The email arrived on a Wednesday afternoon, forwarded from the bakery's general account to Karim with a one-line note: 'you need to see this.' It was a formal complaint from a customer named Gabor, describing being turned away from the counter weeks earlier because he used a service animal and a part-time staff member, unsure of the store's policy, had asked him to leave it outside. Gabor had waited, then escalated, contacting the provincial body responsible for accessibility compliance rather than the bakery directly. That was the first Ghada or Karim had heard that anything had gone wrong at all.

Ghada and Karim had built the bakery together over several years, starting as a weekend stall the two of them ran after their regular jobs, Ghada washing dishes at a restaurant and Karim baking overnight shifts for a larger commercial kitchen, before saving enough to open a small storefront of their own in Picton. The business had grown steadily into something real, close to a hundred thousand dollars a year in revenue, two part-time staff beyond the co-founders themselves, and a loyal local following. Neither of them had run a business with formal compliance obligations before, and neither had thought much about accessibility requirements beyond making sure the doorway was wide enough for a stroller.

Complicating things further, Ghada had relocated out of province the previous year for a family matter, and had been managing her side of the business remotely ever since, mostly through calls with Karim and occasional visits back. She had no way to walk into the store, look at what training records existed, or speak with staff in person. Everything about responding to this complaint, and figuring out what the bakery had or had not done correctly, would have to happen over email and video calls, coordinated across two people in two different places.

The complaint itself, on its face, was one incident involving one staff member's uncertainty about how to handle a service animal, the kind of gap that training is specifically meant to prevent. But the referral to the provincial accessibility body raised the stakes considerably. That body's involvement meant this was not simply a customer service dispute to smooth over with an apology. It meant Gabor's complaint was now sitting in front of an office with the authority to ask harder questions about whether the bakery had met its broader obligations, not just on the day of the incident but as an ongoing matter of compliance.

The problem

Ontario's accessibility legislation requires businesses, including small ones, to meet a customer service standard covering how staff interact with customers who have disabilities, which includes training staff on serving customers who use service animals, support persons, or assistive devices. It is not a one-time policy to post on a wall; it requires actual training delivered to staff and kept up to date as new people are hired. Larger organizations, generally those with twenty or more employees, also have to keep a written record of when the training was given and how many people received it; a business the size of the bakery has to deliver the training but is not required to file a record of it, though keeping one is the only practical way to show later that it happened. The single incident with Gabor traced back cleanly to a training gap: the part-time employee involved had been hired after the co-founders' last general review of store practices and had never received any formal accessibility training at all.

That gap alone would have been a serious but containable problem. What made the situation worse was what turned up once we looked at the bakery's broader compliance history at Ghada and Karim's request. Because no training records existed for any staff member, current or past, there was no file to simply check; each staff member's actual training history had to be reconstructed from hire dates and from what Ghada and Karim could recall themselves. Neither co-founder had realized quite how thin the bakery's real training coverage was, since keeping a record was never something they had been required to do and auditing staff training closely was not the kind of thing either of them had reason to do while running a small storefront day to day. The provincial office that had received Gabor's complaint set its own short deadline, days away when it surfaced, for the bakery to respond in writing with what corrective action it intended to take.

The two problems were connected but not identical, and it mattered to keep them separate in responding. The Gabor complaint was about a specific incident and how the bakery handled a specific customer; the bakery's other untrained employee was a separate, ongoing gap that existed independently of what had happened to Gabor and needed fixing regardless of whether Gabor had ever complained. Fixing only the employee involved in the Gabor incident would help with that complaint but would leave the second untrained employee exposed, and a response that addressed only the one incident without training everyone who needed it would have looked, to any reviewer, like a narrow fix rather than a real correction.

There was also a real question of exposure. The provincial body handling accessibility complaints generally has room to work with businesses that respond promptly and in good faith, particularly small businesses correcting a genuine gap rather than ignoring a known one. But a training gap discovered through a complaint, rather than caught and fixed proactively, is a materially worse position than the same gap found and corrected on the business's own initiative. Time, at that point, mattered as much as the substance of the fix, with the office's own response deadline leaving no room to take the slow route.

What we did

  1. Confirmed exactly when each staff member's training obligation had started applying, working from hiring records Ghada sent over remotely, to establish how far back the bakery's training gap actually went and how complete a picture could reasonably be put together after the fact, rather than guessing at the scope of the problem before deciding what needed fixing first. That timeline mattered directly to how the eventual response would need to be framed.
  2. Mapped every staff member's training history against hire dates, since the gap involving Gabor traced to a single part-time employee, but confirming whether other staff hired around the same time had similar gaps mattered before telling the provincial office the problem had been fully addressed rather than only partly patched. The bakery's other part-time hire turned out to have the same gap, never having received any accessibility training either.
  3. Set up remote training sessions for all current staff, coordinated over video calls since Ghada could not attend in person and Karim needed to run the store during business hours, covering the customer service standard's requirements directly, including how to respond appropriately to a customer with a service animal, a support person, or another assistive device. Scheduling around bakery hours meant splitting the sessions across two evenings rather than one long meeting.
  4. Documented the training formally, with dated records of who was trained, on what material, and by whom, because a training program that exists only informally is very difficult to demonstrate later if a complaint or audit asks for evidence that it actually happened rather than being assembled after the fact. We built the record as a simple log Karim could update himself going forward, without needing to call anyone each time.
  5. Prepared a written response to the provincial office's deadline, working quickly given the narrow window, and set out plainly that the second employee's training gap had been identified and corrected proactively once the complaint surfaced, since a response that shows a business closing a gap on its own reads very differently to a reviewer than one produced only after being caught by an external audit. The response referenced the new training log directly, so it was not just an assurance but backed by real evidence.
  6. Drafted a direct response to Gabor's complaint, acknowledging the incident plainly rather than minimizing it, explaining the training and policy changes already underway, and offering a genuine apology, because a defensive or evasive response to an accessibility complaint tends to escalate matters that a straightforward one can often resolve on its own. Karim reviewed and sent it personally rather than routing it through a generic account.
  7. Communicated with the provincial accessibility office on the bakery's behalf, laying out the corrective steps taken, the training now delivered, and the records now in place, to demonstrate the business had addressed both the specific incident and the underlying gap rather than treating the complaint as the only problem worth fixing. We answered every follow-up question the office raised within a day, rather than letting the file sit.
  8. Reviewed the bakery's broader operating structure with Ghada and Karim afterward, given how easily a training gap had gone unnoticed for so long, and set a recurring reminder tied to hiring dates so future staff would be trained on schedule, and the training logged as a matter of practice, rather than caught only through the next complaint that happened to arrive.

The outcome

The complaint did not disappear, and it should not have. Gabor had been turned away because of a real training gap, and the bakery's written response to him acknowledged that plainly rather than disputing it. The provincial accessibility office accepted the corrective steps taken, the response filed before its deadline, and the documented training as a good-faith resolution of both the specific incident and the second employee's training gap, and closed its involvement without further formal action against the business. That was the best realistic outcome once the complaint had already been made; it was not the same as the incident never having happened.

The training gap carried its own quiet cost. Responding fully and promptly, once the gap was found, avoided any formal action against the business, but it did not erase the fact that a second employee had been serving customers without ever receiving the training the law required, a gap that existed the entire time regardless of whether anyone had complained. Ghada and Karim absorbed the cost of the remote training sessions and the time spent reconstructing each staff member's training history at a point in the year that was already busy for the business, and neither of them treated the resolution as a clean win when we spoke afterward.

What limited the damage was speed and honesty rather than luck. Responding to Gabor directly and without defensiveness, answering the provincial office fully and before its deadline rather than after being formally pursued for it, and documenting the training thoroughly all mattered more than any single legal argument would have. The bakery kept operating without a finding against it and without losing its standing with the provincial office, but the underlying lesson, that hiring outside staff brings compliance obligations a small business will not necessarily notice on its own, stayed with Ghada and Karim well after the complaint itself was resolved.

Gabor, for his part, accepted the apology and the explanation of what had changed, and continued shopping at the bakery afterward. That was not guaranteed; a customer who has been turned away once, and had to escalate to a government office before getting a response, has every reason to simply take his business elsewhere. That he did not was less about the legal outcome than about how directly Karim's response had addressed what actually happened to him, rather than treating him as a compliance problem to be managed.

What you can learn from this

  • Accessibility training obligations apply to every staff member serving customers, including part-time hires added after a business's last general policy review, not just the people who were there when training was last done.
  • Training obligations attach quietly, as soon as a business starts hiring outside staff, and apply regardless of size; only larger organizations must formally record it, but keeping your own log is the only practical way to prove training happened if anyone ever asks.
  • A gap found and corrected on your own initiative is treated very differently than the same gap discovered through a complaint; catching it first is worth real effort.
  • Responding to an accessibility complaint directly and without defensiveness tends to resolve matters faster than a cautious or minimizing response, even when the underlying incident is genuinely your business's fault.
  • Running compliance remotely across co-founders in different locations is workable with clear documentation and scheduled video sessions, but it requires deliberate coordination, not assuming the person on-site has it covered.
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 →