ISO 9001 process mapping
How to move from a list of processes to a managed system — with owners, interactions, risks, controls, and measures that make the process approach real.
The process approach is central to ISO 9001, but many organizations stop at a diagram on the wall. Effective process mapping produces a managed system: an inventory of processes with owners, defined inputs and outputs, understood interactions, identified risks and controls, and measures that reveal performance. This guide walks through that progression.
- Your process maps exist but are not used to manage
- Hand-offs between processes cause recurring problems
- Processes lack clear owners or measures
- You want the process approach to drive performance
Process architecture and inventory
Start with a top-level map of your processes — management, core, and support — then inventory them consistently.
- Group processes into management, core, and support
- Maintain a consistent inventory with a clear naming convention
- Show how processes connect at a high level
Inputs, outputs, and interactions
For each process, define what goes in, what comes out, and where it hands off to others. Interactions are where value and risk concentrate.
- Define inputs, outputs, and the customer of each process
- Map hand-offs and dependencies between processes
- Clarify responsibilities at each interaction
Risks, controls, and owners
Attach risk-based thinking to each process: what could go wrong, what controls exist, and who owns the outcome.
- Identify key risks for each core process
- Define the controls that manage those risks
- Assign a single accountable owner per process
From maps to performance management
Add measures and review to turn a static map into a managed process. This is what makes mapping worthwhile.
- Attach measures to each critical process
- Review process performance on a cadence
- Drive improvement where measures reveal weakness
A process card, at a glance
A simple, repeatable structure for documenting each core process.
Purpose & owner
Why the process exists and who is accountable for its performance.
Inputs & outputs
What triggers the process and what it delivers, and to whom.
Risks & controls
Key risks and the controls that manage them.
Measures
The one or two KPIs that show whether the process performs.
- Drawing maps that are never used to manage performance
- Ignoring interactions where most problems actually occur
- Processes without a single accountable owner
- Mapping every activity in exhaustive detail regardless of risk
Processes connected to measures and review
Cogliva helps you capture processes, owners, risks, and measures in one connected system, so the process approach becomes a way of managing performance rather than a diagram. It supports process management; it does not certify your system.
Keep exploring
Related guides
Product & method
Frequently asked questions
Does ISO 9001 require process maps?
ISO 9001 requires a process approach and understanding of process interactions, but it does not mandate a specific mapping format. Maps are a practical way to meet the intent, provided they are used to manage, not just to display.
How detailed should process maps be?
Detailed enough to manage risk and ensure consistency, no more. High-risk processes justify more detail; low-risk activities may need only a light description. Let risk guide the depth.
What makes process mapping effective?
Clear ownership, defined interactions, identified risks and controls, and measures that are reviewed. A map that drives decisions is effective; a map that only decorates a wall is not.
Turn process maps into performance
Add owners, risks, and measures and the process approach starts driving results.