Essay question: 'Remoteness of damage is no longer a freestanding doctrine but has been absorbed into the question of whether the harm fell within the scope of the defendant's duty.' Discuss.
---
Introduction
The proposition reflects an ongoing debate in tort theory and a detectable shift in judicial reasoning since the House of Lords' decision in South Australia Asset Management Corp v York Montague Ltd (the SAAMCO case) [1997] AC 191 and the Supreme Court's recent affirmation in Hughes-Holland v BPE Solicitors [2017] UKSC 21, [2017] 2 WLR 1029. Traditionally, remoteness has been understood as a distinct stage in the liability enquiry, operative only after duty, breach, and factual causation are proved, and governed by the test in Overseas Tankship (UK) Ltd v Morts Dock & Engineering Co Ltd (The Wagon Mound (No 1)) [1961] AC 388: a defendant is liable only for damage of a kind reasonably foreseeable at the time of breach. The question posed here is whether this distinct stage has been—or should be—subsumed into the prior analysis of the scope or content of the duty of care. I will argue that while scope-of-duty reasoning has gained prominence and overlaps with remoteness, the two remain conceptually and functionally distinct, and collapsing them risks losing analytical clarity and flexibility.
The traditional structure: remoteness as a freestanding filter
English tort law conventionally divides the negligence inquiry into five elements: duty, breach, causation (factual and legal), remoteness, and defences. Remoteness operates as the final causal filter. Once a claimant proves that the defendant's breach was a but-for cause of the damage and that no novus actus interveniens broke the chain, he must still show that the damage was not too remote. The test is reasonable foreseeability of the kind of damage, not its extent or precise manner (Hughes v Lord Advocate [1963] AC 837; Jolley v Sutton LBC [2000] UKHL 31). This structure reflects a sensible division of labour: duty asks whether the defendant owed the claimant a duty; breach asks whether conduct fell below the standard of care; causation asks whether breach caused harm; and remoteness asks whether, given all that, the harm is too distant or unforeseeable to warrant recovery. Each stage serves a distinct normative and practical purpose.
Moreover, remoteness applies across torts, not only negligence. In deceit, for instance, the defendant is liable for all direct consequences, foreseeability being irrelevant (Doyle v Olby (Ironmongers) Ltd [1969] 2 QB 158); in nuisance, foreseeability is required (Cambridge Water Co v Eastern Counties Leather plc [1994] 2 AC 264). This suggests that remoteness is a general principle capable of taking different forms depending on the tort, rather than being fused into the definition of duty for each tort.
*The scope-of-duty turn: SAAMCO and Hughes-Holland***
Lord Hoffmann's judgment in SAAMCO introduced the language of 'scope of duty' (or 'scope of liability') into mainstream tort analysis. He distinguished between cases where a defendant provides information, for which he is responsible only if the information is wrong and causes loss, and cases where a defendant advises a course of action, for which he is responsible for all foreseeable consequences of the course of action being taken. The scope of the duty, not a freestanding remoteness rule, determines which losses are recoverable. In Hughes-Holland, the Supreme Court applied this framework to solicitors' negligence: the solicitor's duty was to protect the client against a particular risk (uncertainty about whether a guarantee would be enforceable), and losses outside that risk were not recoverable even though they were caused by the breach and foreseeable. Lord Sumption and Lord Mance both framed the question as one of 'scope of liability', effectively merging what might traditionally have been analysed as remoteness into the definition of duty.
This approach has several attractions. It is conceptually parsimonious: rather than asking 'what was the duty?', 'was it breached?', 'did breach cause harm?', and then 'was harm too remote?', one asks 'what was the scope of the duty?' and 'did the breach, operating within that scope, cause the harm?'. It also aligns tort law with contract (where the scope of contractual duties limits recovery: Transfield Shipping Inc v Mercator Shipping Inc (The Achilleas) [2008] UKHL 48, [2009] 1 AC 61) and with comparative civil law systems, which explicitly frame the inquiry as Schutzzweck der Norm or the protective purpose of the rule. Finally, it focuses analysis on the normative question: what risks was the defendant supposed to guard against? This can be more transparent than asking whether a consequence was 'foreseeable', a term that is both vague and duplicative (foreseeability already plays a role at the breach stage).
Why remoteness remains distinct
Despite these advantages, there are strong reasons to preserve remoteness as a separate doctrine. First, duty and remoteness ask different questions. Duty asks: did the defendant owe this claimant a duty in respect of this interest or this kind of harm? It is a threshold, relational, and often categorical inquiry (compare Caparo Industries plc v Dickman [1990] 2 AC 605 with Robinson v Chief Constable of West Yorkshire Police [2018] UKSC 4). Remoteness, by contrast, asks: given that a duty was owed and breached, and given that breach caused harm, was the causal chain sufficiently close and the harm sufficiently foreseeable that liability should attach? It is a quantitative and sequential inquiry, not a categorical one. Conflating the two risks category errors: duties are defined ex ante by reference to relationships and interests; remoteness operates ex post by reference to the facts of what actually happened.
Second, the egg-shell skull rule and the kind/extent distinction sit uneasily within a scope-of-duty framework. The rule that a defendant must take his victim as he finds him—accepting liability for unforeseeable extent of harm within a foreseeable kind—is a remoteness principle; it presupposes that duty and breach are already established. One cannot meaningfully say that the duty of care 'included' liability for a latent cancer triggered by a foreseeable burn (Smith v Leech Brain & Co Ltd [1962] 2 QB 405); rather, the duty was to avoid injuring the claimant, and remoteness doctrine determines how far liability extends once injury occurs. Similarly, intervening acts (novus actus interveniens) are traditionally analysed as breaking the chain of causation or rendering harm too remote (Knightley v Johns [1982] 1 WLR 349; Corr v IBC Vehicles Ltd [2008] UKHL 13). These are ex post, fact-sensitive evaluations that do not fit comfortably within the ex ante definition of duty.
Third, as a matter of precedent and structure, the Supreme Court and lower courts continue to treat remoteness as a distinct stage. In Sienkiewicz v Greif (UK) Ltd [2011] UKSC 10, [2011] 2 AC 229, the Court distinguished between proof of causation (on which the appeal turned) and remoteness (assumed). In Darnley v Croydon Health Services NHS Trust [2018] UKSC 50, [2018] 3 WLR 1153, remoteness was noted as a separate question. The profession, textbooks, and judicial practice all retain the five-stage structure. Abandoning it in favour of an all-encompassing 'scope of liability' test would require wholesale doctrinal reconstruction and create transitional uncertainty.
Finally, one must distinguish professional negligence—the primary context of SAAMCO and Hughes-Holland—from general negligence. In professional negligence, the scope of the retainer or advisory duty is relatively easy to articulate and does much work in limiting liability (especially for economic loss). In ordinary personal injury and property damage cases, however, the duty is typically formulated broadly ('take reasonable care not to injure the claimant'), and remoteness provides the necessary limiting principle. Collapsing remoteness into duty in such cases would either render the duty infinitely manipulable or do no work at all.
A complementary relationship
The better view is that scope-of-duty and remoteness are complementary filters, each doing distinct work. Scope-of-duty defines the interests protected and the risks guarded against; remoteness determines whether, within those interests and risks, the particular consequence was sufficiently foreseeable. For example, in a road accident case the duty is to avoid injuring other road users by careless driving. A physical injury is within the scope of that duty. Remoteness then asks: was this injury (e.g., psychiatric harm triggered by minor impact) of a kind foreseeable? The two stages are sequential and mutually reinforcing, not redundant.
In professional negligence, where duties are highly context-specific, scope-of-duty analysis may subsume much of what would otherwise be remoteness. But even there, remoteness retains residual significance: once one identifies the scope of the duty, one must still ask whether the breach, operating within that scope, caused losses in a manner not too remote. For instance, in Hughes-Holland the majority held the loss fell outside the duty's scope; had it been within scope, the defendant might still have argued (though unsuccessfully) that the loss was too remote because unforeseeable.
Conclusion
Remoteness of damage has not been wholly absorbed into the scope-of-duty inquiry, nor should it be. While recent Supreme Court authority has elevated scope-of-duty reasoning—particularly in professional negligence—and has rightly insisted that one must identify the purpose and content of a duty before mechanically applying remoteness tests, the two doctrines remain distinct in function and rationale. Scope-of-duty is an ex ante, categorical inquiry about what the duty protects; remoteness is an ex post, fact-sensitive inquiry about causal and normative proximity. The law benefits from retaining both tools. They operate in tandem, not as rivals. To collapse them into a single 'scope of liability' analysis would sacrifice clarity, precedent, and flexibility for the sake of theoretical elegance. The preferable course is to recognise their complementary roles and to apply each with rigour and transparency at the appropriate stage of the analysis.
---
Word count: c. 1,650 words (tutorial essays typically 1,500–2,000 words)
Examiner's feedback: This essay demonstrates excellent command of the authorities and engages directly with current doctrinal debates. The structure is clear and the argument is sustained. To improve further, one might: (i) engage more explicitly with academic voices (Stapleton, Steel, Stevens) to show familiarity with the literature; (ii) provide more concrete hypothetical examples to illustrate the difference between scope-of-duty and remoteness; (iii) address counterarguments in greater depth (e.g., why proponents of merger think the distinction is illusory). Overall, a strong first-class answer.