hazard-assessment

Which-came-first: hazard-identification (the practice of spotting potential harms) predates and feeds into hazard-assessment (systematically examining identified hazards for likelihood and severity). Assessment is the refinement step that comes after identification.

Risk-assessment as a broader evaluative practice predates and fed into hazard-assessment as a more focused variant. Both DERIVED_FROM edges are valid: hazard-identification (direct precursor step) and risk-assessment (broader parent practice).

Hazard assessment is conducted as part of and for the sake of the safety management system: it provides the systematic evaluation of hazards that the management system requires for decision-making. Law 8d: the designed purpose of hazard assessment is to feed risk-informed decisions into the management system.

Hazard-assessment is maintained for the sake of risk-management: identifying and evaluating hazards provides the input data that risk-management uses to prioritize controls and allocate resources. Law 8d: servant(hazard-assessment)→master(risk-management).

Law 9: job-safety-analysis is a specific kind of hazard-assessment. JSA is a structured method where a worker systematically breaks down a job into steps and identifies hazards at each step. It is one particular methodology under the broader class of hazard-assessment techniques.

Safety-metric is maintained for the sake of hazard-assessment. Quantitative measures of safety performance provide the data that hazard-assessment uses to evaluate risk levels and track improvements.

Safety-reporting collects and communicates safety data (incidents, near-misses, observations) that hazard-assessment uses to evaluate risk levels and identify patterns. Law 8d: servant(safety-reporting)→master(hazard-assessment). Reporting is maintained so hazard-assessment has timely, comprehensive data to work with.

safety-observation SERVES hazard-assessment per Law 8d: servant→master. Systematic observation of safety conditions provides data that hazard-assessment uses to evaluate risk levels and identify patterns.

Root-cause-analysis is a specific form of hazard assessment: it systematically investigates incidents to identify underlying causal factors, making it a concrete method within the broader hazard-assessment practice.

Bow-tie-analysis is a specific hazard-assessment technique that visualizes threats, controls, and consequences in a bow-tie diagram. It is a concrete method within the broader hazard-assessment practice.

safety-case is a specific structured argument that a system's risks are adequately controlled, used to support go/no-go decisions. It is a specific kind of hazard-assessment method. Precheck: safety-case is ACCEPTED, hazard-assessment is ACCEPTED.

FMEA is a systematic, structured method for identifying potential failure modes and their effects. It is a specific instance of the broader hazard-assessment practice. Law 9: FMEA is a specific kind of hazard assessment method.

near-miss-reporting IS built and maintained for the sake of hazard-assessment: reporting near misses produces data that hazard-assessment uses to identify systemic weaknesses before incidents occur. The purpose is by design — near-miss programs are instrumented specifically to feed hazard assessment processes.

safety-climate IS maintained for the sake of hazard-assessment: measuring collective safety attitudes surfaces systemic organizational factors (norms, communication, resource perception) that contribute to hazard creation. Safety climate data feeds into hazard assessment to identify root organizational causes. Purpose is by design.

Near-miss-reporting is a specific practice within the general category of hazard-assessment: it systematically collects and analyzes information about close calls to identify potential hazards before they materialize. A competent speaker would call near-miss-reporting 'a kind of hazard-assessment'.

Safety-observability is built and maintained for the sake of hazard-assessment: it provides the continuous monitoring, dashboards, and alerts that feed into identifying and evaluating hazards. The servant (observability) points at the master (hazard-assessment) — Law 8d.

Hazard-reporting is maintained for the sake of hazard-assessment: it channels frontline hazard data into assessment processes where risks can be evaluated, prioritized, and acted upon. The reporting process serves the broader assessment function. Classic SERVES teleology — the servant (reporting) points at the master (assessment).

Safety-indicators provide data on leading and lagging safety metrics that feed directly into hazard identification and risk assessment. The indicators serve hazard-assessment by surfacing trends, near-misses, and conditions that signal emerging hazards.

Safety permits are designed for the sake of hazard assessment — a permit-to-work system ensures hazards are identified and assessed before hazardous work begins.

A safety-incident-report is produced/designed for the sake of hazard-assessment. Its purpose is to document incident details so hazards can be identified, evaluated, and mitigated. SERVES per Law 8d: the servant (report) points at the master (hazard-assessment). Removing the report format would not stop hazard-assessment from operating, but the report exists specifically to further it.

Safety-metrics are produced and maintained for the sake of hazard-assessment. They provide the quantified data that hazard-assessment operations need to evaluate risk levels and identify trends. SERVES per Law 8d: the servant (safety-metrics) points at the master (hazard-assessment).

Safety-monitoring provides continuous data, sensor readings, and observation records that hazard-assessment relies on to identify changes in risk profile. Its designed purpose is to supply the evidence base for assessment. SERVES direction: servant (monitoring)→master (assessment).

Safety-traceability links safety-relevant information (decisions, test results, incidents, design changes) across the lifecycle, enabling hazard-assessment to build on prior analysis and maintain continuity. Its designed purpose is to serve assessment's need for coherent records. SERVES direction: servant (traceability)→master (assessment).

A hazard-register SERVES hazard-assessment (Law 8d): the register is built and maintained for the sake of hazard-assessment's operation. It catalogs hazards systematically to support the assessment process — its designed purpose is to further hazard-assessment. For whose sake? The servant (hazard-register) points at the master (hazard-assessment).