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

One inspector's letter, two companies, and a lender who wanted his equipment protected first

A stop-work order at a Petawawa manufacturing facility threatened two commonly owned companies at once, and the man financing the equipment inside it had his own idea of how fast the problem should be fixed.

Corporate9 min readPetawawa, OntarioOrders that can close a business
All Corporate case studies
ClientRohan and Rakesh, owners of two companies sharing a Petawawa facility
The issueA stop-work order halted production at a facility shared by two companies, with a third stakeholder's financing at risk
ServiceManaged the remediation and regulatory response while coordinating three parties with different priorities
ResolutionThe order was lifted after deficiencies were fixed, and operations resumed with no further enforcement action

The situation

The letter arrived on a Tuesday, addressed to the facility manager, and it took less than a page to say that the entire assembly line was to stop operating immediately. A workplace safety inspector had visited the Petawawa facility three days earlier, following an incident in which a worker's hand was caught in an unguarded section of a conveyor system, and had returned with a stop-work order covering the affected production area under the Occupational Health and Safety Act. The worker's injuries were not life-threatening, but the order did not care about that distinction. It simply stopped the line.

The facility served two separate companies under common ownership. Rohan, a specialist physician who had moved into manufacturing investment over the previous decade, and Rakesh, his longtime business partner, jointly owned both a precision components manufacturer and a smaller assembly and logistics company that operated out of the same building, sharing equipment and, on the affected line, sharing staff. Combined, the two companies generated somewhere between twenty and sixty million dollars in annual revenue, and the stopped line accounted for a meaningful share of both companies' output.

There was a third party with a direct stake in what happened next. Vincenzo, a retired business owner who had sold his own equipment supply company to Rohan and Rakesh several years earlier, held a vendor take-back note secured against much of the machinery on the affected line, including the conveyor system itself. He was not involved in running the business day to day, but a stopped line meant no revenue to service the note, and equipment sitting idle under a compliance order was, from his perspective, collateral losing value by the week.

The three of them agreed on the basic goal, getting the line running again as fast as possible, but not on much else. Rohan and Rakesh wanted to understand the full scope of what the inspector might find if a broader review followed, and were willing to take the time to do that properly. Vincenzo wanted the fastest possible fix regardless of what else the inspection might turn up, because every week of downtime made him more nervous about the note. Coordinating a single response across two companies and a secured creditor, all with genuinely different incentives, turned out to be almost as much of the work as the compliance issue itself.

What the other side was relying on

The inspector's order rested on a straightforward finding: the conveyor's guarding did not meet the standard the regulation required, and the gap had existed long enough that it should have been caught by the facility's own internal inspection process. The order itself required only that the specific guarding defect be corrected. But an inspector's authority does not come from the wording of any one order. It comes from the Occupational Health and Safety Act itself, and it is broad enough to reach well past the single defect that triggered the visit, on the reasoning that a guarding failure serious enough to injure someone often points to a systemic gap rather than an isolated defect.

That authority mattered a great deal to how the case would unfold, though not because it could keep this particular order open. An order that has actually been complied with is supposed to be lifted on its own terms; the inspector cannot simply hold it open pending a wider audit of the safety program. What the authority meant, practically, was that a broader review could still produce further requirements, or new orders, reaching areas the original order never touched, even after the guarding defect itself was fixed and this order was gone. The inspector's stated position, communicated during an early call, was that the facility's maintenance logs showed the guarding issue had likely been present for at least several months, which, if accurate, suggested a pattern of deferred maintenance rather than a single overlooked defect.

This was the part of the file that most worried Rohan and Rakesh. If the inspector's broader review found other deficiencies elsewhere in the facility, further orders or requirements could reach well beyond the one line, and could extend to areas serving the second company as well, since both operations shared the same maintenance program and the same safety committee. A finding of systemic neglect could also expose the companies to a more serious enforcement track, including the possibility of charges under the same legislation, which carries penalties well beyond the cost of fixing a guard.

Vincenzo's read of the situation was narrower and, in a way, harder to argue with on its own terms. He was not exposed to regulatory penalties in the same way the two companies were, since his interest was as a secured creditor rather than an operator. His priority was getting the equipment back into productive use, and he pushed, more than once, for the companies to fix the immediate defect and push back hard against any broader review, on the theory that the fastest path to resuming operations was also the path that protected his security. That was not entirely wrong, but it was not the whole picture either, and reconciling it with what the regulatory situation actually required took real negotiation among the three of them before we could even approach the inspector with a unified plan.

What we did

  1. Reviewed the order and the inspector's stated basis for it to understand precisely what had to be fixed to lift the stop-work order itself, separate from the broader safety program review the inspector had signalled an intention to conduct, since conflating the two would have either delayed the immediate fix or understated the real scope of what the companies needed to address before production could safely resume. That distinction became the organizing principle for the whole response.
  2. Commissioned an independent facility safety assessment covering the affected line and comparable equipment elsewhere in the building, so that when we approached the inspector, we could speak from our own audit rather than waiting for the inspector's broader review to surface problems we had not anticipated, which put the companies in a stronger negotiating position throughout and gave us a defensible basis for the remediation plan we proposed.
  3. Mediated a joint position among Rohan, Rakesh, and Vincenzo that balanced the need for a genuine, credible remediation with the real cost of extended downtime, persuading Vincenzo that a rushed, superficial fix risked a longer shutdown if the inspector's broader review later found it inadequate, which was ultimately the argument that shifted his position toward supporting a fuller remediation rather than a bare-minimum patch.
  4. Directed remediation of the specific guarding defect immediately, prioritizing the fix that would allow the fastest possible partial resumption, since the regulation did not require every finding from the broader assessment to be resolved before the order itself could be reviewed for lifting, and delaying that first repair would have cost the companies time without buying them anything in return.
  5. Prepared a written remediation report for the inspector documenting both the immediate fix and a committed timeline for the additional items our own assessment had identified, giving the inspector a credible basis to trust the facility's safety program going forward rather than treating the guarding failure as an isolated repair with no follow-through behind it. The report was built around our own audit findings, not just the single defect the inspector had flagged.
  6. Negotiated a phased approach to the broader review, proposing that the affected line resume operation once the specific defect was remediated and verified, with the additional facility-wide items completed on an agreed schedule subject to follow-up inspection, rather than holding the entire operation closed until every item on a longer list was finished, which would have cost far more than the risk actually justified.
  7. Coordinated the second company's operations during the shutdown period, confirming which of its functions could continue using unaffected parts of the shared facility and which needed to pause, to limit the financial impact on the company that was not directly named in the order but shared the same building, staff, and maintenance program with the one that was. That mapping work was done in the first week, before the remediation timeline was even settled.
  8. Kept Vincenzo informed with regular, specific updates rather than general reassurance, sharing the remediation timeline and the inspector's actual feedback as it came in, which reduced the pressure he was putting on Rohan and Rakesh to rush the fix once he could see concrete progress against a credible schedule rather than an open-ended delay with no visible end point. Those updates went out weekly, on a fixed schedule he could rely on.
  9. Confirmed the order was formally lifted in writing once the guarding defect was verified and the phased plan was accepted, and secured written confirmation of the follow-up schedule for the remaining items, so the companies had a clear, documented record of exactly what remained outstanding and by when, rather than relying on an informal understanding with the inspector's office that could later be disputed.

The outcome

The inspector accepted the phased approach. The affected line resumed operation roughly three weeks after the order was issued, once the guarding defect was fixed and verified on site, with the remaining items from the broader safety assessment completed over the following two months under a schedule the inspector reviewed and did not object to. No further enforcement action followed, and no charges were laid, which had been a real possibility given the inspector's initial description of a pattern of deferred maintenance.

The three-week shutdown was not free. Both companies lost roughly three weeks of output from the affected line, and the second company absorbed a smaller but real disruption from operating with part of the shared facility unavailable. Vincenzo's note payments were interrupted for that period, though the companies caught the arrears up within the following quarter once operations were fully back to normal, and he did not pursue any action against the security in the meantime.

What held the three of them together through the disagreement about pace was, in the end, the shared recognition that a fast but incomplete fix risked a longer shutdown later, not a shorter one now. Rohan and Rakesh used the broader assessment to overhaul the facility's ongoing maintenance and inspection program, which they credited, a year later, with catching two smaller guarding issues before an inspector ever needed to. Vincenzo, for his part, said afterward that he had been wrong to push as hard as he did for speed over completeness, though he was quick to add that someone in his position, with a note riding on the equipment, was never going to feel entirely comfortable watching a line sit idle regardless of how sound the reasoning behind it was.

The second company, the smaller assembly and logistics operation, came through with less disruption than initially feared. Because it was never named directly in the order, and because we had mapped in advance which of its functions did not depend on the affected line, it kept roughly two-thirds of its normal output running throughout the three-week period using unaffected parts of the shared facility. That planning meant the financial pressure on the group as a whole was concentrated in the manufacturing company rather than spread evenly across both, which made the numbers easier for Rohan and Rakesh to absorb without touching separate financing arrangements tied to the logistics business.

What you can learn from this

  • A regulator's authority to look past the specific defect that triggered an order comes from the legislation itself, not from the order's wording, and understanding that difference early shapes the right response far more than reacting only to the letter of the order as written.
  • When multiple parties share exposure to a compliance problem but hold different kinds of interest in the outcome, aligning them on a single strategy before approaching the regulator matters as much as the remediation work itself.
  • A rushed, superficial fix can create a longer shutdown than a thorough one, because a regulator deciding whether to trust a safety program again is assessing credibility, not just checking a single box.
  • Commissioning your own independent safety assessment before a regulator's broader review is complete puts a company in a position to negotiate from its own findings rather than reacting defensively to whatever the regulator finds first.
  • A secured creditor's interest in a business it does not operate can pull toward speed in ways that conflict with what a regulatory situation actually requires, and that tension needs to be managed directly rather than left to resolve itself.
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 →