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

An Old Certificate Folder Became the Whole Case

A demand letter accused a Peterborough franchisee corporation of hiring an uninsured subtrade whose worker was hurt on site, and the strongest answer turned out to be sitting in an ordinary admin folder nobody had thought to check first.

Corporate8 min readPeterborough, OntarioBusiness insurance coverage
All Corporate case studies
ClientSampath, co-owner of a Peterborough franchisee corporation and a partner in an engineering firm
The issueA demand letter alleging the franchisee corporation failed to verify a subtrade's insurance before a worker was injured on site
ServiceLocated and authenticated the certificate-of-insurance records the company had actually collected, and used them to reframe the exposure
ResolutionLoss contained: the company was not fully insulated from the claim, but the paper trail it already had cut its exposure well below what the demand letter first suggested

The situation

The letter arrived by courier, addressed to the franchisee corporation directly rather than to its insurer, and it did not waste time on preliminaries. It alleged that a worker employed by a subtrade the company had hired for a commercial fit-out, a man the letter did not name but described as having fallen from an improperly secured platform, had suffered serious injury, and that the franchisee corporation bore responsibility because it had failed to confirm the subtrade carried adequate insurance before allowing the work to begin. It demanded a response within three weeks and referenced a claim already filed against the subtrade's own policy, which the letter said had lapsed months earlier.

Sampath had built the franchisee corporation with Dawit over nearly a decade, growing it from a single location into a company doing tens of millions in annual revenue, running commercial installation and fit-out work across the region. Sampath had trained originally as a structural engineer and still held a partnership stake in an engineering firm on the side, which was part of why the company had, early on, adopted a policy neither owner could remember whose idea it had actually been: every subtrade hired for a job had to submit a certificate of insurance before being allowed onto a site, filed by the office administrator into the job folder as a matter of routine.

Meron, who owned a logistics company the franchisee corporation used regularly to move materials between sites, had been on the same job the week of the incident, delivering equipment, and had briefly spoken with the injured worker that morning, though Meron's company had no direct role in the injury itself. The overlap meant Meron's name appeared in early correspondence about the incident, which added confusion in the first days about who exactly had been responsible for what.

What worried Sampath and Dawit most was not the injury itself, which was genuinely serious, but the specific allegation that the company had never verified the subtrade's coverage at all. If that were true, it would mean the company had exposed itself to exactly this kind of claim knowingly, or at least carelessly, on every job it had run for years.

The legal question

Collecting a certificate of insurance from a subtrade before work begins is common practice, and a reasonable one, but it does not by itself transfer legal responsibility for an injury away from the general contractor or the corporation that hired the subtrade. A certificate is evidence that a policy existed on a given date; it is not, on its own, proof the general contractor exercised proper oversight of site safety, and it does not automatically make the general contractor immune from a claim if the injury also involved conditions the general contractor itself controlled, such as the platform the worker was using when he fell.

The demand letter's central allegation, that the company had never checked the subtrade's insurance at all, was a specific and serious claim, because if true it would suggest a pattern of carelessness rather than a single unfortunate incident, and it would undercut any argument that the company had taken reasonable steps to manage the risk of hiring outside trades. The letter's author clearly believed no such verification had ever happened, likely because the subtrade's policy had lapsed by the time of the injury and no current certificate could be produced for that specific date.

The real legal question, then, split into two separate parts. The first was factual: had the company actually collected a valid certificate before this subtrade started this job, whatever had happened to the policy afterward. The second was legal: even if it had, did that discharge the company's own duty to ensure the site itself, including the platform, was reasonably safe, since a valid insurance certificate covers the subtrade's own liability and does not automatically answer whether the general contractor met its separate obligations around site conditions.

Answering the first question accurately mattered enormously, because it would determine whether the company was defending a genuine oversight failure or a subtrade's own coverage lapsing after the fact, two very different positions with very different consequences for how exposed the company actually was.

That duty to keep the site itself reasonably safe does not disappear just because a certificate was collected, because a certificate speaks to insurance, not to who adjusted a platform or whether that adjustment was communicated to the people using it afterward. Collapsing the two questions into one broad claim of carelessness was doing real work for the other side: a company that had verified insurance but still had a genuine site-safety gap could end up conceding more than it needed to if it treated one clean answer as resolving both.

What we did

  1. Asked the office administrator directly whether any record existed of the subtrade's certificate, rather than relying on Sampath and Dawit's own recollection, since neither owner handled that paperwork personally and neither could say with certainty what had or had not been filed for this particular job. The administrator remembered the routine clearly, even if she could not recall this specific certificate offhand, and pointed us to the shared drive folder where every job's certificates had been filed for years as a matter of ordinary office practice.
  2. Searched the shared certificate folder, organized by job number rather than by subtrade, which took real effort to work through given how the files had accumulated over the years, and located a certificate for the subtrade in question dated roughly three weeks before the job began, showing coverage that was valid and adequate on its face at the time it was collected. It had never been treated as significant by anyone at the company; it was simply routine paperwork, filed and forgotten.
  3. Had the certificate authenticated against the insurer named on it to confirm the policy had genuinely existed on that date, rather than accept the company's own file at face value, since a claim this serious warranted independent verification rather than trusting an internal record without a second source. The insurer's own files corroborated the certificate independently of anything the company itself said, closing off any argument that the document had been reconstructed after the fact.
  4. Reframed the response to the demand letter entirely around the verified certificate, rather than defending against an allegation that no verification had ever occurred, which was false. The response established that the company had followed its ordinary practice, collected a valid certificate before work began, and had no reasonable way of knowing the subtrade's policy would later lapse mid-project — a gap in the subtrade's own conduct, not evidence that the company's own vetting at the outset had been careless.
  5. Arranged an independent engineering review of the site conditions and the platform's setup, since the certificate could not answer the separate question of what the company's own crew had and had not controlled that day, and assuming it resolved everything would have left a real gap unexamined. The review took several weeks and required interviewing the crew members who had worked on the platform earlier that week about exactly what adjustments they had made, when, and why the change had not been flagged before the subtrade's worker used it.
  6. Corresponded directly with the subtrade's insurer and the claimant's counsel once the review's findings were in hand, to make clear the coverage question and the site-safety question were two distinct issues rather than one undifferentiated allegation of carelessness. That separation narrowed what the company was actually being asked to answer for and set the stage for a negotiation that addressed the two questions on their own separate terms instead of collapsing them into a single claim of blanket disregard.
  7. Clarified Meron's logistics company's limited role in the incident with the claimant's counsel early in the process, since the overlap in timing and Meron's brief conversation with the injured worker that morning had already created confusion in the early correspondence about who bore responsibility for what. Left unaddressed, that confusion risked becoming a second, unnecessary front in a dispute the company already had enough to manage without it.

The outcome

The certificate did not end the claim, but it changed its shape substantially. Once the claimant's counsel accepted that a valid policy had existed when the subtrade started the job, the allegation of blanket carelessness in vetting subtrades fell away, and the dispute narrowed to the platform's condition and who had actually controlled it, a much smaller and more specific question than the one the original letter had raised. The independent site review found shared responsibility between the company's own crew, who had adjusted the platform earlier that week, and the subtrade's own worker, who had not reported the adjustment before using it the morning of the fall.

The company ultimately contributed to a settlement reflecting that shared responsibility, a sum in the mid five figures once negotiations concluded over several months, well below what a finding of complete disregard for subtrade vetting would likely have produced, and well below the opening position the demand letter had staked out at the outset. It was not a finding that the company had done nothing wrong; the platform issue was real, the crew's failure to communicate the adjustment mattered, and the settlement reflected genuine, if partial, fault on the company's side rather than a clean vindication.

Meron's logistics company, despite the early confusion around the delivery timing, was never named in the eventual claim once the facts were sorted out, and the correspondence clarifying that point closed off what could otherwise have become a second, unnecessary front in the dispute. Sorting that out early, rather than letting it linger, saved the company from a separate distraction during an already difficult negotiation.

Sampath and Dawit came out of it with a clearer sense of what their existing paperwork practice was actually worth, and what it was not. The certificate-of-insurance policy, treated for years as routine filing nobody thought much about, turned out to be the single most useful piece of evidence in the entire dispute, simply because it had been collected consistently and kept. The site-safety gap it could not answer for became a separate, ongoing project, reviewing how the company documents changes made to shared equipment on active job sites, so the next incident, if one occurs, does not turn on memory the way this one nearly did.

What you can learn from this

  • Collecting a certificate of insurance from every subtrade before work begins is a genuinely useful practice, but keep in mind it proves coverage existed on a specific date; it does not automatically resolve your own separate obligations around site safety.
  • Routine administrative paperwork, filed and forgotten, can become the single most important piece of evidence in a dispute years later; keep it, and know where it lives, even when nobody expects to need it.
  • Checking a subtrade's coverage at the start of a job is the right first step, but most construction contracts require insurance to be carried for the whole of the work; the obligation is normally to keep it in place, not to confirm it once, and whether a later lapse becomes your problem depends on what your contract with the owner and your subcontract actually required.
  • When a demand letter makes a broad allegation of carelessness, check the specific factual claim behind it before assuming the worst; the actual record may tell a narrower and more defensible story than the letter suggests.
  • Shared responsibility for an incident, where both your own crew and an outside subtrade contributed, is a realistic and honest outcome; expect to contribute to resolving a claim rather than expecting full vindication.
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 →