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

One Hundred Guests, No Venue, Six Days Before the Wedding

Ishara and Dilshan had booked an entire countryside estate near Mount Forest for their wedding weekend, with rooms for out-of-town guests already assigned. Six days out, the venue told them the date had been double-booked.

Litigation8 min readMount Forest, OntarioWedding and event vendors
All Litigation case studies
ClientIshara and Dilshan, a condominium-owning couple planning their wedding, an elementary school teacher and an insurance adjuster
The issueA countryside venue double-booked their wedding weekend and offered a Tuesday instead, six days before the event
ServiceUrgent breach of contract action and settlement negotiation to recover deposits and cascading losses
ResolutionWin: full recovery of the booking loss and vendor deposits, secured without a trial

The situation

What Ishara kept coming back to, in the days after the phone call, was not the money. It was the guest list: forty-one people who had already booked flights or long drives to Mount Forest, a dozen of whom were staying at the estate itself because the venue's package included overnight rooms for out-of-town family, and several older relatives who were not going to be able to simply rearrange their travel on six days' notice. The venue had told them, almost apologetically, that a booking error meant another couple also held the date, and that the only alternative on offer was a Tuesday two weeks later, a day when most of those forty-one people would be back at work.

Ishara and Dilshan, who owned a condominium together and had been saving toward the wedding for most of the eighteen months since their engagement, had booked the estate more than a year earlier specifically because it offered a full weekend package: the ceremony space, a reception tent, on-site catering, and lodging for guests, all bundled into one contract with one deposit schedule. That bundling was part of what made the venue's failure so damaging. It was not just a ceremony location falling through. It was the accommodation their families were counting on, the caterer who had built a menu around the venue's kitchen, and a florist and photographer who had scheduled their entire weekends around this specific date and location.

Edwin, who owned and ran the estate, had accepted a full deposit from Ishara and Dilshan roughly a year before the wedding and, as it turned out, a full deposit from a second couple for the same weekend about eight months later, apparently without the double booking being caught by whatever system the venue used to track its calendar. By the time anyone noticed, both couples were six days from their wedding dates, and Edwin's business could not accommodate both.

The financial exposure went well beyond the venue deposit itself. Between the venue package, the non-refundable deposits already paid to the caterer, florist, and photographer who had all built their own weekends around this date, and the practical cost of rebooking flights and accommodations for family members who had already committed to travel, the couple's realistic losses sat somewhere in the range of a hundred thousand to three hundred and fifty thousand dollars if the wedding could not proceed at or near the planned date and location. Ishara's immediate fear was not a courtroom outcome months away. It was what to tell forty-one people in the next six days.

The legal problem

At its core, this was a straightforward breach of contract: Edwin's venue had accepted a booking, taken a deposit, and then failed to deliver the date it had promised. But a straightforward legal wrong does not automatically produce a fast practical solution, and the gap between the two was the real problem Ishara and Dilshan faced. A breach of contract claim, pursued through the ordinary court process, typically takes months at a minimum to resolve, often longer, and a wedding that has already been paid for does not wait for a court date.

The contract itself, like most venue agreements, almost certainly had not contemplated the venue simply being unavailable due to its own scheduling error, and it did not include a workable remedy for that scenario beyond a vague promise to refund the deposit. A refund alone would not have come close to covering the couple's actual losses, which extended well past the venue fee itself into the deposits paid to caterers, florists, and a photographer who had each committed their own weekend to this date and would not simply refund a cancellation on short notice either.

The legal question, then, had two layers. The first was whether Edwin's business was liable not just for the venue fee but for the broader, foreseeable consequences of the double booking, including the deposits paid to other vendors who had coordinated around the venue's date and the reasonable costs of accommodating guests who had already committed to travel. Contract law generally holds a party responsible for losses that were reasonably foreseeable at the time the contract was made, and a venue that markets itself specifically as a full-weekend destination package, with guest lodging built in, should reasonably expect that a cancellation this close to the date would cascade into losses well beyond its own fee.

The second layer was urgency itself. Six days before a wedding, the couple needed either the original venue restored, a genuinely comparable replacement secured immediately, or a resolution fast enough to plan around, not a legal process that would still be running months after the date had come and gone one way or another. That timeline shaped almost every decision made in the days that followed far more than the underlying contract law did.

There was also a question of who else might bear some responsibility. The caterer, florist, and photographer had done nothing wrong themselves; their contracts were with the couple directly, and their own cancellation terms, standard for small event-service businesses booked a year in advance, did not require them to refund deposits simply because an unrelated venue had failed. That meant the couple's realistic path to recovering those losses ran through Edwin's business, as the party whose failure had actually caused the vendor arrangements to collapse, rather than through separate disputes with each individual vendor who had done nothing to cause the problem.

What we did

  1. Reviewed the venue contract within hours of the first call. We treated this as an emergency file from the start, reading the booking agreement, deposit schedule, and cancellation terms the same day Ishara called, because every subsequent decision, including whether to fight for the original date or pivot immediately to a replacement, depended on understanding exactly what Edwin's business had actually promised in writing, and what it had not.
  2. Sent an urgent letter demanding the original booking be honoured or an equivalent resolved immediately. Rather than starting with a claim for damages, we first pressed Edwin directly to explain how the double booking had happened and whether any accommodation, including bumping the later-booked couple to an alternate date or space, was realistically possible, since restoring the wedding itself was worth far more to our clients than money after the fact.
  3. Helped the couple secure a genuinely comparable alternate venue within days. When it became clear Edwin's estate could not accommodate both weddings, we worked with Ishara and Dilshan's wedding planner to identify and lock in a replacement venue capable of hosting the same date and a similar number of guests, and we moved quickly to get that new contract signed so the couple had certainty before the original six days ran out.
  4. Documented every cascading cost as it arose, not after the fact. We asked the couple to keep a running record of every deposit forfeited, every rebooking cost, and every guest accommodation expense incurred because of the venue change, since a claim built on contemporaneous records made and dated as events unfolded is far stronger than one reconstructed months later from memory and scattered receipts.
  5. Pursued the caterer, florist, and photographer deposits as part of the same claim. Rather than treating the vendor deposits as a separate problem for the couple to sort out individually, we folded the loss of those non-refundable payments into the demand against Edwin's business, on the basis that a foreseeable consequence of the venue's failure was the collapse of the coordinated vendor arrangements built around it.
  6. Filed a formal breach of contract claim while settlement discussions continued. To preserve the couple's position and keep pressure on a fast resolution, we commenced a court claim covering the full range of losses, making clear in our correspondence that we were prepared to litigate the matter fully if a reasonable settlement was not reached within a defined and clearly communicated window.
  7. Negotiated a settlement that reflected the full scope of the loss, not just the venue fee. Working from the documented record of deposits, rebooking costs, and the replacement venue's actual price, we negotiated directly with Edwin's insurer and legal representative toward a settlement figure that accounted for every category of loss the double booking had actually caused, rather than settling for a partial refund dressed up as a resolution.

The outcome

Ishara and Dilshan were married on their original date, at the replacement venue secured in the days after the double booking came to light, with the accommodation, catering, and most of the original vendor team intact or rebooked around the new location. Edwin's business ultimately agreed to a settlement that covered the full deposit paid to the original estate, the forfeited deposits to the caterer, florist, and photographer that could not be recovered directly from those vendors, and the couple's reasonable costs of securing and moving to the replacement venue on short notice, landing within the range the couple's actual losses had reached once every category was properly accounted for and tallied.

The settlement was reached without a trial, several months after the wedding itself, once Edwin's side recognized that the documented, contemporaneous record of losses left little realistic room to argue the double booking had caused only minor, easily-refunded harm. Edwin's business did not formally admit fault as part of the settlement, which is typical in resolutions of this kind, but the payment reflected the full scope of what a court would likely have found the venue responsible for, given how foreseeable the cascading losses were for a business marketing itself specifically as a full-weekend package with guest lodging built directly into the price.

What made the real difference, in Ishara's telling afterward, was less the eventual settlement than the speed of the response in the first week, when the wedding itself, not a future court date months away, was what actually hung in the balance for two families already travelling. The legal claim mattered a great deal in the end, but it mattered because it ran alongside the practical work of getting a real venue locked in fast enough that forty-one guests never had to be told the wedding wasn't happening as planned, and never found out how close it came to that.

What you can learn from this

  • When a vendor fails on short notice before a major event, treat the first days as an emergency, not just a future legal claim. Securing a workable replacement fast is often more valuable to you than any later damages award.
  • A business that bundles multiple services into one package, like a venue offering ceremony space, catering, and guest lodging together, can reasonably be held responsible for the full cascade of losses when it fails, not just the fee for the piece it directly provided.
  • Keep a running, dated record of every cost you incur because of someone else's breach as it happens. A claim built on contemporaneous documentation is significantly stronger than one reconstructed from memory months afterward.
  • Losses to third-party vendors, caterers, florists, photographers, caused by another party's breach can sometimes be folded into a single claim against the party who caused the chain reaction, rather than becoming separate disputes you have to chase individually.
  • A formal claim and active settlement negotiation are not mutually exclusive. Filing to preserve your position while continuing to negotiate can produce a faster, fuller resolution than waiting to see whether informal talks succeed on their own.
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 →