Why Presenting Findings Is Where Audits Succeed or Fail
You can spend two days gathering solid evidence, write a technically perfect nonconformity report, and still walk out of the closing meeting with nothing achieved. The auditee is defensive, the manager is dismissive, and the findings get buried in a shared drive somewhere. The audit was technically correct but practically useless.
On this page
Presenting audit findings is a skill that gets far less attention than it deserves. Most auditor training focuses on gathering evidence, writing nonconformities, and following the audit process. The communication side, the part where you actually tell people what you found and why it matters, is often treated as an afterthought. It should not be.
This article is about how to present audit findings in a way that gets them heard, understood, and acted on. Not by softening the message or avoiding difficult truths, but by delivering them in a way that does not put people on the defensive before you have even finished speaking.
Understand Why Auditees Get Defensive
Before you can manage defensiveness, you need to understand where it comes from. Most auditees are not being difficult for the sake of it. They are reacting to how the findings feel, not just what the findings say.
Consider the situation from their perspective. They have spent months or years building and running a system. You have arrived, spent a day or two looking at a sample of their work, and you are now telling them something is wrong. Even if the finding is completely valid, it can feel like a personal criticism. Especially if the person in the room is also the person responsible for the process you just found a gap in.
Common triggers for defensive reactions include:
- Findings that feel like blame rather than observation
- Language that implies negligence or incompetence
- Surprises in the closing meeting that were not flagged during the audit
- Findings that the auditee believes are factually wrong
- A tone that feels condescending or adversarial
When you understand these triggers, you can start to address them before they become a problem. Most of the techniques in this article are about reducing the chance of a defensive reaction, not just managing one once it has started.
Exemplar Global Certified Training ProviderRTP No. 310970Set the Right Tone From the Opening Meeting
The way you present findings in the closing meeting is shaped by everything that happened before it. If the audit felt collaborative and professional throughout, the closing meeting is much easier. If the audit felt like an interrogation, you will be managing defensiveness before you have said a word about findings.
In the opening meeting, be clear about the purpose of the audit. Explain that the goal is to verify conformance and identify opportunities for improvement, not to catch people out. Mean it. Your body language and behaviour throughout the day will either reinforce or undermine that statement.
A well run opening meeting sets expectations, reduces anxiety, and creates a working relationship rather than an adversarial one. If you have not thought carefully about how you run opening meetings, it is worth reading through guidance on running an effective opening meeting before your next audit.
Flag Findings as You Go, Not Just at the End
One of the most common mistakes auditors make is saving all findings for the closing meeting. The auditee hears a list of issues for the first time, has no chance to respond or clarify, and immediately goes into defensive mode.
A much better approach is to communicate potential findings as they emerge during the audit. This does not mean issuing nonconformities on the spot before you have finished your evidence gathering. It means keeping the auditee informed so that nothing in the closing meeting comes as a shock.
For example, if you find that calibration records are missing for three pieces of equipment, you might say to the process owner at the time:
I have noticed that calibration records for these three instruments are not available. I will note this as a potential finding. If there is documentation I have not seen yet, please let me know before the end of the day.
This approach does two things. It gives the auditee a chance to provide additional evidence if it exists. And it means that when you raise the finding in the closing meeting, it is not a surprise. The auditee has had time to process it, and the conversation is more likely to be constructive.
Structure Your Findings Around Evidence, Not Opinion
The single most important thing you can do to reduce conflict when presenting findings is to anchor everything in evidence. When a finding is grounded in specific, documented facts, it is very hard to argue with. When it sounds like your opinion or interpretation, it invites disagreement.
Compare these two ways of presenting the same finding:
Version one:
Your competence management process does not seem to be working properly. Workers do not appear to understand their responsibilities.
Version two:
During interviews with three production operators, none were able to describe the documented procedure for handling nonconforming product. The procedure, QP-07, was issued in March. There is no record of awareness training being conducted after the issue date. This does not meet the requirement of Clause 7.3, which requires the organisation to ensure persons are aware of relevant documented information.
The second version is harder to dispute because it is specific. It names the clause, describes the evidence, and states the gap clearly. The auditee may not like the finding, but they cannot reasonably argue that you made it up.
Good nonconformity writing underpins good finding presentation. If you want to sharpen this skill, the article on writing nonconformity reports that stand up to scrutiny covers this in detail.
Separate the System from the Person
This is one of the most practical techniques you can use. Whenever possible, frame findings as gaps in the system rather than failures of the individual. This is not about being dishonest or letting people off the hook. It is about directing attention toward the right level of the problem.
Most nonconformities in ISO management systems are systemic. A worker did not follow a procedure because the procedure was not communicated, or was unclear, or was not accessible at the point of use. A record was not completed because the form was poorly designed or the expectation was not made clear. Framing the finding at the system level is usually more accurate and always less inflammatory.
Instead of saying:
The warehouse team is not following the goods inwards procedure.
Say:
The goods inwards procedure was not consistently applied. Of eight receipts sampled, three did not have a completed inspection record. This suggests the requirement may not be clearly understood or the process may need reinforcement.
The second version points to the same gap without assigning blame to individuals. It also opens the door to a corrective action conversation rather than a defensive one.
Running the Closing Meeting Well
The closing meeting is where findings are formally presented. How you structure and run this meeting has a significant effect on how findings are received.
Start With Positives
Before you get into findings, acknowledge what was working well. This is not empty flattery. Every system has areas of genuine good practice, and recognising them is fair and accurate. It also signals that you have been paying attention to the whole picture, not just looking for problems.
Keep this brief and specific. Vague praise like the team was very helpful means nothing. Specific observations like the calibration records for the production line were well maintained and up to date carry weight.
Present Findings in a Logical Order
Group findings by clause or by process area rather than presenting them in the order you discovered them. This makes the report easier to follow and easier for the auditee to understand the scope of what needs to be addressed.
Start with the classification. Make it clear whether each finding is a major nonconformity, minor nonconformity, or observation. Auditees often catastrophise when they hear the word nonconformity. Being clear about grading from the outset prevents unnecessary alarm.
State the Requirement, the Evidence, and the Gap
For each finding, follow a consistent structure. State the clause requirement, describe the evidence you found, and explain the gap between the two. This three part structure is clear, defensible, and professional.
Pause after each finding to allow questions. Do not rush through the list. If an auditee wants to clarify something or provide additional context, listen. You may occasionally find that additional information changes your assessment. More often, listening to the response will help you understand what corrective action is realistic.
Avoid Debating During the Meeting
There is a difference between listening to a response and getting drawn into a debate. If an auditee disputes a finding, acknowledge their perspective and explain your basis for the finding calmly. If they have new evidence that genuinely changes the picture, consider it. If they are simply unhappy with the conclusion, hold your ground without escalating.
A useful phrase is:
I understand your perspective, and I have noted it. Based on the evidence I was able to gather during this audit, the finding stands. If you have additional documentation to share, that would be considered as part of the corrective action response.
This keeps the conversation professional and gives the auditee a path forward without turning the closing meeting into an argument.
Language That Helps and Language That Hurts
The words you choose matter more than most auditors realise. Some language patterns reliably trigger defensiveness. Others reduce it.
Avoid These Patterns
- Absolute language: Words like never, always, completely, and totally are rarely accurate and tend to provoke pushback. Replace them with specific observations.
- Loaded words: Failure, negligence, inadequate, and poor all carry emotional weight. Stick to factual descriptors like not evidenced, not consistent with, or not meeting the requirement of.
- Rhetorical questions: Asking an auditee why something was not done in a tone that implies it obviously should have been is not a question, it is an accusation.
- Comparisons: Telling an auditee that another site or organisation does this differently rarely helps and often causes resentment.
Use These Patterns Instead
- Factual descriptions of what you observed
- Direct references to the clause or requirement
- Neutral language that describes a gap without assigning blame
- Phrases that acknowledge complexity: this is a common challenge in high volume environments
When Auditees Push Back Hard
Even with the best preparation and communication, some auditees will push back. A manager who feels their team is being unfairly criticised, a quality manager who believes the finding is technically wrong, or a director who is simply not used to being told that something in their business does not meet a standard.
The key is to stay calm, stay factual, and stay professional. Do not match the emotional temperature of the room. If someone raises their voice or becomes dismissive, lower yours. Slow down. Refer back to the evidence.
If a dispute is genuine and cannot be resolved in the meeting, most audit processes have a formal mechanism for raising a dispute. Make the auditee aware of this option rather than allowing the disagreement to fester. It is far better to have a formal dispute resolved properly than to have a finding withdrawn under pressure.
For a deeper look at managing difficult situations during audits, the article on handling defensive auditees calmly and professionally covers the full range of scenarios you are likely to encounter.
Exemplar Global Certified Training ProviderRTP No. 310970Written Reports That Support What You Said Verbally
The audit report is the permanent record of your findings. It needs to support and reinforce what you communicated in the closing meeting, not contradict or expand on it in ways that create new confusion.
Write findings in the same structure you used verbally: requirement, evidence, gap. Be specific about what you found and where. Include document numbers, record references, and clause citations. Avoid vague language that makes findings hard to act on.
The report should be readable by someone who was not in the room. If a corrective action owner reads a finding and cannot understand what they need to fix, the report has failed. Clear, specific, well evidenced findings are the foundation of effective corrective action.
Soft skills matter enormously in this profession, and communication is central to all of them. If you want to understand what employers and clients actually look for in experienced auditors, the article on soft skills employers want in ISO auditors is worth reading alongside this one.
Building This Skill Through Practice
Presenting findings well is not something you master by reading about it. It develops through practice, feedback, and reflection. Every audit is an opportunity to refine how you communicate, how you read the room, and how you manage difficult moments.
New auditors often focus entirely on technical correctness and miss the communication dimension entirely. Experienced auditors know that a finding only has value if it is understood and acted on. Getting findings across clearly, calmly, and professionally is as much a part of the auditor's job as gathering the evidence in the first place.
If you are working toward your auditor credentials or want to develop these skills in a structured environment, Audit Workshop offers lead auditor and internal auditor training across ISO 9001, ISO 14001, ISO 45001, ISO 27001, and other standards. The training is built around real audit scenarios and practical communication challenges, not just theory. You can explore the available courses at auditworkshop.com.













