1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice
You must be a registered member in order to post messages and view/download attached files in this forum.
Click here to register.

Processes, procedures and requirements

Discussion in 'ISO 9001:2015 - Quality Management Systems' started by Andrew Murray, Nov 22, 2022.

  1. jackdamionds10

    jackdamionds10 New Member

    Joined:
    Apr 21, 2025
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Great topic! Understanding the distinction between processes, procedures, and requirements is key to building an efficient and compliant workflow in any organization. One framework I’ve found especially helpful in managing and continuously improving these elements is the PDCA cycle (Plan-Do-Check-Act). It’s a structured approach that not only helps in setting clear procedures but also ensures they’re aligned with evolving requirements through ongoing evaluation and refinement. Applying the link removed can really elevate how teams document, execute, and optimize their workflows.
     
    Last edited by a moderator: May 8, 2025 at 1:17 PM
  2. Andy Nichols

    Andy Nichols Moderator Staff Member

    Joined:
    Jul 30, 2015
    Messages:
    5,425
    Likes Received:
    2,696
    Trophy Points:
    112
    Location:
    In the "Rust Belt"
    Welcome, Jack Damionds! PDCA is built into the ISO 9001 requirements, and described in the document itself. Implementing ISO 9001 requirements, experience shows, needs much more than software.
     
    John C. Abnet likes this.
  3. pkfraser

    pkfraser Active Member

    Joined:
    Aug 1, 2015
    Messages:
    95
    Likes Received:
    61
    Trophy Points:
    17
    Location:
    Aberdeen Scotland
    Andy
    Is it?(!) 9001 mentions that "Management of the processes and the system as a whole can be achieved using the PDCA cycle" and "The PDCA cycle can be applied to all processes and to the quality management system as a whole". That is as definite as saying that "software can be used to define your management system" - ie stating an opinion, but not specifying a requirement. I have never understood why it is even mentioned in the standard, since it is no more than a problem-solving tool.