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

A Deadline Left by a Retiring Lawyer, and a Band That Never Showed

Aditya and Priya paid a Newmarket event company in full for the wedding they had spent two years planning, including a specific band Priya had chosen. A different act arrived instead, and by the time the file reached us, the clock on their claim was almost out.

Litigation9 min readNewmarket, OntarioWedding and event vendors
All Litigation case studies
ClientAditya and Priya, a Newmarket couple pursuing an inherited vendor breach claim against their wedding event company
The issueA wedding event company sent a substitute band after being paid in full for a specific act, and the client's original lawyer retired mid-file with a deadline approaching
ServiceTook over the file on short notice, secured the filing before the deadline expired, and rebuilt the evidentiary record
ResolutionRecovered a partial settlement that reflected the substitution but fell well short of the full contract value originally claimed

The situation

The email from the courthouse listed a date eleven days out. Under it, forwarded twice, sat a short note from Aditya and Priya's previous lawyer explaining that he was retiring from practice and that his open files were being wound down, theirs included. Nobody had told them clearly, in the weeks before that email landed, that a deadline for taking the next formal step in their claim was about to pass with nothing filed, and Aditya read it three times before he understood what it actually meant for them.

Aditya worked as a construction project manager, running his own small contracting outfit that took on residential renovation jobs around Newmarket, and Priya worked as an optometrist, and the wedding they had spent two years planning had been built around a large Newmarket event company that packaged the venue, catering, and entertainment into a single contract worth several hundred thousand dollars. They had chosen the company precisely because it promised a single point of accountability rather than juggling separate vendors, a decision that would later matter more than either of them expected. The centrepiece, as far as Priya was concerned, was the band: a specific act she had watched perform at a friend's wedding two years earlier and insisted on booking months in advance, named explicitly in the contract and paid for in full as part of the larger package.

On the wedding night, a different band arrived. The event company's representative, a woman named Heather who had signed the contract on the company's behalf, explained on the spot that the act Priya had booked had cancelled and been swapped for a substitute without notice to the couple, framing it as an unavoidable last-minute problem rather than a choice. The evening went ahead because there was no realistic alternative in the moment, guests danced to a band nobody had chosen, and several asked Priya afterward, not realizing the sensitivity of the question, why the group sounded nothing like what she had described beforehand. Aditya and Priya spent the following weeks documenting the difference between what they had paid for and what they had received, eventually retaining a lawyer to pursue the event company for the shortfall.

That lawyer had begun the file competently, gathering contracts and correspondence and sending an initial demand letter that went largely unanswered, but had not yet filed the formal claim when his retirement intervened. The handover happened badly: files transferred late, the approaching deadline buried in a stack of documents the couple had not been told to specifically look for, and eleven days left to either file or lose the claim before it had properly begun.

The legal question

A written contract for wedding services is enforceable like any other commercial agreement, and a supplier who is paid for a specific, named performer and substitutes a different one without the client's consent has very likely breached an essential term of that agreement, not a minor detail the client should simply accept and move past. The band was not incidental to the contract; it was the specific feature Priya had bargained for and the event company had expressly promised in writing, naming the act by name in an appendix to the main agreement.

The more pressing legal question, though, had nothing to do with the band itself and everything to do with time. Claims in Ontario are subject to a limitation period, a deadline set by the Limitations Act after which a claim generally can no longer be pursued at all, and separately, once a claim is filed, court rules impose their own deadlines for taking the next procedural step or risk having the file marked inactive or struck outright. The eleven days remaining were not the original limitation period itself, which had somewhat more room left on it, but a procedural deadline the previous lawyer's office had let slip toward its edge without ever telling the couple that it existed or explaining what would happen if it passed unaddressed.

Missing either kind of deadline does not necessarily end a claim forever, but reviving a lapsed step requires convincing a court that there is a good explanation for the delay and that the other side will not be unfairly prejudiced by allowing the claim to proceed late, an argument that costs time and money to make and is never guaranteed to succeed even when the underlying facts are strong. The straightforward, far safer path was simply not to miss it in the first place, which meant the first eleven days of the file were entirely about procedure rather than the merits of the dispute itself.

There was also a genuine question buried under the deadline pressure about what the couple could actually recover once the immediate crisis passed. The full contract value ran into the hundreds of thousands of dollars, but the band substitution was one element within a much larger event that had otherwise gone ahead largely as planned: the venue was used, the catering was served, and most of the package had been delivered as promised. Valuing a breach confined to one component of a large bundled contract, rather than treating the whole agreement as void, was always going to be the harder, more honest, and more defensible fight to have.

What we did

  1. Filed within the window, before anything else. With days rather than weeks remaining, the first priority was simply protecting the claim procedurally, so we spent the first evening reviewing what the previous lawyer's file already contained and filed the necessary step immediately, treating every other strategic question as secondary until the deadline itself was no longer a threat capable of ending the entire case before it truly began.
  2. Audited the inherited file for gaps. Once the immediate deadline was cleared, we went through the previous lawyer's file line by line and found it thinner than expected: correspondence with the event company existed, but the contract's exact wording on the band, and Priya's own communications establishing how central the choice had been to her, were incomplete or missing entirely.
  3. Rebuilt the record directly with the couple. We asked Aditya and Priya to reconstruct their own communications with the event company from the planning period, working through personal email accounts and message threads the previous file had never captured, including the messages where Priya specifically named the act and the company confirmed it in writing. That direct approach produced a clearer, more complete paper trail than anything the inherited file had preserved, giving us dated proof of what had actually been promised.
  4. Separated the band claim from the rest of the contract. Rather than treating the entire six-figure package as a single breach, we isolated the value the event company itself had attributed to entertainment within its own pricing documents, since a number the company had already put in writing was far harder for its lawyers to dispute than a figure we simply asserted. That gave us a defensible, evidence-backed claim instead of an inflated demand, and let negotiations start from a figure both sides could actually test.
  5. Pressed Heather's company on what actually happened to the original booking. Through formal document requests once the claim was filed, we sought the company's own internal communications about the cancellation and substitution rather than relying on its version of events. Those records showed the original act had cancelled weeks in advance and the company had simply chosen not to tell the couple rather than seeking their consent to a substitute, turning a disputed factual claim into something closer to an admission.
  6. Assessed the realistic recovery honestly. We told Aditya and Priya plainly, before any negotiation began, that a court was unlikely to unwind an entire successful event over one substituted performer when the venue, catering, and most of the package had been delivered as promised. The strongest, most defensible claim was for the value attributable to entertainment plus damages flowing from that specific breach, not the full amount paid for the wedding, and setting that expectation early avoided a painful renegotiation of hopes later.
  7. Negotiated a settlement before trial. With a clear, well-evidenced claim confined to a realistic figure, we opened settlement discussions with the event company's counsel, who had a strong incentive to resolve the matter privately once internal documents showing the company's own conduct were part of the record. Those documents made a public hearing risky for the company's reputation as an event vendor, which gave us real leverage to negotiate a number closer to the entertainment value than the company might otherwise have offered.
  8. Confirmed the settlement addressed the couple's actual grievance, not just the number. Because Aditya and Priya cared as much about acknowledgment as about money, we insisted the settlement terms include a brief written statement from the event company describing what had happened with the booking, giving the couple something closer to the explanation they had never received on the night itself.

The outcome

The claim settled a few months after filing, for an amount that reflected the value of the entertainment portion of the contract plus a modest sum for the breach itself and the cost of arranging alternative entertainment on short notice that night, a figure well below the full six-figure package price and closer to what a court would likely have awarded had the matter gone all the way to trial on the narrower, better-supported claim rather than the couple's original hoped-for number.

Aditya and Priya were candid that the outcome felt smaller than the anger they still carried about their wedding night going differently than planned. The settlement did not undo the substitution or compensate for every disappointed guest who asked about the band afterward, and there was no formal finding that the event company had acted in bad faith beyond the narrow admission the internal documents effectively forced through disclosure. What it did do was close the file with a number that reflected the actual, provable loss rather than the far larger figure the couple had initially hoped for when they first sat down with their original lawyer two years' worth of planning ago.

The near miss with the filing deadline left its own lasting impression, arguably a bigger one than the settlement amount itself. Had the eleven-day window closed without the claim being properly protected, the couple would very likely have had no recovery at all, regardless of how clearly the event company had breached its promise about the band, since a strong case that is never properly filed in time is, for practical purposes, no case at all. The lesson for Aditya and Priya, and the one they mentioned most when the file finally closed, was less about the wedding itself and more about asking early and directly whenever a file changes hands between lawyers, rather than assuming a forwarded email means everything is already being handled.

What you can learn from this

  • When a lawyer retires or transfers a file, ask directly and immediately whether any deadlines are approaching; do not assume a forwarded email means nothing is at risk.
  • A contract naming a specific performer, product, or supplier is enforceable on that specific term; a supplier cannot substitute something different without consent and call it compliance.
  • A breach affecting one part of a large bundled contract is usually valued against that part, not the full contract price, so set expectations around the realistic figure early.
  • Internal communications from the other side, obtained through the claims process, can reveal whether a substitution was a genuine emergency or a choice made and concealed.
  • Procedural deadlines are separate from the original limitation period and can end a claim on their own; missing one does not always mean the story is over, but it should never be tested.
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 litigation problem we handle

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

ContactStart a File →