Skip to main content
Services
Audit & Certification
ISO Gap AnalysisFree ISO 9001 gap analysisInternal AuditAudit PreparationAfter the AuditClose Nonconformities
ISO Standards
ISO 9001 Quality ManagementISO 9001:2026 TransitionISO 14001 Environmental ManagementISO 45001 Occupational Health & SafetyISO 27001 Information SecurityISO 42001 AI ManagementISO 13485 Medical Devices
Support & Training
Management System MaintenanceExternal QMRQM TrainingReview of AI-Generated QMS
Industries
All IndustriesMechanical Engineering & ProductionAutomotive SuppliersLaser Optics, Photonics & SemiconductorsIndustrial Service ProvidersMedical DevicesIT, SaaS & AI
Funding
Resources
Guides and articlesFAQ
Free toolsAboutContactSend emailCall now
EN
Book an initial consultation
Processes, Metrics & Business Control Updated: 29 October 2026

ISO 9001 Process Landscape: How to Identify and Document Your Core Processes

Build an ISO 9001 process landscape for your SME by identifying core, management and support processes and documenting them clearly.

A process landscape shows how your company turns customer requirements into products or services. It makes the main processes, their sequence and their connections visible. A single clear page is often a useful starting point. What matters is that your team recognises the way the business actually works.

This guide explains how to identify core processes, add management and support processes, and choose a useful level of documentation. It complements our ISO 9001 implementation guide for SMEs.

Aquarelle watercolor illustration of two ink-stroke figures at a whiteboard with three rectangular boxes connected by arrows, representing a process mapping workshop
Identifying core processes is best done as a team workshop — starting from the customer and tracing value through the organization.

What Does ISO 9001:2015 Actually Require? (Clause 4.4)

Clause 4.4 is titled "Quality Management System and Its Processes." Among all the clauses in the standard, it is one of the most consequential — and most frequently misunderstood.

Clause 4.4.1 — What You Must Establish

The standard requires that your organization must:
  • Determine the processes needed for the QMS and their application throughout the organization
  • Define the inputs and outputs of each process
  • Determine the sequence and interaction of these processes
  • Determine the criteria and methods needed to ensure effective operation and control of these processes
  • Determine the resources needed for these processes and ensure their availability
  • Assign responsibilities and authorities for each process
  • Address the risks and opportunities associated with each process (see our guide to ISO 9001 risks and opportunities)
  • Evaluate and improve your processes

Clause 4.4.2 — Documented Information

The standard requires that you maintain documented information to support the operation of your processes and retain documented information to have confidence that processes are being carried out as planned.
Practical note: Notice what the standard does NOT say. It does not require flowcharts. It does not require a specific format. It does not require dedicated process documentation software. What it requires is that you can demonstrate — to yourself and to an auditor — that you understand your processes, control them, and improve them. How you do that is your decision.
For deeper context on how Clause 4.4 sits within the broader planning framework, see our guide to ISO 9001:2015 Clause 4.

What Is a Process Landscape?

A process landscape (also called a process map or process house) is a high-level visualization of all processes in your organization, grouped into categories, showing how they relate to each other and how value flows from customer requirements to customer satisfaction. At the landscape level, you are working at the strategic overview — the thirty-thousand-foot view that shows structure before detail. A process landscape typically shows:
  • The three process categories (management, core, support)
  • The process names at the right level of abstraction
  • The overall flow direction — inputs from customers and interested parties on the left, outputs (delivered value) on the right
  • Key interactions between processes
The process landscape is the structural foundation of your QMS. Every other element — objectives, procedures, audit plans, management reviews — connects back to it.
Simplified Sternberg Consulting process landscape, from customer needs to ongoing support. Enlarge the example.
Simplified Sternberg Consulting process landscape, from customer needs to ongoing support. Enlarge the example.

What could your process landscape look like? Use our free generator for an initial AI draft with relevant processes and your logo, delivered by email.

How Complex Does Your Process Landscape Need to Be?

A one-page overview is often a helpful starting point. The example shows how a consultancy can structure its work from the first enquiry to ongoing support. Adapt the processes to your business. Clause 4.4 also concerns control, responsibilities, interactions and evidence of effectiveness; a diagram alone does not demonstrate these. As your business grows and your operations become more complex, a more detailed landscape with sub-processes, process interactions, and performance indicators per process becomes genuinely useful — not for the auditor, but for your own operational clarity. This is when a general one-page overview starts to struggle: you have too many processes to track, too many owners to coordinate, and too many interfaces to manage manually. At that level of complexity, QMS software tools become a practical option. Products like vissibl.ai are built specifically for this: they let you map and maintain your process landscape digitally, assign process owners, track KPIs per process, and connect your risks, objectives, and audits directly to the relevant processes. For an SME starting out, this is not necessary. For a growing organization with 50 or more employees and a maturing QMS, it can eliminate significant administrative overhead. The rule of thumb: start simple, stay simple as long as it works. Add complexity only when your operations demand it, not before.

Three Useful Process Groups for Your Overview

ISO 9001 does not prescribe these three groups. Management, core and support processes are a useful way to organise the overview. Assign processes according to your business model: purchasing, for example, may be a core or support process.
Table 1: ISO 9001 Process Landscape: How to Identify and Document Your Core Processes
Category Description SME Examples
Management Processes Processes that direct and coordinate the organization. They set direction, allocate resources, and ensure the QMS functions and improves. Strategic planning, quality policy and objectives, management review, internal audits, risk management
Core Processes (Value-Adding) Processes that directly create and deliver your product or service to the customer. These are the processes the customer pays for. Sales / order intake, engineering / design, production / service delivery, shipping / installation, customer service
Support Processes Processes that enable the core processes by providing resources, infrastructure, and competence. They do not directly create customer value but are necessary for the core to function. HR / training, purchasing, IT, maintenance, infrastructure management, document and records control
Practical note: The core processes vary significantly by industry. A manufacturing SME's core processes look very different from a professional services firm's. Start from the customer and work backwards — the right list is the one that accurately reflects how your organization creates and delivers value.
Aquarelle watercolor illustration of three stacked horizontal bands in coral, sky blue, and mint green representing the three-tier ISO 9001 process landscape: management processes, core processes, and support processes
Management, core and support processes are useful organising groups. The specific process structure depends on the business.

How to Identify Your Core Processes: Step by Step

The following approach works for SMEs with no prior process documentation. It typically takes one to two workshop sessions of ninety minutes each with the leadership team.

Step 1: Start With the Customer

Ask: What does the customer come to us for? What do they receive when we are done? For a manufacturing SME the answer is a physical product that meets specifications and is delivered on time. For a consulting firm it is advice, a report, or an implemented solution. For a medical device company it is a compliant, safe device. Write the customer requirement on the left side of a blank page. Write the delivered output on the right side. Everything in between is a candidate for your core process map.

Step 2: Trace the Value Stream

Walk through the journey of a typical order from first customer contact to final delivery and payment. At each handover point — where work passes from one team or function to another — you have a process boundary. A typical SME producing custom components might identify: Sales → Order Review → Engineering → Production Planning → Production → Quality Control → Shipping → Invoicing. Each of those transitions is a process. The handover point is where you define inputs and outputs.

Step 3: Add Management Processes

Ask: What processes ensure we have direction, we review our performance, and we improve? For most SMEs, this means at minimum:
  • Strategic planning and management review (Clause 9.3)
  • Internal audit program (Clause 9.2)
  • Corrective action and continual improvement (Clause 10)

Step 4: Add Support Processes

Ask: What must be in place for our core processes to function? Typical SME answers: HR, purchasing/supplier management, IT/infrastructure, document control.

Step 5: Name Your Processes at the Right Level

Resist the temptation to go too detailed too early. Around 8 to 15 processes can be a useful starting point for an SME; there is no prescribed number. With a long list, check which entries are tasks or subprocesses. A process operates over time, has defined inputs and outputs, and can be owned by one responsible person. A task is a step within a process.
Tip: For each entry, ask what triggers it, what output it creates and who uses that output. Duration alone does not determine whether something is a process or an individual task.
Aquarelle watercolor illustration of the turtle diagram structure: a central oval with four directional arrows extending outward representing inputs, outputs, controls, and resources for ISO 9001 process documentation
The turtle diagram: one central process with four arms for inputs, outputs, controls, and resources — the simplest way to document what Clause 4.4.1 requires.

The Turtle Diagram: Documenting Individual Processes

Once the overview is in place, decide which supporting descriptions your team needs to operate and control its processes. A turtle diagram is one compact option for recording important process information:
Table 2: ISO 9001 Process Landscape: How to Identify and Document Your Core Processes
Element Question It Answers Example (Order Processing)
Process Name What process is this? Order Processing
Process Owner Who is accountable? Head of Sales
Inputs What triggers the process? What information or material enters? Customer inquiry or purchase order, product specification
Outputs What does the process produce? What goes to the next process or customer? Confirmed order with delivery date, production order
Controls / Requirements What rules govern this process? ISO 9001 Clause 8.2, customer contract terms, pricing policy
Resources What equipment, tools, systems, or infrastructure are needed? ERP system, CRM, trained sales staff
Competence / Who Who performs the process, and what competence is required? Sales team with product knowledge, authority to commit delivery dates
Performance Indicators How do you know the process is working? What do you measure? Order entry error rate (target ≤0.5%), average quote response time (target ≤24h)
Risks and Opportunities What can go wrong, and what opportunities exist? Risk: customer spec misunderstood; Opportunity: upsell at order review
Turtle diagrams can support your process documentation. The necessary detail depends on complexity, risks and the competence of those involved. You also need appropriate records of actual implementation. Word or Excel may be sufficient tools. For guidance on the work instruction level — one step below the process level — see our free ISO 9001 work instruction template.

The Process Interaction Matrix

ISO 9001 Clause 4.4.1 requires you to determine the sequence and interaction of your processes. The process interaction matrix is the most efficient way to demonstrate this. A simple grid — processes listed on both axes — uses a checkmark or arrow in each cell to indicate that one process passes an output to another. For a 10-process SME, this matrix fits on half a page and immediately makes visible which processes are most interconnected, and therefore where interface problems are most likely to occur.
Practical note: You do not need software to create a process interaction matrix. A table in Excel or Word with your processes on both axes and checkmarks at intersections is entirely sufficient. For critical handovers, add what information or output is passed on. This makes the process connections meaningful.
Aquarelle watercolor illustration of a hand-drawn 5x5 grid matrix with sky blue header row and column and scattered checkmarks showing which ISO 9001 processes interact with each other
A process interaction matrix on one page shows how your processes connect — and where the critical handover points are.

How Much Documentation Does ISO 9001 Actually Require?

This is the question that causes the most confusion. The 2015 revision of ISO 9001 deliberately moved away from mandatory procedures. Here is what is actually required.

Mandatory Documented Information

The standard explicitly requires documented information for:
  • Scope of the QMS (Clause 4.3)
  • Quality policy (Clause 5.2)
  • Quality objectives (Clause 6.2)
  • Competence of personnel (Clause 7.2)
  • Monitoring and measurement results (Clause 9.1)
  • Internal audit program and results (Clause 9.2)
  • Management review outputs (Clause 9.3)
  • Nonconformities and corrective actions (Clause 10.2)
And for the processes themselves, the standard uses careful language: you must maintain documented information to support the operation of your processes and retain documented information to have confidence that processes are being carried out as planned.

A Practical Starting Point for Process Documentation

For your process landscape, this translates to:
  • A process landscape diagram or list showing all processes (1 page)
  • A turtle diagram or equivalent for each key process (1 page per process)
  • A process interaction matrix showing how processes connect (1 page)
This combination is one possible starting point. Format and detail depend on your activities and risks. Audit readiness also requires implemented, effective processes and suitable evidence.
Tip: Do not confuse process documentation with work instructions. A turtle diagram describes the what, who, and how of a process at the management level. A work instruction tells an operator exactly how to perform a specific task. Work instructions are useful where they are needed for safe, consistent execution, for example for critical or complex activities.
For practical guidance on what documents and records your QMS needs to control, and how to manage them without bureaucratic overhead, see our guide to ISO 9001 document control.

Common Mistakes SMEs Make With Process Landscapes

After working through process landscapes with dozens of SMEs, the same failure patterns appear consistently.

Mistake 1: Confusing Organizational Structure With Process Structure

A process landscape is not an org chart. Processes cut across departmental boundaries. Order processing might involve Sales, Engineering, and Production. Drawing your process map along departmental lines means missing the interfaces where most quality problems actually occur.

Mistake 2: Going Too Detailed Too Early

The process landscape is the overview. Detail lives in turtle diagrams and work instructions. If the overview has many entries, check which tasks belong within an overarching process. Keep the overview understandable.

Mistake 3: Processes Without Owners

Assign clear responsibilities and authorities to each process. You can identify a role or a named person. If you use a role, make clear who currently holds it and what decisions they are authorised to make.

Mistake 4: Documentation That Nobody Uses

Process documentation that exists only for the audit creates a false sense of control while providing none of the operational benefit. Write documentation at the level of detail your team actually needs to perform the process correctly. If people ignore it in practice, the documentation is either too detailed (a procedure manual nobody reads) or not detailed enough (too abstract to be useful).

Mistake 5: Never Updating the Process Landscape

Organizations change. New services are added. Processes are restructured. Your process landscape should be a living document, reviewed at every management review. An outdated map can cause confusion. Whether it constitutes an audit finding, and its severity, depends on the circumstances. For a full picture of what goes wrong during implementation, see our guide to common pitfalls in ISO 9001 implementation.

Connecting the Process Landscape to the Rest of Your QMS

The process landscape is the structural backbone that connects to every other element of your QMS:
  • Quality objectives are set per process — or for the organization as a whole, but monitored at process level
  • Risks and opportunities are identified per process (see our guide to risk-based thinking in ISO 9001)
  • Internal audits audit specific processes according to the audit program (see our guide to internal audits according to ISO 9001)
  • Competence requirements are defined per process (who needs what skills to run this process) — covered in Clause 7.2, the topic of the next article in this series
  • Management reviews evaluate process performance using the KPIs defined in your turtle diagrams
If you have completed the previous steps in this series — quality policy, quality objectives, risks and opportunities — you will find that the process landscape makes those elements more concrete. Objectives gain clear ownership (which process does this objective belong to?). Risks become process-specific rather than abstract. The QMS stops feeling like a collection of documents and starts functioning as a connected system.

Source: ISO: The process approach in ISO 9001:2015. The diagram formats described are practical aids.

How We Help SMEs Build Their Process Landscape

At Sternberg Consulting, we help you structure actual workflows, clarify responsibilities and handovers, and choose appropriate documentation. We also identify where AI can support analysis and everyday process work. Explore our ISO 9001 consulting.

Start with the free ISO 9001 readiness check to identify open foundations, or create an initial overview with the process landscape generator.

FAQ

Frequently asked questions

Do we need to flowchart every process?

No. ISO 9001 does not require flowcharts. A turtle diagram, a table, or even a well-structured text description that covers inputs, outputs, controls, resources, competence, and performance indicators can be suitable if it covers the necessary content and process controls. Use flowcharts where they genuinely help — typically for complex branching processes where sequence matters — but do not create them for every process out of obligation.

Can external or outsourced processes be part of our process landscape?

Yes, and they often must be. If you outsource a critical process — logistics, calibration, testing — that outsourced process remains within your QMS scope and must be controlled. It should appear in your process landscape with a clear label that it is externally performed, and your turtle diagram should specify how you control and monitor it.

How often should we update our process landscape?

At minimum, review it at every management review. Update it immediately whenever a significant organizational change occurs — new product lines, restructuring, acquisition of new processes. Do not wait for the next annual review if your business has changed materially.

What is the difference between a process and a procedure?

A process is what happens — the set of activities that transforms inputs into outputs. A procedure describes how it happens — the specific steps, in sequence, with the rules and decisions involved. ISO 9001 requires you to define and control your processes; it does not require written procedures for all of them. Where a process is simple and the people performing it are highly competent, the process can be controlled without a written procedure.

How detailed should turtle diagrams be?

Detailed enough that a new employee with the right baseline competence could understand the process, and brief enough that your team will actually read and use it. A turtle diagram that fills more than one A4 page is generally too detailed. Aim for a half-page structured template per process — everything the standard requires, nothing more.

Do support processes need turtle diagrams too?

Yes, for the key ones. Not every support activity needs a full turtle diagram, but processes critical to QMS function — purchasing, document control, competence management — should have at minimum a basic turtle diagram. For routine administrative tasks, a simpler description is sufficient.

How many processes should our process landscape have?

ISO 9001 does not prescribe a number. Around 8 to 15 processes may offer an initial reference point. What matters is that the overview clearly represents your value creation and important interfaces. A small business may need fewer processes; a complex business may need more.

The Next Step: Competence and Training

With your process landscape defined and your processes documented at the right level, you have the operational core of your QMS in place. The next article in this series is ISO 9001 Competence and Awareness: A Practical Guide for SMEs, covering Clause 7.2 and 7.3 — Competence and Awareness: how to identify the competence your processes require, how to demonstrate that your team has it, and how to manage training in a way that satisfies auditors without creating a bureaucratic training records nightmare.
Next step

Let's talk.

Tell me where you stand and what you need.

Within 24 hours you receive a first assessment and a concrete meeting proposal — free and without commitment.

  • ✓Reply within 24 hours
  • ✓Personal assessment of your project
  • ✓Funding eligibility checked on request
Direct contact

By submitting you agree to the processing of your details for answering your enquiry.

Darstellung anpassen

Wählen Sie, wie Sie diese Website lesen möchten.

100 %

Von 100 % bis 200 % anpassen

Ihre Auswahl gilt für diesen Browser-Tab. Es werden keine Daten übertragen.