Turtle Diagrams: How to Use Them in Process Audits

What Is a Turtle Diagram?

A turtle diagram is a simple visual tool that maps out all the key elements of a process in one structured layout. The name comes from the shape: a central box representing the process itself, with inputs and outputs on either side forming the body, and four additional elements branching off the top and bottom like the legs and head of a turtle.

Those four elements are: the resources needed to run the process, the competence and skills required of the people involved, the methods and procedures used, and the measurements and indicators used to evaluate performance. Together, these six components give you a complete picture of how a process is designed to function.

For auditors, that complete picture is exactly what you need. Rather than jumping straight into records and asking whether procedures exist, a turtle diagram forces you to think about the process as a whole before you start asking questions. It is one of the most practical tools available for process based auditing, and it is underused by many internal auditors who default to checklist driven approaches instead.

Why Process Based Auditing Needs a Structured Framework

ISO 9001, ISO 14001, ISO 45001, and the other major management system standards are built on the process approach. Clause 4.4 of ISO 9001, for example, requires organisations to determine their processes, their sequence and interaction, the inputs and outputs, the criteria for operation, and the resources needed. That is essentially a turtle diagram written in clause language.

When you audit a process without a structured framework, you tend to drift. You follow the documents you are given, you ask about the things you already know, and you miss the gaps that sit between the elements. I have seen internal auditors spend an hour reviewing training records and completely miss the fact that the equipment used in the process had not been calibrated in two years. A turtle diagram would have flagged that immediately because calibrated equipment falls under resources.

The turtle diagram gives you a map. It tells you what to look for in each zone of the process before you walk into the room. That preparation is what separates a thorough process audit from a document review with a site visit attached.

If you want to understand how process based auditing differs from clause based auditing more broadly, the article on process based vs clause based auditing covers that distinction in detail.

The Six Elements of a Turtle Diagram Explained

Inputs

Inputs are what enters the process to trigger it. This might be a customer order, a request from another department, raw materials, data from a previous process, or a regulatory requirement. As an auditor, you want to confirm that inputs are defined, that they arrive in a usable condition, and that there is a mechanism for handling inputs that do not meet requirements.

Common audit questions here include: How does the process know when to start? What form do inputs take? What happens when an input is incomplete or incorrect?

Outputs

Outputs are what the process produces. These might be physical products, completed services, reports, records, or inputs to the next process in the sequence. The key audit question is whether the outputs consistently meet the criteria that were set for them, and what happens when they do not.

Outputs also include unintended outputs. In an environmental context, waste, emissions, and effluent are outputs of a process even if they are not the primary product. Auditors working under ISO 14001 should always ask about what comes out of a process beyond the intended result.

Resources (With What?)

Resources cover the equipment, tools, infrastructure, software, and materials used to run the process. When auditing this element, you are looking at whether the right resources are available, whether they are maintained, and whether there are controls to ensure they remain fit for purpose.

Calibration records, maintenance schedules, equipment registers, and software validation records all sit under this element. This is where many auditors find nonconformities they were not expecting, because resource management issues are often invisible until someone looks specifically for them.

Competence (With Whom?)

This element covers the people who operate the process, their qualifications, training, and experience. It links directly to Clause 7.2 of most ISO standards. When auditing competence, you are not just checking that training records exist. You are verifying that the training was relevant, that it was evaluated for effectiveness, and that the people doing the work are actually capable of doing it to the required standard.

Ask to speak with the people who perform the process, not just the manager who oversees it. Interview the operator. Ask them what they do when something goes wrong. Their answer will tell you more about competence than any training record.

Methods (How?)

Methods cover the procedures, work instructions, standards, and techniques used to perform the process. This is where you look at documented information requirements. Are there procedures in place? Are they current? Are they accessible to the people who need them? Are they actually being followed?

The gap between what the procedure says and what actually happens on the floor is one of the most common sources of nonconformities in any management system audit. The turtle diagram reminds you to check both the document and the practice.

Measurements and Indicators (How Well?)

This element covers the performance data collected on the process. Key performance indicators, inspection results, error rates, cycle times, customer complaints, audit findings, and environmental monitoring data all belong here. The audit question is whether the organisation is measuring the right things, whether the data is being collected consistently, and whether it is being used to drive improvement.

A process with no meaningful performance data is a process that cannot be managed. That is worth noting as a finding even if the process appears to be functioning well on the day of the audit.

How to Build a Turtle Diagram Before an Audit

You do not need special software to build a turtle diagram. A simple table or hand drawn template works perfectly well. Before the audit, identify the process you are going to audit and populate each element of the diagram with what you know or expect to find.

Start with the process name in the centre. Then work through each element systematically. For a procurement process, the inputs might be approved supplier lists and purchase requisitions. The outputs might be purchase orders and received goods records. Resources might include the procurement system, approved supplier database, and budget authorities. Competence might cover the qualifications and delegated authority of purchasing officers. Methods might include the purchasing procedure and supplier evaluation criteria. Measurements might include on time delivery rates, supplier performance scores, and nonconforming goods rates.

Once you have populated the diagram, you can use it to generate your audit questions. Each element becomes a line of inquiry. You are not just asking whether a procedure exists. You are asking whether every element of the process is defined, resourced, performed, and measured effectively.

The article on process mapping for auditors covers related preparation techniques that complement the turtle diagram approach.

Using a Turtle Diagram During the Audit

Bring your populated turtle diagram into the audit room. Use it as a reference, not a script. The diagram tells you what territory to cover. Your questions and observations fill in the detail.

Start by confirming your understanding of the process with the auditee. Ask them to walk you through how the process works from start to finish. As they talk, mentally check their description against your diagram. Are they describing inputs and outputs that match what you expected? Are there elements they are not mentioning?

Then move through each element systematically. You do not have to follow the turtle diagram in order. Follow the conversation and the evidence trail. But keep coming back to the diagram to make sure you have covered all six elements before you close out the process.

When you find a gap, the turtle diagram helps you articulate it clearly. Instead of saying “there is no procedure,” you can say “the methods element of this process is not fully defined because the work instruction referenced in the procedure has not been updated since 2021 and does not reflect the current equipment configuration.” That is a specific, evidence based finding that the auditee can act on.

Turtle Diagrams in Practice: A Real World Example

Consider an audit of a welding process in a manufacturing environment. The turtle diagram for this process might look like this:

• Inputs: Approved drawings, material certificates, weld procedure specifications, job cards
• Outputs: Completed weld assemblies, weld inspection records, nonconformance reports where applicable
• Resources: Welding machines, filler materials, personal protective equipment, calibrated measuring equipment
• Competence: Certified welders with current qualification records, weld inspector competence
• Methods: Weld procedure specifications, inspection and test plans, hold point sign off requirements
• Measurements: Visual inspection results, dimensional checks, destructive and non destructive test results, rework rates

When you walk into the audit with this diagram prepared, you know exactly what to look for. You ask to see the weld procedure specifications and check they are current. You verify welder qualification records and check expiry dates. You look at the calibration status of the measuring equipment. You check that hold points are being signed off before work progresses. You review inspection records to see whether defect rates are being tracked and whether trends are being analysed.

In one real audit I conducted using this approach, the turtle diagram immediately flagged that the welding machines had no maintenance records. The process was running, the welds were passing inspection, and the records looked fine. But the resource element of the diagram had a blank where maintenance history should have been. That became a nonconformity under Clause 7.1.3 of ISO 9001. Without the turtle diagram prompting me to look at resources specifically, I might have missed it entirely.

Common Mistakes When Using Turtle Diagrams

Treating the Diagram as a Checklist

The turtle diagram is a thinking tool, not a tick box exercise. If you use it mechanically, checking elements off one by one without following the evidence, you will miss the connections between elements. A competence gap might only become visible when you look at how the methods element is actually being applied. Stay curious and follow the evidence trail wherever it leads.

Ignoring the Interactions Between Processes

A turtle diagram covers one process. But processes interact. The output of one process is the input to the next. When you finish auditing a process, check that its outputs are actually being received and used correctly by the downstream process. This is where you find systemic issues that individual process audits miss.

Preparing a Generic Diagram

A turtle diagram prepared for “the purchasing process” in general is less useful than one prepared for the specific purchasing process at the specific organisation you are auditing. Use whatever information you have from previous audit reports, the organisation’s procedure documentation, and your pre audit document review to make the diagram as specific as possible before you arrive.

Skipping the Measurements Element

Many auditors focus on inputs, outputs, and methods because those are the most visible elements. Measurements get skipped because they feel abstract. Do not skip them. The measurements element is where you find out whether the organisation actually knows how well the process is performing. A process with no meaningful metrics is a process that cannot be improved, and that is directly relevant to continual improvement requirements across all major ISO standards.

Turtle Diagrams and ISO Clause Connections

One of the most useful aspects of the turtle diagram is that each element maps naturally to specific ISO clauses. This makes it easy to connect process audit findings to the relevant standard requirements when you write your nonconformity reports.

• Inputs and outputs connect to Clause 4.4 (QMS and its processes) and Clause 8.1 (operational planning and control)
• Resources connect to Clause 7.1 (resources), including 7.1.3 (infrastructure) and 7.1.4 (environment for the operation of processes)
• Competence connects to Clause 7.2 (competence)
• Methods connect to Clause 7.5 (documented information) and Clause 8.1 (operational planning and control)
• Measurements connect to Clause 9.1 (monitoring, measurement, analysis and evaluation)

When you write a finding against the measurements element, you cite Clause 9.1.1. When you write a finding against the competence element, you cite Clause 7.2. The turtle diagram does not just help you find nonconformities. It helps you classify and reference them correctly, which makes for a much stronger audit report.

For more on writing findings that hold up to scrutiny, the article on how to write audit findings that stand up to challenge is worth reading alongside this one.

Downloading and Using a Turtle Diagram Template

If you want a ready made template to use in your next process audit, Audit Workshop has published a dedicated turtle diagram template for process audits that you can adapt for any process and any ISO standard. It includes prompts for each element and space to record your audit evidence against each component.

Using a template consistently across your audit programme also makes it easier to compare process audits over time. If the measurements element was weak in last year’s audit and you find the same gap this year, that becomes a pattern finding that warrants escalation at management review.

Building Turtle Diagram Skills Through Training

Understanding the theory of turtle diagrams is straightforward. Using them confidently in a live audit takes practice. You need to be comfortable populating the diagram from limited pre audit information, adapting it as the audit unfolds, and using it to generate probing questions rather than surface level ones.

This is the kind of practical skill that Audit Workshop courses are built around. Whether you are completing an Internal Auditor course for ISO 9001, ISO 14001, or ISO 45001, or working through a Lead Auditor programme, process based auditing techniques including turtle diagrams form a core part of the practical training. The courses are designed by auditors who have conducted hundreds of real certification audits, so the tools you learn are the tools that actually get used in the field, not just in the classroom.

If you are building your auditing skills and want to move from checklist dependence to genuine process understanding, turtle diagrams are one of the most effective tools you can add to your practice.