Skip to content

Independent standards discovery and compliance platform

How we work
Compliance practice

ISO 10013 Audit Evidence Checklist: Build a Record Trail

Use a worked customer complaint to build an audit evidence trail and see how ISO 10013 and ISO 10002 can help organise quality records.

ISO 10013 Audit Evidence Checklist: Build a Record Trail

When a customer complains about a wrong shipment, the strongest evidence often sits in several places: a support ticket, the order system and a warehouse record. A useful audit trail lets a colleague follow the decision across those systems without relying on the person who handled the case. Start with one real workflow and test whether its records tell a complete story.

Disclosure: Some catalogue guides linked here offer an ANSI Webstore purchase option. European Standards may earn a commission on qualifying purchases.

ISO 10013:2021 gives guidance on documented information for a quality management system. ISO 10002:2018 gives guidance on complaints handling. Use the former to think about how records are controlled and the latter to review how the complaint moves from receipt to closure.

Work through one complaint from receipt to closure

Imagine a customer orders item A but receives item B. The support team opens a ticket, a supervisor approves a replacement and the warehouse ships it. To reconstruct the case, start with the ticket ID and trace it to the disputed order, the decision, the replacement dispatch and the communication that closed the complaint.

For each step, capture four things: what happened, who owned the decision, when it happened and where to retrieve the record. If the case triggered a process change, link to the action and any later effectiveness check. A ticket marked “closed” tells you the workflow reached an end state. The linked evidence tells you how and why.

A support ticket, order slip and shipping label illustrate a complaint record trail.
Start with one complaint and follow its ticket, order and shipment references.

Give every record type an owner and a retrieval rule

Use a short register with columns for record type, system of record, owner, access, retention and retrieval key. A replacement approval might live in the order system and use the order ID. A customer message might live in support software and use the ticket ID. Cross-reference those IDs when the systems cannot do it automatically.

Test access with a colleague who has the appropriate role. Can they find the evidence without asking the original handler? For approvals and procedures, can they tell which version applied at the time? Keep customer identifiers out of shared audit examples where they are unnecessary. Use your own retention rules and applicable obligations.

A colleague links approval records and file references at a workstation.
Record where approvals live and how another team member can retrieve them.

Use the record trail in your next internal audit

Pick a routine complaint and one exception, such as an urgent replacement authorised outside normal hours. Compare the written workflow with the decisions in each case. The ISO 19011 internal audit checklist shows how to turn that comparison into a defensible finding. If the workflow uses AI to triage complaints, the AI impact assessment example shows which decisions need their own evidence.

For the source documents, see ISO’s record for documented information and ISO’s record for complaints handling. The linked catalogue guides explain scope and provide purchase options.

Continue reading

Related standards and compliance insights