Duty to Rescue¶

Impose a jurisdiction-specific legal obligation to take reasonable, feasible steps to aid or summon aid for a person in serious peril when a recognized trigger applies and assistance does not create disproportionate danger or conflict.

Version: v2 · 2026-09-06 · History
Domain-specific #: 1731
Origin domain: law
Subdomain: obligations and liability
Aliases: Duty to render aid, Obligation to rescue

Core Idea¶

Duty to rescue is a legal obligation, recognized only under the governing jurisdiction and facts, to take reasonable and feasible steps when another person faces sufficiently serious peril. The required response may be direct assistance, warning, or summoning competent aid; it is not necessarily physical intervention. The trigger, protected persons, required knowledge, feasible response, self-risk limit, conflicting duties, and civil or criminal consequence must all come from applicable law rather than from a free-floating moral intuition.^[1]

Legal systems locate the duty differently. A broad rescue statute may impose a bystander obligation when an accident, common danger, or emergency creates a need for necessary assistance that can reasonably be expected without substantial danger to the rescuer or violation of other important duties. By contrast, the traditional United States tort baseline does not impose a general duty to aid a stranger merely because aid would be easy. Duties can arise through risk creation, an undertaking, a special relationship, custody, contract, role, or statute. The Restatement organizes those affirmative-duty exceptions rather than treating all omissions alike.^[2]

The abstraction is therefore the legally activated responsibility for an omission, not a universal instruction to attempt a rescue. It is distinct from Good Samaritan immunity, which may limit liability for people who voluntarily render aid; from the rescue doctrine, which concerns injuries to rescuers; and from professional standards governing how trained responders perform care. A sound analysis identifies jurisdiction and authority first, then tests trigger, capacity, safety, reasonable response, causation where relevant, and the legal consequence. This entry is descriptive legal information, not jurisdiction-specific advice or emergency procedure.

Structural Signature¶

Governing jurisdiction. Statute, precedent, or another recognized source determines whether a duty exists.
Person in peril. The protected person faces the degree and type of danger specified by law.
Duty trigger. Bystander status, risk creation, undertaking, relationship, custody, office, contract, or statute activates the obligation.
Knowledge condition. Actual awareness or a legally specified constructive-knowledge standard connects the actor to the peril.
Capacity and opportunity. A legally meaningful response is available to the person at the relevant time.
Reasonableness limit. The law calibrates what assistance could reasonably be expected in the circumstances.
Safety limitation. Assistance ordinarily need not expose the rescuer or others to substantial or disproportionate danger.
Conflicting-duty limitation. Other important legal or role obligations may constrain the response.
Permitted response form. Calling competent services, warning, or direct assistance may satisfy different duties.
Omission. The legally relevant conduct is failure to take the required feasible step.
Liability pathway. Criminal offense, tort duty and breach, regulatory consequence, or another remedy is specified separately.
Jurisdictional variation. Scope and consequence are not portable without rechecking authority.

What It Is Not¶

Not a universal moral duty. Ethical arguments may influence legislation but do not alone establish legal liability.
Not Good Samaritan immunity. Immunity protects some voluntary rescuers from liability; a duty compels some response.
Not the rescue doctrine. That doctrine can permit an injured rescuer to recover from the person whose wrongdoing created the peril.
Not a command to perform hazardous intervention. Statutes commonly include feasibility, competence, and self-danger limits.
Not limited to medical treatment. Summoning help, warning, or nonmedical assistance can be the legally relevant act.
Not every special-relationship duty. Parent–child, carrier–passenger, custodian, employer, or land-possessor duties have distinct authorities and scopes.
Not negligence per se automatically. The effect of a statutory breach in civil litigation depends on jurisdictional doctrine.
Not a cross-border rule. Identical facts can yield different duties and consequences under different legal systems.

Scope of Application¶

Duty-to-rescue analysis is literal in comparative criminal law, tort law, regulatory obligations, and institutional roles when liability turns on failure to provide or summon feasible assistance after a legally recognized trigger.

General rescue statutes. Some jurisdictions impose a bounded duty on capable bystanders during specified emergencies.
Risk creation. A person whose conduct creates a danger may have an affirmative duty to prevent or reduce resulting harm.
Voluntary undertaking. Beginning aid can create obligations to exercise reasonable care or avoid worsening reliance-based risk.
Special relationships. Defined relationships can support affirmative duties of protection or assistance.
Custody and control. Institutions or custodians may owe duties because another person cannot protect themselves normally.
Professional or official roles. Employment, licensure, office, or contract can activate role-specific assistance obligations.
Maritime and transportation settings. Specialized statutes and conventions may impose rescue or reporting duties.
Comparative legal research. The construct makes different trigger and exception architectures comparable without pretending they are identical.

Clarity¶

Begin with the jurisdiction, date, authority, and civil, criminal, regulatory, or professional pathway. State who is allegedly obligated, who is protected, what peril existed, what the actor knew, and which fact activates the duty. Identify feasible responses without prescribing unsafe action, and state the statutory or doctrinal safety, competence, and conflicting-duty limits. Separate existence of duty from breach, causation, defenses, immunity, and remedy. Distinguish a duty to summon aid from a duty to provide hands-on treatment. Never infer current law from a comparative example, a moral principle, or the label Good Samaritan law.

Manages Complexity¶

The abstraction converts a large fact pattern into an ordered legal inquiry: governing source, trigger, knowledge, capacity, feasible response, limits, omission, and consequence. It prevents the emotionally intuitive question—why did the person not help?—from replacing the legally antecedent question—what law imposed which act on this person here? It also exposes differences between systems that impose general bystander duties and systems that proceed through enumerated exceptions. Compression must not erase local statutory language, emergency uncertainty, disability, responder competence, causation, or the distinction between calling help and physically intervening.

Abstract Reasoning¶

Fix jurisdiction, relevant date, and the type of liability or enforcement being considered.
Identify authoritative statutes, cases, restatements, regulations, contracts, or role rules.
Characterize the peril and the person within the authority's protected scope.
Test each possible duty trigger: risk creation, undertaking, relationship, custody, role, contract, or general statute.
Determine the actor's legally relevant knowledge, ability, opportunity, and available safe responses.
Apply reasonableness, self-danger, competence, and conflicting-duty limitations.
Define the alleged omission with enough precision to compare it to the required act.
Analyze breach, causation, defenses, immunity, and remedy separately from duty existence.
When comparing jurisdictions, preserve distinct thresholds rather than synthesizing a fictitious universal rule.

Knowledge Transfer¶

The strict parent is Accountability: duty to rescue makes a person legally answerable for failing to take a required action after a recognized trigger. Responsibility Attribution and Threshold-Triggered Rule Activation illuminate parts of the analysis, but the former identifies responsibility more generally and the latter presumes a continuous observable threshold not present in every rescue rule. The legal residual is affirmative omission liability bounded by authority, relationship, feasibility, and safety.

Examples¶

Canonical¶

German Criminal Code section 323c criminalizes failure to render assistance in an accident, common danger, or emergency when assistance is necessary and can reasonably be expected, especially without substantial danger to the helper and without breach of other important duties. The rule illustrates a general statutory trigger but still includes necessity and reasonableness limits; it does not command untrained hazardous intervention.^[1]

Mapped back: specified emergency + statutory coverage + necessary reasonably expected aid + no substantial countervailing danger → legal duty → omission consequence.

Applied / In Practice¶

In a common-law tort analysis, a stranger's ability to help does not by itself finish the duty inquiry. The analyst asks whether the person created the risk, began an undertaking, stood in a recognized special relationship, held custody, assumed a contractual or role duty, or was governed by a statute. Only after a valid trigger is found do reasonable response, breach, causation, and possible immunity become material.^[2]

Mapped back: facts of peril → enumerated affirmative-duty trigger → feasible bounded response → separate breach and liability analysis.

Structural Tensions¶

Moral expectation vs. legal source. Strong ethical intuition does not establish an enforceable duty. Diagnostic: Which authority creates the obligation?
General statute vs. enumerated exception. Systems structure omission liability differently. Diagnostic: Is a foreign rule being imported silently?
Aid requirement vs. rescuer safety. Overbroad phrasing can encourage dangerous action. Diagnostic: What competence and self-risk limits govern?
Direct intervention vs. summoning help. The least dangerous effective response may be legally sufficient. Diagnostic: What act does the authority actually require?
Duty vs. immunity. A Good Samaritan protection does not necessarily create an obligation. Diagnostic: Is the rule compelling conduct or limiting liability?
Autonomous doctrine vs. generic accountability. Accountability travels; affirmative rescue triggers and omission limits define the residual. Diagnostic: Are peril, trigger, feasible aid, and exception architecture specified?

Structural–Framed Character¶

Duty to rescue is legally framed. Its recurring structure is stable, but every operative conclusion depends on jurisdiction, authoritative text, date, role, facts, and liability pathway. Reasonableness and substantial-danger terms invite contextual judgment. Comparative abstraction is useful only when it preserves these differences. Nothing in the construct determines whether intervention is medically safe, and the entry neither supplies emergency instructions nor substitutes for local legal advice.

Structural Core vs. Domain Accent¶

The skeleton is triggered accountability for an omission when a feasible protective act is required. The domain accent is legally recognized peril, affirmative-duty doctrine, bystander or relationship triggers, reasonable assistance, rescuer-safety limits, and civil or criminal consequences. Removing those yields Accountability, Obligation, or Incident Response rather than Duty to Rescue.

Accountability is the strict parent because duty-to-rescue rules make a legally covered person answerable for omitting specified assistance. Accountability applies to many actions, institutions, and standards that have nothing to do with emergency aid.

The prospective workspace queue contains one strict upward edge to prime:accountability. No live DAG mutation is authorized.

Relationships to Other Abstractions¶

Current abstraction Duty to Rescue Domain-specific

Parents (1) — more general patterns this builds on

Duty to Rescue is a kind of Accountability Prime

Accountability is the strict parent because duty-to-rescue rules make a legally covered person answerable for omitting specified assistance.

Hierarchy path (1) — routes to 1 parentless root

Duty to Rescue → Accountability → Authority

Neighborhood in Abstraction Space¶

Duty to Rescue sits in a sparse region of the domain-specific corpus (95^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

Civil death — 0.79
Non-retroactivity — 0.77
Unowned Property — 0.77
Non Bis in Idem — 0.76
Injury (law) — 0.76

Computed from structural-signature embeddings · 2026-09-08

Not to Be Confused With¶

Good Samaritan law. Typically grants protection or sets a care standard for voluntary assistance.
Rescue doctrine. Addresses recovery by rescuers injured because another created peril.
Duty of care. A broader negligence relationship that does not always require affirmative rescue.
Omission liability. The larger class of liability for failures to act.
Necessity defense. Justifies otherwise unlawful conduct under pressure of harm rather than imposing aid.
Professional emergency duty. A role-specific obligation that may coexist with or exceed a bystander rule.
Moral obligation to help. A normative ethical claim without necessary legal enforceability.

References¶

[1] Federal Ministry of Justice and Federal Office of Justice (Germany), German Criminal Code (Strafgesetzbuch—StGB), section 323c, “Failure to render assistance; obstruction of persons rendering assistance,” official English translation, https://www.gesetze-im-internet.de/englisch_stgb/. registry ↩a ↩b

[2] American Law Institute, Restatement of the Law Third, Torts: Liability for Physical and Emotional Harm, volume 2, sections 37–44 (2012), affirmative duties and no-duty baseline, ISBN 978-0-314-61432-2. registry ↩a ↩b