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

A shop-floor injury, a family friend consultant, and a stalled investigation

A Bradford manufacturer reported a critical injury on time, but the safety consultant handling the aftermath was also an old family friend, and that closeness slowed the fixes the company actually needed.

Corporate9 min readBradford, OntarioHealth and safety incidents
All Corporate case studies
ClientCarlos and Elena, co-trustees running a family-trust-owned manufacturing company
The issueA critical shop-floor injury was reported on time, but the follow-up investigation stalled because the safety consultant was a longtime family friend
ServiceRan the post-incident compliance work independently, reset the consultant relationship on contractual terms, and rebuilt the corrective action plan
ResolutionPartial outcome: the file closed with the regulator satisfied, but the friendship took real damage and the company absorbed the cost of redoing work

The situation

Carlos and Elena had already tried to handle it themselves. As co-trustees of a family trust that owned a metal fabrication shop in Bradford doing somewhere in the low millions in annual revenue, they had spent three weeks after the accident leaning on Ioana, a safety consultant who had done informal audits for the shop for years and who also happened to be a close friend of Carlos going back two decades. Carlos worked full time as a mortgage broker and had never expected the trustee role to involve managing a regulatory file on top of it. Their plan was simple: let Ioana write the corrective action report, submit it, and move on. It had not worked.

The accident itself had been handled correctly at the time. A worker operating a press brake suffered a critical injury when a guard failed, and the shop's floor supervisor had reported it to the Ministry within the window the regulations required, secured the scene, and cooperated with the initial inspection. That part was not in question. The trouble started afterward, when the Ministry came back with a list of required corrective actions and a request for a written investigation report showing how the company would prevent a recurrence.

A critical injury under Ontario's workplace safety rules is a defined category, one that automatically triggers this heightened level of scrutiny regardless of how the underlying cause eventually turns out. Ioana had done safety walkthroughs for the shop before, but she had never run a post-incident investigation under this kind of scrutiny, and her report read like a favour rather than a formal document. It repeated management's account of the accident without independently verifying the guard's maintenance history, and it proposed fixes that were vague enough that a regulator would likely send it back. Carlos did not want to tell his old friend her work was not good enough. Elena, who handled the trust's more formal obligations as a municipal planner by profession, could see the report would not hold up, but neither of them wanted to be the one to say so directly to Ioana.

By the time they came to us, six weeks had passed since the accident, the injured worker was still off work, and the Ministry's file was sitting open with a compliance deadline approaching. Carlos wanted the shop protected. He also, understandably, did not want this to become the thing that ended a twenty-year friendship. Those two goals were not automatically compatible, and the first job was figuring out how to serve both without pretending the tension away.

The problem

The core problem was not the accident. Critical injury investigations are common in manufacturing, and a shop with an otherwise reasonable safety record can usually work through one without lasting damage, provided the paperwork and the corrective actions hold up to scrutiny. The problem was that the person responsible for producing that paperwork had a relationship with the client that made candour difficult in both directions.

Ioana's original walkthroughs, going back several years, had flagged the press brake's guarding as needing attention at least twice, informally, in emails that were more suggestion than warning. Neither Carlos nor Elena had acted on those suggestions with any urgency, in part because the relationship made them feel like friendly advice rather than a documented risk. When the accident happened, that history became a liability in two directions: it suggested the company had notice of a hazard it did not fix, and it put Ioana in the position of investigating an incident she had partly foreseen and not escalated formally.

A regulator reading her post-incident report would eventually find those old emails, because the trust's inbox was subject to the same document requests as everything else connected to the incident. A report that omitted them, or that understated how long the guarding issue had been known, would look far worse than a report that disclosed it plainly and explained what changed. Ioana's draft did the former, not out of dishonesty, but because she was too close to the situation to see how it read from the outside.

There was also a practical conflict. Ioana's fee arrangement with the shop had always been informal, paid in occasional cash and small invoices without a written scope of work. If the corrective action plan she wrote turned out to be inadequate and the Ministry escalated, questions about who was professionally responsible for the gap, the shop or its consultant, had no clean answer, because there was no contract defining what she had been retained to do. Carlos's instinct to keep things friendly had left the company without a clear line of accountability exactly when it needed one.

There was a regulatory dimension to weigh as well. An investigation report a Ministry inspector considers inadequate does not simply get revised without cost: it can trigger a reissued order with a shorter compliance window, and for a critical injury it can also influence whether the file gets resolved through compliance orders alone or treated as one worth pursuing charges over under the Act. Getting the report right the first time mattered for more than efficiency; it narrowed the range of outcomes the company was actually exposed to.

What we did

  1. Separated the compliance work from the friendship. We told Carlos plainly that the shop needed an investigation report that would withstand scrutiny regardless of who wrote it, and that meant treating Ioana's prior draft as a starting point to be independently verified, not a finished product to be defended. This let Carlos stop being the one who had to critique his friend's work directly, and it reframed the project for Elena as a compliance exercise rather than an interpersonal negotiation.
  2. Reviewed the maintenance and inspection history in full. We pulled every record connected to the press brake, including the informal emails from Ioana's earlier walkthroughs, work orders from the shop's maintenance vendor, and the supervisor's own notes from the day of the accident, because we needed to know exactly what the company had been told and when, before the Ministry found it first. Disclosing that history on our own terms was far better than having it surface as a gap in the company's account.
  3. Put Ioana's ongoing role on a written contract. Going forward, any work she did for the shop, corrective action follow-up, future audits, or anything else, would be governed by a scope of work and a fee schedule like any other vendor. This protected both her and the trust: she now had a defined, professional role instead of an ambiguous friendly one, and the company had a paper trail showing who was accountable for what, which also mattered for the shop's liability insurer.
  4. Drafted a new investigation report with independent verification. Rather than editing Ioana's draft, we rebuilt the report from the underlying evidence, the maintenance logs, the supervisor's incident notes, and a fresh assessment of the guard failure, so the analysis stood on its own rather than resting on assurances from someone close to the file. We had the guard mechanism itself examined by an outside engineer to confirm what actually failed, rather than relying on Ioana's earlier, informal read of the mechanism.
  5. Built a corrective action plan with dates and named responsibility. The Ministry's earlier feedback had flagged the vagueness of the proposed fixes. We replaced general commitments with specific actions, a guard replacement schedule, a documented inspection routine, and a named person responsible for signing off on each step, so the plan could actually be checked for compliance later rather than read as a list of good intentions.
  6. Managed the Ministry correspondence directly. We took over communication with the inspector so that Carlos and Elena were not fielding technical follow-up questions about maintenance records or the guard's failure mechanism that they were not positioned to answer precisely, which reduced the risk of an inconsistent or incomplete response extending the file further, and gave the shop a single, consistent voice throughout the remainder of the review.
  7. Had a direct conversation with Ioana about the earlier emails. Rather than let her learn from a regulator's letter that her past warnings would be part of the record, we walked her through what disclosure would show and why it was the safer path for everyone, including her own professional exposure, compared to a report that understated the history. That conversation was difficult, but it meant nobody was blindsided once the file was complete.
  8. Trained the floor supervisor on documenting near-misses going forward. Since the guarding issue had first surfaced as an informal, undocumented concern, we set up a simple written near-miss log for the shop floor, reviewed by Elena on a monthly basis, so that future hazard observations, however minor, would be recorded, tracked, and escalated with an actual deadline rather than passed along verbally and forgotten.

The outcome

The Ministry accepted the revised investigation report and corrective action plan roughly ten weeks after the accident, and the file was formally closed without further escalation or penalty. The injured worker returned to modified duties a few months later under a separate return-to-work process handled alongside the compliance work. On the regulatory side, the outcome was close to as good as it could have been once the delay and the earlier gaps in documentation were part of the record, and the negotiated compromise reflected that: the Ministry accepted the disclosed history in exchange for a corrective action plan with real, checkable commitments.

It came at a cost that had nothing to do with money. Ioana's role at the shop changed permanently. She continued doing occasional work under the new written contract, but the informal, drop-in relationship she had with Carlos for two decades did not survive the process intact. Carlos told us afterward that the hardest part was not the regulator, it was the conversation where Ioana realized her old emails were going to be part of a formal government file, and that neither of them had treated her earlier warnings with the seriousness they deserved at the time.

The company also spent real money redoing work that should have been done once. The original informal walkthroughs and the first investigation draft were, in effect, wasted effort against what a regulator required, and the trust absorbed the cost of the second pass, the engineer's assessment, and the professional fees. That was not a small line item for a company this size, and Carlos was candid that it stung to pay twice for work that should have been right the first time.

Carlos and Elena kept the shop compliant and kept their trustee obligations intact, which was the outcome that mattered most for the business and for the family that depended on the trust's income. The near-miss log and the new written contract with Ioana mean the shop is now better positioned than it was before the accident, even though getting there required conceding that the earlier, friendlier way of doing things had left real gaps. The friendship cost was the part nobody could negotiate away, and it is the part that stayed with Carlos longest.

What you can learn from this

  • Informal safety advice from a trusted contact still counts as notice of a hazard once something goes wrong; put safety concerns in writing and act on them regardless of how the relationship feels.
  • A friend or relative doing professional work for your company needs a written scope and fee arrangement just as much as a stranger would, so that accountability is clear if something goes wrong.
  • Reporting an incident on time is necessary but not sufficient; the follow-up investigation and corrective action plan face separate, often tougher scrutiny.
  • Disclosing a known gap in your own documentation, on your own terms, almost always produces a better result than having a regulator find it first.
  • When a close relationship is mixed into a compliance problem, bringing in an independent party to do the actual verification work protects both the business relationship and the outcome.
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 →