Audit note taking is one of those skills that nobody teaches you properly. You sit through a lead auditor course, you learn about evidence, sampling, and nonconformity grading, and then you walk into your first real interview and realise you have a problem. The auditee is talking, you are scribbling, and somewhere in the middle the conversation dies. Either you are so focused on writing that you miss what they just said, or you stop writing entirely and later cannot remember the details you need. Getting this balance right is a genuine craft, and it takes deliberate practice to develop.
On this page
This article covers how experienced auditors capture evidence during interviews and site walks without disrupting the flow of conversation. We will look at what to record, what to leave out, shorthand systems that work in practice, and how to handle the common situations where note taking goes wrong.
Why Audit Notes Matter More Than You Think
Before getting into technique, it is worth being clear about what your notes are actually for. Audit notes are not a transcript. They are not a journal. They are a structured record of evidence that supports your findings, whether those findings are conformances, nonconformities, or observations.
If you raise a nonconformity and the auditee disputes it, your notes are what you refer back to. If a lead auditor reviews your work, they will look at your notes to see whether your conclusions are grounded in evidence. If the certification body audits your audit programme, your working papers need to demonstrate that the audit was conducted properly.
Poor notes create real problems. Vague entries like no procedure found or records not complete are almost useless. They tell you something was wrong, but not what you looked at, who you spoke to, what they said, or what specific records were missing. When you come to write your nonconformity report, you are working from memory rather than evidence, and that is where findings fall apart under challenge.
Good notes, on the other hand, let you write findings with confidence. They give you the specific detail that makes a nonconformity defensible and a conformance genuine rather than assumed.
Exemplar Global Recognised Training ProviderRTP No. 310970
The Core Tension: Writing vs Listening
Every auditor feels this tension. You are in an interview, the auditee is explaining their process, and you want to capture what they are saying. But the moment you look down and start writing, you break eye contact, you stop tracking their body language, and you may miss the next thing they say entirely.
The mistake most new auditors make is trying to write everything. They treat the interview like a dictation exercise, trying to get every word down. This creates two problems. First, the auditee notices that you are transcribing them and starts choosing words more carefully, which kills the natural flow of conversation. Second, you end up with pages of notes that are hard to use when you need to pull out the key evidence points.
Experienced auditors write less, but they write the right things. They listen actively, let the auditee finish a thought, then capture the essential evidence point in a few words. The conversation stays alive because the auditor is genuinely present in it.
What to Actually Write Down
Your notes need to answer a specific set of questions for each area you audit. These questions come directly from your audit criteria.
Document and Record References
Whenever you review a document or record, note the title, the version or date, and any relevant identifier. For example: Maintenance procedure MP-04, Rev 3, dated March 2024, reviewed on screen in maintenance office. This gives you the traceability you need. If a finding relates to that document, you can reference it precisely. If the document showed conformance, you have evidence of what you actually reviewed.
What the Auditee Said
You do not need to write verbatim quotes. You need to capture the substance of what was said in a way that records the evidence. If a supervisor tells you that calibration records are kept in the ERP system and the last calibration for the press was done in January, write that. Not the exact words, but the facts: calibration records in ERP, press last calibrated January 2025, confirmed by production supervisor.
When an auditee says something that directly supports or contradicts a requirement, that is worth a closer paraphrase. If they say something like
we do not actually check the supplier certificates before we use the material, that only happens at the end of the jobthat is significant evidence. Write it close to verbatim and note who said it and when.
What You Observed
Site observations are often the most powerful evidence you have. Write down what you physically saw, not your interpretation of it. Instead of writing poor housekeeping, write: observed three unlabelled containers on floor near mixing station, no MSDS visible, area not demarcated. The interpretation can come later in your finding. The note captures the raw observation.
What Was Not Available
If you asked for a record and it could not be produced, note that. Record what you asked for, who you asked, and the response you received. This is evidence of absence, which is just as important as evidence of conformance.
Shorthand Systems That Work in Practice
You do not need a formal shorthand system, but you do need some consistent abbreviations that you can write quickly and read back reliably. Develop your own, but here are some that work well in audit practice.
- NC for potential nonconformity, flagged for follow up
- C for confirmed conformance against a specific clause
- OFI for an observation or opportunity for improvement
- Doc followed by a reference for any document reviewed
- Rec followed by a reference for any record reviewed
- Obs for a physical observation made on site
- Said: followed by a brief quote or paraphrase of something significant an auditee stated
- ? next to anything you want to follow up or verify
- NP for not provided or not produced when requested
The key is consistency. Use the same abbreviations every time so that when you review your notes two hours later, you can read them quickly without having to decode them.
Structuring Your Notes Before the Interview
One of the most practical things you can do is set up your note pages before the interview starts. This takes five minutes and saves you significant time during the audit.
For each interview or process area, create a simple structure. Write the process name, the auditee name and role, the date and time, and the clauses you plan to cover. Then leave space under each clause reference for your notes. This means that when you are in the interview and something relevant to clause 8.4 comes up, you have a designated place to record it rather than trying to write in the margins or on a separate page.
If you are using a paper checklist, use the checklist itself as your note structure. Write your evidence directly against each question. This saves duplication and means your notes are already organised by clause when you come to write your report.
If you are using a tablet or laptop, the same principle applies. Have your template open before you walk into the room. Do not be fumbling with your device while the auditee is waiting.
Managing the Conversation While You Write
There are some simple techniques that let you write without killing the conversation.
Signal That You Are Still Engaged
When you look down to write, give the auditee a brief verbal signal: just noting that down or simply right or good. This tells them you heard what they said and you are capturing it, not ignoring them. It keeps the conversation from stalling.
Write After the Point, Not During It
Train yourself to listen to a complete thought before you write. Let the auditee finish their sentence or explanation, then write the key point. You will miss less and your notes will be more coherent because you are capturing the complete idea rather than fragments.
Use Pauses Productively
Natural pauses in conversation are your writing time. When the auditee is thinking, when they are pulling up a record on their computer, when they step away to get a document, use that time to write. Do not fill every pause with another question. Let the silence work for you. There is a related article on this at using silence as an audit technique that goes into this in more detail.
Summarise Back to Confirm
At key points in an interview, summarise what you have understood and read it back to the auditee. This does two things. It confirms your understanding is accurate, which protects you from writing down something wrong. And it gives you a moment to complete your notes while the auditee confirms or corrects your summary. Something like: so just to confirm, calibration records are maintained in the ERP, the frequency is set in the equipment register, and the last check for this machine was January, is that right?
Digital vs Paper Notes
This is a genuine debate among practising auditors, and there is no single right answer. Both approaches work, and both have real limitations.
Paper Notes
Paper is fast, flexible, and does not require you to look at a screen. You can sketch a process flow, draw an arrow to connect two points, circle something for follow up, and write in the margins. Many experienced auditors prefer paper for interviews because it feels less formal and does not create a physical barrier between auditor and auditee the way a laptop screen can.
The downside is that paper notes need to be transferred into your report, which takes time. They can also be hard to organise if you are auditing multiple processes across multiple days.
Digital Notes
A tablet or laptop lets you type directly into your working papers, which can save significant time at the report writing stage. Templates can be pre populated with clause references and standard requirements. Some auditors use audit management software that links notes directly to findings.
The downside is the screen barrier. If you are typing while someone is talking, it can feel like you are not listening, even if you are. Some auditees find it off putting. And if you are on a site walk, a tablet can be cumbersome.
Many auditors use a hybrid approach: paper for interviews and site walks, then transfer key points to digital working papers during a break or at the end of the day. This works well if you are disciplined about the transfer. Notes left on paper and not transferred are notes that may not make it into your report.
Note Taking During Site Walks
Site walks present different challenges to interviews. You are moving, there may be noise, and you are observing rather than listening. A few techniques help here.
Keep a small notebook or a printed site walk checklist on a clipboard. Write brief observations as you go: location, what you saw, the time. If you take photos (with permission), note the photo number and what it shows. Do not rely on photos alone. A photo of an unlabelled container is evidence, but your note explaining what the photo shows and where it was taken is what makes it usable.
If you find something significant, stop and write it down properly before moving on. Do not trust your memory to hold five site observations while you continue the walk. The detail fades quickly, especially on a long audit day.
Reference any physical observations back to specific requirements when you write them up. The observation itself is neutral. The significance comes from the clause it relates to.
After the Interview: The Debrief Note
One of the most useful habits you can develop is writing a brief debrief note immediately after each interview or process area. This takes five minutes and is worth every second.
While the conversation is still fresh, write a summary of the key points: what conformances you noted, what potential findings you identified, what you still need to verify, and any questions that arose that you did not have time to pursue. This is not your formal finding, it is your working summary.
This debrief note becomes the bridge between your raw interview notes and your final report. It forces you to process what you heard while it is still clear, rather than trying to reconstruct it at the end of a long audit day when everything blurs together.
For more on how evidence gathering connects to the overall audit process, the article on how to gather audit evidence that stands up to scrutiny covers the broader picture in practical detail.
Common Note Taking Mistakes and How to Fix Them
Writing Conclusions Instead of Evidence
The most common mistake is writing your interpretation rather than the raw evidence. Supplier evaluation not effective is a conclusion. Reviewed supplier evaluation records for three suppliers: ABC, XYZ, DEF. No performance rating completed for ABC or DEF. Last evaluation for XYZ was 2021, requirement is annual per procedure SC-02 is evidence. Train yourself to write what you saw, not what you think it means.
Not Recording Who Said What
Always note the name and role of the person you interviewed. If a finding is later disputed, the auditee saying I never said that is a problem you can only address if your notes record who was present. A simple header on each interview note page is enough: name, role, date, time.
Losing Track of Clause References
If your notes are not organised by clause or process requirement, you will spend significant time at the report writing stage trying to work out which evidence relates to which requirement. Use your checklist or template structure to keep notes anchored to specific requirements as you go.
Letting Notes Slide on Busy Days
On a long audit day, especially a multi site or multi process audit, note taking discipline tends to slip as fatigue sets in. The last interview of the day often has the thinnest notes. Build in brief writing breaks during the day, and use the travel time between sites or the lunch break to catch up on notes from the morning. Related to this, the article on managing audit fatigue on long audit days has practical advice for staying sharp across a full audit day.
Exemplar Global Recognised Training ProviderRTP No. 310970Keeping Your Working Papers Organised
Your notes are part of your working papers. They need to be organised well enough that another auditor could pick them up and understand what you found and how you found it. This matters both for professional practice and for any audit log you are maintaining for certification purposes.
At a minimum, your working papers for each audit should include: the audit plan, your checklists with notes, any document references you reviewed, your debrief summaries, and your draft findings. Keep these together, either in a physical folder or a digital file, and label them clearly with the audit date, organisation, and scope.
If you are building an audit log for Exemplar Global or IRCA certification, your working papers are what you will reference when recording audit hours and scope. Organised, detailed notes make this process straightforward. Vague or missing notes make it difficult.
The article on keeping audit records and working papers in order covers the full requirements for working paper management in more detail.
Building the Skill Over Time
Note taking improves with practice, but only if you reflect on what you are doing. After each audit, spend a few minutes reviewing your notes. Ask yourself: could someone else read these notes and understand what I found and why? Are my evidence points specific enough to support a nonconformity if challenged? Did I capture enough detail from the site walk?
If the answer to any of these is no, identify what went wrong. Were you writing too late? Too vague? Not recording document references? Each audit is a chance to tighten your technique.
If you are in the early stages of building your auditing skills, a structured training environment is one of the fastest ways to develop good habits. At Audit Workshop, the internal auditor and lead auditor courses include practical exercises that put you in real audit scenarios, where you can practise interviewing, evidence gathering, and note taking under the guidance of an experienced lead auditor. Getting the fundamentals right early saves you from years of bad habits that are harder to break later.
