Effective Communication During Audits

An auditor finds that a critical limit was breached three weeks ago and the product shipped. How that news is delivered in the next ten minutes decides whether the site fixes the system or fixes its defences. Shouted accusations produce denial and hidden records. A calm, factual account, delivered to the right people with the evidence in hand, produces a product hold, an investigation, and a change that lasts. Communication is not soft decoration on auditing; it is how findings become action.

Communication runs through the whole audit: agreeing the plan, asking questions that people can answer honestly, giving feedback during fieldwork so there are no ambushes at the end, presenting findings at the closing meeting, and writing a report that still makes sense to a manager who was not in the room. ISO 22000 also requires communication as a system element in clause 7.4, and auditors test that system while depending on their own.

Before and at the opening meeting

Good audit communication starts with notice. Share objectives, scope, criteria, timetable, and who needs to be available, early enough for people to prepare without staging. Explain how findings will be graded and reported, and what happens afterwards. People who understand the process cooperate with it; people ambushed by it protect themselves from it.

Keep the opening meeting short and factual. Introduce the team, confirm scope, timetable, guides, confidentiality, safety and hygiene rules for auditors, and the closing meeting time. Invite the auditee to flag practical issues, such as a line that will not run, at this point. State plainly that findings will be raised as they are confirmed during the day, not stored up. That single commitment removes most closing meeting conflict, because nobody first hears bad news in front of their director.

During fieldwork: questions, listening, feedback

Ask one question at a time, in plain words, and allow silence while people think. Jargon from the standard confuses operators; translate clause language into the language of the task. Instead of asking how clause 8.5 is implemented, ask what the limit is, how it is checked, and what happens when it fails. Take notes visibly and accurately, and read back important statements so the person can correct you on the spot.

Listen for more than content. Hesitation, contradiction between staff, or a joke about a step everyone skips all signal where to look next. Do not argue about conclusions mid-interview. Thank the person, note the evidence, verify it elsewhere, and discuss the conclusion once, with facts complete. Where you confirm a significant issue, inform the auditee contact promptly, especially if product safety may be affected. Delay for the sake of a tidy report is never justified when product could still be leaving the site.

Handling disagreement and difficult moments

Disagreement is normal and often useful: the auditee may hold evidence you have not seen. Ask for it, examine it, and change your conclusion if the evidence warrants. If disagreement remains, restate the requirement and the evidence side by side, and record the auditee’s position fairly in your notes. Never trade findings, soften grading for goodwill, or threaten consequences outside your authority. Auditors report conformity; management decides responses. Staying inside that boundary protects your credibility for the findings that truly matter.

Language and culture deserve care on diverse sites. Some staff may work in a second language or be nervous speaking to an auditor through a supervisor. Where possible, speak directly with the person doing the job, use an interpreter where needed, and never let a guide answer every question on behalf of operators. Evidence filtered through one voice is weaker evidence.

The closing meeting and the written report

Present findings in order of significance, positives first where they are genuine, then each nonconformity as requirement, evidence, and gap. Thank participants, confirm agreed corrections and timescales, explain follow-up and appeal or clarification routes, and end on time. Avoid reading the entire report aloud, introducing new findings not raised during fieldwork, or debating root causes the auditee has not yet investigated. Your job is agreed facts and clear requirements; their job is cause and cure.

Write the report as you would want to receive it: short summary, scope and criteria, evidence sampled, findings with references, and conclusions that answer the audit objectives. Write for an absent reader. Avoid names where roles suffice, avoid humour and sarcasm entirely, and check every number, date, and clause reference before issue, because one wrong reference gives a reluctant reader reason to dismiss ten sound findings. Issue the report within the agreed timescale; late reports signal that the findings were not important, and sites respond accordingly.

After the audit, keep communication open. Answer questions about findings promptly, clarify what evidence would close an action, and attend follow-up discussions in the same factual tone you used on the day. Auditees who can ask what good looks like, without fearing the answer will be used against them, fix problems faster and hide fewer of them next time. Your reputation as a fair, precise communicator is built across many audits, and it directly affects the quality of evidence future audits will be given.

Key points

• Communicate objectives, scope, and process early; no finding should first appear at the closing meeting.
• Use plain, task-level questions, listen actively, and read back important statements for correction.
• Escalate confirmed product safety issues immediately, not at the end of the audit.
• Handle disagreement by comparing requirement and evidence, recording the auditee view fairly, and never trading findings.
• Present closing findings by significance as requirement, evidence, and gap, with agreed actions and timescales.
• Reports must be accurate, readable by absent managers, and issued on time.