An org chart shows who reports to whom. A process map shows what goes in, what comes out, and what gets transformed in between. These are different things, and confusing them is the number one reason a process map stops being useful the moment the certification audit ends.
If your “process map” is really just the org chart with a different name, or a diagram built once for certification that nobody has opened since, this guide is for you. We’ll cover what a process map is under ISO 9001, what clause 4.4 actually requires, and how to build one that reflects your real operation — step by step, with an example.
Table of Contents
What a process map is and what clause 4.4 requires
Clause 4.4.1 states that the organization must determine the processes needed for its quality management system, and for each one: its inputs and outputs, its sequence and interaction with other processes, the criteria for operating and controlling it, the resources it needs, and who is responsible.
More on the full framework: Clause 4 of ISO 9001: Context of the Organization.
A process map is the visual representation of that information: which processes exist, how they relate to each other, and how work flows from the moment a requirement comes in to the moment a product or service goes out. The standard doesn’t require a specific format — no flowchart symbols, no particular tool. It requires the map to reflect the real business, not an idealized version from a manual.
The 3 types of processes your map should distinguish
The most common mistake when mapping processes is mixing different levels into a single diagram without distinguishing their nature. A clear process map separates three categories:
Strategic processes
The ones that steer and plan the system: top management, strategic planning, management review. They set direction, but don’t directly produce the product or service.
Operational (or “core”) processes
The ones that generate value directly for the customer: the sales process, production or service delivery, delivery itself, and after-sales/customer satisfaction. These are the backbone of the map — if these aren’t clear, the map isn’t useful.
Support processes
The ones that sustain the others without generating direct value for the customer: human resources, purchasing, maintenance, IT. They’re necessary, but shouldn’t be confused with operational processes or placed at the center of the map.
Consultant’s tip: if your map puts every process on the same level, without distinguishing strategic, operational, and support, what you actually have is a list, not a map. The hierarchy is what makes the map communicate something.
How to build an ISO 9001 process map step by step
1. List every real process in your organization — not the ones a generic manual says “should” exist, but the ones that actually happen day to day.
2. Classify them into the three types: strategic, operational, and support.
3. Map the inputs and outputs of each one. What each process needs to start (information, materials, a request) and what it delivers when finished (to whom, in what form).
4. Mark the interactions between processes. Where the output of one process is the input of another — this is the part clause 4.4 explicitly requires, and the one most often left out.
5. Validate with each process owner. Quality draws the map, but the person who runs the process every day confirms it. If the process owner doesn’t recognize their own workflow in the map, something is off.
6. Document it as a controlled document. Version, date, approver, and distribution channel — same as any other document in the system.
Example of an ISO 9001 process map
For a typical manufacturing or service company, a process map usually looks like this:
- Input: customer requirements and needs (via sales, a bid, or a direct request).
- Operational processes in sequence: sales process → production or service planning → production/delivery → after-sales and satisfaction measurement.
- Support processes feeding in parallel: purchasing (secures inputs for production), human resources (ensures competent staff), maintenance (ensures equipment availability), IT (ensures the systems that support everything above).
- Strategic processes above: strategic planning and management review, which receive information from all of the above (indicators, nonconformities, audit results) and adjust direction accordingly.
The exact detail changes by industry, but the logic — input, transformation, output, with support processes feeding in and strategic processes overseeing — is the same across sectors.
Common mistakes when mapping processes
- Building it once and never touching it again. A process map that doesn’t reflect an operational change from two years ago isn’t useful evidence anymore — it’s a historical artifact.
- Confusing it with an org chart. The map shows workflow between processes, not the chain of command between people. They’re different documents with different purposes.
- Over-detailing it. A map that tries to show every individual step of every process turns into a 40-box flowchart nobody reads. The process map is high-level; step-by-step detail belongs in each process’s procedures.
- Only quality knows it exists. If the operational process owner doesn’t know the map exists, or doesn’t recognize it as their own work, the document isn’t doing its job.
Frequently asked questions
Is a process map mandatory under ISO 9001?
Yes. It’s a direct output of clause 4.4: the organization must determine its processes, their inputs/outputs, and their interaction, and the map is the most common way to document and communicate that information.
What’s the difference between a process map and a flowchart?
A process map shows the relationship between complete processes, at a macro level. A flowchart details the individual steps within a single process. They’re complementary, not interchangeable.
How often should a process map be updated?
The standard sets no fixed frequency. Update it when the real operation changes: a new process, a merger, a change in the scope of the quality management system.
Does a process map made in PowerPoint or a simple diagramming tool count?
Yes, as long as it’s controlled as a document — with version and approval. The standard doesn’t require a specific tool; it requires the content to be accurate and current.
Should the process map include external suppliers?
When a process critically depends on an external supplier — for example, an outsourced process — it’s worth showing it as an external input on the map, so it’s clear where the system depends on a third party.
