If you disagree with an auditor’s finding, you can challenge it, but it needs to be done in a controlled, evidence-based way. Emotional debate in the audit room usually backfires. Treat it like any other quality issue: understand the requirement, review the evidence, and document your position.
1. Separate the discussion from emotion
- Stay fact-focused and respectful. The goal is accurate conformity assessment, not “winning” an argument.
- Capture notes on exactly what the auditor said, the clause or requirement cited, and the examples they used.
- Avoid on-the-spot commitments to corrective actions before you agree there is a real nonconformance.
2. Clarify the requirement and scope
- Ask the auditor to clearly reference the applicable requirement (e.g., specific AS9100/ISO 9001 clause, customer requirement, internal procedure, or regulatory requirement).
- Confirm the scope: is the finding about a single instance, a systemic pattern, or an interpretation of your documented process?
- Check whether they are auditing against the standard, your QMS, or a customer contract. Misalignment here is a common source of disagreement.
3. Present factual, written evidence
- If you believe you conform, calmly present objective evidence: approved procedures, records, training logs, equipment calibration records, change-control history, or system audit trails.
- Show how your process meets the requirement, even if it is implemented differently from what the auditor expected.
- Use your existing systems (QMS, MES, ERP, PLM, DMS) to pull controlled documents and records, not ad-hoc or unofficial files.
4. Distinguish preference from nonconformance
- Respectfully ask: “Can you clarify whether this is a requirement of the standard or your recommended best practice?”
- If the auditor’s concern is about a preferred method (for example, a different way of structuring forms or using particular software) but your method still meets the requirement, state that clearly.
- Document those cases as “opportunities for improvement” (OFIs) or observations rather than full nonconformities when appropriate, following the certification body’s rules.
5. Use your internal escalation path
- Have a named person (often Quality Manager or Management Representative) who is authorized to formally dispute or accept findings during closing meetings.
- If a line owner or engineer disagrees, they should pass the issue to this owner instead of debating individually with the auditor.
- Consolidate your position before the closing meeting so you present a consistent, documented response.
6. Document your rationale in writing
- Whether you ultimately accept or dispute the finding, record your reasoning and the evidence you reviewed.
- Log the disagreement in your QMS (e.g., as part of the audit record, internal NCR, or CAPA log), with links to any procedures, risk assessments, or change controls.
- In brownfield environments, include notes about legacy equipment or systems that limit certain changes but still allow compliance.
7. Decide whether to accept, partially accept, or formally dispute
- Accept fully if you see a clear gap versus the requirement, even if the risk seems low. Then handle it via your corrective action process.
- Partially accept if the example is valid but the auditor’s characterization (e.g., “systemic” vs “isolated”) seems overstated. Document this nuance and negotiate wording where allowed.
- Formally dispute if you have strong, documented evidence of conformity or believe the auditor is misapplying the standard. Use the certification body’s documented appeals/complaints process.
8. Use the closing meeting effectively
- Ask the auditor to read each finding, clause reference, and objective evidence aloud.
- Request immediate clarification where wording could be interpreted as more severe than warranted (for example, “no process exists” vs “documented process not followed in one instance”).
- If you plan to dispute the finding, state that you will do so through the formal process and summarize the basis (without turning the closing meeting into a prolonged debate).
9. Feed disagreements into your continuous improvement
- Even when you successfully dispute a finding, review whether the confusion exposed weaknesses: ambiguous procedures, inconsistent training, or poor record retrieval.
- Use this to harden your audit readiness: clearer documentation, better tagging/indexing of records across MES/ERP/QMS, and more consistent operator training.
- Where brownfield constraints exist, document justifications and risk assessments so future auditors see a deliberate, controlled approach rather than an undocumented workaround.
10. Constraints and tradeoffs to recognize
- Arguing every borderline issue can damage the relationship with your certification body and consume leadership time that might be better spent fixing genuine gaps.
- Accepting an incorrect or overstated finding can drive unnecessary rework, system changes, or validation effort, especially in complex, legacy environments.
- In regulated and aerospace-grade operations, any response (accepting or disputing) must be traceable, documented, and run through change control where processes or systems are altered.
In summary, you can and sometimes should disagree with an auditor’s finding, but the response must be structured: clarify the requirement, gather objective evidence, use your internal escalation route, document your rationale, and, if needed, use the formal dispute process instead of informal arguments in the audit room.