What it is about
A process turns inputs into an intended result: a customer enquiry into delivered goods, a job advertisement into a new colleague who has been inducted, a security incident into a completed response with lessons learned. Often the output of one process is the input of the next.
In all three standards, clause 4.4 requires the management system to be built with the processes it needs and their interactions. Behind this is the process approach: a company is managed by its workflows, not by its departments. For each process it should be clear what goes in and what comes out, who is responsible, which resources it needs and how you can tell that it works. The handovers between departments are particularly important, because that is where most errors arise.
None of the standards requires a process map, but it is the quickest way to show the overview in the audit. A common split is into management processes that steer the company, core processes that directly create value for the customer, and support processes that make this possible. Which process belongs to which group is for each company to decide.
4.4 reaches into other clauses: the risks and opportunities of a process come from 6.1, criteria and operational control from 8.1, and a change to a workflow is only done once it has been planned, approved and checked for its effect (6.3).
What the auditor checks
“Show me how an order runs through your company.”
The audit of 4.4 often starts with this request. Anyone who opens a folder of procedures or tells the workflow freely from memory has only partly shown the requirement. Convincing is a real case that can be followed through all stations on the map and in the description.
“Show me the last case you worked on.”
Asked at the workplace, not in the meeting room. Within a few minutes it becomes clear whether description and reality match: does the person work with the forms and systems in the description or with a list of their own alongside? Can they say where the case came from and who it goes to next? The follow-up question about the exception, such as a rush order or missing material, is revealing, because that is where practice is most likely to depart from the description.
“Who is responsible for this process, and how do they know it works?”
Whether there is a named process owner and one or two performance indicators they look at regularly, such as on-time delivery, lead time or error rate.
“What happens at the handover from sales to production?”
The interactions. If each department has only described its own part, but not what it passes on to whom, exactly the point where most errors arise is missing.
“Is this the valid version, and who approved it?”
Whether there is exactly one valid version, approved by the process owner, with a date and a date for the next review.
“Which risks have you determined for this process?”
Whether the risks and opportunities are attached to the process and evaluated with the same scheme as all others from 6.1. A capacity bottleneck that threatens the delivery date is a typical example.
“What last changed in this workflow, and how did you inform those affected?”
Whether a change is more than an adjusted diagram: a traceable approval, affected people who know about it, and later a check whether the change worked. The 2026 editions give this point more weight.
Which evidence convinces
A process map with all processes and their interactions
It is not mandatory, but shows on one page which processes exist, which group they belong to and in which order an order passes through them. A return path such as complaints shows that interactions do not only run in one direction. It becomes convincing when a real order can be followed on it and employees can show their place in it; a framed process map in the corridor that nobody can explain only looks good.
Real cases that match the description
An order, a complaint or a purchase that can be followed in the records from trigger to result. They convince more than any diagram, because they show that the process runs as described, including at the handovers.
A one-page description per process
Purpose, process owner, trigger and inputs, outputs, the steps with roles, required resources, performance indicators and associated documents. A flowchart with swimlanes per role makes visible the handovers that matter in the audit.
Performance indicators per core process that are looked at regularly
Without a yardstick it cannot be shown that a process achieves its results. One or two indicators are enough if someone really follows them.
Risks and opportunities per process, evaluated as in 6.1
They link the workflow to planning and show that the company knows where a process is at risk.
Approval and next review date per version
Only approval by the process owner makes a description binding. Who approved which version when, and when it will be reviewed again, answers the question about the valid status immediately.
Typical nonconformities
A process map without life
The process map hangs on the wall, but nobody can say who owns which process. Without process owners nobody looks after performance indicators, risks and changes, and the map stays a picture.
Description and reality differ
In conversation with employees, the process runs differently from how it is documented. If a single step differs and the result is right, this is usually an observation or a minor nonconformity, because the requirement is only partly not met. If the process runs differently at essential points without anyone having updated the description, and errors or complaints result, the system does not work at that point, and it can become a major nonconformity.
No performance indicators
There is no yardstick for whether the process achieves its results. Then it can neither be shown that it works nor recognised when it gets worse.
Handovers missing
Each department has described its part, but not what it passes on to whom. The interactions that 4.4 explicitly requires remain open. If they are missing at individual points, this is usually a minor nonconformity. It becomes serious when something is repeatedly lost at an unregulated handover, such as customer requirements between sales and production: then the system does not work there, and grading it as a major nonconformity is on the table.
Unclear status
Several versions are in circulation, and nobody knows which one applies. People then work to whichever one is at hand, and a change does not reach everyone.
Differences by standard
ISO 9001ISO 9001
ISO 9001 is the most detailed in 4.4. For each process, inputs and outputs, sequence and interaction, criteria with performance indicators, resources, responsibilities and risks and opportunities have to be determined, among other things, and the processes have to be evaluated and improved. Documented information is kept to the extent necessary to operate the processes and to have confidence that they run as planned. In the 2026 edition, 4.4 stays largely the same in content; handling changes in 6.3 gets more weight.
ISO 14001ISO 14001
ISO 14001 says less in 4.4: the management system with its processes and interactions, taking into account the knowledge gained in 4.1 and 4.2. Criteria and control of the processes are in clause 8.1. The 2026 edition has a separate clause 6.3 on planning of changes for the first time.
ISO 27001ISO/IEC 27001
ISO/IEC 27001 has required the processes and their interactions in 4.4 since the 2022 edition. As in ISO 14001, criteria and control are in clause 8.1, meaning the processes for information security. Anyone running several standards does not need separate process landscapes: a process such as purchasing carries requirements for quality, environment and security at the same time.
How IMScollect covers it
In IMScollect, clause 4.4 has its own page. Each process has a BPMN diagram with swimlanes per role; on request, AI creates the first draft from a description in your own words or from a Word or PDF document, and you check and adopt it. Each process has responsible persons, process experts, a reference to the standard, a process type and the resources it uses from the inventory.
You create and evaluate risks and opportunities directly on the process; on approval they appear in risk management. The process owner approves a version with a reason, and only the approved version applies and is visible to everyone. Before each new approval, the app shows what has changed since the last one. The review frequency gives the date of the next review; if it is overdue, a task is created. The process map arranges all processes into management, core and support processes.
Frequently asked questions
What does clause 4.4 of ISO 9001 require?▾
The quality management system has to be built with the processes needed and their interactions. For each process the company determines, among other things, inputs and outputs, sequence and interaction, criteria and performance indicators, resources, responsibilities and risks and opportunities. On top of this comes as much documented information as is needed to operate the processes and to provide evidence.
Is a process map mandatory under ISO 9001?▾
No. The standard requires the sequence and interaction of the processes to be determined, but does not prescribe a particular form of presentation. A process map is nevertheless the usual and quickest way to show this overview in the audit.
What belongs in a process description?▾
Purpose, process owner, trigger and inputs, outputs, the steps with roles, required resources, performance indicators, risks and opportunities and associated documents. A flowchart with swimlanes per role makes the handovers between departments visible.
What is the difference between core, management and support processes?▾
Core processes directly create value for the customer, such as order processing and production. Management processes steer the company, such as setting objectives and the management review. Support processes make the core processes possible, such as purchasing, HR and IT.
How many processes are usual for a medium-sized company?▾
Ten to twenty is typical; more quickly becomes confusing. The fastest way to find them is a workshop with those responsible for sales, production or service delivery, purchasing and administration, asking what an order, a complaint or a new employee passes through.
What do ISO 14001 and ISO 27001 require in clause 4.4?▾
Both require the management system, including the processes needed and their interactions, to be built; ISO/IEC 27001 has done so since the 2022 edition. ISO 14001 additionally requires the knowledge from 4.1 and 4.2 to be taken into account. Both standards set out criteria and control of the processes in clause 8.1.
Further reading and viewing
- Integrated management: what ISO 9001, 14001 and 27001 share
- The auditor asks, episode 2: management system and processes (in German)Watch on YouTube (in German)(opens in a new window)
