How to plan internal audits: the annual programme and auditor independence
In brief
An internal audit programme is not auditing every process once a year. Frequency by risk, completing the scope, auditors not auditing their own work, and the path from finding to closure.
8 November 2026 · 5 min read
Sample company · demo dataAudit programme row
ISO 9001 asks the organisation to carry out internal audits of its management system at planned intervals and to set up an audit programme for this; the programme is expected to define frequency, methods, responsibilities and reporting and to take into account the importance of the processes concerned and the results of previous audits. ISO 19011 is the guideline standard for auditing management systems; it gives guidance from managing the audit programme to auditor competence and treats auditor independence as the basis of audit impartiality. This article turns these two frameworks into a programme that works on the floor.
What does the programme cover?
Scope: which standards, which processes, which units and which suppliers. A process outside the scope should show as “not audited” at year end.
Frequency: risky, changing processes and those with findings in the previous audit more often; settled processes less often. Giving every process the same frequency makes the programme easier and meaningless.
Method: which question list, which clauses of the standard, on site or remote.
Responsibility: who leads the audit, who is on the team, who classifies the finding.
Reporting: how a finding is written, where it goes, when it is taken to management review.
How is frequency set by risk?
Three questions are enough: if something goes wrong in this process, how big is the impact; how many findings came up last year; what changed in the process this year? A process that answers “many” or “large” to two of the three is audited more than once a year. A process answering none is audited once a year, but never skipped, because ISO 9001 asks for the whole system to be audited. The programme is written as a table: processes in rows, months in columns; each cell shows a planned, completed or postponed audit.
Auditor independence
An auditor cannot audit their own work. On paper everyone accepts this rule; on the floor it is often broken: a small company has few auditors and the quality officer audits the procedure they wrote themselves. The practical definition of independence is this: the auditor does not work in the audited unit, is not the manager of that unit or its parent unit, and is not the owner of the audited process. In small companies the solution is cross-auditing: production audits quality, quality audits purchasing, purchasing audits production. If someone inevitably has to audit a process close to their own area, that is written in the programme with its reason and the findings are reviewed by someone else.
Auditor competence
Independence is not enough; the auditor must know the standard, the process and the audit technique. ISO 19011 defines auditor competence in terms of knowledge, skills and personal attributes. In practice a training course, one audit as an observer and a first audit led together with an experienced auditor are a sufficient start for a new auditor. Competence is kept on record; the auditor list is reviewed once a year.
From finding to closure
A finding rests on evidence: which document, which record, which observation. A finding without evidence is opened to argument and never closes.
A finding is classified: non-conformity (a requirement is not met), observation (could become a problem), improvement opportunity. The class determines the next step: a non-conformity goes to a CAPA, an observation to an action, an opportunity to a suggestion.
Every finding has an owner and a date; closure is verified with evidence.
The next audit asks about the effectiveness of previous findings; a finding that looks closed but recurs is a CAPA topic.
The programme and its results are an input to management review; the audit report does not stay in a cupboard.
Common mistakes
Bunching the programme at year end: ten internal audits done a month before the certification audit are a rehearsal, not a programme.
Document-only audits: the procedure is read, the floor is not seen. The evidence-based approach of ISO 19011 asks for practice to be seen alongside the record.
Writing the finding against a person: a finding is written against the process; the owner is the process owner, not an individual.
Keeping no record of postponements: if a postponed audit's new date and reason are not written, the programme quietly melts away.
Sample company · demo dataInternal audit programme
How it is done in Gemy
The annual audit programme is set up with a year, a name and a scope note; each row carries what will be audited (process, unit or party, template, system clauses to look at), when (month or date range) and who will audit. The programme is approved; a programme changed after approval asks for approval again.
In an approved programme the row's audit opens by itself the set number of days before the planned period and lands in the auditor's tasks; a row can be postponed or cancelled with a reason. The row × 12 month chart and the coverage box show processes without a row and clauses not looked at.
The independence check is in the programme: an auditor who works in the audited unit, manages that unit or its parent, or owns the process counts as “not independent”. The company chooses block, warn (a reason is written) or ignore.
The audit is done with scores, findings and photos; the finding class is the company's setting, a non-conformity is linked to a CAPA, and findings close as actions with evidence. In a supplier audit the finding is shared on the party portal.
Audit results arrive as an input to management review. An external auditor is given time-limited, read-only guest access. Gemy does not assess auditor competence by itself; competence is kept in training and skills matrix records.
In short
An internal audit programme sets scope, frequency by risk, method, responsibility and reporting; risky and changing processes are audited often, settled ones rarely, but none is skipped. An auditor does not audit their own work; in a small company cross-auditing is the solution. A finding rests on evidence, is classified, closes with an owner and a date, and its effectiveness is asked at the next audit. The audit is not complete until the programme and its results are taken to management review.
You may copy and share this article with attribution (Gemy, https://www.gemydigital.com/en/blog/ic-denetim-nasil-planlanir-yillik-program-denetci-bagimsizligi).
Every solved problem is a piece of knowledge; in most companies it leaves with the person who solved it. The four places where knowledge is lost, the view of ISO 30401 and ISO 9001, and five habits that make knowledge independent of people.
A supplier audit is a process, not a visit: which supplier, which question, which finding, which evidence. The audit principles of ISO 19011, the structure of the question list, finding classes and how the reply returns to the same record.
Document control ensures the right version of the right document is with the right person. What ISO 9001 asks for, document types and numbering, the approval chain, distribution and reading, withdrawing the old version and the five most common gaps.
9 November 2026 · 6 min
Cookies
Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.