Skip to content
Internal Audits | Part 1 of 6

The Audit Program: Which Process, How Often, and Why

How to score your processes for risk in five criteria and turn the result into an audit program with classes, dates, auditors and two slots kept free.

Most audit programs are a rotation. Every process once a year, in the order of the process map, starting in January. The packing bench gets the same attention as final test, and the plant spends its scarcest resource, the time of people who can audit, on the places where nothing much can go wrong.

A valve plant with 320 employees counted what the rotation produced. Of 24 planned audits, 19 were done. They raised 144 findings, 7.6 per audit, mostly about single records. Of those findings, 49 had already been raised in an earlier audit. The program cost EUR 33,280 in auditor, auditee and management hours, and nobody in the plant could say what it returned.

What a program has to answer

A program is not a calendar. It is a list of audits with a reason for each one, and it answers four questions in writing: which processes belong to the scope, how often each of them is audited and why, who audits it, and over how many years every process is covered at least once.

The reason is risk. Not the risk of the product, which the design team handles, but the risk that this process quietly stops working the way it is described.

Five criteria, twenty points

Score every process in the scope on five criteria, each from 0 to 4. The whole exercise takes an afternoon with the process map on the table.

  • Customer impact: a failure here stops a delivery or ships a defect.
  • Defect history: complaints, scrap or deviations came from this process in the last twelve months.
  • Change activity: new product, new people, a new system or a new layout.
  • Complexity: many steps and variants, several departments, or an outsourced part of the process.
  • Last audit result: the last audit found nonconformities, or the process has never been audited.

Twenty points at most. The plant scored assembly at 17, final test and release at 16, machining at 15, and internal audit and management review at 3.

Class and frequency

The thresholds are a decision, not a formula. Set them so that the program fits the hours you actually have.

Class Score Frequency Processes Audits
A 13 to 20 Twice a year 6 12
B 7 to 12 Once a year 7 7
C 0 to 6 Every second year 5 3
Event Added during the year 2
Total 18 24

Six class A processes carry half the program: assembly, final test and release, machining, purchasing and supplier selection, design and development, and complaint handling. Three of the five class C processes fall into this year and the other two into the next.

From the list to the calendar

Three rules turn the list into dates that survive contact with the plant.

Spread the risk. The two audits of a class A process sit at least four months apart, so the action from the first one has time to work before the second audit looks for it. In this plant assembly is audited in March and September, machining in January and July.

Name the auditor with the audit. An audit without a name is a wish. Nobody audits the process they are responsible for, and the program records how that is kept.

Keep two slots free. A complaint, a relocation or a weak result will need an audit you cannot foresee in January. This plant used one slot in September after a customer complaint and one in December after a line was moved.

What changed

The second year ran 24 audits out of 24 planned. The same hours, spread by risk instead of by habit, produced 118 findings and a program the plant could explain to its management in one page.

Newsletter

One Lean idea.
Every two weeks.