What a safety case should demonstrate

In process safety, a safety case explains how relevant hazards have been identified, which measures control them and why those measures are considered adequate for the operation being described and assessed.

It is not simply a folder containing procedures, certificates and drawings. A reader should be able to follow the relationship between a claim, the reasoning supporting it and the information used to check it. Assumptions and analytical limitations also need to remain visible.

Scope and conditions of validity

The installation, its activities and its interfaces define what is being justified. A conclusion concerning normal operation does not automatically cover maintenance, start-up, staffing changes, simultaneous operations or eventual dismantling of the facility.

For example, claiming that a barrier is available requires identification of its function and the conditions under which it must operate. Test history, acceptance criteria and defect resolution provide more useful support than a general statement of commitment to safety.

Legal requirements and wider use

Some regulatory regimes require submission and acceptance of a safety case. HSE distinguishes safety cases for offshore oil and gas installations from safety reports for onshore upper-tier COMAH establishments managing major accident hazards.

That British reference does not make the document a universal legal requirement for every Spanish or Latin American business. Sector, activity, competent authority and applicable requirements must be established before deciding which submission is needed or how it should be organised.

Keep the argument connected to operations

Documentation needs review when the conditions supporting it change. New equipment, modified use or inspection findings may undermine an earlier claim even though the original submission remains available in the company’s records.

Administrative acceptance does not guarantee that accidents cannot occur. HSE guidance distinguishes assessment of the case from subsequent verification through inspection and oversight. For day-to-day management, assign responsibilities, retain current evidence and check that the controls described actually exist and work. Unresolved gaps should be explicit rather than concealed by adding more unrelated documentation to the same file.