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

When a Caterer's Morning-Of Collapse Ended Up in Court

A caterer showed up short-staffed and short on food on a Brampton couple's wedding day. What began as a bad morning turned into a lawsuit over a delayed payment neither side had handled well.

Litigation8 min readBrampton, OntarioWedding and event vendors
All Litigation case studies
ClientVartan and Jacek, a Brampton couple sued by their wedding caterer over a delayed final payment
The issueA caterer sued for the full contract balance after showing up short-staffed and short on food on the wedding day
ServiceDocumented the day-of shortfall, addressed a family member's angry message and reviews, and filed a counterclaim for the loss
ResolutionSettled for $6,500, well below the roughly $41,000 originally demanded

The situation

Vartan and Jacek's wedding plan was about as ordinary as weddings get. They booked a banquet hall in Brampton for a Saturday in September, invited around 140 guests, and signed a catering contract nine months out with Wojciech, whose company had done several weddings for people they knew. The contract set the price at just under $56,000 for a plated dinner, passed appetizers, and a late-evening snack station, payable in three installments: a deposit at signing, a second payment four months out, and the balance due the week of the wedding.

Vartan, a hairdresser, and Jacek, who worked as an administrative assistant, were paying for most of the wedding themselves, with some help from both families, and had built their budget carefully around the catering contract as the single largest expense. The first two payments went out on schedule without incident. Planning otherwise proceeded the way most weddings do, with a florist, a photographer, and a DJ booked separately, a guest list finalized, and seating arrangements worked out over several long evenings at Jacek's parents' kitchen table.

About six weeks before the wedding, Vartan's uncle, who knew someone in the local catering business, mentioned he had heard that Wojciech's company had recently lost a large commercial contract and might be struggling financially. Worried about losing the money already paid if the business failed before the wedding, Vartan's uncle strongly encouraged the couple to hold back the third and final payment until closer to the date, just to be safe, rather than send it on the schedule the contract set out. Vartan, wanting to protect the deposit already paid and trusting his uncle's instinct, quietly told Wojciech the final payment would be a few weeks late, without asking us or anyone else whether that was the right call under the contract.

Wojciech did not raise any objection at the time beyond a brief note acknowledging the delay, and the wedding planning continued through its final weeks with no sign, from either side, that anything was seriously wrong. Neither Vartan nor Jacek gave the delayed payment much more thought once the acknowledgment came back; their attention was on final headcounts, seating charts, and the dozens of small details that fill the last weeks before a wedding. Nobody in either family raised the payment again before the day itself arrived.

Where it went wrong

On the morning of the wedding, Wojciech's crew arrived roughly two hours later than the contracted setup time, with what turned out to be food for closer to eighty guests rather than the contracted 140. Wojciech told the venue coordinator by phone that a walk-in cooler failure at his commercial kitchen overnight had ruined a large portion of the prepared food, and that he was doing what he could to bring in replacements, but there was no realistic way to have a full plated dinner ready for the full guest list by service time.

Jacek's parents and Vartan's uncle spent the two hours before guests arrived calling every caterer, restaurant, and grocery store they could reach, eventually arranging trays of food from a local restaurant to supplement what Wojciech's crew had brought, at an additional cost of just under $4,000 paid on the spot. The reception went ahead, but roughly a third of the guests were served a noticeably different, later meal than everyone else, appetizers never arrived at all, and the late-evening snack station included in the contract did not appear.

In the days after the wedding, before Vartan and Jacek had spoken to a lawyer, Vartan's uncle, upset on the couple's behalf, sent Wojciech a lengthy text message on Vartan's phone, with Vartan's knowledge but largely in the uncle's own words, stating that they would not pay another cent no matter what happened and that they intended to leave detailed negative reviews naming Wojciech's company across several platforms, which Vartan then did within the week. The message and the reviews were understandable reactions to a difficult day, but they became a problem once Wojciech's company filed a claim.

Wojciech's lawyer framed the case around the delayed final payment, not the morning of the wedding. The claim argued that Vartan's decision to delay payment on the third installment was itself the breach of contract, that Wojciech had been entitled to treat the contract as compromised once payment was late, and that the reduced service on the day was a reasonable response to a client who had already fallen out of compliance with the payment schedule, not a breach on Wojciech's part at all. The claim sought the full remaining balance of just over $41,000, plus the cost of defending against what it characterized as defamatory reviews, treating the uncle's message and the reviews as evidence that Vartan had already decided not to pay before anything went wrong on the day.

What we did

  1. Separated the payment delay from the day-of failure. We reviewed the contract's payment terms and confirmed that a several-week delay on the final installment, acknowledged without objection by Wojciech at the time, did not amount to a breach serious enough to excuse Wojciech from delivering the contracted meal for the full guest list. This reframed the case around what actually happened on the wedding day, not the payment timing Wojciech's claim tried to lead with, which was the argument most likely to sway a decision-maker either way.
  2. Gathered contemporaneous evidence of the shortfall. We collected the venue coordinator's notes, timestamped photos from the day, guest headcount records, and the receipt for the emergency food order, building a clear record that Wojciech delivered food for roughly eighty of 140 contracted guests, arrived late, and never provided the appetizers or snack station the contract required. This evidence anchored the claim that Wojciech, not Vartan, had materially failed to perform under the contract.
  3. Addressed the uncle's message and the reviews head-on. Rather than let Wojciech's lawyer use the not-another-cent message and the reviews as proof of bad faith, we obtained a clear account of when they were sent, by whom, and why, and advised Vartan to take the reviews down as a show of good faith while preserving the underlying record of what had actually happened at the wedding, which mattered far more to the outcome than any single message sent in frustration the morning after a difficult day.
  4. Assessed whether the cooler failure was Wojciech's risk to bear. We requested Wojciech's own records about the alleged cooler failure, including any insurance claim or supplier correspondence, and found no documentation supporting that an equipment failure, rather than simple understaffing or overbooking, had caused the shortfall, which weakened the excuse Wojciech's claim relied on to justify the reduced service.
  5. Calculated the actual loss and a fair offset. We worked out the value of what was contracted against what was delivered, factoring in the emergency food cost the family had paid out of pocket, and arrived at a defensible position on what, if anything, was still owed once Wojciech's own shortfall was credited against the outstanding balance instead of treated as a separate, unrelated question.
  6. Responded to the claim with a counterclaim for the shortfall. We filed a defence that laid out the day-of failure in detail and included a counterclaim for the emergency food costs and a partial refund of amounts already paid, shifting the claim from one where Vartan was purely defending to one where Wojciech faced real financial exposure of his own.
  7. Negotiated a resolution before trial. Once Wojciech's side saw the day-of evidence and the counterclaim, we opened settlement discussions rather than pushing toward a hearing date. Both claims carried genuine risk for both sides, so we negotiated a settlement that resolved the claim and counterclaim together rather than litigating the payment timing question to a full trial, sparing Vartan and Jacek the cost, delay, and uncertainty of a result that either side could have come out of worse than the negotiated number.

The outcome

The matter settled about four months after Wojciech's claim was filed, with both the claim and the counterclaim resolved together. Vartan and Jacek paid Wojciech an additional $6,500, well below the roughly $41,000 Wojciech had originally sought, reflecting a modest amount still owed under the contract's payment terms once the delayed installment was accounted for, offset against credits for the missed appetizers, the missing snack station, and roughly half the reduced dinner service. Wojciech's claim for damages related to the reviews was dropped entirely once it was clear the reviews had already come down and the underlying account of the wedding day was not in serious dispute. That part of Wojciech's claim had leaned entirely on the reviews and the message rather than on anything about the actual quality of service, and it did not hold up once the reviews had come down and the day-of record was in front of both sides.

The settlement meant Vartan and Jacek avoided both a trial and the risk of a judgment closer to Wojciech's original demand, while still paying something, since the delayed final installment was a genuine, if minor, breach on their side that could not be argued away entirely. The emergency food costs the family had covered on the day were not separately reimbursed as cash, but were factored into the lower final number, so the family was not, in practical terms, left further out of pocket than the settlement reflected.

Vartan has since spoken to Jacek's parents and to his uncle about the episode, and the family's general view, looking back, is that the decision to delay the payment and the decision to send an angry message before getting legal advice both came from a good place but made an already difficult dispute harder to resolve cleanly. The wedding itself, awkward late food service aside, went ahead and the marriage was unaffected by any of it; the dispute that followed was a contract question, resolved months later, entirely separate from the day guests actually remembered.

What you can learn from this

  • Never deviate from a contract's payment schedule without getting advice first, even with good intentions. A late payment, however reasonable it feels at the time, can hand the other side an argument that you breached first, shifting the story away from what actually went wrong.
  • Keep contemporaneous records of what a vendor actually delivers against what was contracted, including photos, timestamps, and headcounts. Documenting a shortfall while it is happening is worth far more later than memory alone.
  • Well-meant advice from family, sent in anger before a lawyer is involved, can become evidence used against you. Wait until you have spoken to a lawyer before sending anything in writing, or posting anything publicly, about an active or brewing dispute.
  • A vendor's own failure to perform can offset, or even outweigh, a client's minor breach elsewhere in the same contract. Do not assume that being imperfect yourself means you have no claim against a vendor who failed you more seriously.
  • Settling a dispute that runs both directions, a claim and a counterclaim together, often resolves faster and more predictably than litigating either side's version of events to a full trial. Consider what you are owed, not just what is being demanded of you.
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 →