Prepare a Customer Audit: Checklist for Supplier Requirements
How companies prepare for customer audits in a structured way: clarify requirements, collect evidence, prepare roles and track actions effectively.
A customer audit is best prepared when customer requirements, processes, evidence and contact persons are brought together before the audit date. The decisive factor is not a perfect folder, but a traceable answer to three questions: What did the customer require, how does your company implement those requirements, and which evidence shows that it works in daily operations?
What Is a Customer Audit?
A customer audit is an assessment performed by an existing or potential customer. The customer evaluates whether a supplier, service provider or project partner can reliably meet its requirements. This often involves quality, delivery capability, complaint handling, information security, occupational health and safety, regulatory interfaces or industry-specific requirements.
The difference from a certification audit is important: a certification body audits against a standard such as ISO 9001, ISO 13485 or ISO 27001. A customer also audits against its own expectations, contractual requirements, technical specifications, supplier manuals or project-related risks. An ISO certificate alone is therefore not always sufficient.
Why Customer Audits Are Demanding
Customer audits often feel more difficult than internal audits because they are less standardized. Some customers send a clear checklist, while others arrive with general questions. Several functions are often involved: sales, project management, purchasing, production, development, service, IT, HSE or quality management.
Typical risk points are:
- unclear or outdated customer requirements
- records that exist but cannot be found quickly
- differences between contractual commitments and the lived process
- open complaints, 8D reports or actions without effectiveness review
- employees who work correctly but cannot explain the process clearly in the audit
Preparation in Seven Steps
1. Clarify Audit Scope and Expectations
Before preparation begins, you need a clear audit context. Ask for the audit plan, focus areas, participants, sites, language, preferred evidence format and deadlines. If the customer uses its own checklist or supplier manual, that basis must be available.
2. Transfer Customer Requirements into a Matrix
A simple requirements matrix is often more effective than long continuous text. Record each relevant customer requirement, the affected process, the internal owner and the matching evidence. This makes visible where requirements are still unclear or not supported by records.
3. Collect Critical Evidence by Process
A customer audit rarely checks documents only. Nevertheless, key evidence must be quickly available: contracts, specifications, process descriptions, inspection plans, training records, complaints, action lists, supplier evaluations, approvals, change records and KPIs.
4. Check Interfaces in Particular
Many findings do not arise in one isolated process but at handovers: from sales to project, from development to purchasing, from incoming goods to production, from service to complaint handling or from the internal team to subcontractors. Review these interfaces deliberately.
5. Prepare the Contact Persons
People in the audit do not need to know standards by heart. They should be able to explain what they do, where relevant requirements are documented, which records are created and how they handle deviations. Short mock interviews help more than long training slides.
6. Close Open Points Before the Date
If gaps are known, they should not remain open until the audit. Decide whether an immediate correction is possible or whether a robust action plan is needed. Responsibility, deadline and effectiveness review must be defined.
7. Control Audit Communication
Define one central person to coordinate agenda, documents, room or video meeting, participants and follow-up questions. Especially in customer audits, clear communication prevents contradictory statements or unfinished documents from being shared in an unstructured way.
Checklist: Which Evidence Should Be Ready?
| Review Field | Typical Evidence | Typical Customer Question |
|---|---|---|
| Customer requirements | Contract, specification, supplier manual, requirements matrix | How do you ensure that our requirements are known internally? |
| Quality and processes | Process map, work instructions, inspection plans, quality objectives | How do you detect process deviations early? |
| Competence | Competence matrix, training records, onboarding plan | Who is allowed to perform critical tasks, and how is that demonstrated? |
| Suppliers and subcontractors | Supplier evaluation, approvals, complaints, performance data | How do you control external services that affect our project? |
| Deviations and actions | 8D reports, root cause analysis, action list, effectiveness review | How do you prevent the same deviation from recurring? |
Typical Mistakes Before Customer Audits
Most problems do not arise because companies have no processes. They arise because requirements are not translated cleanly, evidence is not maintained or responsibilities are not clarified. I see these mistakes particularly often:
- Preparation starts only once the customer's agenda arrives.
- The quality function collects documents alone, although the departments must explain the content.
- Customer requirements are filed as contract text but not transferred into processes.
- Action lists contain open points without clear priority.
- Mock interviews are missing, so correct work is explained unclearly in the audit.
After the Customer Audit: Close Findings Properly
After the audit, speed matters, but so does substance. Assess each finding for risk, cause, affected processes and customer impact. Not every observation requires a large project, but every promised action needs an owner, a deadline and a traceable effectiveness review.
If customer audits recur regularly, findings should feed into the internal audit program, management review and process KPIs. That way, the next audit is not prepared again as a special exercise, but is supported by the management system itself.
How Sternberg Consulting Supports You
We support companies with audit preparation for customer audits, structured document checks, mock interviews and actions after the audit. If there is no fixed QMR role internally, the external QMR model is also suitable as ongoing support for audit readiness, internal audits and management system maintenance. For an initial assessment, you can contact us directly.
Frequently Asked Questions
Is a customer audit the same as a certification audit?
No. A certification audit checks against a standard and is performed by an independent certification body. A customer audit additionally checks customer-specific, contractual or project-related requirements.
How far in advance should a customer audit be prepared?
Ideally several weeks before the date. If many customer requirements, open complaints or several sites are involved, preparation should begin earlier. At short notice, a focused document check with mock interviews can help.
Who should participate in preparation?
Besides quality management or the QMR, the departments the customer will audit should participate: sales, project management, purchasing, production, service, IT, HSE or top management. The decisive factor is that the people in the audit can explain their processes.
What should we do if customer requirements are unclear?
Unclear requirements should be clarified in writing before the audit. If that is not possible, document your interpretation, the affected processes and the open questions. This shows in the audit that the requirement was controlled and not ignored.
How should deviations from a customer audit be handled?
Each deviation needs a clear description, root cause analysis, corrective action, responsibility, deadline and effectiveness review. Simply submitting documents afterwards is usually not enough if the cause lies in a process or interface.
