Skip to main content
    QHSEtech
    Updated
    All glossary terms
    Content date: · No individual check logged· AI use

    SOPStandard Operating Procedure

    Also known as: Operating procedure

    Definition

    Standard Operating Procedure — documented instructions for carrying out a defined activity consistently, usually as ordered steps with the checks and limits.

    Editorial definition: The QHSE Standard, updated 3 October 2026 · https://qhsetech.com/glossary/sop

    Scope: A current procedure still needs competent implementation and review when the work changes.

    What HSE and OSHA say about written procedures

    HSE's human factors pages describe procedures, including method statements, work instructions and permits to work, as the agreed safe ways to do a job. They usually consist of the instructions and related information needed to carry out a task safely, and may take forms such as stepwise instructions, checklists, decision aids, diagrams or flow-charts. HSE links numerous incidents to problems with procedures. The main causes it names are too much reliance on procedures to control risk, failure to follow safe working procedures and the use of inadequate procedures, and it adds that operating procedures may not be the most suitable way of controlling hazards when they are the only defence against human error.

    HSE's design principles start from risk assessment, which should establish whether a procedure is an appropriate control. Procedures and competence are described as two sides of the same coin, and procedures do not replace competence. HSE asks for a system for managing procedures, covering which tasks need them and how they are developed, complied with and reviewed or updated. It suggests task analysis, such as walking and talking through the task with the people who do it, and a format that fits the user, the task and the consequences of failure, because one size does not fit all.

    Some rules require written procedures for particular hazards. In the US, 29 CFR 1910.119(f), for covered chemical processes, requires written operating procedures with clear instructions for each operating phase from startup to shutdown, operating limits with the consequences of deviation, and safety and health considerations. They must be readily accessible, reviewed as often as necessary to reflect current practice, and certified annually as current and accurate. Rule 1910.147(c)(4) requires documented procedures for control of hazardous energy, subject to a stated exception. These are examples of where the law requires written procedures, not a general rule for every SOP. This page is general information.

    Sources opened :

    What an SOP record holds in software

    • The title, number, owner, version, effective date and next review date.
    • The scope: the task, equipment, site and roles it covers, and what it excludes.
    • The hazards and controls it relies on, linked to the risk assessment behind it.
    • The steps, limits and checks in order, with any decision points.
    • Approvals and the change history, with the reason for each revision.
    • Where the current version is available to the people doing the work.
    • Training or read-and-understood records for the version in force.
    • Superseded versions retained and marked as withdrawn.

    SOP, work instruction, method statement and policy

    HSE groups method statements, work instructions and permits to work under procedures and does not separate them. Organisations draw the lines differently. A policy states intent, an SOP usually describes how a repeated activity is carried out, a work instruction may give finer step detail for one task or machine, and a permit authorises one piece of work. None of these distinctions is fixed by the sources here, so define the terms in your own document control procedure and use them consistently.

    A hypothetical example: changing a blade on a cutting machine

    This workshop and its machine are invented, and the account describes no real business. A supervisor drafts an SOP for changing the blade on a cutting machine, writing the steps from memory. Before approving it she walks through the task at the machine with two operators. They find that step four refers to a guard that was replaced last year, and that a torque value in step seven is missing from the machine manual. The isolation step points to the site's lockout procedure instead of repeating it. She checks that the hazards listed match the current risk assessment.

    The SOP is trialled for two weeks. One operator suggests moving the cleaning step before the blade is removed, and the change is logged as version two with the reason. The old copy is withdrawn from the machine, and the training record shows who has read the new version. The site sets a review date a year ahead and says the SOP will be reviewed sooner if the blade type or the guard changes.

    Common misunderstandings about SOPs

    • A current SOP is not a competent workforce. HSE says procedures do not replace competence, and the two have to support each other.
    • A controlled copy in the system is not the version at the machine. People can only follow what they can reach, and the US rule for covered processes asks that procedures be readily accessible.
    • More procedures are not safer by themselves. HSE warns against too much reliance on procedures and against inadequate ones, and notes they may not be the most suitable control when they are the sole defence.
    • A deviation is not always defiance. HSE says violations often arise from poorly designed tasks and unworkable rules, so the first question is why the step was skipped.
    • A sign-off is not proof of accuracy. An annual certification, where a rule requires one, still depends on someone checking the steps against how the work is done.

    How SOPs relate to other glossary terms

    A procedure is one output of hazard analysis and the thing a change process must keep current.

    • Job safety analysis: breaks one task into steps and hazards that an SOP can then fix as the agreed method.
    • LOTO: an energy-isolation procedure that the US rule requires to be documented.
    • Management of change: the process that should trigger an SOP revision when equipment or methods change.
    • Permit to work: authorises a specific piece of work, whereas an SOP covers a repeated activity.

    Records and evidence that usually exist for SOPs

    • A register of procedures with owner, version and review date.
    • The approved current version and the history of earlier ones.
    • The task analysis or walk-through notes used to write it.
    • Training or read-and-understood records for each version.
    • Feedback and deviation reports from users, and what was done about them.
    • Review records, and observations comparing the work with the procedure.

    What a software tool needs to capture for SOPs

    • Version control with effective and superseded dates, and withdrawal of old copies.
    • Owner and review-date fields with reminders.
    • An approval workflow with an audit trail of who approved what.
    • Links to the hazards, equipment and training that relate to each procedure.
    • Controlled access at the point of work, including where there is no network.
    • Read-and-understood tracking per version and per person.
    • A route for users to report problems, linked to the change process, and an export for auditors.

    Catalog profiles documenting work instructions and procedures

    The profiles listed record a work-instruction or procedure capability. Approval, distribution and retirement of procedures as described here are separate points to test.

    Same rule for every product: tagged “Work Instructions”, with a sourced work-instruction or procedure capability in its record, or one the vendor stated to us, labelled as vendor-stated. Documented and conditional capabilities qualify; check the linked scope before treating a module as included.

    Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered

    All 8 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.

    Related software

    Frequently asked questions

    Is an SOP legally required?

    It depends on the activity and the jurisdiction. Some rules, such as the US process safety and hazardous energy standards, require written procedures for covered work. HSE advises using risk assessment to decide when a procedure is the right control.

    How often should an SOP be reviewed?

    OSHA's process safety rule asks for review as often as necessary and an annual certification for covered processes. HSE asks for a system that covers review and updating. Set your own interval by risk and by how often the work changes.

    What is the difference between an SOP and a work instruction?

    HSE groups work instructions, method statements and permits to work together as procedures, and organisations draw the lines differently. Define the terms in your own document control procedure.

    More quality terms

    Related guides