A hazard-log is a structured register maintained to record identified hazards, their assessment status, and the controls applied or planned. It is parameterized by: (1) a unique identifier for each recorded hazard, (2) a description of the hazard and its potential consequences, (3) a risk rating derived from severity and likelihood, (4) a status field tracking whether the hazard is open, under review, or closed, and (5) a reference to the control measures assigned to each entry. The hazard-log persists as a living document that is updated throughout the lifecycle of a system or project, enabling systematic hazard management and auditability. It is sustained by organized review practices and integrated into risk assessment workflows. [formal: periclitatio periculorum | substrate: behavior | horizon: a life | explicit: yes | epoch: 0.01]
Accepted ontology entry
hazard-log
A hazard-log is a structured register maintained to record identified hazards, their assessment status, and the controls applied or planned. It is parameterized by: (1) a unique identifier for each recorded hazard, (2) a description of the…
Definition
Why it is in scope
A human-made register used in safety engineering and risk management to record identified hazards, their risk ratings, assigned controls, and review status. It persists through structured documentation practices and is maintained as a living document across project or organizational lifecycles.
Names and aliases
- hazard-logen · CANONICAL
Relations from this entry
- cms8a929t007573fkafm8ap7iSERVES →
A hazard log is a structured register of identified hazards maintained for the sake of risk management. Law 8d: the log exists and is sustained to feed risk assessments with the current hazard inventory. Removing risk-management would remove the purpose of the log — it is built for the sake of risk-management, not the other way around.
- cms81mqtv00jeh6s8s7t3j6hySERVES →
A hazard-log is maintained to feed identified hazards into risk assessments — its designed purpose is to serve risk-assessment. Law 8d: the servant points at the master.
- cms83xe5u00s0h6s88lc8rrb4INSTANCE_OF →
A hazard-log is a specific type of risk-register: both are structured records of identified threats, but the hazard-log narrows the scope to hazards specifically (dangers that could cause harm) while a risk-register covers all risk categories (financial, operational, strategic, etc.). Pinning INSTANCE_OF against risk-register (the nearest kind) follows Law 11e.
- cms8yd4ib02lb73fk4rt35q7mDERIVED_FROM →
Hazard-log derived from hazard-recognition: hazard-recognition (the practice of identifying hazards) existed first and fed into the creation of hazard-log (the structured record of identified hazards). Which came first? Recognition precedes logging — you must recognize hazards before you can log them. Historical priority test passes (Law 7).
Relations to this entry
No accepted relations in this direction.
Record identity
- Created
- Jul 31, 2026, 6:53 AM UTC
- Content hash
- 4ac4b735921b435c2647e8073b446b9c8492418660ea72773d13f13a8e4458fd