← University
Third Party Claims: Bringing Someone Else Into the Fight
0 of 4

A structural engineer's report, commissioned after staff noticed water damage in the basement of a renovated community services facility, confirmed what everyone feared: the foundation work was defective and the building's structural integrity had been compromised. The non-profit agency that operated the facility had completed the renovation approximately 4 years earlier, transforming an aging property into a modern program space where vulnerable populations received essential services. The project had been celebrated at the time, with volunteer board members, staff, and community partners gathering for a ribbon-cutting ceremony that marked what was supposed to be the beginning of decades of reliable service delivery.

The renovation had involved a general contractor selected through a competitive bidding process overseen by the agency's board. The general contractor had in turn subcontracted the foundation work—including waterproofing and drainage installation—to a specialty foundation contractor. At the time, the subcontractor had assured everyone that the waterproof membrane was properly installed and had signed off on the drainage specifications. The work had passed inspection, invoices had been paid, and the project had closed out without apparent incident.

The problems emerged gradually over the following years. What initially appeared to be minor settling in the foundation revealed itself as something far more serious. Water began seeping through the basement walls after heavy rains, pooling in storage areas where the agency kept supplies for its programs. Cracks spread along the foundation walls. Water stains bloomed across ceiling tiles in the program space. The structural engineer's report, completed approximately 6 months after staff first documented the water damage, traced the infiltration to improper foundation waterproofing and inadequate drainage installation—work that had been performed by the subcontractor during the original project.

When the agency's executive director contacted the general contractor to discuss the deficiencies, the response came not from the contractor directly but from the contractor's lawyer. The letter pointed the finger squarely at the subcontractor, asserting that the subcontractor had handled all foundation work and bore responsibility for any failures. The agency now faced a decision about whether to commence litigation, and the general contractor faced a parallel decision about whether to bring the subcontractor into any resulting legal action. The damages at issue included hundreds of thousands of dollars in remediation costs, disruption to programming for vulnerable populations, and the prospect of extensive structural repairs to a building that was supposed to serve the community for decades.

The Third Party's Position: Rights and Obligations of a New Party

The envelope arrived at Apex Foundation Works Ltd. on a grey Tuesday morning in late October, delivered by a process server who waited at the reception desk until someone signed for it. Inside was a thick bundle of documents: a statement of claim naming Ridgewood Community Services Society as plaintiff and Hartland General Contracting Inc. as defendant, followed by a third party notice naming Apex as the third party. The claim alleged that structural deficiencies and water infiltration at the Ridgewood facility had caused hundreds of thousands of dollars in damage, disrupted programming for vulnerable populations, and required extensive remediation. The third party notice, filed by Hartland, alleged that if Hartland was liable to Ridgewood for any of these damages, then Apex was liable to Hartland for contribution and indemnity because Apex had performed the foundation work that allegedly caused or contributed to the problems. Marcus Chen, the owner of Apex Foundation Works, sat in his cramped office reading the documents three times before calling his lawyer. He had completed the foundation work on the Ridgewood project more than five years earlier, had been paid in full, had never received any complaint from Hartland or anyone else about the quality of his work, and had assumed the project was long finished and forgotten. Now he found himself pulled into litigation he had not known existed, facing allegations he believed were baseless, and confronting a thicket of procedural and substantive questions about what exactly he was required to do and what rights he possessed to defend himself.

The position of a third party in civil litigation is both precarious and surprisingly powerful, though many parties served with third party claims fail to appreciate the full scope of their procedural rights until those rights have been compromised through inaction or ignorance. When Hartland served Apex with the third party notice, it initiated a separate but connected proceeding that runs parallel to the main action between Ridgewood and Hartland. Apex did not choose to be in this lawsuit. Unlike Ridgewood, which made a deliberate decision to sue, and unlike Hartland, which knew from the outset of the project that litigation was always a theoretical possibility, Apex was brought into the fight by someone else's decision. This fundamental involuntariness shapes much of what follows, because the rules governing third party proceedings must balance the defendant's legitimate interest in spreading liability against the third party's legitimate interest in not being unfairly burdened by litigation it did not initiate and may have no connection to beyond the defendant's unilateral allegations.

The Alberta Rules of Court establish the framework within which third party proceedings operate, and these rules confer upon a properly added third party a range of rights that mirror, in most respects, the rights enjoyed by the original defendant. When Apex received the third party notice, its first obligation was straightforward: it had to decide whether to file a defence. Under the Rules, a third party served with a third party claim must file a statement of defence to the third party claim within the time prescribed, typically twenty days from service if served within Alberta. This defence responds to the specific allegations made by the defendant against the third party. In Apex's case, this meant responding to Hartland's allegations that Apex's foundation work was deficient and that Apex owed Hartland contribution or indemnity for any liability Hartland might face. The statement of defence to the third party claim functions much like any other statement of defence: Apex could deny the allegations, raise affirmative defences, plead alternative versions of the facts, and generally put Hartland to the proof of every element of its claim. Failure to file this defence within the prescribed time would expose Apex to the possibility of default judgment on the third party claim, which could result in Apex being bound by findings of liability without ever having had the opportunity to contest them.

But the right to defend against the third party claim itself represents only part of the third party's procedural arsenal. The Rules also permit a third party to defend against the main action, meaning Apex could file a defence to Ridgewood's claim against Hartland, even though Ridgewood has not sued Apex directly. This right exists because the outcome of the main action directly affects the third party's exposure. If Ridgewood succeeds against Hartland, that success forms the predicate for Hartland's claim against Apex. The quantum of damages awarded against Hartland in the main action becomes the ceiling for what Hartland can claim from Apex on contribution or indemnity. The findings of fact made in the main action may bind Apex on issues relevant to both claims. For all these reasons, Apex has a legitimate interest in seeing Hartland mount the best possible defence against Ridgewood's claim, and if Hartland fails to do so adequately, Apex can step in and raise defences that Hartland has neglected or chosen not to pursue.

The practical operation of this right to defend the main action raises delicate questions of litigation strategy that Marcus Chen and his lawyer had to consider carefully. When Apex reviewed Hartland's statement of defence to Ridgewood's claim, it found the defence competent but, from Apex's perspective, insufficient in certain respects. Hartland had denied the allegations of deficiency and pleaded that any problems with the building resulted from design errors, improper maintenance by Ridgewood, or intervening causes unrelated to the construction. Hartland had also raised a limitation defence, arguing that Ridgewood's claim was brought outside the two-year limitation period established by the Limitations Act because Ridgewood had known or ought to have known of the problems more than two years before commencing the action. What Hartland had not done, and had no incentive to do, was raise certain defences that might be available to Apex specifically. Hartland's limitation defence focused on when Ridgewood knew or ought to have known of the deficiencies. But a separate limitation issue existed with respect to the third party claim itself: when did Hartland know or ought to have known that it had a claim against Apex? This question had a different temporal starting point than the question of when Ridgewood discovered its claim against Hartland, and the answer to this question would determine whether the third party claim was itself statute-barred.

The limitation defence available to a third party deserves careful consideration because it operates independently of any limitation defence available to the defendant in the main action. Apex's position was that even if Ridgewood's claim against Hartland was timely, Hartland's claim against Apex might not be. The Limitations Act provides that a claim must be brought within two years of the day on which the claimant knew or ought to have known of the claim, subject to an ultimate limitation period of ten years from the date the act or omission occurred. For Hartland's claim against Apex, the relevant inquiry was when Hartland first knew or ought to have known that the foundation work was deficient and that this deficiency might give rise to a claim for contribution. Hartland had received communications from Ridgewood about building problems as early as three years after construction was completed, and Ridgewood had retained an engineering consultant who identified foundation-related issues in a report delivered to both Ridgewood and Hartland more than four years before Hartland filed its third party notice. If Hartland knew or ought to have known of its potential claim against Apex upon receiving that engineering report, then the two-year limitation period might have expired before the third party claim was even filed. This limitation defence was Apex's own to raise, and it would not be raised by anyone else because neither Ridgewood nor Hartland had any interest in seeing the third party claim dismissed on limitation grounds.

The interaction between limitation defences in third party proceedings creates what can appear to be anomalous results, though these results follow logically from the statutory framework. It is entirely possible for a plaintiff's claim against a defendant to be timely while the defendant's claim against a third party is statute-barred, or vice versa. This is because each claim has its own discovery date determined by when the relevant claimant knew or ought to have known of that particular claim. A defendant might learn of facts giving rise to a contribution claim well before the plaintiff learns of facts giving rise to the main claim, or the sequence might be reversed. In the Ridgewood litigation, the timeline was complicated by the nature of construction defects, which often remain latent for years before manifesting visibly, and by the agency's poor documentation practices, which made it difficult to establish precisely when anyone first learned of what. The engineering report that Apex's lawyer considered potentially dispositive of the limitation issue on the third party claim had been delivered at a meeting attended by representatives of Hartland, Ridgewood, and the government funder who had contributed capital toward the renovation. The report identified foundation movement as a contributing factor in the water infiltration, but it also identified other contributing factors including flashing deficiencies and grading problems. Hartland's lawyer argued that the report did not clearly establish that the foundation work was deficient, only that foundation movement had occurred, and that Hartland could not reasonably have known it had a claim against Apex until a subsequent investigation specifically attributed the movement to inadequate compaction of fill material beneath the footings.

The question of when someone knows or ought to know of a claim against a particular party involves both factual knowledge of the material circumstances and sufficient awareness that those circumstances may give rise to legal responsibility. A defendant who learns of a problem may not immediately know who caused the problem or may have reasonable grounds to believe the problem resulted from causes for which no third party is responsible. The jurisprudence on discoverability requires examining what a reasonable person in the defendant's position would have understood and what inquiries a reasonable person would have made. Hartland's position was that it had no reason to suspect Apex's work until the supplemental investigation, and that the limitation period on the third party claim therefore ran from the date of that later investigation rather than from the date of the original engineering report. Apex's position was that the original report provided sufficient information to put Hartland on inquiry, and that a reasonable person in Hartland's position would have made further inquiries and discovered the foundation issue well within the limitation period. These competing positions would need to be resolved by the court, either on a summary judgment application or at trial, and the resolution would determine whether Apex faced potential liability at all or whether it would be dismissed from the proceeding on limitation grounds before the merits were ever reached.

Beyond the limitation defence, Apex possessed the right to raise any other defence that might defeat or reduce Hartland's claim for contribution. The law of contribution among tortfeasors provides that a defendant held liable to a plaintiff may recover contribution from any other person who is liable to the plaintiff in respect of the same damage. This formulation contains an important limitation: the third party must be "liable to the plaintiff" for contribution to be available. If Apex's work was not in fact deficient, or if any deficiency in Apex's work did not cause or contribute to the damage Ridgewood suffered, then Apex is not liable to Ridgewood and Hartland cannot recover contribution from Apex regardless of what the main action determines. The third party's liability to the plaintiff is assessed hypothetically, as if the plaintiff had sued the third party directly, and all defences that would be available to the third party in such a hypothetical action are available in the third party proceeding. Apex could therefore argue that its foundation work met the applicable standard of care, that any deviation from that standard did not cause the problems Ridgewood experienced, that the problems resulted entirely from other causes such as Hartland's supervision of the work or Ridgewood's failure to maintain the building properly, or that Apex's contract with Hartland limited its liability in ways that precluded recovery.

The contractual relationship between the defendant and the third party often plays a significant role in third party proceedings, particularly in construction contexts where chains of contracts link owners, general contractors, subcontractors, and suppliers. Apex had entered into a subcontract with Hartland to perform the foundation work on the Ridgewood project. That subcontract contained provisions allocating risk between the parties, including indemnification language, warranty provisions, and a limitation on liability capping Apex's total exposure at the subcontract price. Whether these contractual provisions affected Hartland's contribution claim required interpretation of the subcontract and application of principles governing the enforceability of limitation and indemnification clauses. Apex argued that the limitation of liability clause capped any recovery Hartland could obtain, while Hartland argued that the clause did not apply to claims arising from Apex's negligence or fundamental breach of contract. These arguments about the proper interpretation of the subcontract were arguments between Hartland and Apex, not arguments that involved Ridgewood directly, and they illustrated how the third party proceeding could involve issues entirely distinct from those in the main action.

The obligations of a third party are less extensive than its rights, but they are no less important. Once served with a third party claim, Apex was obligated to participate in the litigation in accordance with the rules governing all parties. This meant complying with timelines for filing pleadings, responding to demands for discovery, attending questioning, producing relevant documents, and participating in pretrial processes. A third party that ignores these obligations does so at its peril, because default judgment can be entered, adverse findings can be made, and the third party can find itself bound by the outcome of proceedings it chose not to engage with. The Rules treat a third party who has been properly served and who fails to defend as having admitted the defendant's allegations, just as a defendant who fails to defend is treated as having admitted the plaintiff's allegations. This means that Apex's decision to file defences and actively participate was not merely strategic but necessary to preserve its ability to contest liability.

The documentary obligations of parties in litigation apply with full force to third parties, and in the Ridgewood litigation, Apex's document production became a significant undertaking. Despite Marcus Chen's initial belief that the foundation work was routine and unremarkable, the subcontract file contained extensive records including site meeting minutes, daily logs, soil compaction test results, communications with Hartland's site supervisor, photographs taken during construction, and correspondence about change orders. These documents were relevant not only to Hartland's claim against Apex but also to the main action between Ridgewood and Hartland, and both Ridgewood and Hartland sought production of Apex's records. The obligation to produce documents extends to all documents relevant to the issues in the proceeding, and a third party cannot narrow its production obligation by claiming that certain documents relate only to the main action and not to the third party claim. Once a party to the litigation, the third party's documents become available to all other parties to the extent they are relevant and not protected by privilege.

The questioning process similarly includes third parties as both examining and examined parties. Apex had the right to question representatives of Ridgewood and Hartland, and both Ridgewood and Hartland had the right to question Marcus Chen as the representative of Apex. These questioning sessions revealed the complexity of the factual matrix underlying the litigation. Ridgewood's executive director testified about the sequence of events leading to discovery of the building problems, the communications between Ridgewood and Hartland, the investigations that were conducted, and the impacts on programming. Hartland's project manager testified about the construction process, the supervision of subcontractors, the inspections that were performed, and the communications with Ridgewood after problems emerged. Marcus Chen testified about Apex's scope of work, the methods used for foundation construction, the soil conditions encountered, and the testing that was performed to verify compaction. Each of these witnesses provided information relevant to multiple issues in the litigation, and the questioning sessions generated thousands of pages of transcripts that would form part of the evidentiary record.

The procedural integration of third party claims with main actions serves important efficiency goals but creates complexity in the sequencing of proceedings. The Rules contemplate that third party claims will ordinarily be tried together with main actions, so that all issues can be resolved in a single proceeding and inconsistent findings avoided. This means that Apex's limitation defence, if not resolved on summary judgment, would be tried at the same time as the main action, and the judge would need to determine not only whether Ridgewood's claim against Hartland was timely but also whether Hartland's claim against Apex was timely. The determination of Apex's liability to Ridgewood, made hypothetically as part of assessing the contribution claim, would be made by the same judge who determined Hartland's actual liability to Ridgewood. This consolidation prevents the possibility that one court might find the foundation work deficient while another court might find it adequate, an outcome that could occur if the third party claim were tried separately from the main action.

The rights of a third party extend to participating in settlement discussions and to accepting or rejecting settlement offers that affect its interests. If Hartland chose to settle with Ridgewood, that settlement would have consequences for Apex depending on how it was structured and whether Apex consented to it. A defendant who settles with a plaintiff and then seeks contribution from a third party must establish that the settlement was reasonable and made in good faith, because a third party should not be responsible for contributing to a settlement that was inflated or unreasonable. This gives the third party an indirect voice in settlement negotiations even when it is not directly involved, because the defendant knows that an unreasonable settlement may not be recoverable from the third party. Conversely, a third party who is offered the opportunity to participate in a settlement and refuses may face arguments that it failed to mitigate its exposure when it had the chance. The dynamics of multi-party settlement negotiations are intricate, and the rights and obligations of third parties in these negotiations reflect the broader principle that third parties should neither be unfairly burdened by the defendant's decisions nor allowed to avoid responsibility for damage they caused.

As the Ridgewood litigation progressed toward trial, Apex exercised its full range of procedural rights while meeting its obligations as a party. It filed defences to both the third party claim and the main action, produced documents, attended questioning, retained experts, and participated in case management conferences. The limitation defence on the third party claim remained a central issue, with Apex bringing a summary judgment application seeking dismissal of Hartland's claim on the basis that it was filed more than two years after Hartland knew or ought to have known of the claim. That application required the court to examine the evidence about what Hartland knew and when, and to determine whether the original engineering report was sufficient to start the limitation clock or whether the subsequent investigation was the true discovery date. The outcome of that application would determine whether Apex remained exposed to

Continue with University access

This lesson is part of a $79 course. Purchase the course or sign in with an active membership to keep reading.

See purchase options