Mapping processes for ISO 9001
A process map shows how work really flows through your organisation. ISO 9001 asks you to determine the processes you need and how they interact. The official ISO page gives the standard’s context. In the ISO 9001 step-by-step plan, this is one step, while the requirements page places the process approach in clause 4.4.
Start from the result for the customer, not from the clause numbers of the standard. A standard clause is not automatically a business process. “Internal audit”, for example, can be one activity within evaluation, whereas “order to delivery” is a real chain across sales, planning, warehouse and invoicing.
1. Draw the process landscape first
Make an overview on three levels:
- Core processes: work that delivers direct value, such as designing, producing or delivering.
- Supporting processes: work that makes the core processes possible, such as staff administration, IT and maintenance.
- Governing processes: choices, objectives, evaluation and improvement.
Keep the first overview small enough to discuss the connections. Only then zoom in on processes where risk, variation or unclear ownership sits.
2. Describe each process with the same questions
Use a process map, workflow or digital record. The ISO/IAF APG guidance on processes lists, among other things, inputs, outputs, interactions, resources, responsibilities, measurements, risks and changes as topics for an audit. The format is up to you. The map must make the work understandable and controllable. You find a fully completed example at process description example for ISO 9001.
| Element | Question to answer |
|---|---|
| Purpose and output | What result does the process deliver, and who receives it? |
| Input | Which information, materials or decisions are needed to start? |
| Steps | Which activities determine the quality of the result? |
| Owner | Who monitors the process and may adjust it? |
| Criteria | When is the output good enough? |
| Resources | Which people, systems, knowledge or equipment are needed? |
| Risks and opportunities | What could disrupt or improve the result? |
| Measurement | Which indicator gives timely insight into performance? |
| Changes | How do you assess a new way of working, customer or supplier? |
Example (fictional): wholesaler DeltaParts maps order processing as: customer order, then stock check, then picking or purchasing, then delivery, then invoice. The stock check gives a decision to planning. The process map shows that stock updates are sometimes only processed at the end of the day. DeltaParts therefore links a daily check to the indicator “orders with stock correction”.
3. Record the interactions
A process rarely stands alone. Note who supplies the input, who receives the output and what information accompanies the handover. Look especially for handovers where errors arise: sales to planning, design to production, or supplier to goods-in inspection.
A simple table often works better than a complicated diagram:
| From process | Output | To process | Check at handover |
|---|---|---|---|
| Sales | Confirmed order with requirements | Planning | Is the order complete and feasible? |
| Planning | Work order and delivery date | Warehouse | Have the version and stock status been checked? |
| Warehouse | Checked shipment | Customer | Are release and proof of dispatch present? |
Have employees test the map using one real order. If nobody can explain where information comes from or what happens when there is a nonconformity, the map is still too abstract.
4. Choose measurements that help you steer
An indicator must support a decision. Think of lead time, error rate, the percentage that is right first time, rework or on-time delivery. Also note the source, owner and review point. Two indicators that contradict each other need explaining: working faster is not an improvement if rework rises as a result.
Use risk to set the depth. A simple administrative process can get by with a short map and periodic checks. A process with legal, customer or safety-critical consequences deserves clear criteria, records and a targeted audit.
Do not create a process map per standard clause just because it looks tidy. An audit preferably follows your actual processes and their results, not a stack of separate chapters.
Frequently asked questions
Must every process have a separate procedure?
No. A process map, work instruction, software workflow or record can be suitable. Only record what is needed to run the process under control and to have confidence in the result.
How many processes must a small company describe?
That depends on the activities and how they connect. Start by describing the chain from customer request to result, then add supporting and governing processes where they influence the outcome. A small company often has fewer processes than a large organisation.
Who makes the process map?
Involve the people who do the work and the person who receives the result. The process owner keeps the final version, but a map made only at a desk often misses important handovers.
Related links
Sources
- ISO 9001:2015, official standard page : ISO, accessed 5 September 2026; the edition is listed as under revision
- ISO/IAF APG: Processes : audit guidance, not an additional standard requirement
- NEN-EN-ISO 9001:2015, standard information : NEN