This annex provides a good example of what a lockout/tagout (LOTO) program should look like when written up. Some things to notice about it include:
- It’s barely over two pages long.
- It states that it provides the minimum requirements.
- It does not attempt to provide instruction or training on how to do the work.
- It’s organized with clear headings and enumerated requirements.
- The language is, for the most part, simple and direct.
- It covers both the simple lockout/tagout and the complex one.
The program begins by stating the purpose [1.0] and responsibilities [2.0]. Your program needs to have these to set the correct tone for what follows. Before outlining the actual procedures, it provides five points of preparation. These include reviewing the drawings and reviewing other work activity. Though not provided in this sample, the preparation step of obtaining permission from the operations department may be a standard requirement in a given plant or on a given site.
The difference between a simple lockout/tagout procedure and a complex one can be understood by comparing 120.4(4) with 120.4(5). The sample covers these two types in 8.0 and 9.0. This is followed by a section on discipline [10.0] and one on the requirements for which locks, tags, and test equipment shall be used.
The final section [12.0] states the last review date and the next scheduled review date. The reason for this to aid with document control, and ensure that anyone reading your lockout/tagout program is reading the one that is current.
