Unsafe Supervision

The HFACS stratum in which supervisory planning, correction, and rule- enforcement decisions transmit organizational conditions into the operator's immediate environment and thereby stage unsafe acts.

Core Idea

Unsafe supervision is the HFACS layer in which supervisory decisions and omissions create or sustain conditions for unsafe acts. It includes inadequate supervision, inappropriate planned operations, failure to correct known problems, and supervisory violations.

The canonical identity is narrower than the phrase’s everyday use. A supervisory role has authority over planning, staffing, training, monitoring, correction, or rule enforcement; an exercise or failure of that authority changes the operator's immediate conditions; and a credible pathway connects it to an unsafe act or elevated accident risk.

Structural Signature

• It is the second HFACS level, between organizational influences and preconditions for unsafe acts.
• It concerns supervisor-level planning, task assignment, known-problem correction, and supervisory violations.
• It transmits or locally amplifies organizational choices rather than originating the resource, culture, or process regime at the apex.
• Its output is an operator or team situation that raises the likelihood of an unsafe act, not the act itself.
• It supports supervisory-level remedies distinct from operator retraining and organization-wide redesign.

What It Is Not

Organizational influences sit upstream in resources, climate, and process. Preconditions describe operator, team, or environmental states. Unsafe acts are the front-line errors and violations. Generic poor management lacks HFACS's layer and causal routing.

• Organizational influence failure, the apex resource, climate, and process layer.
• Preconditions for unsafe acts, the immediate operator-and-team state produced downstream.
• Active failure or unsafe act at the sharp end.
• Supervision in general outside an HFACS accident-causation finding.

Scope of Application

Aviation, healthcare, mining, and maritime cases carry the same safety taxonomy, but that is reuse of HFACS across high-risk sectors. Removing supervisory authority and accident causation leaves generic dependency.

A shared label or downstream consequence is insufficient; the load-bearing roles must survive.

Clarity

Unsafe Supervision separates a specific relation from neighboring ideas that can produce similar observations. Organizational influences sit upstream in resources, climate, and process. Preconditions describe operator, team, or environmental states. Unsafe acts are the front-line errors and violations. Generic poor management lacks HFACS's layer and causal routing.

Manages Complexity

The abstraction compresses recurring cases into one inspectable model. An analyst can track the structural roles, compare mechanisms, and locate exactly which missing commitment invalidates an analogy.

Abstract Reasoning

Identify the candidate roles, test the defining relation, then challenge the nearest boundary case. A front-line worker's unforeseeable lapse is not unsafe supervision unless a supervisory action or omission helped create the conditions in which it occurred.

Knowledge Transfer

Aviation, healthcare, mining, and maritime cases carry the same safety taxonomy, but that is reuse of HFACS across high-risk sectors. Removing supervisory authority and accident causation leaves generic dependency. Transfer is warranted only when the same causal, formal, or relational work survives.

Examples

Qualifying pattern. Unsafe supervision is the HFACS layer in which supervisory decisions and omissions create or sustain conditions for unsafe acts. It includes inadequate supervision, inappropriate planned operations, failure to correct known problems, and supervisory violations.

Boundary case. A front-line worker's unforeseeable lapse is not unsafe supervision unless a supervisory action or omission helped create the conditions in which it occurred.

Structural Tensions

T1 — Reach versus identity inflation. Broad use is valuable only while every defining role survives.

T2 — Observation versus mechanism. Similar outcomes can arise from neighboring mechanisms, so classification follows the relation and its counterfactual rather than appearance.

Structural Core vs. Domain Accent

Aviation, healthcare, mining, and maritime cases carry the same safety taxonomy, but that is reuse of HFACS across high-risk sectors. Removing supervisory authority and accident causation leaves generic dependency. The transferable residue is thinner than the named mechanism, whose domain vocabulary and causal apparatus remain constitutive.

Relationships to Other Abstractions

Current abstraction Unsafe Supervision Domain-specific

Foundational — no parent edges in the catalog.

Children (1) — more specific cases that build on this

• Human Factors Analysis and Classification System Domain-specific is part of Unsafe Supervision

  Unsafe supervision is the second constituent stratum of HFACS.

Not to Be Confused With

Organizational influences sit upstream in resources, climate, and process. Preconditions describe operator, team, or environmental states. Unsafe acts are the front-line errors and violations. Generic poor management lacks HFACS's layer and causal routing.

• Organizational influence failure, the apex resource, climate, and process layer.
• Preconditions for unsafe acts, the immediate operator-and-team state produced downstream.
• Active failure or unsafe act at the sharp end.
• Supervision in general outside an HFACS accident-causation finding.

Notes

(Canonical first draft from the adjudicated missing-node gate. Queued for Claude house-style re-authoring and independent citation review; no citations have been fabricated.)