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

One roofing dispute, two courtrooms, and a wage he could not afford to lose

A Cornwall contractor's payment dispute with a homeowner had already reached a scheduled hearing date when a second, overlapping claim showed up in a different court, threatening the payroll he needed to cover for his own crew.

Litigation9 min readCornwall, OntarioRelitigating decided issues
All Litigation case studies
ClientHua, a roofing contractor caught between two overlapping court proceedings with the same homeowner
The issueThe same payment dispute was being pursued in two separate court proceedings at once, with an institutional processing delay slowing everything down
ServiceConsolidated the overlapping claims into one coherent position and negotiated a workable compromise once the parallel proceedings were addressed
ResolutionPartial win: a negotiated compromise that resolved both proceedings together, with each side giving up some ground

The situation

What Hua was actually afraid of was simple to say and hard to plan around: if the money owed on the Cornwall roofing job did not come in soon, he would not be able to cover the next payroll for the two people who worked with him, Qing and a part-time labourer he brought on for bigger jobs. He ran a small roofing operation, mostly residential work, and had completed a full re-roof for a homeowner, Bohdan, several months earlier under a signed contract with a payment schedule tied to project milestones. The work had gone through its early stages without complaint, and Hua had no reason to expect the final instalment would be any different from the ones before it.

The final payment, the largest single instalment under the contract, never came. Hua started a claim in Small Claims Court for the outstanding balance, a modest amount by most measures but a meaningful chunk of his working capital, enough to matter directly to whether he could keep two people on payroll through a slower stretch of the season. That claim had already progressed partway through the court process, with a hearing date eventually set, when Hua's own paperwork search turned up something that stopped him cold: Bohdan had separately filed a proceeding in a different court, raising many of the same facts about the roofing job but framing them as a claim against Hua for deficient work, seeking damages that would, if successful, wipe out most of what Hua was owed and then some.

Two proceedings, two different court files, both circling the same roofing job and the same set of facts, but never formally connected to each other. Hua had not chosen this. He had simply filed his claim in the court that made sense for the amount involved, only to discover later that Bohdan had gone a separate route with an overlapping dispute of his own, apparently in response to being pursued for the outstanding balance rather than as an independent complaint raised earlier.

Complicating the timeline further, part of Bohdan's claim rested on a building inspection report that a municipal department had not yet finished processing, and the pace of that report was setting the schedule for how quickly either proceeding could realistically move forward. Hua could not simply wait it out. Every week of delay was a week closer to a payroll he might not be able to meet, and he had no way to speed up a municipal process he had no part in starting.

By the time he sat down with our office, Hua had already begun dipping into personal savings to cover payroll gaps, a stopgap he knew could not continue indefinitely. He needed a plan that addressed both the duplicated litigation and the underlying cash pressure together.

The problem

Two active proceedings covering the same underlying dispute is a problem courts take seriously, not because either party necessarily did anything improper in starting them, but because the system is not built to run the same factual argument twice in front of two different decision-makers who might reach two different conclusions on the same set of facts. There is a real risk in that scenario: a finding in one proceeding that Hua's work met the required standard, followed by a finding in the other that it did not, would leave both parties and the courts with an outcome that made no practical sense.

The immediate legal question was what to do about the duplication itself before either claim could be meaningfully advanced. One option was to ask that the two proceedings be brought together, or that one be paused pending the outcome of the other, so the same set of facts was not litigated twice in parallel. Raising that issue meant identifying, clearly and specifically, how much factual overlap actually existed between the two files, since a court asked to intervene in an existing proceeding wants to see the duplication demonstrated concretely, not just asserted in general terms.

Underneath that procedural problem sat the practical one that mattered most to Hua: the municipal inspection report Bohdan's claim relied on had not yet been completed, and neither party had control over when it would be. Government processing timelines do not move faster because a private dispute is waiting on them, and the report's completion date effectively set a floor under how quickly either proceeding could progress to a meaningful hearing. That left Hua in a position where the legal problem, the duplication between two courts, and the practical problem, a payroll he needed to meet on a timeline the court process could not match, were pulling in different directions.

Bohdan, for his part, had his own version of urgency. He believed the roofing work had genuine deficiencies that needed addressing before another winter, and he was not inclined to simply withdraw one of the two proceedings without getting something in exchange, which meant the duplication problem could not be solved by a purely procedural motion alone. It needed a negotiated piece as well, one that would have to wait until the inspection report gave both sides something concrete to negotiate around rather than competing impressions of the work.

There was a further wrinkle worth naming honestly: pursuing the procedural argument to a full hearing would itself cost time and money that neither side particularly wanted to spend on a dispute of this size. A motion to address duplication is not free just because the underlying problem is procedural rather than substantive, and that cost had to be weighed against simply negotiating a combined resolution directly with Bohdan's side.

What we did

  1. Mapped the overlap between the two proceedings in detail, setting out precisely which facts, which contract terms and which allegations appeared in both files, so the duplication could be demonstrated concretely rather than argued about in general terms. This groundwork became the basis for everything that followed, both the procedural argument and the eventual negotiation, and it made clear to Bohdan's side exactly how much genuine overlap existed between what looked, on the surface, like two separate disputes.
  2. Raised the duplication directly with Bohdan's side, proposing that the two proceedings be addressed together rather than left to run separately, on the basis that neither party benefited from the cost and inconsistency risk of fighting the same dispute twice in front of two different decision-makers. This opened a practical conversation before either side had spent significantly more on either file, at a point where both sides still had room to compromise without having sunk further cost into positions that would be hard to walk back.
  3. Prepared the procedural groundwork to bring the claims together or stay one pending the other, in case a negotiated approach did not succeed, so Hua was not left without a fallback if Bohdan's side preferred to keep both proceedings active rather than resolve them jointly. Having this ready, rather than only threatened, strengthened our negotiating position by showing Bohdan's side we were genuinely prepared to pursue it if a reasonable settlement conversation went nowhere.
  4. Pressed for a realistic timeline on the municipal inspection report, contacting the department directly to understand where it stood in its processing queue, since neither proceeding could move toward resolution until that document existed and both sides could see what it said about the roof's condition. Following up directly, rather than waiting for the file to advance on its own, produced an actual estimated completion window, and let us tell Hua honestly how many more payroll cycles the delay was likely to cost him instead of leaving him guessing.
  5. Assessed Hua's actual exposure under Bohdan's deficiency claim against the roofing contract's terms and industry-standard workmanship expectations, to give Hua a realistic picture of his risk rather than either dismissing Bohdan's concerns outright or over-crediting them before the inspection report was even available to test either position against. That honest assessment mattered because it shaped what we were prepared to concede once negotiations opened, and it meant Hua went into settlement talks with a defensible number in mind rather than either an unrealistic best case or an unnecessarily fearful one.
  6. Kept Hua informed of the cash-flow pressure driving the timeline at every stage, adjusting the pace of negotiation where possible to reflect his payroll deadlines without abandoning the underlying legal position, since a rushed settlement accepted purely out of financial pressure often ends up worse than a properly negotiated one reached later. This meant flagging which stages could be compressed safely and which could not, so Hua could plan his own finances around a realistic timeline rather than assuming legal help would make the payroll pressure disappear on its own.
  7. Opened settlement discussions covering both proceedings at once, rather than negotiating the payment claim and the deficiency claim separately, since resolving only one would have left the other still open and the underlying dispute unresolved regardless of which court eventually decided it first. Framing the conversation around a single combined resolution also gave Bohdan's side a reason to engage seriously, since a partial settlement that left one file active would have solved nothing for either party and simply delayed the same negotiation to a later date.
  8. Structured the eventual compromise so it addressed both files simultaneously, with formal discontinuance of both proceedings built into the settlement terms, closing the duplication problem at the same moment the underlying payment and workmanship dispute was resolved for good. Making the discontinuance of each file a condition of the other, rather than trusting a verbal understanding, ensured neither proceeding could be revived later if one side had second thoughts, and gave Hua the clean, final closure the file needed.

The outcome

The dispute resolved through a negotiated settlement that addressed both proceedings together, once the municipal inspection report finally came back and gave both sides a clearer picture of the actual condition of the roofing work. Hua received a reduced payment from Bohdan, well below the full amount originally sought in his Small Claims proceeding, reflecting a modest allowance for minor workmanship issues the inspection report identified alongside the larger items that were not attributable to the work at all.

Bohdan, in turn, agreed to withdraw his separate claim in full as part of the settlement, and to release any further claims tied to the roofing job. Neither side got everything it had originally sought. Hua accepted less than the full contract balance he was owed, and Bohdan accepted that most of what he had alleged did not hold up once the inspection report was in hand, but each side avoided the cost, delay and uncertainty of pushing two overlapping proceedings through to separate hearings that risked producing conflicting results on the same facts.

For Hua, the compromise came later than he would have liked, shaped by a government processing timeline neither he nor Bohdan controlled, but it arrived in time to matter. The reduced payment, while smaller than what the original claim had sought, was enough to cover the payroll obligations that had been the real pressure behind the file from the beginning, and it closed both court proceedings cleanly rather than leaving either one open to resurface later in a different form.

The result was not the clean win Hua had originally hoped for when he filed his claim for the full outstanding balance. He gave up real money to reach it, and the delay caused by waiting on the inspection report meant several tighter payroll cycles than he would have liked. What the settlement did deliver was certainty on a timeline he could work with, and an end to the risk that two separate courts might have reached inconsistent conclusions about the same roof.

What you can learn from this

  • If you discover a dispute you are already litigating has also been filed in a separate proceeding by the other side, raise the overlap early. Courts take duplicated litigation seriously, and addressing it sooner limits wasted cost on both sides.
  • A negotiated settlement covering all related proceedings at once is usually more efficient than resolving them one at a time, since a partial resolution can leave the underlying dispute, and your exposure, still open.
  • When a government report or process is feeding into a private dispute's timeline, push for realistic information about when it will be ready rather than assuming the private proceeding can simply outpace it.
  • A partial or compromise outcome, where you accept less than the full amount claimed, is often the more economically sound result once the cost and risk of a full contested hearing on two fronts is factored in honestly.
  • Document your contract milestones and payment schedule clearly at the outset of any project. A well-documented payment schedule makes it far easier to demonstrate exactly what was owed once a dispute reaches this stage.
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 →