How to Create a QMS Process Map in 7 Steps

Last Updated: November 2, 2026

Table of Contents

• What a QMS Process Map Is and Why It Matters
• How Process Maps Support Your Quality Management System
• Step 1: Choose Which Process to Map
• Step 2: Define Scope, Boundaries and Process Owners
• Step 3: Document Steps, Decision Points and Interactions
  • Use a consistent symbol set
  • Use swimlanes to show who does what
  • Capture decision points properly
  • Record controls, risks and records at each step
  • Keep the first draft simple
• Worked Example: A Quality Management System Process Map and SIPOC Diagram
  • Step 1: Define the scope and boundaries
  • Step 2: Identify roles and handoffs
  • Step 3: Map the steps, decisions and controls
  • Step 4: Summarise with a SIPOC
  • Step 5: Link the map to ISO 9001
  • Step 6: Add measures and review points
  • Step 7: Version control and approval
• Next Steps: Keeping Your Process Map Current and Useful
• Frequently Asked Questions

What a QMS Process Map Is and Why It Matters

A QMS process map is a visual diagram that shows how work moves through your quality management system, from the first input to the final output.

Many organisations find that much of their process knowledge sits in people's heads.

For ISO 9001, a process map is a practical way to show the processes your organisation has identified and how they interact.

Watch out: A map that looks neat but does not match what people really do is worse than no map.

How Process Maps Support Your Quality Management System

A quality management system works as a set of connected processes. A process map makes those connections visible.

Process maps also support the wider documentation structure. Your policy sets direction, your procedures explain how key processes run, and your work instructions give detail for specific tasks.

Maps help during internal audits and management reviews too. They give auditors and leaders a quick way to see how a process is designed, rather than reading through pages of text.

Step 1: Choose Which Process to Map

Start with one process rather than the whole system. Choose a process that is important, frequently used or causing problems. Common starting points include:

• Customer enquiry to quote
• Order receipt to delivery
• Purchasing and supplier approval

Pick a process with a clear start and end point. A small, well-defined process is easier to map accurately and gives you a working model to repeat for others.

Step 2: Define Scope, Boundaries and Process Owners

Before drawing anything, agree on the scope. Write down:

• Start point: the trigger that begins the process, such as a customer order
• End point: the result that closes it, such as delivery and invoicing
• Boundaries: what is in and out of scope

Involve the people who do the work. They know the real steps, including the workarounds. A process owner should review the final map and confirm it reflects how the process runs. For general implementation guidance to place the map within your wider system, start there.

Step 3: Document Steps, Decision Points and Interactions

Now map the actual steps in order. Gather information by watching the process, talking to the people who do the work, and reviewing existing records such as job cards, inspection sheets, purchase orders and email trails. Do not map the process as you think it should run, map it as it actually runs, then improve it afterwards.

For each step, capture the following:

• The action taken, described with a verb (for example, "inspect incoming steel" rather than "inspection")
• Who performs it, by role rather than by name, so the map survives staff changes
• The inputs needed and the outputs produced

Use a consistent symbol set

A small, standard set of flowchart symbols keeps maps readable and lets new staff interpret them without training. A workable key is:

You do not need a complex notation to satisfy ISO 9001. The standard does not prescribe a diagram type, so choose a format your team can read. Simple flowcharts, swimlane diagrams and SIPOC tables all work, and many organisations use more than one for different audiences.

Use swimlanes to show who does what

A swimlane diagram places each role or department in its own horizontal or vertical lane, and the steps sit in the lane of whoever performs them. This makes handoffs visible, which is where most delays and errors occur. For a construction example, lanes might be Site Supervisor, Quality Manager, Subcontractor and Client Representative. When an arrow crosses from one lane to another, that is a handoff, note what triggers it and what the receiving party needs to proceed.

Capture decision points properly

Every diamond should ask a clear question with a yes/no or defined set of outcomes. Avoid vague decisions such as "check quality" without stating the criteria. Write the decision as "Does the weld pass visual inspection against the ITP acceptance criteria?" and label the outgoing arrows "Yes, proceed" and "No, raise nonconformance". This is where process maps earn their keep, because unclear decision criteria are a common source of inconsistent outcomes.

Record controls, risks and records at each step

ISO 9001 expects you to determine the risks and opportunities relevant to your processes and to apply controls.

Get Your Free ISO Starter Pack →

Watch out: A common mistake is to draw a map so detailed that no one reads it.

Keep the first draft simple

Draw the high-level flow first, confirm it with the process owner and the people who do the work, then add decision points, controls and records in a second pass. This staged approach reduces rework and keeps the people involved engaged rather than overwhelmed.

Worked Example: A Quality Management System Process Map and SIPOC Diagram

Most guides describe process mapping in the abstract. This section walks through a complete example so you can see how scope, roles, decisions, controls, records and ISO 9001 linkages fit together. The example below is a generic, illustrative small manufacturer mapping its nonconforming product handling process, a common starting point because it touches production, quality and customer communication.

Step 1: Define the scope and boundaries

• Start point: A product fails an inspection check or is identified as suspect during production or at final inspection.
• End point: The product is dispositioned (released, reworked, accepted as-is, or scrapped) and the record is closed.
• In scope: Identification, segregation, evaluation, disposition, re-inspection, and recording.

Step 2: Identify roles and handoffs

Roles involved: Inspector (Production), Quality Manager, Production Supervisor, Stores, and, where a concession is sought, the Customer. Handoffs occur between Inspector and Quality Manager (for disposition), Quality Manager and Production (for rework), and Quality Manager and Stores (for scrap).

Step 3: Map the steps, decisions and controls

The flow runs as follows, with controls and records noted at each step:

1. Identify and tag, Inspector tags the item and records the defect on a nonconformance report (NCR). Control: tag colour and quarantine area. Record: NCR.
2. Segregate, Stores moves the item to the quarantine area. Control: physical segregation and labelled hold area. Record: location entry in the NCR.
3. Evaluate, Quality Manager reviews the defect against specifications and customer requirements. Control: specification and contract review. Record: evaluation notes on the NCR.
4. Decide disposition, Diamond: "Can the item be reworked to meet specification?"
   • Yes → Production reworks and Inspector re-inspects. Record: rework record and re-inspection result.
   • No → Diamond: "Is a concession or use-as-is acceptable, and does the customer or contract permit it?"
     • Yes → Customer or authorised approver signs off. Record: concession approval.
     • No → Scrap. Record: scrap record and loss entry.
5. Close the record, Quality Manager confirms disposition is complete and closes the NCR. Control: sign-off. Record: closed NCR.
6. Handoff to corrective action, If the defect is recurring or significant, raise a corrective action request. Record: CAR reference linked to the NCR.

Step 4: Summarise with a SIPOC

A SIPOC diagram gives a one-page overview for management and auditors. The same process looks like this:

Step 5: Link the map to ISO 9001

This is where a QMS-specific map differs from a generic flowchart. The map should visibly support the clauses it relates to:

• Clause 8.7 (Control of nonconforming outputs), the disposition options and records on the map are the evidence that nonconforming outputs are controlled.
• Clause 8.5.1 (Control of production and service provision), the rework and re-inspection steps show controlled conditions.
• Clause 10.2 (Nonconformity and corrective action), the handoff to corrective action shows the link between the NCR and root cause analysis.

Note that ISO 9001 does not require a specific diagram. The map is a tool you choose to use; the requirement is that the process is determined, controlled and produces the records the standard expects.

Step 6: Add measures and review points

A map that stops at the diagram does not tell you whether the process works. Add a small set of measures and a review point:

• Measures: number of NCRs raised, average time from identification to disposition, proportion of NCRs closed within target, number of concessions granted, and repeat defects linked to corrective action.
• Review point: the Quality Manager reviews NCR trends at the monthly management review, and the process owner reviews the map annually or whenever the process changes.

Step 7: Version control and approval

Record the map's version number, approval date, approver and next review date.

Watch out: A frequent mistake is to map the process in isolation and never show how it connects to purchasing, production and corrective action.

If you want a reusable starting point, a process map template, symbol key and SIPOC worksheet can save time and keep your maps consistent across the system. Explore practical ISO documentation resources to see how templates and registers fit together. If you are just starting out, the Free ISO Starter Pack is a no-cost way to get foundational documents in place before you map processes in detail.

Next Steps: Keeping Your Process Map Current and Useful

A process map is only useful while it matches reality. Set a review schedule, and update the map whenever the process changes.

Store the map where your team can find it easily. Shared digital storage with version control helps prevent people using outdated copies.

Measure whether the map helps. Look for fewer errors, faster handoffs or fewer repeated questions from staff.

For a complete approach to managing your documentation, explore practical ISO documentation resources. If you are preparing for an assessment, an audit preparation checklist can help you confirm your mapped processes are ready. Organisations that want structured guidance through the full certification pathway can look at IntegriSURE Guided, which is designed for teams building their own system with support along the way.

Add integrisure.com.au as a preferred source on Google →