The process approach in ISO 9001 means managing the QMS as connected processes whose activities and interactions contribute to intended results. In practice, the organisation needs to understand how work is arranged, how it is controlled and how evidence shows whether it operates effectively.
This article focuses on putting that approach into a working ISO 9001-based system. The process management guide connects it to mapping, ownership and performance review. The official standard is the requirements reference; the examples here are implementation suggestions.
Translate the approach into management decisions
A list of departments is not enough to explain a process system. Identify meaningful outputs, the work needed to produce them and the relationships with other activities. Determine where decisions about inputs, resources, responsibility and acceptance are made.
Do not assume that every task needs its own separately managed process. Choose a level that allows the organisation to understand and control the work. Equally, one box labelled business operations may conceal significant differences and interfaces.
The existing quality-principle explanation introduces the concept. Here the question is how the organisation establishes an operating arrangement and evaluates it against applicable criteria.
Build a coherent inventory
Identify the processes relevant to the QMS scope and explain their purposes. Use actual work and intended results rather than create one process for each clause heading.
Check what enables delivery as well as what directly produces the customer’s output. Competence, information, purchasing and maintenance can affect results even when their contribution is indirect.
The process identification article explains how to test boundaries and avoid gaps or unnecessary duplication. The inventory should support governance, not merely satisfy a request for a diagram.
Define interactions and operational arrangements
For important interfaces, identify what is transferred, who receives it and what makes it suitable for use. A customer change can be recorded correctly by sales while failing to reach the production instruction.
Clarify responsibility for incomplete or conflicting inputs. An arrow between two boxes does not establish that the receiving activity has the information or authority it needs.
| Implementation area | Evidence direction |
|---|---|
| Process identity | Purpose and meaningful boundaries |
| Interactions | Usable inputs, outputs and handover decisions |
| Responsibility | Owners and relevant decision authority |
| Control | Criteria and actions for actual operating conditions |
| Evaluation | Measures and review linked to intended results |
This is an original evaluation framework, not reproduced clause wording or a mandatory checklist.
Use suitable descriptions and controls
The organisation can use process maps, procedures, system workflows or other proportionate information. A flowchart or SIPOC can help, but a particular drawing convention or software package is not the objective.
Controls should address relevant failure conditions. If an input can be incomplete, define how that is recognised and resolved. If release depends on a check, make responsibility and the action on an adverse result clear.
Evaluate resources and competence alongside documentation. An instruction can describe an adequate method while the organisation lacks the equipment, information or capability needed to use it.
Evaluate operation rather than documents alone
Follow a real case through the process. Compare the intended arrangement with actual decisions, records and outputs. Include relevant exceptions rather than examine only a prepared successful example.
A current approved description supports understanding; it does not prove every case followed it. Conversely, an organisation may use a suitable method different from an auditor’s preference. Evaluate the applicable requirement and evidence.
Historical ISO process-approach guidance can provide background, but it is not a substitute for checking the current edition or a source of extra mandatory criteria.
Review results and respond to change
Use evidence to assess whether processes achieve intended outcomes and whether interactions remain effective. Define measures carefully so local success does not hide downstream rework or delay.
When a process changes, identify effects on connected activities. A faster approval route might remove a necessary check or overwhelm the next team. Consider relevant consequences before declaring the change beneficial.
Where an interface repeatedly fails, identify who can make the cross-functional decision. Assigning corrective tasks separately to two departments may leave the shared acceptance problem unresolved. Process governance should provide a practical route to coordinate the response and evaluate whether the receiving activity now obtains a usable output.
Keep implementation proportionate
An effective arrangement can be concise when the work is simple and responsibilities are understood. Complexity, variation and consequence can justify more detailed controls and evidence elsewhere.
Ask whether people can explain their process, obtain suitable inputs, act on exceptions and evaluate results. Those tests reveal more than the number of documents or map boxes. The process approach becomes operational when the organisation manages these relationships consistently, with evidence that decisions about one activity account for the wider system.
A process review can also reveal an inventory problem. If responsibility remains unclear because the defined boundary excludes the critical decision, revisit the process architecture rather than repeatedly escalate individual cases. The definition should support control of the work, not preserve a diagram that experience has shown to be misleading.