Six Dundas neighbours, one drainage claim, and a report they never saw

The situation

The plan had been simple enough at first. Six townhouses on the same short row in Dundas had all developed basement seepage within about a year of each other, starting a few years after the row was built, and the owners assumed it was one shared problem with one shared fix. Sunita, a bookkeeper who had lived in the row longest, took it on herself to organize the group, kept a shared spreadsheet of repair estimates, and became the person the others looked to when the builder finally responded to their complaints.

The builder's response, when it came, was to send a contractor to inspect two of the worst-affected units, including Sunita's, and to offer a modest repair and a small payment in exchange for each owner signing a release. Ines, who worked as a pharmacy technician and lived two doors down, held off signing, wanting to see what the repair actually fixed before agreeing to anything. Rui, who lived at the end of the row and had dealt with a warranty dispute on a previous home, told the group he thought the release looked like it covered more than just the repair, but the point did not land at the time. Sunita, eager to get the water out of her basement before another winter, signed the document the contractor handed her without having anyone review it first.

The repair did not hold. Within eighteen months, five of the six units were showing the same seepage again, and it became clear the underlying cause was a grading and drainage error made across the whole row when it was originally built, not a problem specific to any one unit. The owners, now including Sunita, pooled their claims and brought a joint action against the builder for the cost of a proper fix, estimated across the group at around 70,000 dollars.

Early in the case, the group's lawyer discovered that the builder had commissioned its own investigation into the drainage problem shortly after the first complaints came in, well before Sunita signed anything. That investigation, conducted by an engineering consultant on the builder's instructions, would have shown exactly what the builder knew about the cause of the flooding and when. The builder refused to produce it, claiming it was protected.

The group had not planned for a fight over documents at all. Their original expectation, when they pooled their repair estimates and retained a lawyer, was that the case would turn on straightforward proof: photographs of the water damage, contractor quotes, and an expert opinion on the grading defect. Nobody on the row had anticipated that a large part of the case would instead turn on what the builder had written down about itself, and whether the neighbours would ever get to see it.

What the other side was relying on

The builder's position rested on a rule that protects documents prepared mainly in anticipation of litigation from being handed over to the other side during a lawsuit. The idea behind that protection is that a party facing a potential claim should be able to investigate its own exposure candidly, with its lawyers, without handing the other side a roadmap of its own weaknesses. Courts take that protection seriously, and it can cover an internal report even if litigation has not actually started yet, as long as the dominant reason the report was created was to prepare for a reasonably anticipated claim.

The builder argued that by the time it commissioned the engineering investigation, it had already received a formal complaint letter from Sunita and expected a claim was likely, and that the investigation had been directed by its own lawyer specifically to assess legal exposure. If that framing held, the report and the engineer's underlying working notes would stay out of the neighbours' hands entirely, leaving them to prove causation from scratch using their own expert.

There was a second layer to the builder's position that mattered just as much. Its lawyers pointed to the release Sunita had signed and argued it was broader than a simple acknowledgment of a repair; it also included language releasing the builder from further claims connected to water infiltration at her unit. If that release held as written, Sunita's own claim would be barred regardless of what the withheld investigation showed, and the builder pressed that point hard, since removing one plaintiff from a group claim weakens the group's shared leverage.

The group's task was to test both positions rather than accept either at face value: whether the investigation genuinely qualified for protection given how early it was commissioned relative to any real anticipation of a lawsuit, and whether the release Sunita signed, obtained through a contractor rather than explained by a lawyer, was fair to enforce as written.

Ines, who had refused to sign anything until she saw whether the initial repair actually held, found herself in a stronger position than Sunita almost by accident, and the group had to grapple honestly with what that meant. If the release stood as written, the neighbours were not six plaintiffs with identical claims; they were a group with at least one materially weaker claim sitting inside it, and the builder's lawyers clearly understood that and intended to use it.

What we did

1. Gathered a detailed account from Sunita and each neighbour of exactly what was said and shown to them by the builder's contractor, including whether anyone explained the release's scope or suggested independent advice before signing, and Rui's earlier, dismissed observation that the document looked broader than a repair acknowledgment turned out to be an important early flag once we tested it against the actual wording. The group's collective memory of those conversations mattered as much as the document itself, since it shaped how the release was later challenged.
2. Reviewed the timeline of the builder's investigation against the first complaint letters, because protection for a document depends on when and why it was created, and the gap between the first complaint and the engineering report's start date turned out to be only a few days. That narrow gap became central to the privilege argument, since a report commissioned almost immediately after a complaint is far easier to characterize as anticipating litigation than one commissioned weeks or months later.
3. Requested the retainer instructions the builder had given its consultant, arguing that a document is not automatically protected just because a lawyer's name appears somewhere in the file; the dominant purpose still has to be genuine anticipation of a claim, not routine maintenance review dressed up afterward. Pressing for these instructions forced the builder to show its work rather than simply assert protection and expect the group to accept it.
4. Brought a motion to compel production of the investigation report, or in the alternative to have the court review it privately to decide whether the claimed protection actually applied to the whole document or only parts of it. Asking for a private judicial review as a fallback meant the group had a realistic path to at least partial disclosure even if the builder's broader privilege claim held up.
5. Separately reviewed the release Sunita had signed against what she was actually told at the time, gathering her account of the conversation with the contractor and confirming no lawyer or independent advisor had reviewed the document with her before she signed. Building this record mattered because a release is far easier to challenge when the signer can show she was never given a genuine chance to understand what she was giving up.
6. Assessed whether the release could be limited or set aside on the basis that it was presented without a fair opportunity to understand its scope, while being candid with the group that releases signed in exchange for even a modest benefit are difficult to unwind entirely. Setting realistic expectations early kept the group from assuming Sunita's share would simply match everyone else's regardless of how the release issue resolved.
7. Retained an independent drainage engineer to assess the row's grading directly, so the group's claim did not depend entirely on getting access to the builder's own report if the privilege motion failed. Having our own expert opinion in hand also strengthened the group's negotiating position regardless of how the document fight came out, and it meant the six owners were never left waiting on a single court ruling to know whether they had a case worth pursuing at all.
8. Negotiated a group settlement once the privilege motion outcome and the release issue were both reasonably clear, rather than pushing every point to a full trial with six separate plaintiffs and uncertain results on two contested issues at once. Settling at that stage let the group fund the actual drainage repair sooner, instead of spending further months and legal costs chasing a marginally better result at trial.

The outcome

The court reviewed the investigation report privately and found that most of it, including the engineer's core findings on the cause of the drainage failure, was properly protected, since the builder had genuinely anticipated a claim by the time the work was commissioned. A smaller portion, factual site notes made before the lawyer's instructions were given, was ordered produced. It was not the full picture the group had hoped for, but it confirmed the timing and scope of what the builder had known.

On the release, the court did not set it aside entirely but narrowed its effect, finding that Sunita had not been given a fair opportunity to understand it and limiting it to the specific repair work already performed rather than reading it as a bar to the new, broader claim about the underlying grading defect. That kept her in the group claim, though her individual settlement share ended up smaller than the other owners' to reflect the benefit she had already received under the release.

The group settled for a total of about 46,000 dollars against an original claim closer to 70,000 dollars, funding a proper drainage correction across the row but not fully covering every owner's incidental costs. Sunita later said the hardest lesson was not the privilege fight but the document she signed at her own kitchen table, months before any of it became a lawsuit, and how much that one signature ended up shaping her share of the outcome.

What you can learn from this