Untangling a Condo Water Damage Claim Without Stopping the Business

The situation

The statement of claim arrived by courier on a Tuesday, addressed to Duc personally and to the numbered company that held his second-floor condominium unit. Valentina, who ran three franchise storefronts on the ground floor of the same Peterborough building, was claiming just over one million dollars. Her position was that renovation work Duc had commissioned upstairs had flooded her stores twice in four months, ruining inventory and forcing two locations to close for repairs while the water damage was traced and dried out.

Duc's day job left him little room to manage a lawsuit. He ran a logistics company with a dispatch floor that operated seven days a week, coordinating a fleet that could not simply idle while a legal file worked its way through the courts. The condominium units were meant to be a passive investment on top of that business, something his sister Daniela managed on his behalf between her own work running several franchise outlets elsewhere in the region. Daniela had handled the renovation contractor, fielded the first complaint from building management, and forwarded Valentina's insurance claim to Duc's property insurer, who had denied coverage on the basis that the cause of the leak was still unclear and could equally have originated in the building's own plumbing.

By the time the claim was served, the relationship between the two owners had gone from cordial to adversarial. Valentina's lawyer had sent two demand letters before litigation, both of which Daniela had answered informally by email rather than through counsel, disputing the cause of the flooding without committing to a firm position either way. Those emails became part of the record once the lawsuit started, and a few of them, written quickly between other calls, read as more concessive about the renovation timeline than Duc had ever intended them to be.

Duc came to us not looking for a fight so much as an exit. He needed the claim resolved in a way that let him keep running his business without spending his weeks preparing for motions and attending case conferences in person, and he needed a clear-eyed answer on how exposed he actually was before deciding whether to settle early, push for a quick trial date, or let the case run its ordinary course. The renovation contractor had since gone quiet, which meant Duc could not simply point the claim in another direction and walk away from it.

The problem

Once we filed a defence and the matter moved into the discovery stage, the case stopped making progress. Valentina's lawyer demanded a broad set of records: renovation invoices, contractor correspondence, the building's maintenance logs, and Duc's internal emails about the units going back three years. Some of that request was reasonable given the size of the claim; a lot of it was not, and answering it in full would have meant weeks of Daniela's time pulling old files instead of running the franchise locations that were her actual job.

Our position was that the claim should turn on a narrower set of facts: what caused the two specific leaks, what the contractor knew and when, and what the building's own plumbing inspection records showed about the condition of the shared risers before the renovation began. Valentina's side disagreed, arguing that the full three-year email history was needed to show a pattern of neglect. For nearly two months the two firms exchanged letters about the scope of document production without resolving anything of substance. Proposed deadlines passed unmet on both sides. A scheduled examination for discovery was cancelled twice because the document exchange it depended on had not happened, and each cancellation reset the clock on the next round of scheduling. Every letter exchanged in that period added to the cost of the file without moving either side's underlying position, since neither firm was willing to concede scope by half-measures while the other held firm.

The real cost of the stall was not legal fees, though those were adding up steadily. It was that Duc's logistics company could not treat the lawsuit as background noise indefinitely. A dispute of this size, left open and unresolved on paper, affected how his bank viewed the company's risk profile at a moment he was trying to renew a line of credit for new equipment, and it kept Daniela pulled away from franchise operations she was supposed to be growing rather than defending. Neither side had a real incentive to let the case drift forever, but neither side was willing to move first either, and letters between counsel were not going to break that pattern on their own.

What the file needed was not another round of correspondence. It needed a judge or associate judge with the authority to set a schedule both sides were actually bound to follow, and a forum where the scope argument could be resolved once and recorded in an order, instead of relitigated by letter every time a new document request landed on either desk.

What we did

1. Reviewed the claim and the full renovation file end to end before responding to any document request, so that we understood which records genuinely mattered to the question of what caused the two leaks and which were being requested mainly to raise Duc's cost of defending the file. That groundwork let us take a defensible, specific position on scope rather than negotiating production in the abstract, letter by letter, with no fixed reference point.
2. Filed a defence that took a clear, evidence-based position on causation, pointing to the building's own maintenance records as a plausible alternative source of the leaks rather than issuing a generic denial. A specific defence, tied to identifiable documents, gave us standing later to argue that broad, unfocused requests going back three years were disproportionate to what the case actually turned on.
3. Requested a case management conference once it became clear the document exchange had stalled twice on its own and correspondence between counsel was not going to resolve the scope dispute. A case management conference puts a judicial officer in direct charge of the schedule, which changes the incentives for both sides to keep the file moving instead of drifting. It is a lower-cost, faster step than a formal motion, and it gave us a fixed date to work toward rather than an open-ended exchange of letters that neither side had any real incentive to end.
4. Prepared a short position paper before the conference setting out exactly which categories of documents we would produce, which we opposed and why, with proposed dates attached to each category. Judges managing a stalled file respond far better to a concrete, itemized proposal than to open argument, and it gave the conference something specific to rule on rather than a general complaint about delay.
5. Used the twenty-minute conference to secure a binding schedule rather than treat it as another round of negotiation. The presiding officer adopted most of our proposed scope, trimmed the maintenance-log request to a shorter and more relevant window, and set firm dates for the outstanding examinations for discovery, with no further extensions available absent consent from both sides.
6. Kept Daniela's involvement to what the schedule actually required, batching document collection into two focused efforts rather than responding to an open-ended, ongoing stream of requests. That structure meant her time on the file was measured in a handful of days rather than the weeks the original request would have consumed, which mattered because she was managing the file alongside her own franchise business, not as her main job.
7. Opened a without-prejudice settlement conversation once discovery produced a clearer picture of what had actually caused the flooding, sharing enough of what we had found to make a serious settlement number possible without disclosing our full evidentiary position ahead of trial. This let both sides start valuing the case realistically rather than negotiating from opposite extremes, and it let Valentina's lawyer take a concrete number back to her rather than continuing to argue causation in the abstract.
8. Negotiated a resolution that reflected shared, not sole, responsibility once the building's maintenance records showed the risers had already been flagged as due for replacement before the renovation started, which weakened but did not eliminate an argument that Duc's renovation work had also played a role in what happened. That mixed picture, rather than a clean finding either way, is what made a negotiated number more realistic for both sides than a trial neither could confidently predict.

The outcome

The case settled roughly a year after it was filed, well short of a scheduled trial date. Duc's contribution to the settlement, funded partly through his property insurer once the maintenance records shifted the picture of fault, came in at a little under half of what Valentina had originally claimed. Valentina, for her part, accepted less than she had asked for and gave up the argument that Duc's renovation was the sole cause of the flooding, since the building's own deferred maintenance on the shared risers was now firmly part of the record either side could put in front of a judge.

Neither side got a clean win, and the settlement said so directly: no admission of liability by Duc, no concession by Valentina that her claim had been overstated, just a number both sides could live with rather than gamble on a trial outcome that would ultimately turn on which expert a judge found more persuasive on causation. That is a realistic result for a case built on competing theories of what caused water damage in an older, shared building, and it let both businesses close the file rather than keep funding a dispute with an uncertain ceiling.

The case management conference itself did not decide who was right, and it was never going to. What it did was stop the file from drifting indefinitely in correspondence, which is where disputes like this one often lose the most time and money without either side actually being wrong about anything. Daniela's involvement dropped back to ordinary property management within weeks of the schedule being set, and Duc's line of credit renewal went ahead with the bank able to see a defined settlement rather than an open-ended lawsuit sitting on the company's books. For a business owner in Duc's position, that predictability was worth as much as the dollar figure itself: a lawsuit with a known ceiling is a very different thing to carry on a balance sheet than one still moving through discovery with no end date attached.

What you can learn from this