The Doorbell Footage That Settled a Repair Dispute in Thornhill

The situation

Arben had eleven days left to file a defence when he first called our office, and by the time we spoke, three of those days were already gone to a weekend and a missed callback. The claim, filed in Small Claims Court, was for roughly 28,000 dollars, alleging that a repair Arben had done on a client's high-end espresso machine had caused a water leak that damaged the flooring and cabinetry in the client's kitchen weeks later.

Arben worked full time in a warehouse, and the appliance repair work was something he did on evenings and weekends, mostly through word of mouth among neighbours and a small circle of regular clients built up over several years. His partner Anh, a pharmacy technician, often took the calls and kept track of who owed what, since Arben himself was not much for paperwork. Duc had been one of those regulars, a client Arben had done small jobs for twice before without incident. This particular repair, replacing a worn seal inside the machine's water line, was routine work Arben had done dozens of times, and he had never before had a complaint about a job going wrong.

The dispute had actually started months earlier, and it had briefly looked like it might resolve without a lawsuit at all. Both Arben and Duc, communicating directly, had agreed early on to bring in a single independent appliance technician to inspect the machine and the damaged flooring and give an opinion on what had caused the leak, an approach that would have been faster and cheaper than dueling experts on each side. That agreement fell apart within weeks, before any inspection took place, over a disagreement about exactly what the technician should be asked to assess.

By the time the claim was filed, there was no expert report, no agreed account of what had gone wrong, and a deadline that did not care how the negotiation had unraveled. Arben, who had never been sued before and did not know Small Claims procedure at all, was staring at a number that was more than a year of his warehouse income and a process he did not understand how to navigate in the time remaining. Anh had suggested weeks earlier that they get advice, but Arben, embarrassed and hoping the whole thing would resolve itself, had kept putting it off until the claim itself arrived and the choice was no longer his to delay.

What the review found

Once we were retained, the first task was understanding exactly where the joint expert process had broken down, since that history mattered both practically and strategically. Arben and Duc had agreed on the technician to use, but had never agreed in writing on the scope of the questions the technician would answer. Duc's version of the instructions asked the technician to assess whether the repair had been performed to a competent standard at all. Arben's version asked only whether the specific seal replacement could plausibly have caused a leak weeks after the work was completed. Those are different questions with different answers, and neither side would defer to the other's framing, so the technician never received agreed instructions and the inspection never happened, and by the time either side realized the arrangement had quietly died, several weeks had already passed with nothing done.

With the joint process dead and no expert report on either side, we reviewed what evidence actually existed rather than what either party remembered or asserted. Arben kept minimal paperwork for his side jobs, mostly text message confirmations of appointments and rough handwritten notes of what parts he had used, which was thin but not nothing. Duc's claim relied heavily on his own account of when the leak was first noticed and an assumption, not independently verified, that it began immediately after Arben's visit.

The review turned up something neither side had thought to check: Duc's home security system included a doorbell camera that, because of how its storage was configured, retained footage and event logs going back several months. Those logs showed the exact date and duration of Arben's original visit, and, more importantly, showed no plumber, contractor or maintenance visit to the property in the seven weeks between Arben's repair and the date Duc said the leak was discovered, a gap Duc's own claim had never explained.

That timeline gap did not clear Arben entirely. It was equally consistent with a slow, gradually worsening leak from a competent repair that developed a minor defect over time as it was with an outright installation error. But it directly undercut Duc's stronger claim, that the damage was sudden and obviously tied to negligent work, and that distinction mattered a great deal to how a Small Claims deputy judge was likely to weigh the case. It reframed the dispute from a question of whether Arben had done careless work into a question of how much any single, unverifiable cause could fairly be blamed for a slow-developing problem in a busy household kitchen.

What we did

1. Filed a defence within the deadline that preserved Arben's full range of arguments. With days to spare, we filed a defence that did not concede the cause of the leak while it was still under investigation, avoiding the far more common mistake of filing a bare, vague denial that leaves little room to raise new evidence later in the process.
2. Reconstructed the joint expert breakdown from the message history. Anh, who had handled most of the scheduling and client communication for Arben's side work, still had the full text exchange between Arben and Duc from months earlier, and we used it to establish, clearly and in writing, that the joint process had failed over a genuine disagreement about scope, not because Arben had refused to cooperate, which mattered for how the court would view his conduct throughout.
3. Requested the security system logs through the Small Claims disclosure process. Once we learned Duc had a doorbell camera, we formally requested the retained footage and event logs covering the period between the repair and the alleged discovery of the leak, since this was the only independent, timestamped record of what had actually happened at the property, and it existed regardless of what either party remembered or was prepared to say under oath, which made it far more persuasive than either side's own account.
4. Retained a technician for a limited, targeted opinion. Rather than restart a broad joint process that had already failed once, we retained our own appliance technician to answer one narrow question: whether the timeline shown in the security logs was more consistent with a sudden failure or a slow developing one, keeping the cost proportionate to a Small Claims matter, since a full re-inspection of the machine and the kitchen would have cost more than the difference it was likely to make.
5. Used the timeline gap to challenge the core of Duc's claim. We built our position around the seven-week gap with no recorded maintenance visits, arguing this was inconsistent with Duc's account of sudden, obvious damage traceable directly to Arben's repair, which shifted the practical question from fault to degree, and meant the case would turn on proportion rather than on whether Arben had done anything wrong at all.
6. Proposed a settlement conversation before the hearing date. With the technician's narrow opinion and the timeline evidence in hand, we approached Duc's side to discuss resolving the matter without a hearing, framing the security footage as evidence that would likely reduce, not eliminate, whatever a deputy judge ultimately awarded, and pointing out that a contested hearing carried real cost and uncertainty for both sides.
7. Negotiated a reduced payment reflecting shared uncertainty. We settled on a figure that acknowledged Arben's repair was a plausible contributing factor without accepting Duc's full account of sudden, obvious negligence, closing the file without a contested hearing and the added cost, delay and uncertainty a hearing would have brought for both sides regardless of who ultimately won, and without either side conceding the version of events they still genuinely disputed.

The outcome

Arben settled the claim for roughly 11,000 dollars, well below the 28,000 dollars Duc had originally claimed, and the settlement included no admission that the repair had been performed negligently. The figure reflected a genuine compromise: enough to acknowledge that Arben's repair was a plausible contributing cause, not so much that it treated the seven-week gap in the timeline evidence as irrelevant to how the damage actually developed.

This was not a case where our client walked away clean, and it would be misleading to describe it that way. Arben paid an amount that represented a real financial setback for someone doing side work to supplement a warehouse income, roughly equivalent to several months of what that side work brought in after parts and travel costs. The months of stress leading up to the settlement, including the period when the joint expert process collapsed and he had no clear idea what evidence existed or how strong Duc's case actually was, cost him time and sleep that a better-documented process from the start, or earlier advice, might have avoided.

What the settlement did accomplish was containment, which for a Small Claims matter of this size is often the realistic and honest goal rather than an outright win. Without the security footage timeline, Arben was facing a real risk of a judgment closer to the full amount claimed, based largely on Duc's own uncorroborated account of when the damage first appeared and how quickly it had worsened. The gap in the maintenance record, an ordinary piece of evidence neither side had thought to look for when the joint expert process was still alive and everyone assumed a formal inspection would settle things, ended up doing more to limit the loss than either side's original expert plan ever would have accomplished on its own.

What you can learn from this