Developing an Effective Audit Plan

Production stops for unplanned maintenance, the food safety team leader is called away, the auditor arrives with a generic checklist, and by midday everyone agrees the audit was a waste of a day. None of that is bad luck. Each failure traces back to planning: no agreed objectives, no time allocation by risk, no preparation by either side. A written audit plan is the control that prevents the day collapsing.

Clause 9.2 requires an audit programme, and for each audit a plan is the working document that turns programme intent into a timetable. ISO 19011 treats the audit plan as the arrangement agreed between the audit team leader, the audit client, and the auditee: objectives, scope, criteria, locations, dates, expected time, team roles, and reporting arrangements. Building it well takes an hour. Skipping it costs far more.

Programme first, then the plan for one audit

Keep the two documents distinct. The audit programme is the longer-term arrangement: which processes, clauses, and sites will be audited over the cycle, at what frequency, by whom, using what methods, and how results are reported and followed up. Clause 9.2 requires the programme to consider the importance of processes, changes, and previous audit results, to define criteria and scope for each audit, to select auditors who are objective and impartial, to report results to relevant management and the food safety team, and to retain documented information as evidence.

The plan for a single audit sits under that programme. It names the specific audit, its dates, its team, and its timetable. When a plan conflicts with the programme, for example by auditing the same friendly department twice while a high-risk area waits, the programme should win and the plan should be corrected. Review both together at planning time; drift between them is common and easy to catch early.

Contents of a workable audit plan

A usable plan contains at least the following:

• Audit objectives, stated as questions the audit must answer
• Scope: sites, departments, processes, products, shifts, and evidence period
• Criteria: the ISO 22000 clauses, procedures, specifications, and legal requirements to be used
• Audit team members, their roles, and any areas they must not audit because of their own work
• A timetable allocating time by area, weighted toward high-risk processes
• People to be interviewed and documents to be made available
• Opening and closing meeting times, and who should attend
• Reporting arrangements: format, distribution, and timescales for findings and follow-up

Objectives deserve real thought. To audit the packing department is an activity, not an objective. To determine whether allergen controls on the two shared packing lines conform to the hazard control plan and are effective in practice is an objective, because it tells the auditor what evidence would settle the question and tells the auditee what a conclusion will rest on.

Allocating time and people

Time follows risk, not floor area. Hazard control, monitoring, and handling of nonconforming product usually deserve the largest share. Support processes receive time in proportion to their effect on safety: maintenance and calibration may warrant more attention than document control in a site with ageing equipment. Build in time for tracing evidence across departments, for the closing meeting, and for writing up findings while evidence is fresh. A timetable with no slack fails at the first delayed interview, and rushed final hours produce the weakest findings.

Choose auditors for competence and impartiality. Auditors must not audit their own work. In a small site that rule takes planning: the production supervisor cannot audit production, but may audit warehousing if trained and not responsible for it. Where internal resources cannot cover an area impartially, use a trained person from another site or an external resource. Record how objectivity was achieved rather than hoping nobody asks.

Logistics that protect evidence

Confirm practical arrangements in the plan: access to areas and protective clothing, safety induction requirements, availability of records including electronic systems, and coverage of shifts. If a process runs only at night, plan for night evidence, either by attending or by using records and interviews that genuinely cover that shift, and note any limitation. Checking a line while it is cleaned rather than running answers different questions than the plan set, so align visit times with production schedules when observation of operation is an objective.

Communicating and adjusting the plan

Send the plan to auditees with enough notice for them to arrange people and records without staging a performance. Surprise has a limited place in internal auditing; cooperation and honest access usually produce better evidence. During the audit, the team leader may adjust allocation as findings emerge, following a serious lead rather than completing a timetable for its own sake. Record significant changes and the reasons. At the closing meeting, confirm that objectives were met or state plainly where they were not and what happens next.

Review the finished plan once with fresh eyes before issuing it. Could a relief auditor run this audit from the plan alone? Are objectives testable, times realistic, and responsibilities named rather than implied? Does the timetable protect the closing meeting from being squeezed when fieldwork runs long? A plan that survives those questions will still meet surprises on the day, but it will bend instead of breaking, and the audit will still answer the questions it was set.

Key points

• The audit programme sets cycle-wide coverage; the audit plan turns it into objectives, scope, criteria, and a timetable for one audit.
• Clause 9.2 requires the programme to reflect process importance, changes, and previous results, with objective auditors.
• Objectives should be questions the audit must answer, not departments to visit.
• Allocate time by risk, include tracing and reporting time, and protect impartiality in team selection.
• Plan logistics such as shift coverage and record access, and record any changes or limitations during the audit.