1. Why conduct an internal audit before certification
The internal audit is the check the organisation carries out on itself before the certification body does. It serves to find nonconformities while they can still be corrected calmly, and to show that the system checks itself. The standard requires it explicitly as part of the improvement cycle. The value of the audit lies in its method, not in the final stamp. Whoever carries it out must be able to say what they looked at, how, and with what result.
A useful internal audit is not a formal check carried out just before the certification body's review. It is a verification spread over time, starting from the most critical processes and producing concrete actions. If the first time anyone looks at the system is the external audit, the surprises arrive at a moment when fixing them is costly. It is better to discover a problem well in advance than during the certification body's review.
2. Who can conduct the audit and with what independence
The internal auditor must be a trained person with sufficient knowledge of the standard and of the processes, but who does not directly manage the activity being audited. This separation is the crucial point: anyone checking their own work tends not to see the same problems. In a small organisation it is not always possible to separate all roles, and in that case it is advisable to document how independence was handled.
You can entrust the audit to an internal person from another area or to an external consultant. A consultant brings a fresh perspective, but cannot be the same person who prepared the system, because the review would then lose its value. Whatever the choice, record the name of the person conducting the audit together with the date and the scope verified. Also note the selection method, so that the reason for the choice is clear.
3. Preparing the audit programme
The programme establishes what will be checked during the year, how often and who is responsible. There is no need to verify everything each time. It is best to organise the work by process or by groups of controls, prioritising what carries the highest risk or has recently changed. Follow these steps. Each step produces a document that will remain in the system and be read by the certification body.
The programme must be approved by management and reviewed when the scope changes or significant incidents occur. Reviewing the programme is an opportunity to close checks left behind and to decide whether certain areas should be brought forward, particularly after significant organisational or technological changes. Keep the approved version alongside the report of the latest audit, so that anyone reading it can verify that the work followed the plan.
- List the processes and controls included in the scope, with the owner of each.
- Assign a priority to each process based on risks, recent changes and past incidents.
- Choose an auditor for each area, checking that they are not the head of that area.
- Set a realistic timetable that leaves time for collecting evidence and making corrections.
- Communicate the programme to managers before it starts, explaining purpose and methods.
- Record the programme and approve it formally.
4. Running the audit: questions, samples and evidence
During the check it is not enough to ask whether a procedure exists. The auditor must ask how it is applied, look at the records and verify a sample of real cases. If the procedure requires that the access of departed employees be revoked, the check consists of taking some recent cases and verifying that the revocation took place, within the set timescales and with a written trail.
The best questions start from a fact: show me the last case, how you did it, where it is recorded. Generic answers, such as 'we always do it this way', must always be verified against a document. For each check, note what you asked, what you saw and what you found, because these notes become the proof that the audit was really carried out. If an answer is not documented, record the absence of evidence as a fact, without judging the person.
5. Documenting findings and closing them
Each check produces an outcome. The audit report describes the area, the controls verified, the evidence examined and the findings identified. Each finding must be handled consistently, with a classification and an action to close it. The table shows the most common outcomes and what they involve. Use the same scale for all audits, so results can be compared over time. The report must be signed by the person who carried out the check.
A corrective action is not considered closed when someone says it has been done. You must verify that the problem has been eliminated and does not recur, and record that verification together with the action. Set a follow-up check date already when the action is opened, otherwise the verification never happens. An action closed without verification is one of the reasons the same findings return at the next audit.
| Outcome | What it means | What to do |
|---|---|---|
| Conformity | The control is applied and supported by evidence | Record the check and, if relevant, flag an area for improvement |
| Observation | The control works, but with a risk of future deviation | Agree a preventive improvement with the manager |
| Minor nonconformity | A requirement is not met in an isolated way | Open a corrective action with an owner and a deadline |
| Major nonconformity | A requirement is not met or the system does not work | Open an urgent action and review the process with management |
6. Common mistakes and how to tell whether the audit has helped
The first mistake is limiting the audit to reading documents without verifying practice. The second is treating every finding as personal blame, because then managers hide problems rather than reporting them. The third is closing actions without verifying their effectiveness, and finding the same problem at the next audit. A fourth mistake, common in small organisations, is treating the audit as a one-off event to be done once and forgotten.
An audit has worked when it produces real decisions and improvements. Check whether findings were closed with evidence, whether the management review discussed the results and whether any process has changed as a result. An audit that changes nothing is simply a cost. If findings were closed and no process has changed, the audit was probably too light.
7. How to start
This week, list the processes within the scope and choose one: the one with the highest risks or recent changes. Assign it an auditor who does not manage it and set a date for the check with the owner. Prepare a simple checklist with the questions to ask and the evidence to request. You do not need software to begin: a shared document with the questions and required proofs is sufficient.
After the first check, use the annual programme to cover the other processes. The results will feed into the management review, which is the next step on the path to certification. Once the first cycle is complete, review the programme together and decide what to bring forward in the next cycle, based on the outcomes. The management review must receive a clear summary of these outcomes.
Frequently Asked Questions
Is an internal audit mandatory before certification?
Yes. The standard requires the organisation to conduct internal audits at planned intervals, as part of checking its own system. The certification body will verify that they exist, that they were carried out independently and that findings were managed. A process without documented internal audits is one of the most frequent causes of nonconformities.
Can I carry out the internal audit with the same people who wrote the documents?
They can take part, but they cannot audit their own work. Whoever wrote a procedure tends to check its application starting from intentions rather than facts. If the number of people is small, document how you ensured a minimum of separation, for example by having a process checked by a colleague from another area.
How long should an internal audit take?
Duration depends on the breadth of the area verified, the complexity of the processes and the amount of evidence to examine. There is no standard duration that works for everyone. Plan the time according to the programme, leaving room for gathering evidence and writing the report, which takes longer than the interviews.
What happens if the internal audit finds many nonconformities?
It is a normal result for a first run and should not be hidden. Nonconformities must be recorded, classified and assigned to an owner with a deadline. If there are many, management must assess the priorities and decide what to fix first. Presenting them honestly to the certification body is far better than presenting a system that appears perfect but is not.
Can a corrective action be considered closed when it is completed?
No. Closing an action also means verifying that it removed the root cause of the problem. Ask to see evidence of the change, for example an updated procedure, a completed log or a modified configuration, and record the verification. If the problem reappears, the cause had not been identified.
What is the relationship between the internal audit and the management review?
The internal audit produces the findings, and the management review evaluates them. The audit report is presented to management together with other system data: incidents, objectives, changes in context. Management decides priorities, allocates resources and approves changes. The management review minutes are among the records most closely examined during certification.