Common Audit Interview Mistakes and How to Avoid Them

Audit interviews are where competence meets reality. A well conducted interview can reveal systemic issues that documentation alone would never show. A poorly conducted one wastes everyone's time, damages credibility, and produces findings that don't stick. Most auditors never receive formal training in interview technique. They're taught the standards, the paperwork, the compliance framework. But when they walk into a conference room across from a production manager or a finance controller, they're often operating on instinct and good intentions. This is where interviews fail.

The mistakes auditors make during interviews aren't academic. They create friction with auditees, undermine audit conclusions, and eventually damage the auditor's professional reputation. Over fifteen years of training auditors and reviewing audit reports, certain patterns emerge repeatedly. These aren't obscure problems requiring advanced technique. They're fundamental errors that better preparation and awareness can eliminate entirely.

Understanding What an Audit Interview Actually Is

Before discussing mistakes, clarify what you're actually doing when you conduct an audit interview. It isn't a conversation. It isn't an investigation in the criminal sense. It isn't a training session disguised as an audit. An audit interview is a structured exchange of information where you, as the auditor, gather evidence against defined audit criteria. The auditee is the source of that evidence.

ISO 19011, the standard governing audit practice, describes the auditor's role as someone who gathers objective evidence, evaluates it against criteria, and determines conformity. The interview is the tool through which much of that gathering happens. But interviews introduce variables that documentation doesn't. People interpret questions differently. They become defensive. They forget details. They tell you what they think you want to hear.

Understanding this distinction matters because it changes how you approach the conversation. You're not trying to be friendly or reach consensus. You're gathering evidence. That clarity of purpose prevents many of the mistakes that follow.

Mistake 1: Asking Questions Without Knowing the Answer

This is the most common error auditors make, and it's often defended as an act of neutrality. The logic sounds reasonable: if you don't know the answer in advance, you won't bias the response. In practice, the opposite happens.

Walking into an interview without reviewing relevant documentation first means you'll ask vague questions. Vague questions produce vague answers. When the auditee says something unclear, you won't know whether to dig deeper or move on because you lack the context to recognise what matters. You'll ask follow up questions that confuse the conversation. You'll miss contradictions between what the person says and what the records show.

Consider a real example. An auditor asks a maintenance supervisor, "How do you manage preventive maintenance?" The supervisor responds, "We do it monthly." The auditor nods and moves on. If the auditor had reviewed the maintenance schedule beforehand, they would know that for some equipment, preventive maintenance is supposed to be quarterly, not monthly. The answer already contained evidence of non conformity, but the auditor couldn't recognise it because they lacked the baseline knowledge.

Before every audit interview, review the relevant documented procedures, previous audit reports, records relevant to the auditee's area, and the specific clause or requirement you're testing. This isn't about creating leading questions. It's about having sufficient knowledge to ask intelligent questions and recognise meaningful answers.

There's also a practical side benefit. When auditees see that you've done your homework, they treat the audit more seriously. They're less likely to give off hand responses or dismiss your findings as uninformed criticism.

Mistake 2: Leading and Loaded Questions

The opposite problem is asking questions that telegraph the answer you want. Leading questions bias the response and contaminate your evidence. They also show immediately to experienced auditees that your mind is already made up, which damages your credibility.

Leading questions typically take one of several forms. Sometimes the auditor includes the desired answer in the question itself: "You do conduct management reviews monthly, don't you?" The auditee hears the expected answer and confirms it, regardless of whether it's true. Sometimes the auditor loads the question with assumptions: "When you train new operators on this safety procedure, how do you document it?" This assumes training happens and documentation exists. If neither is true, the auditee might either agree to avoid confrontation or derail the conversation correcting your assumption.

Loaded questions also appear when auditors ask multiple questions at once: "Do you perform risk assessments, and if so, are they updated annually?" The auditee can answer "yes" and you won't know which part they're confirming. They might confirm both, or they might be answering only the first question.

The solution is to ask simple, single questions with neutral phrasing. Instead of "You do conduct management reviews monthly, don't you?" ask "What is the frequency of management reviews?" Instead of "When you train new operators on this safety procedure, how do you document it?" ask "Describe the process for documenting operator training on safety procedures." These questions don't tell the auditee what answer you expect. They invite description rather than confirmation.

This approach also works better across different auditees. A subsidiary in another state might run management reviews quarterly. A department might have a different interpretation of what constitutes documentation. Your open questions reveal these variations rather than collapsing them into a false yes or no.

Mistake 3: Accepting Vague or Second Hand Answers

When an auditee gives a vague answer, many auditors accept it and move on. They do this to keep the conversation flowing, to avoid seeming difficult, or because they're not quite sure what they're hearing. This surrenders the entire purpose of the interview.

An example: You ask the operations manager, "How do you ensure that equipment is maintained according to schedule?" The response is, "Our maintenance team handles that. They're very professional. We don't have any issues." This is vague and potentially second hand. The operations manager might believe what they're saying, but they haven't described the actual process. You don't know whether written schedules exist, whether they're followed, who verifies compliance, or what happens when maintenance is missed.

The correct response is to probe further. "Who specifically is responsible for the maintenance schedule?" "Show me the schedule for the last six months." "How is compliance with the schedule verified?" "What happens when maintenance is missed?" These follow up questions convert vague assurance into specific evidence.

Second hand answers are similar. If you ask about a process and the auditee says, "The quality team does that," you haven't actually interviewed anyone about the process. You've interviewed someone about their assumption regarding what another department does. These answers often contain gaps or inaccuracies that become apparent only when you speak to the people actually performing the work.

Best practice is to interview the people who actually perform the process you're auditing, not their supervisors. If that's not possible, you verify what you're told through documentation and observation.

Mistake 4: Failing to Distinguish Between What Should Happen and What Actually Happens

This mistake appears constantly in auditor interviews. The auditor asks about the documented procedure, gets a description that matches the procedure, and concludes that the requirement is met. The reality is often different. The documented procedure might describe what should happen, but the actual practice might be something else entirely.

A documented quality procedure might state that all customer complaints are logged in a database, reviewed within two days, and responded to within five days. When you interview the customer service team, they confirm this is what the procedure requires. You then note that the documented procedure exists and the requirement is met. But you haven't verified that this actually happens. You haven't reviewed the complaint database to see whether they're logged promptly. You haven't checked whether the two day review actually occurs. You haven't tracked response times.

The only way to distinguish between what should happen and what actually happens is to examine evidence beyond the person's word. This might include reviewing records, observing the process, or speaking to people who interact with the process from outside perspectives. A customer might say that response times are poor even though staff believe they're meeting the five day target. Records might show that complaint logging happens weeks after the complaint is received.

When conducting interview, always include questions that test actual practice against documented procedures. "Show me the last three complaints that came in." "Walk me through what happened from the moment this complaint arrived until the customer received a response." "How many complaints in the last month were responded to within the target timeframe?" These questions ground the audit in reality rather than aspiration.

Mistake 5: Poor Question Sequencing and Logic Flow

Auditor interviews often jump from topic to topic without logical flow. This confuses auditees, makes the interview longer than necessary, and produces disjointed evidence that's hard to analyse later.

A poorly sequenced interview might start with a question about management review, jump to supplier evaluation, then ask about training, then return to management review with a follow up question. The auditee has to constantly shift context. They might provide answers that were true in the context of the first question but have changed by the time you revisit the topic. You might miss connections between different processes that would be obvious if you'd covered them sequentially.

Good interview structure follows the process flow. If you're auditing a sales order process, you start at the beginning: how does an order arrive? Then move through the sequence: how is the order recorded? How is it verified? How is it assigned to production? When does production occur? When is it shipped? When is it invoiced? This sequence mirrors how the process actually works. The auditee can describe it as a narrative rather than as disconnected fragments. You can ask logical follow up questions and spot inconsistencies.

Structure also means grouping related topics together. If you're asking about training, ask all your training questions in one section before moving to another topic. If you're asking about supplier management, cover supplier selection, evaluation, monitoring, and remediation in sequence. This makes the interview easier to follow and the evidence easier to analyse.

Mistake 6: Dominating the Conversation

Some auditors talk more than the auditees. They explain the standard, describe what they expect to find, offer opinions, and generally fill silences. Auditors often do this because they're nervous or because they think explaining the requirement will help the auditee give a better answer. In reality, it prevents the auditor from hearing what the auditee actually knows.

When you dominate the conversation, you're not gathering evidence. You're performing. You might feel like you're making progress because words are being exchanged, but you're probably learning very little about how the organisation actually operates.

The mental model to adopt is that the auditee should be talking approximately seventy percent of the time and you about thirty percent. Your role is asking questions and listening. The auditee's role is answering. If you find yourself explaining things frequently or filling silences with commentary, you're off balance.

Silence is actually useful in interviews. After you ask a question, pause. Wait for an answer. Don't fill the silence with additional comments. Auditees often need a moment to formulate a response. Some people think while they talk. Others think in silence before speaking. If you interrupt with follow up questions or clarifications, you're preventing them from completing their thought.

This also means resisting the urge to help the auditee find the right answer. If they're struggling to express something, you might think you're being helpful by suggesting possible answers. In reality, you're leading them toward your expected answer. Instead, ask clarifying questions: "Can you give me an example?" "What do you mean by that?" "Walk me through that process step by step."

Mistake 7: Not Securing Concrete Examples

Auditors often accept general statements when they should be asking for specific examples. "We train all operators" is a claim. "We trained these three operators in the last month using this documented training program" is evidence.

The difference matters tremendously when you later need to defend your audit conclusions. If your audit report states that training is occurring and someone later asks how you verified this, you need to point to specific evidence. If your answer is that the auditee told you training happens, that's weak evidence. If your answer is that you reviewed training records for five operators completed in the last month, each with documentation of the training content and the person's competency assessment, that's strong evidence.

Make it a practice to ask for examples in almost every interview. "Can you show me a recent example of how that works?" "Show me the documentation from the last time that happened." "Who performed that action most recently?" "Give me three examples from the last month." These requests turn abstract descriptions into concrete evidence.

Examples also serve as a check on whether the auditee actually knows their job. Someone who can't provide an example of something they claim happens regularly is either not actually familiar with the process or is making assumptions about what happens.

Mistake 8: Becoming Defensive or Argumentative When Challenged

Some audit interviews turn into arguments. The auditee pushes back on a question or interpretation, and the auditor defends their position rather than gathering more information. This happens especially when the auditor has already formed a conclusion and the auditee is contradicting it.

An example: You ask about the frequency of internal audits. The auditee says, "We do them quarterly." You've reviewed previous audit reports and know the last audit was seven months ago. You respond, "Actually, that's not what your records show. The last audit was seven months ago." Now you're in a debate about facts rather than gathering evidence. The auditee becomes defensive. The conversation deteriorates.

The better response is to gather more information. "Describe the schedule for the next four quarters of internal audits." Then compare what they say to the records. If there's a discrepancy, continue gathering evidence to understand why. Perhaps the schedule changed. Perhaps the previous audit was delayed. Perhaps the quarterly schedule isn't being met. You're investigating, not arguing.

This distinction matters for how to become an ISO internal auditor and the professional standards expected of you. Your role is to gather evidence objectively, not to win arguments. If auditees perceive you as argumentative, they stop cooperating fully. They become guarded in their answers. They might refuse to show you certain areas or records. The audit becomes adversarial rather than collaborative.

The approach to adopt is curiosity rather than judgment. When you encounter something that doesn't match your expectation, express genuine interest in understanding why. "I see a gap between the documented procedure and what you're telling me happened. Help me understand that." This opens investigation rather than closing it down through confrontation.

Mistake 9: Failing to Test Understanding of Requirements

Some auditors accept that people perform tasks without verifying that they understand why those tasks matter. This is particularly important when auditing compliance with ISO standards. Many organisations perform actions because they're required, not because they understand the underlying logic.

An example: You ask about risk assessment. The auditee describes a process. You verify that the process occurs. You conclude the requirement is met. But you haven't verified that the risk assessment actually achieves its purpose. You haven't asked whether the identified risks drive any actual management decisions. You haven't asked what happens to the risk assessment after it's completed.

In some organisations, risk assessments are generated to satisfy ISO compliance requirements, filed away, and never consulted again. The process meets the literal requirement but fails its actual purpose. Effective auditing reveals this gap.

Questions that test understanding include: "What do you do with the results of this risk assessment?" "How does this feed into management decisions?" "Give me an example of a risk identified in this process that led to a management action." "How is this tied to your objectives?" These questions test whether the requirement is genuinely embedded in the organisation or merely performed as a compliance exercise.

Mistake 10: Poor Documentation of Interview Notes

Many auditors take minimal notes during interviews and try to complete them afterward from memory. This creates several problems. Details are forgotten or misremembered. You can't accurately quote what someone said. You lose the connection between what was said and where the evidence is located. Your later analysis of audit findings relies on incomplete or inaccurate information.

Taking good interview notes means recording specific details as you hear them. Note exact quotes when they're important. Record the names and titles of people you interviewed. Note the specific documents you reviewed or examples you examined. Note dates and reference numbers for things you're following up on. Record questions that remained unanswered so you remember to pursue them.

You don't need to transcribe every word. That's distracting and prevents you from listening effectively. But you need enough detail that someone reading your notes weeks or months later would understand what evidence you gathered and what it showed.

Good note taking also helps with accuracy. If you're unsure whether you've recorded what the auditee said correctly, you can clarify during the interview. "Let me make sure I have this right. You're saying that the last management review was conducted in March, is that correct?" This protects you from later disputes about what was said.

Mistake 11: Not Following Up on Inconsistencies

During interviews, you'll encounter inconsistencies. One person says something different from another person. Records show something different from what someone claims. Verbal descriptions conflict with written procedures. The auditor's natural impulse is often to ignore these inconsistencies or note them casually. This is a mistake.

Inconsistencies are where audit findings live. They indicate problems in compliance, communication, understanding, or record keeping. Ignoring them means missing the point of the audit.

When you encounter an inconsistency, flag it immediately. Ask follow up questions to understand the gap. Is the discrepancy due to a recent change that wasn't communicated? Is one person mistaken about the actual practice? Has the procedure changed but records haven't been updated? Is there a genuine gap in compliance?

For example, if you interview two supervisors and one says that non conformities are documented and corrected within 48 hours while the other says they're corrected within a week, that's a red flag. You need to follow up. Review actual records of non conformities. Determine what the actual practice is. Determine whether a procedure exists that clarifies the requirement. Find out why the two supervisors have different understandings.

This kind of investigation is essential for conducting an audit that actually drives improvement. Without it, you're left with anecdotal information rather than evidence of systematic issues.

Mistake 12: Inadequate Questioning About Non Conformities

When you identify a non conformity during an interview, how you respond matters. Some auditors accept a quick explanation and move on. This prevents you from understanding the root cause, the scope, and the systemic nature of the problem.

Suppose you ask to see employee training records and notice that one employee's annual refresher training is six months overdue. You ask why. The supervisor says, "Oh, he's been busy. We'll get him trained." You note a non conformity and move on. But you haven't determined whether this is an isolated incident or a pattern. You haven't investigated why the training schedule isn't being monitored. You haven't examined whether other employees are also overdue. You haven't identified what's causing the issue: lack of training schedule visibility, competing priorities, or something else.

Proper questioning in this scenario includes: "How many employees do you have?" "How many have completed their annual training?" "Which employees are overdue?" "When are they due?" "How is training progress monitored?" "How do you ensure overdue training is caught?" "What's preventing this person's training from being completed?" These questions convert a single anecdotal observation into evidence of a systemic issue or an isolated exception.

Understanding the root cause also allows you to write nonconformity reports that actually lead to corrective action rather than superficial fixes. Someone might argue that one employee being overdue on training is an isolated incident that's already being addressed. But if you can show that monitoring systems are deficient, allowing multiple overdue items to accumulate undetected, that evidence supports a more substantial finding that will drive meaningful change.

Mistake 13: Interviewing at the Wrong Organisational Level

Some auditors spend significant time interviewing senior managers and administrative staff while neglecting the people who actually perform the work. This limits what you learn and often produces findings that don't match operational reality. The quality procedure might be explained perfectly by the quality manager, but the people on the production line might not be following it.

Effective audits require interviewing across levels. You interview management to understand policy and strategy. You interview supervisors to understand how work is organised and monitored. You interview operators and technicians to understand how work is actually performed. You interview administrative staff to understand record keeping and documentation. Each level provides different evidence.

When progressing from internal auditor to lead auditor, this becomes even more critical. Lead auditors often oversee audits of larger organisations and need to ensure their teams interview at appropriate levels to get a complete picture.

A practical approach is to plan your interviews to cover different levels and functions. For a process like complaint handling, interview the customer service manager, the supervisors who handle complaints, and the people who actually process them. Interview a customer if possible. Interview accounting to understand how complaints feed into cost analysis. This layered approach reveals inconsistencies between what's intended and what's actually happening.

Mistake 14: Failing to Manage Your Own Bias

Every auditor brings assumptions, past experiences, and beliefs to an audit. These biases can interfere with objective evidence gathering. You might expect a particular problem and unconsciously focus on confirming it while ignoring contrary evidence. You might dislike a particular manager and be more critical of their department. You might assume that because a previous audit found an issue, the same issue exists in the current audit.

Bias is subtle and difficult to eliminate, but awareness helps. Recognise that you can't be perfectly objective. But you can work toward objectivity by being conscious of your own perspectives. Before interviews, identify what assumptions you're bringing. During interviews, actively look for evidence that contradicts your expectations. In your analysis, give weight to evidence that challenges your initial conclusions.

One practical technique is to deliberately ask yourself: "What evidence would prove me wrong?" If you find a non conformity, ask whether there's evidence that contradicts this finding. If you find a strength, ask whether there's evidence that suggests the strength is weaker than it appears. This self interrogation reduces the impact of bias on your conclusions.

Practical Tools for Better Audit Interviews

Several practical tools improve interview quality. An audit checklist used properly provides structure without becoming checklist dependent. The checklist should prompt you to cover certain areas but not dictate the exact questions you ask or prevent you from following leads that emerge during the interview.

An interview plan prepared before the audit helps. This plan should identify the person you're interviewing, their role, the topics you're covering, and the key evidence you're looking for. This doesn't need to be detailed. A brief outline suffices. It keeps you focused without constraining you.

A technique called the "five whys" helps you dig deeper when you encounter issues. When you identify a problem, ask why it occurred. When you get an answer, ask why again. Repeat this cycle five times. By the fifth why, you've usually identified the root cause rather than just a symptom. This technique surfaces systemic issues rather than isolated incidents.

Finally, a post interview debrief with yourself helps. Before moving to the next interview, spend five minutes reviewing your notes. Are there gaps you need to follow up on? Did anything contradict previous evidence? Are there questions you want to ask in the next interview based on what you learned in this one? This practice helps you learn from each interview and apply those lessons to the next one.

Audit Workshop offers accredited ISO auditor training at Foundation, Internal Auditor, and Lead Auditor levels for ISO 9001, ISO 14001, and ISO 45001. Our courses are Exemplar Global recognised and include practical exercises, case studies, and assessment support.