ISO 9001 Clause 4.4: Make QMS Processes Work Together

What clause 4.4 requires in practice

Clause 4.4 requires the organisation to operate its quality management system as a set of connected processes. It establishes, implements, maintains and continually improves the system, including the processes needed and how they interact. The detail sits in two subclauses. Clause 4.4.1 covers how processes are defined and controlled, from inputs and outputs through criteria, resources, responsibilities, risks and opportunities, evaluation and improvement. Clause 4.4.2 covers the documented information that supports operation and gives evidence that processes ran as planned.

The clause uses the process approach, so a process is judged by the result it delivers and by how well it connects with others, not by whether a diagram exists. The organisation chooses its own level of detail. The outputs are working processes with clear ownership and enough information to run them and to show how they performed, without a fixed number of procedures.

Identify processes through the work they accomplish

Start with a representative product or service and identify the activities that turn a need into an accepted output. Establish inputs and expected outputs, sequence and interaction. Include supporting and management processes where they affect outcomes. A department is an organisational unit; a process may pass through several departments before producing its result.

Define criteria and methods for operation and control, including suitable monitoring and performance indicators. The person responsible should understand what acceptable performance means and what to do when conditions move outside the agreed basis. Resources and authority need to support that responsibility. Assigning ownership without decision access leaves a name on the diagram but an unresolved management problem.

Why connected processes matter to the business

Most delivery failures happen at handovers: sales to operations, operations to support, one site to another. A system built from isolated departmental routines can look tidy while customers still receive the wrong thing. Treating the business as connected processes makes the hand-offs visible, gives each result an owner and shows where measures encourage the wrong behaviour. The commercial benefit is steadier delivery, fewer reworked orders and quicker identification of who should act when something goes wrong. It also helps growth, outsourcing and acquisition, because responsibilities can be reallocated without losing the thread of the customer's requirement.

How to implement clause 4.4

Start with real work and build outwards; the standard requires effective processes, not a drawing exercise. The clause requires effective processes and their interaction, so keep the description light and spend the effort on controlling the handovers.

1. Trace one representative product or service from the customer's need to accepted delivery and note the activities involved.
2. Group those activities into processes with a clear purpose, a main input and an expected output.
3. Mark where one process hands work to another and what information must travel with it.
4. Appoint an owner for each process with authority to resolve issues, and confirm resources are available.
5. Agree how each process will be monitored, using indicators the owner can act upon.
6. Decide what information supports operation and shows results, then connect risks and opportunities from planning to the relevant processes.
7. Review the system after changes or recurring failures and adjust the processes rather than adding layers.

Evidence an auditor expects for clause 4.4

An auditor follows the work, often tracing one product or service through several processes.

• Interviews with process owners who can explain inputs, outputs, interactions and what good performance looks like.
• Records of monitoring results and the actions taken when results were poor.
• Observation that handovers between teams carry the information the next process needs.
• Evidence that resources and responsibilities have been assigned and are understood.
• Records showing that process changes followed a review of results.

A process map can help, but the auditor tests whether the processes work, not whether a map exists.

Illustrative software example: an agreed feature reaches release

Connect risk and opportunity decisions to process controls

Clause 4.4 links process management with the risks and opportunities determined under clause 6. A risk assessment should change a relevant decision where action is needed. For instance, a vulnerable approval handover may require an alternative authorised reviewer. An opportunity may justify a pilot that removes unnecessary re-entry of information. Both need evaluation against the intended result.

Process evaluation is not limited to whether people followed instructions. The organisation also assesses whether processes achieve their intended results and introduces necessary changes. A meticulously followed method that repeatedly produces unusable outputs needs attention. Distinguish a failure to apply the current method from evidence that the method itself needs improvement.

Illustrative construction example: drawing changes reach subcontractors

A hypothetical construction company controls its drawing register centrally, while a subcontractor receives revisions through a different contact. A revised detail is approved but does not reach the point of work. Examining the process shows that internal document approval and external communication were treated as separate completions.

The company assigns responsibility for the complete handover, identifies affected work and establishes a check that current information reached authorised recipients. Evidence might include the revision decision, distribution acknowledgement and a sample of information actually used on site. Technical verification and site-specific safety controls remain the responsibility of competent project personnel; the QMS process does not replace them.

Document enough to operate and demonstrate the process

Under 4.4.2, documented information supports operation and provides confidence that processes were carried out as planned. The amount depends on complexity, consequences and the capability of the people involved. An experienced small team may use concise integrated instructions; a distributed process may need more explicit interfaces and evidence.

Useful audit evidence can include work records, approvals, performance reviews and explanations from people doing the work. A reviewer may trace a selected transaction between functions, comparing the planned handover with actual practice. A large process manual is not automatically stronger evidence than a short, controlled instruction supported by consistent operation.

Avoid the three common disconnects

Explore each numbered part