Standard Operating Procedure

Standard Operating Procedure (hereinafter referred to as SOP) is a document describing the sequence of actions when performing a specific operation. The purpose of an SOP is to ensure safety, consistent quality of work performed, and a unified approach to personnel work.

Using the example of JSC Rosatom Steklovolokno, it is clear that an SOP details:

• the name of the operation;
• the frequency of execution;
• necessary materials and tools;
• step-by-step actions of personnel;
• HSE requirements and PPE;
• risks and mitigation measures.

How an SOP is developed:

1. Process analysis: every action performed by the worker is studied. A photo of the step is taken, and risks are assessed. To assess and rank risks according to the methodology during SOP development, a separate tab in the file is used (the SOP file is attached to the article).
2. Description of operations: step-by-step instructions indicate what the worker does, what tools they use, and how they control the result.
3. Recording risks: next to each operation in the working procedure, the corresponding cell is colored according to the risk level, and the main hazards that may affect the worker during this step are specified.
4. PPE: each step specifies the PPE that may be specific to that step, for example: the use of protective gloves or earplugs, etc.
5. Review and approval: the document is approved by the department head and the HSE specialist, and may also be coordinated with other departments as necessary.

What to pay attention to:

• all instructions must be clear and practically applicable;
• photographs increase clarity;
• it is important to pay attention to key safety points;
• the SOP should be regularly reviewed when technology changes or new risks are identified.

The process of developing an SOP is not simple and takes a considerable amount of time and effort. In practice, SOPs should be developed by department heads/services/specialists who know the process, but this is not a mandatory requirement. An SOP can even be developed by an employee unrelated to the type of work being performed; however, the final version must be shown to the employee directly performing the work. Sometimes, the experience of having a third party develop an SOP helps identify risks that were not initially reflected anywhere.

If you decide to implement and develop SOPs at your enterprise, you need to determine the priority operations, compile an estimated list for document development for the year, discuss deadlines with colleagues in advance, and only then begin the work.

To identify priority operations, you can pay attention to the following indicators:

• the frequency of HSE violations during operations;
• incidents: near misses, micro-injuries, accidents;
• the frequency of work performed: there is no point in developing an SOP for work performed 2-3 times a year (as an example);
• high-hazard work: since high-hazard work involves high risks, developing an SOP for this type of work should probably be prioritized.

An SOP not only helps reduce occupational risks and prevent incidents, but the document also serves as an excellent foundation for personnel training. Thus, a well-developed SOP is not just a formality, but an important tool for managing safety and labor efficiency.