The MOC Program – Operation

MOC systems are different at every corporation and even slightly different at each location. They must be developed to fit the specific hazards, the available resources, the culture of the organization, and any required regulations. The result is broad differences in review and authorization philosophy.

For example, some organizations would require only 1 signature for authorization of a specific change while others could require 5 for the same type of change.

Despite the differences, the programs are all built on the same fundamental principles and with the same goal of preventing incidents.

Flowchart of a Management of Change Program

The diagram illustrates a possible flow chart for the operation of a MOC program – it is based on a flowchart used by Brian Kelly.

(Note – the chart may be too small in landscape view and thus a slide is available in portrait view )

The program starts with the identification of a change. The change is then subjected to a risk ranking procedure (discussed later). High and medium risk changes continue down the path, while low risk changes can skip to the implementation step.

The change must be reviewed by a team leader/manager at this point to provide approval for the process to continue.